linux-kernel - Re: [PATCHv3 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] [thread-next>] [day] [month] [year] [list]

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

2015-09-10 18:35 GMT+02:00 Enric Balletbo i Serra <eballetbo@...il.com>:
> 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/bridge/anx7814.txt   | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/video/bridge/anx7814.txt
>
> diff --git a/Documentation/devicetree/bindings/video/bridge/anx7814.txt b/Documentation/devicetree/bindings/video/bridge/anx7814.txt
> new file mode 100644
> index 0000000..a8cc746
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/video/bridge/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>;
> +       };
> +
> --
> 2.1.0
>

I saw after sending the series that there was some discussion here,
let me paste to not forget it.

> > 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 ?
--
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/