From: Rob Herring <robh@kernel.org>
To: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Yannick Fertre <yannick.fertre@foss.st.com>,
Philippe Cornu <philippe.cornu@foss.st.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Christophe Roullier <christophe.roullier@foss.st.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 03/13] dt-bindings: display: st: add new compatible to LVDS device
Date: Thu, 14 Aug 2025 09:01:19 -0500 [thread overview]
Message-ID: <20250814140119.GA2748790-robh@kernel.org> (raw)
In-Reply-To: <2c13bf48-5453-4302-9cde-eac51e314af1@foss.st.com>
On Thu, Aug 14, 2025 at 02:36:47PM +0200, Raphael Gallais-Pou wrote:
>
>
> On 8/14/25 11:09, Krzysztof Kozlowski wrote:
> > On Tue, Aug 12, 2025 at 03:49:00PM +0200, Raphael Gallais-Pou wrote:
> >> Update the compatible to accept both "st,stm32mp255-lvds" and
> >> st,stm32mp25-lvds" respectively. Default will fall back to
> >> "st,stm32mp25-lvds".
> >>
> >> Signed-off-by: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
> >> ---
> >> Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml | 8 +++++++-
> >> 1 file changed, 7 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml b/Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml
> >> index 6736f93256b5cebb558cda5250369ec4b1b3033c..b777c55626e4b322d77ef411ad9e4a3afb6c9131 100644
> >> --- a/Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml
> >> +++ b/Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml
> >> @@ -31,7 +31,13 @@ description: |
> >>
> >> properties:
> >> compatible:
> >> - const: st,stm32mp25-lvds
> >> + oneOf:
> >> + - items:
> >> + - enum:
> >> + - st,stm32mp255-lvds
> >> + - const: st,stm32mp25-lvds
> >> + - items:
> > Drop. This should be just enum or const, no need for items.
>
> Why would items not be applicable in this case ? I want the compatible field to
> be either:
>
> compatible = "st,stm32mp255-lvds", "st,stm32mp25-lvds";
>
> or
>
> compatible = "st,stm32mp25-lvds";
Krzysztof is only talking about the 2nd 'items' here. For cases with a
single entry, you can skip 'items'. It's just a shorter version. Either
way will work the same.
Rob
next prev parent reply other threads:[~2025-08-14 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 13:48 [PATCH v2 00/13] Enable display support for STM32MP25 Raphael Gallais-Pou
2025-08-12 13:48 ` [PATCH v2 01/13] dt-bindings: display: st: add new compatible to LTDC device Raphael Gallais-Pou
2025-08-14 9:08 ` Krzysztof Kozlowski
2025-08-14 12:38 ` Raphael Gallais-Pou
2025-08-12 13:48 ` [PATCH v2 02/13] dt-bindings: display: st,stm32-ltdc: add access-controllers property Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 03/13] dt-bindings: display: st: add new compatible to LVDS device Raphael Gallais-Pou
2025-08-14 9:09 ` Krzysztof Kozlowski
2025-08-14 12:36 ` Raphael Gallais-Pou
2025-08-14 14:01 ` Rob Herring [this message]
2025-08-12 13:49 ` [PATCH v2 04/13] dt-bindings: display: st,stm32mp25-lvds: add access-controllers property Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 05/13] dt-bindings: display: st,stm32mp25-lvds: add power-domains property Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 06/13] dt-bindings: arm: stm32: add required #clock-cells property Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 07/13] drm/stm: ltdc: support new hardware version for STM32MP25 SoC Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 08/13] drm/stm: ltdc: handle lvds pixel clock Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 09/13] arm64: dts: st: add ltdc support on stm32mp251 Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 10/13] arm64: dts: st: add lvds support on stm32mp255 Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 11/13] arm64: dts: st: add clock-cells to syscfg node on stm32mp251 Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 12/13] arm64: dts: st: enable display support on stm32mp257f-ev1 board Raphael Gallais-Pou
2025-08-12 13:49 ` [PATCH v2 13/13] arm64: dts: st: add loopback clocks on LTDC node Raphael Gallais-Pou
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=20250814140119.GA2748790-robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=philippe.cornu@foss.st.com \
--cc=raphael.gallais-pou@foss.st.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=will@kernel.org \
--cc=yannick.fertre@foss.st.com \
/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).