From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-renesas-soc@vger.kernel.org,
tomoharu.fukawa.eb@renesas.com,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v12 1/2] rcar-csi2: add Renesas R-Car MIPI CSI-2 receiver documentation
Date: Fri, 26 Jan 2018 01:32:04 +0100 [thread overview]
Message-ID: <20180126003204.GA18950@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20180126002358.GA19915@bigcity.dyn.berto.se>
Hi again,
On 2018-01-26 01:23:58 +0100, Niklas Söderlund wrote:
[snip]
> >
> > Furthermore, as explained in a comment I made when reviewing the VIN patch
> > series, I wonder whether we shouldn't identify the CSI-2 receiver instances by
> > ID the same way we do with the VIN instances (using the renesas,id property).
> > In that case I think the endpoint numbering won't matter.
>
> The endpoint numbering here plays no part in identify the CSI-2 receiver
> instances nor dose it carry any other information. I still think it's
> neat to define the binding like this as it more explicit and IMHO this
> makes it easier to understand.
I now see that the commit message implies that they do matter but this
is wrong. It was true before the 'renesas,id' was added to the VIN
bindings, but as having cross dependences on bindings are bad this is no
longer the case. I will remove that paragraph for the next version.
Sorry for the noise.
--
Regards,
Niklas Söderlund
prev parent reply other threads:[~2018-01-26 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171129193235.25423-1-niklas.soderlund+renesas@ragnatech.se>
2017-11-29 19:32 ` [PATCH v12 1/2] rcar-csi2: add Renesas R-Car MIPI CSI-2 receiver documentation Niklas Söderlund
2017-12-05 13:39 ` Sakari Ailus
[not found] ` <20171129193235.25423-2-niklas.soderlund+renesas-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org>
2017-12-11 18:00 ` Laurent Pinchart
2018-01-26 0:23 ` Niklas Söderlund
2018-01-26 0:32 ` Niklas Söderlund [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=20180126003204.GA18950@bigcity.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=hverkuil@xs4all.nl \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomoharu.fukawa.eb@renesas.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).