From mboxrd@z Thu Jan 1 00:00:00 1970 From: thierry.reding@avionic-design.de (Thierry Reding) Date: Fri, 20 Apr 2012 16:49:43 +0200 Subject: [PATCH 3/7] DRM: add sdrm layer for general embedded system support In-Reply-To: <20120420142558.GB20681@sirena.org.uk> References: <1334158428-23735-1-git-send-email-s.hauer@pengutronix.de> <1334158428-23735-4-git-send-email-s.hauer@pengutronix.de> <20120420123842.GA25662@avionic-0098.adnet.avionic-design.de> <20120420142558.GB20681@sirena.org.uk> Message-ID: <20120420144942.GA8327@avionic-0098.adnet.avionic-design.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Mark Brown wrote: > On Fri, Apr 20, 2012 at 02:38:43PM +0200, Thierry Reding wrote: > > * Dave Airlie wrote: > > > I get the feeling the drm can just be a virtual platform device of > > > some sort, then it reads the device tree and binds all the information > > > on what crtc/encoders are available, > > > That's pretty much what I've come up with in the second round of Tegra DRM > > patches. Basically display controllers and outputs (RGB, HDMI, TVO, DSI) get > > separate drivers and register themselves with the DRM driver which then looks > > at the device tree to see which display controllers to register as CRTCs and > > parses a list of connector nodes to create encoder/connector pairs that > > define the physical connectors and their corresponding outputs. > > > I did take a brief look at the SDRM patches as well and they didn't quite > > seem to fit what was needed for Tegra. But if time allows I'll take a closer > > look. > > This sounds an awful lot like how ASoC hangs together... What in particular sounds awful? Thierry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thierry Reding Subject: Re: [PATCH 3/7] DRM: add sdrm layer for general embedded system support Date: Fri, 20 Apr 2012 16:49:43 +0200 Message-ID: <20120420144942.GA8327@avionic-0098.adnet.avionic-design.de> References: <1334158428-23735-1-git-send-email-s.hauer@pengutronix.de> <1334158428-23735-4-git-send-email-s.hauer@pengutronix.de> <20120420123842.GA25662@avionic-0098.adnet.avionic-design.de> <20120420142558.GB20681@sirena.org.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0301733178771956212==" Return-path: In-Reply-To: <20120420142558.GB20681@sirena.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Mark Brown Cc: kernel@pengutronix.de, Sascha Hauer , Dave Airlie , linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0301733178771956212== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Mark Brown wrote: > On Fri, Apr 20, 2012 at 02:38:43PM +0200, Thierry Reding wrote: > > * Dave Airlie wrote: > > > I get the feeling the drm can just be a virtual platform device of > > > some sort, then it reads the device tree and binds all the information > > > on what crtc/encoders are available, >=20 > > That's pretty much what I've come up with in the second round of Tegra = DRM > > patches. Basically display controllers and outputs (RGB, HDMI, TVO, DSI= ) get > > separate drivers and register themselves with the DRM driver which then= looks > > at the device tree to see which display controllers to register as CRTC= s and > > parses a list of connector nodes to create encoder/connector pairs that > > define the physical connectors and their corresponding outputs. >=20 > > I did take a brief look at the SDRM patches as well and they didn't qui= te > > seem to fit what was needed for Tegra. But if time allows I'll take a c= loser > > look. >=20 > This sounds an awful lot like how ASoC hangs together... What in particular sounds awful? Thierry --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAk+Rd4YACgkQZ+BJyKLjJp9IQwCeM2dNFI/ZYHjfH1dOs78JqORd pFwAoLEJbZWO6gbrwhWNwcTzcxCpadEh =C+O/ -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- --===============0301733178771956212== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============0301733178771956212==--