From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] media: dt-bindings: media: renesas,csi2: Node port@0 is not mandatory
Date: Wed, 21 Apr 2021 14:31:02 +0200 [thread overview]
Message-ID: <YIAbBoqEAZONAYii@oden.dyn.berto.se> (raw)
In-Reply-To: <YH/zyzfgpmXvkDpB@pendragon.ideasonboard.com>
Hi Laurent and Geert,
On 2021-04-21 12:43:39 +0300, Laurent Pinchart wrote:
> Hi Niklas,
>
> On Fri, Apr 16, 2021 at 10:05:46AM +0200, Niklas Söderlund wrote:
> > On 2021-04-15 22:09:12 +0300, Laurent Pinchart wrote:
> > > On Tue, Apr 13, 2021 at 05:53:46PM +0200, Niklas Söderlund wrote:
> > > > When converting the binding to use the video-interfaces schemas the node
> > > > port@0 was incorrectly made a mandatory property.
> > > >
> > > > The port@0 node describes which CSI-2 transmitter the R-Car CSI-2
> > > > receiver is connected too. Not all boards connects all CSI-2 receivers
> > > > to an CSI-2 transmitter.
> > >
> > > Ports are properties of the device, they should always be there,
> > > regardless of connections. It's the endpoints that describe connections.
> >
> > I understand what you are saying and if that is the way things are done
> > I'm fine with it. As this was brought to light by a recent change in the
> > bindings I wish to understand if this was always the case the bindings
> > have been wrong all along or not.
> >
> > I only ask as because if we keep the port@0 mandatory there will be
> > board files that needs to add empty port@0 nodes as we know they are not
> > used. And as the media bindings are already quiet large for some Renesas
> > boards I want to understand this before spewing out a lot of patches
> > adding empty nodes ;-)
>
> In my opinion port@0 should be in the SoC .dtsi, not in the board .dts.
> Individual boards can then add endpoints when the CSI-2 receiver is
> connected. Would that make sense for you ?
I think this is a case of pragmatism vs being technically correct, and
of course 'technically correct' being the best kind of correct ;-)
Any of the two options works for me as long as we fix the DT validation
errors that currently exists. Laurent seems to prefers keeping the
port@0 mandatory and adding empty port@0 nodes to dtsi files.
@Geert: Does this work for you?
>
> > > > Fixes: 066a94e28a23e04c ("media: dt-bindings: media: Use graph and video-interfaces schemas")
> > > > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> > > > ---
> > > > Documentation/devicetree/bindings/media/renesas,csi2.yaml | 1 -
> > > > 1 file changed, 1 deletion(-)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/media/renesas,csi2.yaml b/Documentation/devicetree/bindings/media/renesas,csi2.yaml
> > > > index 20396f1be9993461..395484807dd5ed47 100644
> > > > --- a/Documentation/devicetree/bindings/media/renesas,csi2.yaml
> > > > +++ b/Documentation/devicetree/bindings/media/renesas,csi2.yaml
> > > > @@ -78,7 +78,6 @@ properties:
> > > > modules connected the CSI-2 receiver.
> > > >
> > > > required:
> > > > - - port@0
> > > > - port@1
> > > >
> > > > required:
>
> --
> Regards,
>
> Laurent Pinchart
--
Regards,
Niklas Söderlund
next prev parent reply other threads:[~2021-04-21 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 15:53 [PATCH] media: dt-bindings: media: renesas,csi2: Node port@0 is not mandatory Niklas Söderlund
2021-04-15 19:09 ` Laurent Pinchart
2021-04-16 8:05 ` Niklas Söderlund
2021-04-19 9:06 ` Geert Uytterhoeven
2021-04-21 9:43 ` Laurent Pinchart
2021-04-21 12:31 ` Niklas Söderlund [this message]
2021-04-21 12:38 ` Geert Uytterhoeven
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=YIAbBoqEAZONAYii@oden.dyn.berto.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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