On 24/09/15 19:06, Luis de Bethencourt wrote:
> 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?
Ah, sorry, I misread. Yes, I think there
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. T
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 wor
On Thu, Sep 24, 2015 at 01:41:56PM +0300, Tomi Valkeinen wrote:
>
> On 17/09/15 17:21, Luis de Bethencourt wrote:
> > This platform driver has a OF device ID table but the OF module
> > alias information is not created so module autoloading won't work.
> >
> > Signed-off-by: Luis de Bethencourt
On 17/09/15 17:21, Luis de Bethencourt wrote:
> This platform driver has a OF device ID table but the OF module
> alias information is not created so module autoloading won't work.
>
> Signed-off-by: Luis de Bethencourt
> ---
> drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 1 +
> 1 file changed, 1
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
Signed-off-by: Luis de Bethencourt
---
drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/omapdrm/omap_dmm_
