linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Andreas Kemnade <andreas@kemnade.info>,
	Matti Vaittinen <matti.vaittinen@linux.dev>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sebastian Reichel <sre@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-rtc@vger.kernel.org
Subject: Re: [PATCH v4 14/16] power: supply: bd71828: Support wider register addresses
Date: Fri, 14 Nov 2025 15:22:00 +0200	[thread overview]
Message-ID: <2334e57c-a384-4a1e-9708-19d14b8f082c@gmail.com> (raw)
In-Reply-To: <20251114121509.629d171b@kemnade.info>

Thanks Andreas,

On 14/11/2025 13:15, Andreas Kemnade wrote:
> On Thu, 13 Nov 2025 10:55:39 +0200
> Matti Vaittinen <matti.vaittinen@linux.dev> wrote:
> 
>> As a side note, we can reduce the "wasted space / member / instance" from
>> 3 bytes to 1 byte, by using u16 instead of the unsigned int if needed. I
>> rather use unsigned int to be initially prepared for devices with 32 bit
>> registers if there is no need to count bytes.
> 
> Well, this is totally internal to the module, so no ABI/API changes, so
> there is no advantage of using 32bit now I think. We can switch any time.

The only advantage is to avoid the churn if 32bit ICs are to be added.

> But we have 32bit stuff in the regmap cache anyways, so that is not above
> the general level of wasting space.

Exactly. And, I am not sure if sparing ~hundred bytes is worth the 
hassle - even if it is hassle internal to the driver. But yeah, we can 
squeeze a few bytes if it is seen beneficial. That's why I mentioned it 
here :)

Yours,
	-- Matti

---
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~

  reply	other threads:[~2025-11-14 13:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13  8:51 [PATCH v4 00/16] Support ROHM BD72720 PMIC Matti Vaittinen
2025-11-13  8:51 ` [PATCH v4 01/16] dt-bindings: regulator: ROHM BD72720 Matti Vaittinen
2025-11-13 10:53   ` Rob Herring (Arm)
2025-11-14 16:22   ` Rob Herring (Arm)
2025-11-13  8:51 ` [PATCH v4 02/16] dt-bindings: battery: Clarify trickle-charge Matti Vaittinen
2025-11-13  8:52 ` [PATCH v4 03/16] dt-bindings: battery: Add trickle-charge upper limit Matti Vaittinen
2025-11-13  8:52 ` [PATCH v4 04/16] dt-bindings: power: supply: BD72720 managed battery Matti Vaittinen
2025-11-13 10:53   ` Rob Herring (Arm)
2025-11-14  9:04     ` Matti Vaittinen
2025-11-14 16:39       ` Rob Herring
2025-11-14 17:40         ` Andreas Kemnade
2025-11-17  8:12         ` Matti Vaittinen
2025-11-17 15:23           ` Rob Herring
2025-11-17 15:48             ` Matti Vaittinen
2025-11-13  8:52 ` [PATCH v4 05/16] dt-bindings: mfd: ROHM BD72720 Matti Vaittinen
2025-11-15 11:31   ` Krzysztof Kozlowski
2025-11-18 23:06   ` Linus Walleij
2025-11-13  8:52 ` [PATCH v4 06/16] dt-bindings: leds: bd72720: Add BD72720 Matti Vaittinen
2025-11-13  8:53 ` [PATCH v4 07/16] mfd: rohm-bd71828: Use regmap_reg_range() Matti Vaittinen
2025-11-13  8:53 ` [PATCH v4 08/16] mfd: bd71828: Support ROHM BD72720 Matti Vaittinen
2025-11-13  8:54 ` [PATCH v4 09/16] regulator: bd71828: rename IC specific entities Matti Vaittinen
2025-11-13  8:54 ` [PATCH v4 10/16] regulator: bd71828: Support ROHM BD72720 Matti Vaittinen
2025-11-13  8:54 ` [PATCH v4 11/16] gpio: Support ROHM BD72720 gpios Matti Vaittinen
2025-11-13  8:55 ` [PATCH v4 12/16] clk: clk-bd718x7: Support BD72720 clk gate Matti Vaittinen
2025-11-14  3:53   ` Stephen Boyd
2025-11-13  8:55 ` [PATCH v4 13/16] rtc: bd70528: Support BD72720 rtc Matti Vaittinen
2025-11-13  8:55 ` [PATCH v4 14/16] power: supply: bd71828: Support wider register addresses Matti Vaittinen
2025-11-14 11:15   ` Andreas Kemnade
2025-11-14 13:22     ` Matti Vaittinen [this message]
2025-11-13  8:55 ` [PATCH v4 15/16] power: supply: bd71828-power: Support ROHM BD72720 Matti Vaittinen
2025-11-13  8:56 ` [PATCH v4 16/16] MAINTAINERS: Add ROHM BD72720 PMIC Matti Vaittinen

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=2334e57c-a384-4a1e-9708-19d14b8f082c@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andreas@kemnade.info \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=matti.vaittinen@linux.dev \
    --cc=mturquette@baylibre.com \
    --cc=pavel@kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sre@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 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).