From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Rob Herring <robh@kernel.org>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
Jose Abreu <Jose.Abreu@synopsys.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Ulrich Hecht <ulrich.hecht@gmail.com>,
devicetree@vger.kernel.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org,
Russell King <rmk+kernel@arm.linux.org.uk>,
Andy Yan <andy.yan@rock-chips.com>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Subject: Re: [PATCH 14/22] dt-bindings: display: dw-hdmi: Clean up DT bindings documentation
Date: Wed, 07 Dec 2016 11:53:50 +0200 [thread overview]
Message-ID: <3719786.y6Dc2uNlMe@avalon> (raw)
In-Reply-To: <20161206211550.oprrw3m76locagfo@rob-hp-laptop>
Hi Rob,
On Tuesday 06 Dec 2016 15:15:50 Rob Herring wrote:
> On Fri, Dec 02, 2016 at 01:43:29AM +0200, Laurent Pinchart wrote:
> > Make it clear that the core bridge/dw_hdmi.txt document isn't a device
> > tree binding by itself but is meant to be referenced by platform device
> > tree bindings, and update the Rockchip and Freescale DWC HDMI TX
> > bindings to reference it.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> >
> > .../devicetree/bindings/display/bridge/dw_hdmi.txt | 85 +++++++----------
> > .../devicetree/bindings/display/imx/hdmi.txt | 51 +++++++------
> > .../bindings/display/rockchip/dw_hdmi-rockchip.txt | 43 +++++++----
> > 3 files changed, 91 insertions(+), 88 deletions(-)
>
> Acked-by: Rob Herring <robh@kernel.org>
>
> Really, the ddc-i2c-bus prop needs to move to a connector node, but
> that's a separate problem.
I fully agree. One step at a time though :-)
> We might also want to drop the 'ddc-' part and have a generic way to refer
> to an i2c bus. There's a couple of other cases.
Right, but a DT node might need to refer to multiple I2C buses (probably not
for connectors though). The ddc- prefix serves a similar purpose than the
power supply or GPIO name in the *-supply or *-gpios properties.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-12-07 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1480635817-1258-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
2016-12-01 23:43 ` [PATCH 14/22] dt-bindings: display: dw-hdmi: Clean up DT bindings documentation Laurent Pinchart
2016-12-06 21:15 ` Rob Herring
2016-12-07 9:53 ` Laurent Pinchart [this message]
[not found] ` <1480635817-1258-1-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2016-12-01 23:43 ` [PATCH 15/22] dt-bindings: display: renesas: Add R-Car Gen3 HDMI TX DT bindings Laurent Pinchart
2016-12-06 21:18 ` Rob Herring
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=3719786.y6Dc2uNlMe@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Jose.Abreu@synopsys.com \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@freescale.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robh@kernel.org \
--cc=ulrich.hecht@gmail.com \
--cc=vladimir_zapolskiy@mentor.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