From: Mickael GUENE <mickael.guene@st.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v1 1/3] dt-bindings: Document MIPID02 bindings
Date: Mon, 18 Mar 2019 09:08:57 +0000 [thread overview]
Message-ID: <a8dff925-3ec4-3a40-f129-ea162ca25aed@st.com> (raw)
In-Reply-To: <20190318084825.3hpejk5xg2xt2h4b@valkosipuli.retiisi.org.uk>
Sakari,
>>>> +
>>>> +Example:
>>>> +
>>>> +mipid02: mipid02@14 {
>>>
>>> The node should be a generic name. "csi2rx" is used by a few devices now.
>>>
>> If I understand you well, you would prefer:
>> csi2rx: mipid02@14 {
>> I show no usage of csi2rx node naming except for MIPI-CSI2 RX controller.
>
> The other way around. :)
>
> The label can be more or less anything AFAIK.
>
Ok got it !!! So something like 'mipid02: bridge@14 {' should be ok ?
Thx
next prev parent reply other threads:[~2019-03-18 9:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 6:44 [PATCH v1 0/3] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-12 6:44 ` [PATCH v1 1/3] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-16 21:46 ` Sakari Ailus
2019-03-18 8:28 ` Mickael GUENE
2019-03-18 8:48 ` Sakari Ailus
2019-03-18 9:08 ` Mickael GUENE [this message]
2019-03-25 7:55 ` [PATCH v2 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-25 7:55 ` [PATCH v2 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-26 10:03 ` [PATCH v3 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-26 10:03 ` [PATCH v3 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-26 12:17 ` Sakari Ailus
2019-03-26 13:40 ` Mickael GUENE
2019-03-26 13:44 ` Sakari Ailus
2019-03-27 9:55 ` [PATCH v4 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-27 9:55 ` [PATCH v4 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-28 17:43 ` Rob Herring
2019-04-06 10:35 ` Sakari Ailus
2019-04-06 10:38 ` Sakari Ailus
2019-04-08 6:20 ` Mickael GUENE
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=a8dff925-3ec4-3a40-f129-ea162ca25aed@st.com \
--to=mickael.guene@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
/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).