On Wed, Oct 09, 2013 at 01:17:30PM +0100, srinivas kandagatla wrote:
.../devicetree/bindings/media/remote-control.txt | 31
1 files changed, 31 insertions(+), 0 deletions(-)
create mode 100644
Documentation/devicetree/bindings/media/remote-control.txt
Thanks Mark,
The blocking issue for st-rc driver is now closed.
On 18/10/13 12:37, Mark Rutland wrote:
Mauro C. had an option that this is not a real use-case and let's not
overdesign the API, thinking on a possible scenario that may never happen.
Do you still think that this use case
.../devicetree/bindings/media/remote-control.txt | 31
1 files changed, 31 insertions(+), 0 deletions(-)
create mode 100644
Documentation/devicetree/bindings/media/remote-control.txt
diff --git a/Documentation/devicetree/bindings/media/remote-control.txt
On 01/10/13 15:49, Mauro Carvalho Chehab wrote:
Btw, we're even thinking on mapping HDMI-CEC remote controller RX/TX via
the RC subsystem. So, another L1 protocol would be hdmi-cec.
Ok.
Yet, it seems unlikely that the very same remote controller IP would use
a different
Em Wed, 02 Oct 2013 17:22:06 +0100
Srinivas KANDAGATLA srinivas.kandaga...@st.com escreveu:
On 01/10/13 15:49, Mauro Carvalho Chehab wrote:
Btw, we're even thinking on mapping HDMI-CEC remote controller RX/TX
via
the RC subsystem. So, another L1 protocol would be hdmi-cec.
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
Em Mon, 30 Sep 2013 09:27:02 +0100
Srinivas KANDAGATLA srinivas.kandaga...@st.com escreveu:
On 27/09/13 14:57, Mauro Carvalho Chehab wrote:
Em Fri, 27 Sep 2013 14:26:12 +0100
Srinivas KANDAGATLA srinivas.kandaga...@st.com escreveu:
On 27/09/13 12:34, Mark Rutland wrote:
+ -
On 27/09/13 14:57, Mauro Carvalho Chehab wrote:
Em Fri, 27 Sep 2013 14:26:12 +0100
Srinivas KANDAGATLA srinivas.kandaga...@st.com escreveu:
On 27/09/13 12:34, Mark Rutland wrote:
+ - rx-mode: Can be infrared or uhf. rx-mode should be present iff
+ the rx pins are wired up.
I'm unsure on
On Fri, Sep 27, 2013 at 02:47:19PM +0100, Mauro Carvalho Chehab wrote:
Em Fri, 27 Sep 2013 12:34:58 +0100
Mark Rutland mark.rutl...@arm.com escreveu:
On Fri, Sep 27, 2013 at 10:33:11AM +0100, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch attempts to collate generic bindings which can be used by
the remote control hardwares. Currently the list is not long as there
are only 2 drivers which are device tree'd.
Mainly this patch tries to document few bindings used by ST
On Fri, Sep 27, 2013 at 10:33:11AM +0100, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch attempts to collate generic bindings which can be used by
the remote control hardwares. Currently the list is not long as there
are only 2 drivers which are
On 27/09/13 12:34, Mark Rutland wrote:
+ - rx-mode: Can be infrared or uhf. rx-mode should be present iff
+the rx pins are wired up.
I'm unsure on this. What if the device has multiple receivers that can
be independently configured? What if it supports something other than
infrared or
Em Fri, 27 Sep 2013 12:34:58 +0100
Mark Rutland mark.rutl...@arm.com escreveu:
On Fri, Sep 27, 2013 at 10:33:11AM +0100, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch attempts to collate generic bindings which can be used by
the remote
Em Fri, 27 Sep 2013 14:26:12 +0100
Srinivas KANDAGATLA srinivas.kandaga...@st.com escreveu:
On 27/09/13 12:34, Mark Rutland wrote:
+- rx-mode: Can be infrared or uhf. rx-mode should be
present iff
+ the rx pins are wired up.
I'm unsure on this. What if the device
14 matches
Mail list logo
