Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1232223

Re: [PATCH 3/5] drm: omapdrm: tiler: Fix module autoload for OF platform driver

From Luis de Bethencourt <luis@debethencourt.com>
Newsgroups linux.kernel
Subject Re: [PATCH 3/5] drm: omapdrm: tiler: Fix module autoload for OF platform driver
Date 2015-09-24 18:10 +0200
Message-ID <qchfP-7YI-3@gated-at.bofh.it> (permalink)
References <q9Ime-6cb-29@gated-at.bofh.it> <qccg9-Bw-1@gated-at.bofh.it> <qcgMP-7bv-45@gated-at.bofh.it> <qcgWv-7mP-29@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Sep 24, 2015 at 06:43:33PM +0300, Tomi Valkeinen wrote:
> 
> On 24/09/15 18:36, Luis de Bethencourt wrote:
> 
> > I am a bit confused.
> 
> Yes, it's an interesting mess due to legacy reasons. Maybe we manage to
> fix it some day...
> 
> > So how the OMAP DRM auto loading is supposed to work when using Device Trees?
> 
> omapdrm isn't a real HW device driver at the moment. There's another
> driver, omapdss, which is the HW driver, and omapdrm uses omapdss.
> omapdrm platform device is created by omap platform code at boot time,
> the same way for both DT and non-DT boots.
> 
> > As far as I can tell, the main omap drm driver does not have a OF device ID
> > table and a .of_match it only has a MODULE_ALIAS("platform:" DRIVER_NAME),
> > but the tiler driver (that is built-in the omap drm driver) does have a a
> > OF device ID table and I see in DTS that are device nodes using those compatible
> > strings
> > 
> > $ git grep omap4-dmm arch/arm/boot/dts/omap*
> > arch/arm/boot/dts/omap4.dtsi:                   compatible = "ti,omap4-dmm";
> > 
> > Does that mean there is no need for MODULE_ALIAS("platform:" DMM_DRIVER_NAME)?
> 
> No, I think that's the thing that makes omapdrm load.
> 
>  Tomi
> 

Makes sense. Thank you for the explanation.

I didn't know that a omapdrm platform device was registered explictly by platform
code.

Please notice that I wrote MODULE_ALIAS("platform:" DMM_DRIVER_NAME) not
MODULE_ALIAS("platform:" DRIVER_NAME)
In other words, I meant if alias: platform:dmm is needed besides alias:
platform:omapdrm?

Thanks,
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH 3/5] drm: omapdrm: tiler: Fix module autoload for OF  platform driver Tomi Valkeinen <tomi.valkeinen@ti.com> - 2015-09-24 12:50 +0200
  Re: [PATCH 3/5] drm: omapdrm: tiler: Fix module autoload for OF  platform driver Luis de Bethencourt <luis@debethencourt.com> - 2015-09-24 17:40 +0200
    Re: [PATCH 3/5] drm: omapdrm: tiler: Fix module autoload for OF  platform driver Tomi Valkeinen <tomi.valkeinen@ti.com> - 2015-09-24 17:50 +0200
      Re: [PATCH 3/5] drm: omapdrm: tiler: Fix module autoload for OF  platform driver Luis de Bethencourt <luis@debethencourt.com> - 2015-09-24 18:10 +0200
        Re: [PATCH 3/5] drm: omapdrm: tiler: Fix module autoload for OF  platform driver Tomi Valkeinen <tomi.valkeinen@ti.com> - 2015-09-24 18:20 +0200

csiph-web