From: Andreas Kemnade <andreas@kemnade.info>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
lee@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mfd: Add ROHM BD71879
Date: Fri, 5 Apr 2024 08:31:37 +0200 [thread overview]
Message-ID: <20240405083137.2291ea9d@aktux> (raw)
In-Reply-To: <0295c8db-b01e-45e7-b44e-79d36d81cd48@gmail.com>
On Fri, 5 Apr 2024 09:01:25 +0300
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> > Yes. If there are reasons against, please briefly mention them in commit
> > msg.
>
> I would like to understand the rationale for allowing:
> compatible = "rohm,bd71879", "rohm,bd71828".
>
> Is the intention to:
> 1) allow boards which tell the software that "the hardware may be
> bd71828 or bd71879", or
> 2) to tell a binding reader that these ICs are likely to be usable as
> replacements to each others?
> (Or, is there some other rationale beyond these?)
As far as I understand the second compatible can be a fallback for
software which does not know the bd71879 (remember the devicetree is
not only for linux). Especially if that software does not use the full
functionality of the device, like drivers in bootloaders do. E.g.
mmc drivers in bootloaders might not use high speed modes at all, so
differences in them do not matter.
Regards,
Andreas
next prev parent reply other threads:[~2024-04-05 6:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 19:35 [PATCH 0/2] mfd: Add ROHM BD71879 Andreas Kemnade
2024-04-02 19:35 ` [PATCH 1/2] dt-bindings: " Andreas Kemnade
2024-04-03 8:23 ` Matti Vaittinen
2024-04-04 6:59 ` Krzysztof Kozlowski
2024-04-04 10:30 ` Andreas Kemnade
2024-04-04 12:04 ` Krzysztof Kozlowski
2024-04-05 6:01 ` Matti Vaittinen
2024-04-05 6:31 ` Andreas Kemnade [this message]
2024-04-05 6:35 ` Krzysztof Kozlowski
2024-04-05 6:58 ` Matti Vaittinen
2024-04-02 19:35 ` [PATCH 2/2] mfd: rohm-bd71828: Add software-compatible variant BD71879 Andreas Kemnade
2024-04-03 8:21 ` Matti Vaittinen
2024-04-05 6:35 ` Lee Jones
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=20240405083137.2291ea9d@aktux \
--to=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--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).