From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
dri-devel@lists.freedesktop.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 1/4] ARM: dts: am437x-gp-evm: add HDMI support
Date: Fri, 13 Dec 2019 13:42:07 +0200 [thread overview]
Message-ID: <20191213114207.GC4860@pendragon.ideasonboard.com> (raw)
In-Reply-To: <2f5cfca4-d36d-da2d-59ba-b76669daeded@ti.com>
Hi Tomi,
On Fri, Dec 13, 2019 at 12:56:31PM +0200, Tomi Valkeinen wrote:
> On 13/12/2019 12:42, Laurent Pinchart wrote:
>
> >> I think the correct way would be to have DRM framework understand that we have two displays, which
> >> are mutually exclusive, and the display pipeline drivers would have the means to switch the gpio.
> >> And that the display setup could be communicated properly to the userspace, and the userspace would
> >> understand it. I don't think any of those exists.
> >
> > Isn't this what possible_clones in drm_encoder is for ? It notifies
> > userspace of mutual exclusions between encoders.
>
> Hmm, how would that work here? Isn't encoder cloning about having two encoders, which take the input
> from the same video source, and then outputting to two displays?
That's the idea. If you have one encoder for HDMI and one for the panel,
you can mark them as non-clonable, and then only one of the two can be
active at a time.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2019-12-13 20:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 13:10 [PATCH 1/4] ARM: dts: am437x-gp-evm: add HDMI support Tomi Valkeinen
2019-11-25 13:10 ` [PATCH 2/4] ARM: dts: am437x-epos-evm: " Tomi Valkeinen
2019-11-25 13:10 ` [PATCH 3/4] ARM: dts: dra76-evm: add HDMI output Tomi Valkeinen
2019-11-25 13:11 ` [PATCH 4/4] ARM: dts: am57xx-idk-common: add HDMI to the common dtsi Tomi Valkeinen
2019-12-12 17:21 ` [PATCH 1/4] ARM: dts: am437x-gp-evm: add HDMI support Tony Lindgren
2019-12-12 17:31 ` Tony Lindgren
2019-12-13 9:24 ` Tomi Valkeinen
2019-12-13 10:42 ` Laurent Pinchart
2019-12-13 10:56 ` Tomi Valkeinen
2019-12-13 11:42 ` Laurent Pinchart [this message]
2019-12-13 12:04 ` Tomi Valkeinen
2019-12-13 12:28 ` Laurent Pinchart
2019-12-13 12:33 ` Tomi Valkeinen
2019-12-13 14:57 ` Tony Lindgren
2019-12-13 12:36 ` Tomi Valkeinen
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=20191213114207.GC4860@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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).