linaro-pm-wg team mailing list archive

[Daniel Lezcano <857382@xxxxxxxxxxxxxxxxxx>]

There is no information about the unit used for a specific file. The
userspace needs to take a decision depending on what kind of hardware it
is running despite the sysfs interface should be a generic interface.

We have several solution:
 * display a raw value with mC / mV units and powerdebug does not take care of that. The fix is trivial.
 * display a raw value but let the user to switch from one unit to another unit. The fix is not trivial and we can have for the same directory some files displayed in mC and others in mV.

My advice would be to send a patch to add a sysfs temp#_unit file and let the different maintainer to fill it with the right value.
So in the future, powerdebug would be able to display correctly the result.

** Changed in: linaro-powerdebug
   Importance: Undecided => Medium

** Changed in: linaro-powerdebug
     Assignee: (unassigned) => Daniel Lezcano (daniel-lezcano)

** Changed in: linaro-powerdebug
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Linaro
Powerdebug Commits, which is subscribed to Linaro PMWG Powerdebug.
Matching subscriptions: powerdebug commits
https://bugs.launchpad.net/bugs/857382

Title:
  [powerdebug] sensors are displayed with the wrong unit

Status in Powerdebug - a tool to help ARM developers:
  Confirmed

Bug description:
  The different sensors temperatues informations give sometimes the value in millivolt instead of millidegree.
  Powerdebug is assuming the result is always in millidegree.

  Example of a sensor semantic:
   * GPADC - ADC_AUX1, connected to NTC R2148 next to RTC_XTAL on HREF
   * GPADC - ADC_AUX2, connected to NTC R2150 near DB8500 on HREF
   * Hence, temp#_min/max/max_hyst refer to millivolts and not
   * millidegrees
   * This is not the case for BAT_CTRL where millidegrees is used

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-powerdebug/+bug/857382/+subscriptions