| Message ID | 20170802084242.14947-2-hverkuil@xs4all.nl (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
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 > + > +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>; > +}; >
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 >
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 + +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>; +};