From: Guenter Roeck <linux@roeck-us.net> To: Brandon Wyman <bjwyman@gmail.com>, Joel Stanley <joel@jms.id.au>, openbmc@lists.ozlabs.org, Jean Delvare <jdelvare@suse.com>, linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org, Eddie James <eajames@linux.ibm.com> Subject: Re: [PATCH] hwmon: (pmbus/ibm-cffps) Fix write bits for LED control Date: Wed, 28 Jul 2021 16:14:52 -0700 [thread overview] Message-ID: <2517b3a8-6549-3ee6-76d3-6545a38cf6ea@roeck-us.net> (raw) In-Reply-To: <20210728224140.3672294-1-bjwyman@gmail.com> On 7/28/21 3:41 PM, Brandon Wyman wrote: > From: "B. J. Wyman" <bjwyman@gmail.com> > > When doing a PMBus write for the LED control on the IBM Common Form > Factor Power Supplies (ibm-cffps), the DAh command requires that bit 7 > be low and bit 6 be high in order to indicate that you are truly > attempting to do a write. > > Signed-off-by: B. J. Wyman <bjwyman@gmail.com> Please be consistent and use "Brandon Wyman". Guenter > --- > drivers/hwmon/pmbus/ibm-cffps.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/drivers/hwmon/pmbus/ibm-cffps.c b/drivers/hwmon/pmbus/ibm-cffps.c > index 5668d8305b78..df712ce4b164 100644 > --- a/drivers/hwmon/pmbus/ibm-cffps.c > +++ b/drivers/hwmon/pmbus/ibm-cffps.c > @@ -50,9 +50,9 @@ > #define CFFPS_MFR_VAUX_FAULT BIT(6) > #define CFFPS_MFR_CURRENT_SHARE_WARNING BIT(7) > > -#define CFFPS_LED_BLINK BIT(0) > -#define CFFPS_LED_ON BIT(1) > -#define CFFPS_LED_OFF BIT(2) > +#define CFFPS_LED_BLINK (BIT(0) | BIT(6)) > +#define CFFPS_LED_ON (BIT(1) | BIT(6)) > +#define CFFPS_LED_OFF (BIT(2) | BIT(6)) > #define CFFPS_BLINK_RATE_MS 250 > > enum { >
next prev parent reply other threads:[~2021-07-28 23:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-28 22:41 Brandon Wyman 2021-07-28 23:14 ` Guenter Roeck [this message] 2021-08-06 22:35 ` Brandon Wyman
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=2517b3a8-6549-3ee6-76d3-6545a38cf6ea@roeck-us.net \ --to=linux@roeck-us.net \ --cc=bjwyman@gmail.com \ --cc=eajames@linux.ibm.com \ --cc=jdelvare@suse.com \ --cc=joel@jms.id.au \ --cc=linux-hwmon@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=openbmc@lists.ozlabs.org \ --subject='Re: [PATCH] hwmon: (pmbus/ibm-cffps) Fix write bits for LED control' \ /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
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).