All of lore.kernel.org
 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,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-doc@vger.kernel.org, linux-hwmon@vger.kernel.org,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 0/2] hwmon: (lm75) Add NXP P3T1755 support
Date: Wed, 18 Dec 2024 08:27:02 +0100	[thread overview]
Message-ID: <Z2J5RoFiuyUlZ162@shikoro> (raw)
In-Reply-To: <b30a1b76-cad4-4d53-837f-64a72993d267@roeck-us.net>

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

Guenter,

> I just sent a RFC/RFT patch converting all chip access code to regmap
> to the hwmon list. This should help with adding I3C support. It would
> be great if you can have a look.

Thanks, this is really awesome! It surely will help me adding I3C
support. I already sketched multiple paths to handle the regmap problem
of config reg being 8 bits while all other are 16 bits. A custom read
callback was also one option I considered. I will check your patch later
today and base my work on top of it.

All the best,

   Wolfram


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

      reply	other threads:[~2024-12-18  7:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 12:03 [PATCH 0/2] hwmon: (lm75) Add NXP P3T1755 support Wolfram Sang
2024-12-17 12:03 ` [PATCH 1/2] dt-bindings: hwmon: lm75: Add NXP P3T1755 sensor Wolfram Sang
2024-12-17 18:18   ` Conor Dooley
2024-12-18  7:19     ` Wolfram Sang
2024-12-17 12:03 ` [PATCH 2/2] hwmon: (lm75) Add NXP P3T1755 support Wolfram Sang
2024-12-17 21:26   ` Guenter Roeck
2024-12-18  7:22     ` Wolfram Sang
2024-12-18  9:15       ` Wolfram Sang
2024-12-17 22:59 ` [PATCH 0/2] " Guenter Roeck
2024-12-18  7:27   ` 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=Z2J5RoFiuyUlZ162@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh@kernel.org \
    /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.