* Belisko Marek <marek.belisko@xxxxxxxxx> [131210 14:13]: > On Tue, Nov 12, 2013 at 12:31 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > It would be best to set it up as omap-ctrl.c driver under drivers > > somewhere with few functions exported for DSS and MMC drivers. > > I create small dummy driver based on phy-omap-control which can be > used but before sending patch (with more updates) I would like to get > some feedback if my direction is correct. Cool thanks. Yeah what you have can easily be combined with the patches Balaji has posted to make HSMMC use drivers/mfd/syscon.c via regmap for the SCM register access. Maybe take a look at the work in progress patches in thread: [PATCH v4 0/7] mmc: omap_hsmmc: pbias dt and cleanup And also see my comments regarding using the SCM GENERAL register area as base for the syscon.c driver. That should work for your driver too, right? And then you can access the SYSCON1 register that way from your consumer driver ;) 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
