From: "Rob Herring (Arm)" <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v2] docs: dt: writing-bindings: Extend compatible fallbacks guideline
Date: Tue, 5 May 2026 10:40:09 -0500 [thread overview]
Message-ID: <177799560843.2973367.1894381541645031550.robh@kernel.org> (raw)
In-Reply-To: <20260427160739.175451-2-krzysztof.kozlowski@oss.qualcomm.com>
On Mon, 27 Apr 2026 18:07:40 +0200, Krzysztof Kozlowski wrote:
> Extend the guidelines when to use fallback compatibles to cover to
> common review responses. Devices are most likely compatible and should
> use fallbacks when having:
>
> 1. Compatible programming interface, meaning one is a subset, and Linux
> device drivers can use the subset to correctly match/bind and still
> operate with the subset features.
>
> 2. Device variant discovery through some means, like registers.
>
> Devices are incompatible and fallback is not suitable when that
> fallback cannot be used by the drivers to match/bind. In the same time
> commit message should clearly explain when the code suggests devices
> are compatible, but the binding does not define them as such.
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
> ---
>
> Changes in v2:
> 1. Include Conor's suggestion about commit msg, a bit rephrased.
> 2. Add tag
> 3. Drop double-space, because file does not use that format (old habit).
> ---
> .../devicetree/bindings/writing-bindings.rst | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
Applied, thanks!
prev parent reply other threads:[~2026-05-05 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 16:07 [PATCH v2] docs: dt: writing-bindings: Extend compatible fallbacks guideline Krzysztof Kozlowski
2026-04-27 19:02 ` Conor Dooley
2026-05-05 15:40 ` Rob Herring (Arm) [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=177799560843.2973367.1894381541645031550.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.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