From: Shawn McCarney <shawnmm@linux.ibm.com>
To: Mike Jones <proclivis@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: No dbus objects for phosphor-regulators
Date: Fri, 11 Feb 2022 09:32:13 -0600 [thread overview]
Message-ID: <1858988f-100f-b3b4-c599-80cddaa7247a@linux.ibm.com> (raw)
In-Reply-To: <6D1561E1-59FC-4126-9271-A7C8BFDB0B11@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On 2/9/2022 4:30 PM, Mike Jones wrote:
> The journal shows an I2C error: Device or resource busy. Does hwmon
> lock out phosphor-regulators if it uses the same address? Sent from my
> iPad On Feb 1, 2022, at 10:38 AM, Shawn McCarney
> <shawnmm@linux.ibm.com> wrote:
>
> The journal shows an I2C error: Device or resource busy.
>
> Does hwmon lock out phosphor-regulators if it uses the same address?
>
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.
I have not tested using phosphor-regulators when a driver is bound to
the regulator, but I suspect you may be right. I assume hwmon is using
read sensor data from a driver, and the driver being bound is stopping
the phosphor-regulators read from succeeding.
Thanks,
Shawn
[-- Attachment #2: Type: text/html, Size: 1530 bytes --]
next prev parent reply other threads:[~2022-02-11 15:33 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 [this message]
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
-- 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=1858988f-100f-b3b4-c599-80cddaa7247a@linux.ibm.com \
--to=shawnmm@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=proclivis@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).