public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: devel@driverdev.osuosl.org, Rob Herring <robh@kernel.org>,
	Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	span@analogixsemi.com, Kumar Gala <galak@codeaurora.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	Nathan Chung <nathan.chung@mediatek.com>
Subject: Re: [PATCHv2 2/3] devicetree: Add new ANX7814 SlimPort transmitter binding.
Date: Thu, 10 Sep 2015 18:37:57 +0300	[thread overview]
Message-ID: <2441988.GBbudkNyP4@avalon> (raw)
In-Reply-To: <CAFqH_50BZPNbKhQrT+8fNEeFHUsGF0Bzdn-TKMzDTtF9ftetYg@mail.gmail.com>

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@kernel.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@collabora.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

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

      reply	other threads:[~2015-09-10 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  7:25 [PATCHv2 2/3] devicetree: Add new ANX7814 SlimPort transmitter binding Enric Balletbo i Serra
2015-09-09  0:40 ` Rob Herring
2015-09-10 14:11   ` Enric Balletbo Serra
2015-09-10 15:37     ` Laurent Pinchart [this message]

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=2441988.GBbudkNyP4@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=javier@dowhile0.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nathan.chung@mediatek.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sjoerd.simons@collabora.co.uk \
    --cc=span@analogixsemi.com \
    /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