From: Jyri Sarha <jsarha@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: dri-devel@lists.freedesktop.org, airlied@linux.ie,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
bcousson@baylibre.com, tony@atomide.com, tomi.valkeinen@ti.com,
robdclark@gmail.com, moinejf@free.fr
Subject: Re: [PATCH v4 3/7] drm/tilcdc: Add support for external tda998x encoder
Date: Wed, 15 Apr 2015 18:04:16 +0300 [thread overview]
Message-ID: <552E7DF0.9020105@ti.com> (raw)
In-Reply-To: <20150401222030.GD4027@n2100.arm.linux.org.uk>
On 04/02/15 01:20, Russell King - ARM Linux wrote:
> This is where the DRM model is weak - we don't really have a way to
> say "this is the set of CRTCs which/can/ be associated with this
> connector, can any of the CRTCs accept this mode?" and eliminate
> modes which fail that check.
>
> This problem seems to be one which recurrs, so I wonder if it's
> something which ought to be solved properly.
>
> It's made slightly more difficult because we don't really know which
> connectors could be associated with which CRTCs - that information is
> stored at the encoder level (with the encoders possible_crtcs), and
> I'm not sure we have a way for generic DRM code to know which encoders
> could be associated with which connectors.
I agree that this is not the most elegant solution to the problem, but
it works with Beaglebone-Black - which is AFAIK the only piece of HW
that uses tda998x with tilcdc.
I would like to get these patches merged and revisit the mode validation
code once we have a better solution for it.
Best regards,
Jyri
next prev parent reply other threads:[~2015-04-15 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 8:49 [PATCH v4 0/7] Use DRM component API in tilcdc to connect to tda998x Jyri Sarha
2015-04-01 8:49 ` [PATCH v4 1/7] drm/tilcdc: Fix module unloading Jyri Sarha
2015-04-01 8:49 ` [PATCH v4 3/7] drm/tilcdc: Add support for external tda998x encoder Jyri Sarha
[not found] ` <e22d703d6ee5fe02e8c34b78a63f98a4b2ea1f22.1427877412.git.jsarha-l0cyMroinI0@public.gmane.org>
2015-04-01 22:20 ` Russell King - ARM Linux
2015-04-15 15:04 ` Jyri Sarha [this message]
[not found] ` <cover.1427877412.git.jsarha-l0cyMroinI0@public.gmane.org>
2015-04-01 8:49 ` [PATCH v4 2/7] drm/tilcdc: Remove tilcdc slave support for tda998x driver Jyri Sarha
2015-04-01 8:49 ` [PATCH v4 4/7] drm/tilcdc: Add DRM_TILCDC_SLAVE_COMPAT for ti,tilcdc,slave binding support Jyri Sarha
2015-04-01 8:49 ` [PATCH v4 7/7] drm/tilcdc: Decrement refcount of ep-node from of_graph_get_next_endpoint Jyri Sarha
2015-04-01 8:49 ` [PATCH v4 5/7] drm/tilcdc: Force building of DRM_TILCDC_SLAVE_COMPAT Jyri Sarha
2015-04-01 8:49 ` [PATCH v4 6/7] ARM: dts: am335x-boneblack: Use new binding for HDMI Jyri Sarha
2015-05-07 9:44 ` [PATCH v4 0/7] Use DRM component API in tilcdc to connect to tda998x Tomi Valkeinen
2015-05-07 13:38 ` Jyri Sarha
2015-05-08 11:17 ` Jyri Sarha
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=552E7DF0.9020105@ti.com \
--to=jsarha@ti.com \
--cc=airlied@linux.ie \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
--cc=robdclark@gmail.com \
--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).