On Monday 01 September 2014 08:49:18 Lee Jones wrote: > On Fri, 22 Aug 2014, Pankaj Dubey wrote: > > > From: Tomasz Figa <t.figa@xxxxxxxxxxx> > > > > Currently a syscon entity can be only registered directly through a > > platform device that binds to a dedicated driver. However in certain use > > cases it is desirable to make a device used with another driver a syscon > > interface provider. For example, certain SoCs (e.g. Exynos) contain > > system controller blocks which perform various functions such as power > > domain control, CPU power management, low power mode control, but in > > addition contain certain IP integration glue, such as various signal > > masks, coprocessor power control, etc. In such case, there is a need to > > have a dedicated driver for such system controller but also share > > registers with other drivers. The latter is where the syscon interface > > is helpful. > > > > This patch decouples syscon object from syscon driver, so that it can be > > registered from any driver in addition to the original "syscon" platform > > driver. > > > > Signed-off-by: Tomasz Figa <t.figa@xxxxxxxxxxx> > > Signed-off-by: Pankaj Dubey <pankaj.dubey@xxxxxxxxxxx> > > --- > > > > RFC patch [1] was posted by Tomasz Figa. This patch addresses some of > > comments given by Arnd to RFC patch, and further decouples syscon from > > device model. It also gives flexibility of registering with syscon at > > early stage using device_node object. > > It would be helpful if Arnd gave this revision his blessing (Ack). I never saw a reason why we don't take this all the way as discussed a few times: Completely remove the dependency of syscon on having a platform driver for it, and make it possible to just call syscon_regmap_lookup_by_phandle() without having to register it first. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |