dbus-sensors:hwmontemp: additional attribute proposal

[Jason Ling]

> What about making the device/type lists in PSUSensors extendable using
JSON?

> Say more about what you're wanting to do here.....

 Take
https://github.com/openbmc/dbus-sensors/blob/master/src/PSUSensorMain.cpp#L43
 and
https://github.com/openbmc/dbus-sensors/blob/master/src/PSUSensorMain.cpp#L59
and
make it so those can be extended using (for example) without an upstream
code change. I picked JSON as the easiest example.
IIRC PSUSensors does validity checks to make sure that the device emits a
name in its 'permit list' (hwmontempsensor is less picky) so tricking
PSUSensors into gathering telemetry for a non-public device is tricky.

Can you give an
> example of what you would use it for?

Sure, the primary use case would be
It's a non public device. Would rather not broadcast information about it
or have to obfuscate the device name. Really would rather not maintain
patches until the device is made public.



On Fri, Aug 7, 2020 at 9:39 AM Ed Tanous <ed at tanous.net> wrote:

> On Fri, Aug 7, 2020 at 9:36 AM Jason Ling <jasonling at google.com> wrote:
> >
> > Slightly different topic:
> > What about making the device/type lists in PSUSensors extendable using
> JSON?
> >
>
> Say more about what you're wanting to do here.....  Can you give an
> example of what you would use it for?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200807/5bd34077/attachment.htm>