From: Stephen Warren <swarren@wwwdotorg.org>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: srinivas.kandagatla@st.com, Mark Rutland <mark.rutland@arm.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Landley <rob@landley.net>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] media: rc: OF: Add Generic bindings for remote-control
Date: Wed, 02 Oct 2013 11:44:33 -0600 [thread overview]
Message-ID: <524C5B81.5040602@wwwdotorg.org> (raw)
In-Reply-To: <20131002143340.18639f1a@samsung.com>
On 10/02/2013 11:33 AM, Mauro Carvalho Chehab wrote:
...
> Well, from userspace PoV, it should have just one devnode for each
> TX/RX.
I'm fine with that.
> So, if the device has N TX and/or RX simultaneous connections, it should
> be exposing N device nodes, and the DT should for it should have N entries,
> one for each.
DT is based on the actual HW construction, not how a particular OS wants
to expose that HW through its APIs. If there is a single HW block, there
should be a single DT node, even if that HW block supports multiple
channels.
In some circumstances, it might make sense for the single top-level node
that represents the HW-block to have child nodes that represent the
channels, depending on what exactly the HW is doing and whether this
level of detail is useful in DT. I would qualify this as rare though.
next prev parent reply other threads:[~2013-10-02 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 9:33 [PATCH RFC] media: rc: OF: Add Generic bindings for remote-control Srinivas KANDAGATLA
[not found] ` <1380274391-26577-1-git-send-email-srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
2013-09-27 11:34 ` Mark Rutland
2013-09-27 11:34 ` Mark Rutland
2013-09-27 13:26 ` Srinivas KANDAGATLA
2013-09-27 13:57 ` Mauro Carvalho Chehab
2013-09-30 8:27 ` Srinivas KANDAGATLA
2013-10-01 14:49 ` Mauro Carvalho Chehab
2013-10-02 16:22 ` Srinivas KANDAGATLA
2013-10-02 17:33 ` Mauro Carvalho Chehab
2013-10-02 17:44 ` Stephen Warren [this message]
2013-09-27 13:47 ` Mauro Carvalho Chehab
[not found] ` <20130927104719.6637368f-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-09-30 16:51 ` Mark Rutland
2013-09-30 16:51 ` Mark Rutland
2013-10-09 12:17 ` srinivas kandagatla
2013-10-18 11:37 ` Mark Rutland
2013-10-18 12:23 ` srinivas kandagatla
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=524C5B81.5040602@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=srinivas.kandagatla@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.