From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Francesco Dolcini <francesco@dolcini.it>
Cc: Marek Vasut <marex@denx.de>, Stefan Agner <stefan@agner.ch>,
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>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] dt-bindings: lcdif: Add endpoint bus-width property
Date: Thu, 13 Aug 2026 11:03:06 +0200 [thread overview]
Message-ID: <cf1e1514-fb92-46cd-95a3-9c857bf08f66@kernel.org> (raw)
In-Reply-To: <7661119.LvFx2qVVIh@steina-w>
On 13/08/2026 10:56, Alexander Stein wrote:
> Am Donnerstag, 13. August 2026, 10:34:02 CEST schrieb Francesco Dolcini:
>> On Thu, Aug 13, 2026 at 10:10:43AM +0200, Krzysztof Kozlowski wrote:
>>> On Wed, Aug 12, 2026 at 03:29:49PM +0200, Francesco Dolcini wrote:
>>>> From: Francesco Dolcini <francesco.dolcini@toradex.com>
>>>>
>>>> The DPI output of the LCD interface can be configured with a bus width
>>>> of 16, 18, or 24 bits. Introduce a bus-width property to the output
>>>> endpoint, specifying the number of parallel RGB bits connected.
>>>>
>>>> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
>>>> ---
>>>> v3: use video-interfaces.yaml
>>>> v2: use the common bus-width property instead of the legacy interface-pix-fmt
>>>> ---
>>>> Documentation/devicetree/bindings/display/fsl,lcdif.yaml | 9 +++++++++
>>>> 1 file changed, 9 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
>>>> index 2dd0411ec651..1f3daf002707 100644
>>>> --- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
>>>> +++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
>>>> @@ -71,6 +71,15 @@ properties:
>>>> $ref: /schemas/graph.yaml#/properties/port
>>>> description: The LCDIF output port
>>>>
>>>> + properties:
>>>> + endpoint:
>>>> + $ref: /schemas/media/video-interfaces.yaml
>>>
>>> This won't work, you need to test your DTS. The port schema does not
>>> allow video-interfaces properties. You need port-base, like in every
>>> other case.
>>
>> Thanks for the review Krzysztof
>>
>> Given my testing was not ok, and I am not sure what I did wrong exactly
>> on my tests, is this the change I should do?
Yes
>>
>> diff --git a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
>> index 1f3daf002707..89cea0c14cf1 100644
>> --- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
>> +++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
>> @@ -68,7 +68,8 @@ properties:
>> maxItems: 1
>>
>> port:
>> - $ref: /schemas/graph.yaml#/properties/port
>> + $ref: /schemas/graph.yaml#/$defs/port-base
>> + unevaluatedProperties: false
>> description: The LCDIF output port
>
> With that change:
> Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Please do not. Build testing is not testing (in the meaning of
"Tested-by" tag), otherwise where is Rob's tested-by tag for all the
patches he build tested?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-13 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 13:29 [PATCH v3 0/4] drm: mxsfb: Support LCDIF interface bus width Francesco Dolcini
2026-08-12 13:29 ` [PATCH v3 1/4] dt-bindings: lcdif: Add endpoint bus-width property Francesco Dolcini
2026-08-12 13:39 ` sashiko-bot
2026-08-12 14:18 ` Frank Li
2026-08-13 8:10 ` Krzysztof Kozlowski
2026-08-13 8:34 ` Francesco Dolcini
2026-08-13 8:56 ` Alexander Stein
2026-08-13 9:03 ` Krzysztof Kozlowski [this message]
2026-08-13 9:06 ` Alexander Stein
2026-08-12 13:29 ` [PATCH v3 2/4] drm: mxsfb: Add optional DPI output bus-width configuration Francesco Dolcini
2026-08-12 14:20 ` Frank Li
2026-08-12 15:02 ` Marco Felsch
2026-08-12 15:07 ` Francesco Dolcini
2026-08-13 8:53 ` Alexander Stein
2026-08-12 13:29 ` [PATCH v3 3/4] ARM: dts: imx6ull-colibri: Set LCDIF bus-width Francesco Dolcini
2026-08-12 13:29 ` [PATCH v3 4/4] ARM: dts: imx7-colibri: " Francesco Dolcini
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=cf1e1514-fb92-46cd-95a3-9c857bf08f66@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=simona@ffwll.ch \
--cc=stefan@agner.ch \
--cc=tzimmermann@suse.de \
/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