All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Ling <jasonling@google.com>
To: James Feist <james.feist@linux.intel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: dbus-sensors:hwmontemp: additional attribute proposal
Date: Fri, 7 Aug 2020 09:34:34 -0700	[thread overview]
Message-ID: <CAHBbfcUDMOZjxSvy8wVW_F9f3+NaX-WU3G5PF1oUoRx5VP7ZoQ@mail.gmail.com> (raw)
In-Reply-To: <2bb88ede-4d35-8b9c-936f-be8dc9a453e5@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]

ack,
sounds like I'm better off just moving temp sensors over to being handled
by PSUSensors.

Slightly different topic:
What about making the device/type lists in PSUSensors extendable using JSON?



On Fri, Aug 7, 2020 at 9:24 AM James Feist <james.feist@linux.intel.com>
wrote:

> On 8/6/2020 3:52 PM, Jason Ling wrote:
> > Assuming that you mean "Omit Name attribute from the sensor
> > configuration definition and then change hwmontemp to require any Name.*"
> > This won't work since Entity-Manager requires Name (tried it,
> > entity-manager does indeed complain about not finding name).
> >
> > My rationale for an omit list vs permit list
> > (1) if it's a permit list then everytime you add another temp you want
> > to monitor you need to add to this list..if you want to drop a temp then
> > you have to modify the list again.
> > (2) General assumption is that the primary use case is to display all
> > named temperatures which means a permit list is typically large
> > (3) adding a permit list also breaks all existing code. Everyone has to
> > go back into their json config and add all the sensor values to the list.
> >
> > My rationale for using the value for the "Name" attribute rather than
> > labels or referencing sysfs attributes
> > (1) Looking at just the config , it's obvious as to what you're omitting.
> > (2) If it's label base, a label change in a driver would mean a breakage
> > in the userspace daemon. Not a big deal; but it can be annoying.
> > (3) if it's sysfs attribute based then it's my opinion that it's not as
> > readable.
> >
>
> I'm not a huge fan of this as the PSU sensor already has a way of
> handling this, and it adds a new way of handling it. I'd rather follow
> what is already there. It's already confusing enough that hwmontemp and
> psu do things in slightly different ways.
>
> >
>

[-- Attachment #2: Type: text/html, Size: 2447 bytes --]

  reply	other threads:[~2020-08-07 16:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 23:42 dbus-sensors:hwmontemp: additional attribute proposal Jason Ling
2020-08-06  6:07 ` Zbyszek
2020-08-06 20:40 ` James Feist
2020-08-06 22:52   ` Jason Ling
2020-08-07 16:24     ` James Feist
2020-08-07 16:34       ` Jason Ling [this message]
2020-08-07 16:39         ` Ed Tanous
2020-08-07 16:54           ` Jason Ling
2020-08-07 17:06             ` James Feist
2020-08-07 17:17               ` Jason Ling
2020-08-07 17:40                 ` James Feist
2020-08-07 18:04                   ` Jason Ling
2020-08-07 18:17                     ` James Feist
2020-08-07 18:29                       ` Jason Ling
2020-08-07 19:27                         ` Ed Tanous
2020-08-07 19:17                     ` Ed Tanous
2020-08-07 21:05                       ` Jason Ling
2020-08-07 21:53                         ` Ed Tanous
2020-08-11  0:08                           ` Alex Qiu
2020-08-11 23:02                             ` Ed Tanous
2020-08-12  0:46                               ` Alex Qiu
2020-08-12  1:42                                 ` Ed Tanous
2020-08-12 16:19                                   ` Alex Qiu
2020-08-07 17:24             ` Ed Tanous
2020-08-07 17:01         ` James Feist
2020-08-07 16:37       ` Ed Tanous

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHBbfcUDMOZjxSvy8wVW_F9f3+NaX-WU3G5PF1oUoRx5VP7ZoQ@mail.gmail.com \
    --to=jasonling@google.com \
    --cc=james.feist@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.