From: Guenter Roeck <linux@roeck-us.net>
To: Jeff Lin <jefflin994697@gmail.com>, jdelvare@suse.com
Cc: cedricjustine.encarnacion@analog.com, ninad@linux.ibm.com,
andriy.shevchenko@linux.intel.com,
johnerasmusmari.geronimo@analog.com, Mariel.Tinaco@analog.com,
jbrunet@baylibre.com, kimseer.paller@analog.com,
leo.yang.sy0@gmail.com, nuno.sa@analog.com,
chiang.brian@inventec.com, gregkh@linuxfoundation.org,
grantpeltier93@gmail.com, peterz@infradead.org,
william@wkennington.com, krzysztof.kozlowski@linaro.org,
tzungbi@kernel.org, thorsten.blum@linux.dev,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/hwmon/pmbus: Add support for raa229141 in isl68137
Date: Fri, 26 Sep 2025 06:24:39 -0700 [thread overview]
Message-ID: <c29014bd-d441-4e4b-802a-7c6f5caf2cf5@roeck-us.net> (raw)
In-Reply-To: <20250926014552.1625950-1-jefflin994697@gmail.com>
On 9/25/25 18:45, Jeff Lin wrote:
> In chip RAA229141 there exist ISYS pin which can report the current data
> for the device connected to this chip through this pin by routed by Direct
> Memory Access(DMA) command. To read the data in ISYS pin, we have to set
> the DMA address to 0xC5 and then read the DMA data from 0xC7. And then use
> the Direct read format with 10mA per LSB to transfer the data in 0xC7.
> And for ISYS input pin, the DMA address is 0xE0D3 and for ISYS output pin,
> the DMA address is 0xEE42.
>
> Signed-off-by: Jeff Lin <jefflin994697@gmail.com>
> ---
...
> diff --git a/drivers/hwmon/pmbus/isl68137.c b/drivers/hwmon/pmbus/isl68137.c
> index c52c55d2e7f4..04a582ba9416 100644
> --- a/drivers/hwmon/pmbus/isl68137.c
> +++ b/drivers/hwmon/pmbus/isl68137.c
> @@ -63,6 +63,9 @@ enum chips {
> raa228228,
> raa229001,
> raa229004,
> ++#if IS_ENABLED(CONFIG_SENSORS_RAA229141)
> ++ raa229141,
> ++#endif /* CONFIG_SENSORS_RAA229141 */
I just realized (as did 0-day): This code doesn't even build.
Obviously that means that I can't trust that the code coming from you actually
works, even if it does build. Please keep that in mind if/when submitting
subsequent versions. I will want to see very detailed and verifiable
information about this chip and its supposed functionality.
Guenter
next prev parent reply other threads:[~2025-09-26 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 1:45 [PATCH] drivers/hwmon/pmbus: Add support for raa229141 in isl68137 Jeff Lin
2025-09-26 8:27 ` Guenter Roeck
2025-11-06 9:33 ` Jeff Lin
2025-09-26 13:05 ` kernel test robot
2025-09-26 13:24 ` Guenter Roeck [this message]
2025-09-26 14:20 ` kernel test robot
2025-11-06 9:31 ` [PATCH v2] " Jeff Lin
2025-11-06 9:42 ` Andy Shevchenko
2025-11-10 1:09 ` Jeff Lin
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=c29014bd-d441-4e4b-802a-7c6f5caf2cf5@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Mariel.Tinaco@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=cedricjustine.encarnacion@analog.com \
--cc=chiang.brian@inventec.com \
--cc=grantpeltier93@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=jdelvare@suse.com \
--cc=jefflin994697@gmail.com \
--cc=johnerasmusmari.geronimo@analog.com \
--cc=kimseer.paller@analog.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=leo.yang.sy0@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ninad@linux.ibm.com \
--cc=nuno.sa@analog.com \
--cc=peterz@infradead.org \
--cc=thorsten.blum@linux.dev \
--cc=tzungbi@kernel.org \
--cc=william@wkennington.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