From: Patrick Williams <patrick@stwcx.xyz>
To: Shawn McCarney <shawnmm@linux.ibm.com>
Cc: openbmc@lists.ozlabs.org, Mike Jones <proclivis@gmail.com>
Subject: Re: No dbus objects for phosphor-regulators
Date: Fri, 11 Feb 2022 14:53:20 -0600 [thread overview]
Message-ID: <YgbMwFhqMO5ikp5E@heinlein> (raw)
In-Reply-To: <1858988f-100f-b3b4-c599-80cddaa7247a@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On Fri, Feb 11, 2022 at 09:32:13AM -0600, Shawn McCarney wrote:
> On 2/9/2022 4:30 PM, Mike Jones wrote:
> > iPad On Feb 1, 2022, at 10:38 AM, Shawn McCarney
> > <shawnmm@linux.ibm.com> wrote:
> phosphor-regulators currently communicates directly with voltage
> regulators using i2c-dev; it does not use device drivers.
>
> The reason is that most regulator drivers provide either no or very
> limited ability to configure regulators. For the systems I work on, we
> need to do extensive regulator configuration to fine tune things (output
> voltage, pgood min/max, timing, etc.) Redundant phase fault detection is
> also pretty device-specific and on involves communicating with multiple
> devices.
Out of curiosity, had you done any investigation with getting the support you
need upstreamed in drivers? If you had upstream discussions I'd like some
pointers to them (lore links) since, as Ed pointed out, we're having design
discussions on this same problem generally speaking.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-11 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 22:25 No dbus objects for phosphor-regulators Mike
2022-02-01 17:37 ` Shawn McCarney
2022-02-09 22:30 ` Mike Jones
2022-02-11 15:32 ` Shawn McCarney
2022-02-11 15:42 ` Mike Jones
2022-02-11 16:06 ` Shawn McCarney
2022-02-11 20:20 ` Ed Tanous
2022-02-11 22:56 ` Mike Jones
2022-02-11 20:53 ` Patrick Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-25 22:15 Mike Jones
2022-01-26 22:43 ` Shawn McCarney
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=YgbMwFhqMO5ikp5E@heinlein \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
--cc=proclivis@gmail.com \
--cc=shawnmm@linux.ibm.com \
/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.