public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Robby Cai <robby.cai@nxp.com>,
	Frank.Li@nxp.com, martink@posteo.de, rmfrfs@gmail.com,
	kernel@puri.sm, mchehab@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com,
	martin.kepplinger@puri.sm, imx@lists.linux.dev,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: dt-bindings: nxp,imx8mq-mipi-csi2: Fix example endpoint label typo
Date: Wed, 6 May 2026 16:24:35 +0200	[thread overview]
Message-ID: <73111cb1-2019-4faf-abc6-c7deea603eb1@kernel.org> (raw)
In-Reply-To: <20260506142155.GR1598374@killaraus.ideasonboard.com>

On 06/05/2026 16:21, Laurent Pinchart wrote:
> On Wed, May 06, 2026 at 03:33:57PM +0200, Krzysztof Kozlowski wrote:
>> On 06/05/2026 11:01, Robby Cai wrote:
>>> The example in imx8mq-mipi-csi2.yaml uses imx8mm_mipi_csi_{in,out} endpoint
>>> labels, which is confusing for an i.MX8MQ binding. Rename the labels to
>>> imx8mq_mipi_csi_{in,out} for consistency.
>>>
>>> Fixes: 37255747ecbd ("media: dt-bindings: media: document the nxp,imx8mq-mipi-csi2 receiver phy and controller")
>>
>> Nothing to fix here. Otherwise explain the bug.
>>
>>> Signed-off-by: Robby Cai <robby.cai@nxp.com>
>>> ---
>>>  .../devicetree/bindings/media/nxp,imx8mq-mipi-csi2.yaml       | 4 ++--
>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/media/nxp,imx8mq-mipi-csi2.yaml b/Documentation/devicetree/bindings/media/nxp,imx8mq-mipi-csi2.yaml
>>> index 4fcfc4fd3565..71f79651dd96 100644
>>> --- a/Documentation/devicetree/bindings/media/nxp,imx8mq-mipi-csi2.yaml
>>> +++ b/Documentation/devicetree/bindings/media/nxp,imx8mq-mipi-csi2.yaml
>>> @@ -220,7 +220,7 @@ examples:
>>>              port@0 {
>>>                  reg = <0>;
>>>  
>>> -                imx8mm_mipi_csi_in: endpoint {
>>> +                imx8mq_mipi_csi_in: endpoint {
>>
>> Drop the labels instead - they are not used.
> 
> I think the label has value, it improves readability of the example by
> making the purpose of the endpoints more explicit. I won't fight for it
> though, I know it's hard to change your mind.

Then should not have imx8mq in the first place. The only information
coming here is that it is input endpoint. IMO it is close to obvious
from the opposite of "remote-endpoint = <&imx477_out>;" (if remote is
OUT, then this must be IN). But keeping the redundant data or actually
correcting wrong redundant data into correct redundant data, is still
undesirable. Such patterns then keep spreading to new code.

Best regards,
Krzysztof

  reply	other threads:[~2026-05-06 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  9:01 [PATCH] media: dt-bindings: nxp,imx8mq-mipi-csi2: Fix example endpoint label typo Robby Cai
2026-05-06 11:20 ` Laurent Pinchart
2026-05-06 13:33 ` Krzysztof Kozlowski
2026-05-06 14:21   ` Laurent Pinchart
2026-05-06 14:24     ` Krzysztof Kozlowski [this message]
2026-05-06 14:30       ` Laurent Pinchart
2026-05-06 14:38         ` Krzysztof Kozlowski

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=73111cb1-2019-4faf-abc6-c7deea603eb1@kernel.org \
    --to=krzk@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=kernel@puri.sm \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=martin.kepplinger@puri.sm \
    --cc=martink@posteo.de \
    --cc=mchehab@kernel.org \
    --cc=rmfrfs@gmail.com \
    --cc=robby.cai@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.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