Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-renesas-soc@vger.kernel.org,
	Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org
Subject: Re: [RFC PATCH 5/5] hwmon: (lm75) add I3C support for P3T1755
Date: Fri, 20 Dec 2024 09:20:51 +0100	[thread overview]
Message-ID: <Z2Uo4yodY0VfU6ZB@ninjato> (raw)
In-Reply-To: <8c8b2249-75ca-4835-a693-a5df841190b7@roeck-us.net>

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

Hi Guenter,

> For the few i3c chips which do happen do be lm75 compatible, we should have
> something like
> 
> struct lm75_i3c_devices {
> 	enum lm75_type type;
> 	const char *name;
> };

Sigh, OK, let's have that info a third time.

> And I think "lm75compatible" is really a terrible hwmon device name ;-).

The series is RFC for a reason :D

> i3c doesn't seem to have any access functions (kernel helpers) similar to i2c,
> other than i3c_device_do_priv_xfers(), so unless those are made available
> I think we'll have to bite the bullet and use local access functions.

Well, yes, there are not many I3C target drivers, so there is no
critical mass for I3C helpers yet. With helpers I meant more convesion
helpers like cpu_to_be16 and the likes. I see them rarely used in hwmon,
so I wondered about this.

> The other patches look good to me. If you send me a Reviewed-by: and/or
> Tested-by: to my patch, I'll queue it all up (except for this patch)
> for 6.14.

Done. Thank you!

All the best,

   Wolfram

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-12-20  8:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 22:55 [RFC PATCH 0/5] hwmon: (lm75) add I3C support Wolfram Sang
2024-12-19 22:55 ` [RFC PATCH 1/5] hwmon: (lm75) simplify lm75_write_config() Wolfram Sang
2024-12-20  8:48   ` Geert Uytterhoeven
2024-12-20 14:56   ` Guenter Roeck
2024-12-19 22:55 ` [RFC PATCH 2/5] hwmon: (lm75) simplify regulator handling Wolfram Sang
2024-12-20  8:50   ` Geert Uytterhoeven
2024-12-20 14:57   ` Guenter Roeck
2024-12-19 22:55 ` [RFC PATCH 3/5] hwmon: (lm75) Remove superfluous 'client' member from private struct Wolfram Sang
2024-12-20 14:57   ` Guenter Roeck
2024-12-19 22:55 ` [RFC PATCH 4/5] hwmon: (lm75) separate probe into common and I2C parts Wolfram Sang
2024-12-20 14:58   ` Guenter Roeck
2024-12-19 22:55 ` [RFC PATCH 5/5] hwmon: (lm75) add I3C support for P3T1755 Wolfram Sang
2024-12-20  6:10   ` Guenter Roeck
2024-12-20  8:20     ` Wolfram Sang [this message]

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=Z2Uo4yodY0VfU6ZB@ninjato \
    --to=wsa+renesas@sang-engineering.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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