devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.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 06:57:32 -0800	[thread overview]
Message-ID: <20191213145732.GH35479@atomide.com> (raw)
In-Reply-To: <3900f4b3-4604-cb64-ebdd-ae168ef1d2fb@ti.com>

* Tomi Valkeinen <tomi.valkeinen@ti.com> [191213 12:34]:
> On 13/12/2019 14:28, Laurent Pinchart wrote:
> 
> > > So... In the DT file, we would have multiple endpoints in the same output port in DSS, one going to
> > > the panel, one to the SiI9022? omapdrm could then create two encoders, one abstracting the DPI
> > > output and the connection to the panel, one abstracting the DPI output and SiI9022?
> > 
> > That's the idea, yes.
> > 
> > > And then someone would need to handle the GPIO, and set it based on the output used. These kind of
> > > gpios are always difficult, as they don't belong anywhere =).
> > 
> > https://lore.kernel.org/lkml/20191211061911.238393-5-hsinyi@chromium.org/
> > 
> > Still, the infrastructure in omapdrm would need quite a bit of work.
> > We're just about to get a helper layer for linear pipelines merged, and
> > we already need to go one step further :-)
> 
> Alright, sounds like this will be doable in the future. So let's drop this
> and the epos HDMI patches for now.

Oh OK. Sounds like no other solution is usable right now short of
separate dts files like you've done.

> This does sound like quite a bit of work, as you say, so I have no idea when
> we can get there (on the omapdrm side). In the minimum we should first get
> the big omapdrm rework done, in order to avoid nasty conflicts.
> 
> Thanks for educating me =).

Sounds a nice plan though :)

Thanks,

Tony

  reply	other threads:[~2019-12-13 20:38 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
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 [this message]
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=20191213145732.GH35479@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --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 \
    /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).