From: Thierry Reding <thierry.reding@gmail.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
seanpaul@google.com, daniel.vetter@ffwll.ch, joshi@samsung.com,
dri-devel@lists.freedesktop.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
ajaynumb@gmail.com, prashanth.g@samsung.com,
Ajay Kumar <ajaykumar.rs@samsung.com>
Subject: Re: [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties
Date: Mon, 22 Sep 2014 09:54:25 +0200 [thread overview]
Message-ID: <20140922075424.GB1470@ulmo> (raw)
In-Reply-To: <5419760A.7020908@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 2711 bytes --]
On Wed, Sep 17, 2014 at 02:52:42PM +0300, Tomi Valkeinen wrote:
> On 27/08/14 17:39, Ajay Kumar wrote:
> > Add documentation for DT properties supported by ps8622/ps8625
> > eDP-LVDS converter.
> >
> > Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
> > ---
> > .../devicetree/bindings/video/bridge/ps8622.txt | 20 ++++++++++++++++++++
> > 1 file changed, 20 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/video/bridge/ps8622.txt
> >
> > diff --git a/Documentation/devicetree/bindings/video/bridge/ps8622.txt b/Documentation/devicetree/bindings/video/bridge/ps8622.txt
> > new file mode 100644
> > index 0000000..0ec8172
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/video/bridge/ps8622.txt
> > @@ -0,0 +1,20 @@
> > +ps8622-bridge bindings
> > +
> > +Required properties:
> > + - compatible: "parade,ps8622" or "parade,ps8625"
> > + - reg: first i2c address of the bridge
> > + - sleep-gpios: OF device-tree gpio specification for PD_ pin.
> > + - reset-gpios: OF device-tree gpio specification for RST_ pin.
> > +
> > +Optional properties:
> > + - lane-count: number of DP lanes to use
> > + - use-external-pwm: backlight will be controlled by an external PWM
>
> What does this mean? That the backlight support from ps8625 is not used?
> If so, maybe "disable-pwm" or something?
>
> > +
> > +Example:
> > + lvds-bridge@48 {
> > + compatible = "parade,ps8622";
> > + reg = <0x48>;
> > + sleep-gpios = <&gpc3 6 1 0 0>;
> > + reset-gpios = <&gpc3 1 1 0 0>;
> > + lane-count = <1>;
> > + };
> >
>
> I wish all new display component bindings would use the video
> ports/endpoints to describe the connections. It will be very difficult
> to improve the display driver model later if we're missing such critical
> pieces from the DT bindings.
I disagree. Why would we want to burden all devices with a bloated
binding and drivers with parsing a complex graph when it's not even
known that it will be necessary? Evidently this device works fine
using the current binding. Just because there are bindings to describe
ports in a generic way doesn't mean it has to be applied everywhere.
After all the concept of ports/endpoints applies to non-video devices
too, yet we don't require the bindings for those devices to add ports
or endpoints nodes.
Also it won't be very difficult to extend the binding in a backwards
compatible way if that becomes necessary.
One thing that I'd like to see in this binding, though, is how to hook
up the bridge to a panel. However I'm still catching up on mail after
vacation, so perhaps this has already been discussed further down the
thread.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-09-22 7:54 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 14:39 [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties Ajay Kumar
2014-08-27 14:39 ` [PATCH V7 10/12] Documentation: devicetree: Add vendor prefix for parade Ajay Kumar
2014-08-27 14:39 ` [PATCH V7 09/12] Documentation: drm: bridge: move to video/bridge Ajay Kumar
2014-09-17 11:52 ` [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties Tomi Valkeinen
2014-09-17 14:29 ` Ajay kumar
2014-09-17 16:22 ` Tomi Valkeinen
2014-09-18 5:50 ` Ajay kumar
2014-09-19 12:54 ` Tomi Valkeinen
2014-09-19 13:59 ` Ajay kumar
2014-09-19 14:28 ` Tomi Valkeinen
2014-09-20 11:22 ` Ajay kumar
2014-09-20 15:27 ` Javier Martinez Canillas
2014-09-22 6:00 ` Ajay kumar
2014-09-22 15:05 ` Tomi Valkeinen
2014-10-07 10:30 ` Tomi Valkeinen
2014-10-07 10:36 ` Ajay kumar
2014-10-07 14:49 ` Laurent Pinchart
2014-10-08 7:09 ` Thierry Reding
2014-10-10 13:03 ` Ajay kumar
2014-10-16 8:23 ` Ajay kumar
2014-10-16 9:04 ` Laurent Pinchart
2014-10-28 9:12 ` Javier Martinez Canillas
2014-10-28 11:12 ` Ajay kumar
2014-09-22 8:26 ` Thierry Reding
2014-09-22 14:42 ` Tomi Valkeinen
2014-09-23 5:53 ` Thierry Reding
2014-09-23 8:41 ` Tomi Valkeinen
2014-09-23 9:28 ` Thierry Reding
2014-09-23 11:15 ` Tomi Valkeinen
2014-09-23 14:29 ` Thierry Reding
2014-09-23 15:25 ` Tomi Valkeinen
2014-09-22 8:10 ` Thierry Reding
2014-09-22 8:31 ` Ajay kumar
2014-09-22 10:41 ` Thierry Reding
2014-09-22 11:23 ` Ajay kumar
2014-09-22 11:35 ` Thierry Reding
2014-09-22 12:12 ` Ajay kumar
2014-09-23 0:00 ` Laurent Pinchart
2014-09-23 5:55 ` Thierry Reding
2014-09-23 6:11 ` Ajay kumar
2014-09-23 6:28 ` Thierry Reding
2014-09-23 11:47 ` DT property to selectively disable device features (was [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties) Laurent Pinchart
2014-09-22 8:06 ` [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties Thierry Reding
2014-09-22 14:23 ` Tomi Valkeinen
2014-09-23 6:04 ` Thierry Reding
2014-09-23 7:24 ` Andrzej Hajda
2014-09-23 8:35 ` Thierry Reding
2014-09-23 9:40 ` Tomi Valkeinen
2014-09-23 10:01 ` Thierry Reding
2014-09-23 12:09 ` Tomi Valkeinen
2014-09-23 14:38 ` Thierry Reding
2014-09-23 15:33 ` Tomi Valkeinen
2014-09-23 9:43 ` Andrzej Hajda
2014-09-23 10:10 ` Thierry Reding
2014-09-23 10:34 ` Andrzej Hajda
2014-09-23 14:41 ` Thierry Reding
2014-09-24 7:11 ` Andrzej Hajda
2014-09-24 8:27 ` Tomi Valkeinen
2014-09-23 11:33 ` Laurent Pinchart
2014-09-23 8:54 ` Tomi Valkeinen
2014-09-23 9:39 ` Thierry Reding
2014-09-23 11:31 ` Tomi Valkeinen
2014-09-23 14:45 ` Thierry Reding
2014-09-24 8:42 ` Tomi Valkeinen
2014-10-06 14:40 ` Laurent Pinchart
2014-10-07 7:06 ` Tomi Valkeinen
2014-10-07 7:23 ` Laurent Pinchart
2014-10-07 8:25 ` Tomi Valkeinen
2014-10-07 16:14 ` Laurent Pinchart
2014-09-22 7:54 ` Thierry Reding [this message]
2014-09-22 14:04 ` Tomi Valkeinen
2014-09-23 6:21 ` Thierry Reding
2014-09-23 9:30 ` Tomi Valkeinen
2014-09-23 9:53 ` Thierry Reding
2014-09-23 11:12 ` Laurent Pinchart
2014-09-23 14:50 ` Thierry Reding
2014-09-23 12:00 ` Tomi Valkeinen
2014-09-23 14:58 ` Thierry Reding
2014-09-24 9:08 ` Tomi Valkeinen
2014-09-25 6:23 ` Thierry Reding
2014-10-06 11:34 ` Tomi Valkeinen
2014-10-06 13:55 ` Laurent Pinchart
2014-09-23 10:02 ` Andrzej Hajda
2014-09-23 10:02 ` Andrzej Hajda
2014-09-23 11:10 ` Laurent Pinchart
2014-09-23 11:18 ` Andrzej Hajda
2014-09-23 11:23 ` Laurent Pinchart
2014-09-23 11:47 ` Andrzej Hajda
2014-09-23 11:52 ` Laurent Pinchart
2014-09-23 12:40 ` Andrzej Hajda
2014-09-23 12:40 ` Andrzej Hajda
2014-09-23 14:49 ` Thierry Reding
2014-10-06 14:38 ` Laurent Pinchart
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=20140922075424.GB1470@ulmo \
--to=thierry.reding@gmail.com \
--cc=ajaykumar.rs@samsung.com \
--cc=ajaynumb@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=joshi@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prashanth.g@samsung.com \
--cc=seanpaul@google.com \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).