From: Nicolas THERY <nicolas.thery@st.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Magnus Damm <magnus.damm@gmail.com>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>,
Willy POISSON <willy.poisson@st.com>,
Jean-Marc VOLLE <jean-marc.volle@st.com>,
Pierre-yves TALOUD <pierre-yves.taloud@st.com>
Subject: Re: [RFC v4] V4L DT bindings
Date: Fri, 31 Aug 2012 09:11:15 +0000 [thread overview]
Message-ID: <50407FB3.3050209@st.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1208242356051.20710@axis700.grange>
Hello,
On 2012-08-25 01:27, Guennadi Liakhovetski wrote:
[snip]
> csi2: csi2@0xffc90000 {
> compatible = "renesas,sh-mobile-csi2";
> reg = <0xffc90000 0x1000>;
> interrupts = <0x17a0>;
> #address-cells = <1>;
> #size-cells = <0>;
>
> /* Ok to have them global? */
> clock-lanes = <0>;
> data-lanes = <2>, <1>;
>
> ...
> imx074_1: videolink@1 {
> reg = <1>;
> client = <&imx074 0>;
> bus-width = <2>;
>
> csi2-ecc;
> csi2-crc;
>
> renesas,csi2-phy = <0>;
> };
> ceu0: videolink@0 {
> reg = <0>;
> immutable;
> };
> };
videolink@1 makes the description of the CSI-2 rx board-specific. Would it be
possible to keep the description of the SoC nodes board-agnostic to ease reuse
of the SoC description in multiple board DTs?
Would this be as simple as replacing &imx074 with a generic well-known name
defined in the board part of the DT?
Best regards,
Nicolas
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas THERY <nicolas.thery@st.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Magnus Damm <magnus.damm@gmail.com>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>,
Willy POISSON <willy.poisson@st.com>,
Jean-Marc VOLLE <jean-marc.volle@st.com>,
Pierre-yves TALOUD <pierre-yves.taloud@st.com>
Subject: Re: [RFC v4] V4L DT bindings
Date: Fri, 31 Aug 2012 11:11:15 +0200 [thread overview]
Message-ID: <50407FB3.3050209@st.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1208242356051.20710@axis700.grange>
Hello,
On 2012-08-25 01:27, Guennadi Liakhovetski wrote:
[snip]
> csi2: csi2@0xffc90000 {
> compatible = "renesas,sh-mobile-csi2";
> reg = <0xffc90000 0x1000>;
> interrupts = <0x17a0>;
> #address-cells = <1>;
> #size-cells = <0>;
>
> /* Ok to have them global? */
> clock-lanes = <0>;
> data-lanes = <2>, <1>;
>
> ...
> imx074_1: videolink@1 {
> reg = <1>;
> client = <&imx074 0>;
> bus-width = <2>;
>
> csi2-ecc;
> csi2-crc;
>
> renesas,csi2-phy = <0>;
> };
> ceu0: videolink@0 {
> reg = <0>;
> immutable;
> };
> };
videolink@1 makes the description of the CSI-2 rx board-specific. Would it be
possible to keep the description of the SoC nodes board-agnostic to ease reuse
of the SoC description in multiple board DTs?
Would this be as simple as replacing &imx074 with a generic well-known name
defined in the board part of the DT?
Best regards,
Nicolas
next prev parent reply other threads:[~2012-08-31 9:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 23:27 [RFC v4] V4L DT bindings Guennadi Liakhovetski
2012-08-24 23:27 ` Guennadi Liakhovetski
2012-08-30 15:19 ` Nicolas THERY
2012-08-30 15:19 ` Nicolas THERY
2012-08-30 20:21 ` Sylwester Nawrocki
2012-08-30 20:21 ` Sylwester Nawrocki
2012-08-30 20:58 ` V4L DT @ plumbers (was Re: [RFC v4] V4L DT bindings) Guennadi Liakhovetski
2012-08-30 20:58 ` Guennadi Liakhovetski
2012-08-30 22:30 ` Laurent Pinchart
2012-08-30 22:30 ` Laurent Pinchart
2012-08-30 22:39 ` Guennadi Liakhovetski
2012-08-30 22:39 ` Guennadi Liakhovetski
2012-08-30 22:39 ` Guennadi Liakhovetski
2012-08-31 0:59 ` Hans Verkuil
2012-08-31 0:59 ` Hans Verkuil
[not found] ` <le0u47eut2t0gh4pxyuu5vse.1346374764563-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2012-08-31 16:05 ` Guennadi Liakhovetski
2012-08-31 16:05 ` Guennadi Liakhovetski
2012-08-31 16:05 ` Guennadi Liakhovetski
2012-08-31 6:46 ` [RFC v4] V4L DT bindings Nicolas THERY
2012-08-31 6:46 ` Nicolas THERY
2012-08-31 19:38 ` Sylwester Nawrocki
2012-08-31 19:38 ` Sylwester Nawrocki
2012-08-31 9:11 ` Nicolas THERY [this message]
2012-08-31 9:11 ` Nicolas THERY
2012-09-05 10:57 ` [RFC v5] " Guennadi Liakhovetski
2012-09-05 10:57 ` Guennadi Liakhovetski
2012-09-05 23:23 ` Stephen Warren
2012-09-05 23:23 ` Stephen Warren
2012-09-11 14:02 ` Guennadi Liakhovetski
2012-09-11 14:02 ` Guennadi Liakhovetski
2012-09-11 14:02 ` Guennadi Liakhovetski
2012-09-11 15:22 ` Stephen Warren
2012-09-11 15:22 ` Stephen Warren
2012-09-11 15:22 ` Stephen Warren
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=50407FB3.3050209@st.com \
--to=nicolas.thery@st.com \
--cc=benjamin.gaignard@st.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski@gmx.de \
--cc=jean-marc.volle@st.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=pierre-yves.taloud@st.com \
--cc=s.nawrocki@samsung.com \
--cc=swarren@wwwdotorg.org \
--cc=willy.poisson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.