From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/5] drm/bridge: Add RGB to VGA bridge support
Date: Thu, 6 Oct 2016 09:21:06 +0200 [thread overview]
Message-ID: <20161006072106.GA4684@lukather> (raw)
In-Reply-To: <8795dc49-26f9-0505-f442-2ca74b51872f@codeaurora.org>
Hi Archit,
On Mon, Oct 03, 2016 at 04:40:57PM +0530, Archit Taneja wrote:
> Hi Maxime,
>
> On 09/30/2016 08:07 PM, Maxime Ripard wrote:
> >Some boards have an entirely passive RGB to VGA bridge, based on either
> >DACs or resistor ladders.
> >
> >Those might or might not have an i2c bus routed to the VGA connector in
> >order to access the screen EDIDs.
> >
> >Add a bridge that doesn't do anything but expose the modes available on the
> >screen, either based on the EDIDs if available, or based on the XGA
> >standards.
> >
> >Acked-by: Rob Herring <robh@kernel.org>
> >Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> >---
> > .../bindings/display/bridge/rgb-to-vga-bridge.txt | 48 +++++
> > drivers/gpu/drm/bridge/Kconfig | 7 +
> > drivers/gpu/drm/bridge/Makefile | 1 +
> > drivers/gpu/drm/bridge/rgb-to-vga.c | 229 +++++++++++++++++++++
> > 4 files changed, 285 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/display/bridge/rgb-to-vga-bridge.txt
> > create mode 100644 drivers/gpu/drm/bridge/rgb-to-vga.c
> >
> >diff --git a/Documentation/devicetree/bindings/display/bridge/rgb-to-vga-bridge.txt b/Documentation/devicetree/bindings/display/bridge/rgb-to-vga-bridge.txt
> >new file mode 100644
> >index 000000000000..a8375bc1f9cb
> >--- /dev/null
> >+++ b/Documentation/devicetree/bindings/display/bridge/rgb-to-vga-bridge.txt
> >@@ -0,0 +1,48 @@
> >+Dumb RGB to VGA bridge
> >+----------------------
> >+
> >+This binding is aimed for dumb RGB to VGA bridges that do not require
> >+any configuration.
> >+
> >+Required properties:
> >+
> >+- compatible: Must be "rgb-to-vga-bridge"
>
> I'd talked to Laurent on IRC if he's okay with this. And I guess you to
> had discussed it during XDC too. He's suggested that it'd be better to
> have the compatible string as "simple-vga-dac".
I just wished this bikeshedding had taken place publicly and be
actually part of that discussion, but yeah, ok.
> Some of the reasons behind having this:
>
> - We don't need to specify "rgb" in the compatible string since most
> simple VGA DACs can only work with an RGB input.
Ok.
> - Also, with "dac" specified in the string, we don't need to
> specifically mention "bridge" in the string. Also, bridge is a drm
> specific term.
>
> - "simple" is considered because it's an unconfigurable bridge, and it
> might be misleading for other VGA DACs to not use "vga-dac".
All those "simple" bindings are just the biggest lie we ever
told. It's simple when you introduce it, and then grows into something
much more complicated than a non-simple implementation.
> What do you think about this? If you think it's good, would it be
> possible for you to change this? I guess it's okay for the rest of
> the patch to stay the same.
I'll update and respin the serie.
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161006/701c158a/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Archit Taneja <architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Daniel Vetter
<daniel.vetter-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Boris Brezillon
<boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH v5 2/5] drm/bridge: Add RGB to VGA bridge support
Date: Thu, 6 Oct 2016 09:21:06 +0200 [thread overview]
Message-ID: <20161006072106.GA4684@lukather> (raw)
In-Reply-To: <8795dc49-26f9-0505-f442-2ca74b51872f-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 3115 bytes --]
Hi Archit,
On Mon, Oct 03, 2016 at 04:40:57PM +0530, Archit Taneja wrote:
> Hi Maxime,
>
> On 09/30/2016 08:07 PM, Maxime Ripard wrote:
> >Some boards have an entirely passive RGB to VGA bridge, based on either
> >DACs or resistor ladders.
> >
> >Those might or might not have an i2c bus routed to the VGA connector in
> >order to access the screen EDIDs.
> >
> >Add a bridge that doesn't do anything but expose the modes available on the
> >screen, either based on the EDIDs if available, or based on the XGA
> >standards.
> >
> >Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> >Signed-off-by: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
> >---
> > .../bindings/display/bridge/rgb-to-vga-bridge.txt | 48 +++++
> > drivers/gpu/drm/bridge/Kconfig | 7 +
> > drivers/gpu/drm/bridge/Makefile | 1 +
> > drivers/gpu/drm/bridge/rgb-to-vga.c | 229 +++++++++++++++++++++
> > 4 files changed, 285 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/display/bridge/rgb-to-vga-bridge.txt
> > create mode 100644 drivers/gpu/drm/bridge/rgb-to-vga.c
> >
> >diff --git a/Documentation/devicetree/bindings/display/bridge/rgb-to-vga-bridge.txt b/Documentation/devicetree/bindings/display/bridge/rgb-to-vga-bridge.txt
> >new file mode 100644
> >index 000000000000..a8375bc1f9cb
> >--- /dev/null
> >+++ b/Documentation/devicetree/bindings/display/bridge/rgb-to-vga-bridge.txt
> >@@ -0,0 +1,48 @@
> >+Dumb RGB to VGA bridge
> >+----------------------
> >+
> >+This binding is aimed for dumb RGB to VGA bridges that do not require
> >+any configuration.
> >+
> >+Required properties:
> >+
> >+- compatible: Must be "rgb-to-vga-bridge"
>
> I'd talked to Laurent on IRC if he's okay with this. And I guess you to
> had discussed it during XDC too. He's suggested that it'd be better to
> have the compatible string as "simple-vga-dac".
I just wished this bikeshedding had taken place publicly and be
actually part of that discussion, but yeah, ok.
> Some of the reasons behind having this:
>
> - We don't need to specify "rgb" in the compatible string since most
> simple VGA DACs can only work with an RGB input.
Ok.
> - Also, with "dac" specified in the string, we don't need to
> specifically mention "bridge" in the string. Also, bridge is a drm
> specific term.
>
> - "simple" is considered because it's an unconfigurable bridge, and it
> might be misleading for other VGA DACs to not use "vga-dac".
All those "simple" bindings are just the biggest lie we ever
told. It's simple when you introduce it, and then grows into something
much more complicated than a non-simple implementation.
> What do you think about this? If you think it's good, would it be
> possible for you to change this? I guess it's okay for the rest of
> the patch to stay the same.
I'll update and respin the serie.
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-06 7:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 14:37 No subject Maxime Ripard
2016-09-30 14:37 ` (unknown), Maxime Ripard
2016-09-30 14:37 ` [PATCH v5 1/5] drm/sun4i: rgb: Remove the bridge enable/disable functions Maxime Ripard
2016-09-30 14:37 ` Maxime Ripard
2016-09-30 14:37 ` [PATCH v5 2/5] drm/bridge: Add RGB to VGA bridge support Maxime Ripard
2016-09-30 14:37 ` Maxime Ripard
2016-10-03 11:10 ` Archit Taneja
2016-10-03 11:10 ` Archit Taneja
2016-10-06 7:21 ` Maxime Ripard [this message]
2016-10-06 7:21 ` Maxime Ripard
2016-10-06 11:39 ` Archit Taneja
2016-10-06 11:39 ` Archit Taneja
2016-10-06 17:27 ` Laurent Pinchart
2016-10-06 17:27 ` Laurent Pinchart
2016-10-06 19:53 ` Sean Paul
2016-10-06 19:53 ` Sean Paul
2016-10-06 21:04 ` Laurent Pinchart
2016-10-06 21:04 ` Laurent Pinchart
2016-10-07 4:57 ` Archit Taneja
2016-10-07 4:57 ` Archit Taneja
2016-10-07 9:14 ` Maxime Ripard
2016-10-07 9:14 ` Maxime Ripard
2016-10-10 5:35 ` Archit Taneja
2016-10-10 5:35 ` Archit Taneja
2016-10-10 7:15 ` Laurent Pinchart
2016-10-10 7:15 ` Laurent Pinchart
2016-10-10 9:34 ` Archit Taneja
2016-10-10 9:34 ` Archit Taneja
2016-10-07 9:28 ` Laurent Pinchart
2016-10-07 9:28 ` Laurent Pinchart
2016-10-07 13:42 ` Laurent Pinchart
2016-10-07 13:42 ` Laurent Pinchart
2016-09-30 14:37 ` [PATCH v5 3/5] ARM: sun5i: a13-olinuxino: Enable VGA bridge Maxime Ripard
2016-09-30 14:37 ` Maxime Ripard
2016-09-30 14:37 ` [PATCH v5 4/5] ARM: multi_v7: enable " Maxime Ripard
2016-09-30 14:37 ` Maxime Ripard
2016-09-30 14:37 ` [PATCH v5 5/5] ARM: sunxi: Enable " Maxime Ripard
2016-09-30 14:37 ` Maxime Ripard
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=20161006072106.GA4684@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.