From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] drm/sun4i: Introduce A33 display driver
Date: Tue, 6 Sep 2016 20:54:52 +0200 [thread overview]
Message-ID: <20160906185452.GI9040@lukather> (raw)
In-Reply-To: <CAGb2v65Ui5ys_=5fmW4FkfR+oc7sCnwq0cHbgGFt3r-Kgg=k5w@mail.gmail.com>
On Tue, Sep 06, 2016 at 10:50:09AM +0800, Chen-Yu Tsai wrote:
> >> The implementation might be along the lines of
> >>
> >> 1. having multiple output ports, each for a different interface type.
> >> (Some platforms go this route)
> >>
> >> Or
> >>
> >> 2. having a DT property describe what the output interface is.
> >>
> >> The RGB/TCON driver would then setup the registers accordingly.
> >
> > Hmmm, yeah, we would need to adjust the bindings too...
> >
> > I guess I'd prefer 1), but that would also be the most invasive
> > solution. I'm not sure how the DT maintainers feel about that.
>
> I wonder if the TCON could use its 2 channels simultaneously?
No, it's mutually exclusive.
> Like output to one LCD, then mirror through HDMI/VGA?
> The first option would be able to cover this better?
Even if it wasn't exclusive, that wouldn't be possible
unfortunately. Or rather, this would be possible if the LCD and the
HDMI screen had the same timings, which is very unlikely.
> And you still need to add outgoing endpoints for the HDMI block.
Indeed.
> In addition we'll have to rework the TV encoder binding as well.
>
> The 2 TV encoders (on the A20) each have four DACs, which map
> onto 4 external pins. The address space includes a not so easy
> to use mux. More importantly, the binding needs to specify which
> pin is used for what signal (RGB, YUV, S/Video, composite).
> There seems to be an implicit rule that 1 pin is always used
> for composite, and the 3 others RGB, though.
I'm not sure why we would need to rework this one though. We have no
way to detect whether the screen is connected or not on either
connectors, and we can't have both output running at the same time for
the same reason than mention above.
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/20160906/906fe9ee/attachment.sig>
next prev parent reply other threads:[~2016-09-06 18:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 15:31 [PATCH 0/7] drm/sun4i: Introduce A33 display driver Maxime Ripard
2016-09-01 15:31 ` [PATCH 1/7] drm/sun4i: support TCONs without channel 1 Maxime Ripard
2016-09-02 1:47 ` Chen-Yu Tsai
2016-09-01 15:31 ` [PATCH 2/7] drm/sun4i: support A33 tcon Maxime Ripard
2016-09-02 6:02 ` Chen-Yu Tsai
2016-09-05 20:22 ` Maxime Ripard
2016-09-01 15:32 ` [PATCH 3/7] drm/sun4i: Add SAT and DRC drivers Maxime Ripard
2016-09-02 6:45 ` Chen-Yu Tsai
2016-09-05 20:27 ` Maxime Ripard
2016-09-04 20:03 ` [linux-sunxi] " Peter Korsgaard
2016-09-06 13:59 ` Maxime Ripard
2016-09-01 15:32 ` [PATCH 4/7] drm/panel: Add Sinlinx SinA33 7" panel Maxime Ripard
2016-09-02 7:01 ` Chen-Yu Tsai
2016-09-04 17:03 ` Icenowy Zheng
2016-09-05 20:02 ` Maxime Ripard
2016-09-06 2:53 ` Chen-Yu Tsai
2016-09-06 9:12 ` Thierry Reding
2016-09-06 14:33 ` Maxime Ripard
2016-09-01 15:32 ` [PATCH 5/7] ARM: sun8i: a33: Add display pipeline Maxime Ripard
2016-09-02 6:28 ` Chen-Yu Tsai
2016-09-05 20:21 ` Maxime Ripard
2016-09-06 2:51 ` Chen-Yu Tsai
2016-09-01 15:32 ` [PATCH 6/7] ARM: sun8i: a33: Add RGB666 pins Maxime Ripard
2016-09-02 1:44 ` [linux-sunxi] " Chen-Yu Tsai
2016-09-01 15:32 ` [PATCH 7/7] ARM: sun8i: sina33: Enable display Maxime Ripard
2016-09-02 1:30 ` [PATCH 0/7] drm/sun4i: Introduce A33 display driver Icenowy Zheng
2016-09-02 19:06 ` Maxime Ripard
2016-09-03 1:43 ` Chen-Yu Tsai
2016-09-05 20:37 ` Maxime Ripard
2016-09-06 2:50 ` Chen-Yu Tsai
2016-09-06 18:54 ` Maxime Ripard [this message]
2016-09-07 4:49 ` Chen-Yu Tsai
2016-09-12 9:56 ` 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=20160906185452.GI9040@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 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).