From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Hardware Monitoring <linux-hwmon@vger.kernel.org>
Subject: Re: [RFC/RFT PATCH v2] hwmon: (lm75) Hide register size differences in regmap access functions
Date: Wed, 18 Dec 2024 17:07:25 +0100 [thread overview]
Message-ID: <Z2LzPeqyxqJz06dZ@ninjato> (raw)
In-Reply-To: <20241218150404.2713377-1-linux@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Hi Guenter,
quick response, will test your new patch later.
> ---
> v2: Fix accesses to 16-bit configuration register.
Great, thanks, I missed that more fixing is needed.
> Use regmap access functions for all operations on config register.
> Declare regmap bus and use devm_regmap_init().
The regmap_bus solution is really nice! Didn't know about it.
> Drop local configuration register copy; let regmap handle bit updates.
And one patch is gone from my queue. I had this as well :)
> Note: The driver could use additional cleanup, such as using bit macros
> and using devm_regulator_get_enable(). That is left for another day.
I didn't do BIT yet (although tempted), but I have the regulator cleanup
already. Also, 'client' can go from the priv struct with just a little
bit of reordering. I hope I can send all the stuff tomorrow.
I have the proof-of-concept running on I3C already, need to remove some
FIXMEs, though.
Thanks and happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-18 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 15:04 [RFC/RFT PATCH v2] hwmon: (lm75) Hide register size differences in regmap access functions Guenter Roeck
2024-12-18 16:07 ` Wolfram Sang [this message]
2024-12-18 16:21 ` Guenter Roeck
2024-12-18 16:25 ` Wolfram Sang
2024-12-18 16:36 ` Guenter Roeck
2024-12-18 16:41 ` Guenter Roeck
2024-12-18 17:39 ` Wolfram Sang
2024-12-18 17:53 ` Guenter Roeck
2024-12-20 6:21 ` Wolfram Sang
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=Z2LzPeqyxqJz06dZ@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-hwmon@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