From: Maarten Zanders <maarten.zanders@mind.be>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: leds-lp55xx: add ti,charge-pump-mode
Date: Thu, 2 Feb 2023 15:12:07 +0100 [thread overview]
Message-ID: <fa47912f-ec10-f22b-0447-0b7c998711b3@mind.be> (raw)
In-Reply-To: <5fbb6d80-7280-604a-3e1e-4bd98e9776cd@linaro.org>
On 2/2/23 14:43, Krzysztof Kozlowski wrote:
>
> Strings in DTS are usually easier to for humans to read, but it's not a
> requirement to use them. The problem of storing register values is that
> binding is tied/coupled with hardware programming model, so you cannot
> add a new device if the register value is a bit different (e.g.
> LP55XX_CP_OFF is 0x1). You need entire new binding for such case. With
> string - no need.
I understand and this is why I started with the string in the first
place (as suggested by yourself in V1).
> With binding constants (IDs) also no need, so was this
> the intention? Just to be clear - it is then ID or binding constant, not
> a value for hardware register.
>
For simplicity sake, yes, now the setting is propagating directly into
the register as a bit value. But this is how the current implementation
of the drivers work. If we add a device in the future which indeed has
different bit mappings, that driver will have to do a mapping of the DT
binding to its own bit field definitions. I consider this DT binding as
the "master", which is now conveniently chosen to match the register values.
Cheers,
Maarten
next prev parent reply other threads:[~2023-02-02 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 10:10 [PATCH v4 0/2] leds: lp55xx: configure internal charge pump Maarten Zanders
2023-02-02 10:10 ` [PATCH v4 1/2] dt-bindings: leds-lp55xx: add ti,charge-pump-mode Maarten Zanders
2023-02-02 13:13 ` Krzysztof Kozlowski
2023-02-02 13:15 ` Krzysztof Kozlowski
2023-02-02 13:35 ` Maarten Zanders
2023-02-02 13:43 ` Krzysztof Kozlowski
2023-02-02 14:12 ` Maarten Zanders [this message]
2023-02-02 20:11 ` Krzysztof Kozlowski
2023-02-02 20:13 ` Krzysztof Kozlowski
2023-02-03 15:38 ` Maarten Zanders
2023-02-03 17:54 ` Krzysztof Kozlowski
2023-02-02 10:10 ` [PATCH v4 2/2] leds: lp55xx: configure internal charge pump Maarten Zanders
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=fa47912f-ec10-f22b-0447-0b7c998711b3@mind.be \
--to=maarten.zanders@mind.be \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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).