* Pantelis Antoniou <panto@xxxxxxxxxxxxxxxxxxxxxxx> [121030 13:18]:
> On Oct 30, 2012, at 9:39 PM, Tony Lindgren wrote:
>
> > * Pantelis Antoniou <panto@xxxxxxxxxxxxxxxxxxxxxxx> [121030 12:00]:
> >> +
> >> + priv->lcdc_oh = omap_hwmod_lookup("lcdc");
> >> + if (priv->lcdc_oh == NULL) {
> >> + dev_err(&pdev->dev, "Failed to lookup omap_hwmod lcdc\n");
> >> + return -ENODEV;
> >> + }
> >> +
> >> + priv->lcdc_pdev = omap_device_build("da8xx_lcdc", 0, priv->lcdc_oh,
> >> + &priv->lcd_pdata,
> >> + sizeof(struct da8xx_lcdc_platform_data),
> >> + NULL, 0, 0);
> >> + if (priv->lcdc_pdev == NULL) {
> >> + dev_err(&pdev->dev, "Failed to build LCDC device\n");
> >> + return -ENODEV;
> >> + }
> >
> > ..and these kind of things need to become private to
> > arch/arm/mach-omap2, we already have it working for other
> > devices with device tree.
> >
> > Regards,
> >
> > Tony
>
> I see,
>
> I know that if the device driver is DTified it will pick up the hwmod automatically.
> The issue is that the driver is question is not yet; how would I go about
> creating the platform device and having it pick up the hwmod automatically?
Maybe you should make this DT only driver for omap? We already
have am33xx DT only to start with.
If you really need the platform device still, just take a look
at the many platform device creating files under arch/arm/mach-omap2.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
