devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: linux-media@vger.kernel.org
Cc: devicetree@vger.kernel.org, Hans Verkuil <hans.verkuil@cisco.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] dt-bindings: document the CEC GPIO bindings
Date: Thu, 10 Aug 2017 10:11:49 +0200	[thread overview]
Message-ID: <e64f40cb-f53c-4de9-180c-a6a30e052965@xs4all.nl> (raw)
In-Reply-To: <64803004-6bea-44db-a651-cc21806250b5@xs4all.nl>

On 10/08/17 10:03, Hans Verkuil wrote:
> On 02/08/17 10:42, Hans Verkuil wrote:
>> From: Hans Verkuil <hans.verkuil@cisco.com>
>>
>> Document the bindings for the cec-gpio module for hardware where the
>> CEC pin is connected to a GPIO pin.
> 
> ping?
> 
>>
>> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
>> ---
>>  Documentation/devicetree/bindings/media/cec-gpio.txt | 18 ++++++++++++++++++
>>  1 file changed, 18 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/media/cec-gpio.txt
>>
>> diff --git a/Documentation/devicetree/bindings/media/cec-gpio.txt b/Documentation/devicetree/bindings/media/cec-gpio.txt
>> new file mode 100644
>> index 000000000000..58fa56080cda
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/cec-gpio.txt
>> @@ -0,0 +1,18 @@
>> +* HDMI CEC GPIO driver

OK, reading your comments from an other bindings patch I realize that 'bindings
refer to hardware, not drivers'. I'll fix and repost :-)

Regards,

	Hans

>> +
>> +The HDMI CEC GPIO module supports CEC implementations where the CEC pin
>> +is hooked up to a pull-up GPIO pin.
>> +
>> +The CEC GPIO
>> +
>> +Required properties:
>> +  - compatible: value must be "cec-gpio"
>> +  - gpio: gpio that the CEC line is connected to
>> +
>> +Example for the Raspberry Pi 3 where the CEC line is connected to
>> +pin 7 aka BCM4 aka GPCLK0 on the GPIO pin header:
>> +
>> +cec-gpio {
>> +       compatible = "cec-gpio";
>> +       gpio = <&gpio 4 GPIO_ACTIVE_HIGH>;
>> +};
>>
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-08-10  8:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02  8:42 [PATCH 0/3] cec-gpio: add HDMI CEC GPIO-based driver Hans Verkuil
     [not found] ` <20170802084242.14947-1-hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2017-08-02  8:42   ` [PATCH 1/3] dt-bindings: document the CEC GPIO bindings Hans Verkuil
     [not found]     ` <20170802084242.14947-2-hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2017-08-10  8:03       ` Hans Verkuil
2017-08-10  8:11         ` Hans Verkuil [this message]
2017-08-02  8:42   ` [PATCH 3/3] MAINTAINERS: add cec-gpio entry Hans Verkuil
2017-08-02  8:42 ` [PATCH 2/3] cec-gpio: add HDMI CEC GPIO driver Hans Verkuil

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=e64f40cb-f53c-4de9-180c-a6a30e052965@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-media@vger.kernel.org \
    /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).