From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/8] drm/sun4i: Add optional 'mode' property to TCON
Date: Mon, 13 Feb 2017 09:14:47 +0100 [thread overview]
Message-ID: <20170213081447.r2jhkcx3ex5tsspi@lukather> (raw)
In-Reply-To: <20170211174405.28395-5-plaes@plaes.org>
Hi,
On Sat, Feb 11, 2017 at 07:44:01PM +0200, Priit Laes wrote:
> Add variable to enable either 'rgb' or 'lvds' output.
>
> Signed-off-by: Priit Laes <plaes@plaes.org>
> ---
> Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> index b82c004..c367ede 100644
> --- a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> +++ b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> @@ -43,6 +43,9 @@ Required properties:
> - reset-names: the reset names mentioned above
> - clock-output-names: Name of the pixel clock created
>
> +- mode: Defines which encoder will be enabled. Values are 'rgb', 'lvds'.
> + Defaults to 'rgb' if not set.
> +
Unfortunately, this won't really work. You could very well have two
panels and switch from one to another by changing the pin muxing, so
we have to use an enpoint for that.
This is pretty much the same case that we have with the A10s where we
need to have two output endpoints for the TV Encoder and HDMI,
something we cannot support right now in our binding, since we assume
that we have the two channels that only have one user, which turned
out to be wrong.
I guess an easy way would be to have an extra property defining which
channel the endpoint is attached to.
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: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170213/232111eb/attachment.sig>
next prev parent reply other threads:[~2017-02-13 8:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 17:43 [PATCH 0/8] drm/sun4i: Add basic LVDS support for A10 Priit Laes
2017-02-11 17:43 ` [PATCH 1/8] ARM: sunxi_defconfig: Enable simple panel Priit Laes
2017-02-13 4:06 ` [linux-sunxi] " Chen-Yu Tsai
2017-02-11 17:43 ` [PATCH 2/8] ARM: sun4i: Add display blocks for the sun4i dtsi Priit Laes
2017-02-13 9:16 ` Maxime Ripard
2017-02-13 9:20 ` Chen-Yu Tsai
2017-02-13 16:46 ` [linux-sunxi] " Priit Laes
2017-02-14 8:24 ` Maxime Ripard
2017-02-11 17:44 ` [PATCH 3/8] drm/panel: simple: Add support for LG LP097x02-slq2 panel Priit Laes
2017-02-11 17:44 ` [PATCH 4/8] drm/sun4i: Add optional 'mode' property to TCON Priit Laes
2017-02-13 8:14 ` Maxime Ripard [this message]
2017-02-11 17:44 ` [PATCH 5/8] drm/sun4i: Add encoder type argument to sun4i_tcon0_mode_set Priit Laes
2017-02-13 8:32 ` Maxime Ripard
2017-02-11 17:44 ` [PATCH 6/8] drm/sun4i: Add initial LVDS stub Priit Laes
2017-02-11 17:44 ` [PATCH 7/8] drm/sun4i: Add various bits and pieces to enable LVDS support on sun4i Priit Laes
2017-02-13 8:08 ` Maxime Ripard
2017-02-11 17:44 ` [PATCH 8/8] ARM: dts: sun4i: gemei-g9: Add LVDS display support Priit Laes
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=20170213081447.r2jhkcx3ex5tsspi@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