linux-kernel - Re: [PATCHv2 2/3] devicetree: Add new ANX7814 SlimPort transmitter binding.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2441988.GBbudkNyP4@avalon>
Date:	Thu, 10 Sep 2015 18:37:57 +0300
From:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:	dri-devel@...ts.freedesktop.org
Cc:	Enric Balletbo Serra <eballetbo@...il.com>,
	Rob Herring <robh@...nel.org>, devel@...verdev.osuosl.org,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Pawel Moll <pawel.moll@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org,
	Sjoerd Simons <sjoerd.simons@...labora.co.uk>,
	Rob Herring <robh+dt@...nel.org>, span@...logixsemi.com,
	Kumar Gala <galak@...eaurora.org>,
	Mark Rutland <mark.rutland@....com>,
	Javier Martinez Canillas <javier@...hile0.org>,
	Nathan Chung <nathan.chung@...iatek.com>
Subject: Re: [PATCHv2 2/3] devicetree: Add new ANX7814 SlimPort transmitter binding.

Hi Enric,

On Thursday 10 September 2015 16:11:03 Enric Balletbo Serra wrote:
> 2015-09-09 2:40 GMT+02:00 Rob Herring <robh@...nel.org>:
> > On 09/08/2015 02:25 AM, Enric Balletbo i Serra wrote:
> >> The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
> >> designed for portable devices.
> >> 
> >> You can add support to your board with current binding.
> >> 
> >> Example:
> >>       anx7814: anx7814@38 {
> >>               compatible = "analogix,anx7814";
> >>               reg = <0x38>;
> >>               pd-gpios = <&gpio0 1 GPIO_ACTIVE_HIGH>;
> >>               reset-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
> >>       };
> >> 
> >> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@...labora.com>
> >> ---
> >> 
> >>  .../devicetree/bindings/video/anx7814.txt          | 22 ++++++++++++++++
> >>  1 file changed, 22 insertions(+)
> >>  create mode 100644 Documentation/devicetree/bindings/video/anx7814.txt
> >> 
> >> diff --git a/Documentation/devicetree/bindings/video/anx7814.txt
> >> b/Documentation/devicetree/bindings/video/anx7814.txt new file mode
> >> 100644
> >> index 0000000..a8cc746
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/video/anx7814.txt
> >> @@ -0,0 +1,22 @@
> >> +Analogix ANX7814 SlimPort (Full-HD Transmitter)
> >> +-----------------------------------------------
> >> +
> >> +The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
> >> +designed for portable devices.
> >> +
> >> +Required properties:
> >> +
> >> + - compatible        : "analogix,anx7814"
> >> + - reg               : I2C address of the device
> >> + - pd-gpios  : Which GPIO to use for power down
> >> + - reset-gpios       : Which GPIO to use for reset
> >> +
> >> +Example:
> >> +
> >> +     anx7814: anx7814@38 {
> >> +             compatible = "analogix,anx7814";
> >> +             reg = <0x38>;
> >> +             pd-gpios = <&gpio0 1 GPIO_ACTIVE_HIGH>;
> >> +             reset-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
> > 
> > No ports needed for describing data connections?
> 
> IMHO I'm not sure if this is applicable here, in this case the bridge
> is transparent so it's not required another device node. For example,
> I've an evaluation board, whre I connect in one side an HDMI input
> signal an in the other side a DP monitor, the driver only configures
> the chip and waits for different events (cable plug, cable unplug, etc
> ..)

But what if the chip is connected to a display controller, for instance to the 
HDMI output of an SoC ? Is that a use case for the hardware ?

-- 
Regards,

Laurent Pinchart

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/