On Tue, 20 Jan 2015, Nicolas Ferre wrote: > Le 20/01/2015 16:05, Alexandre Belloni a écrit : > > On 20/01/2015 at 09:47:39 +0000, Lee Jones wrote : > >>>> This driver looks pretty pointless. Why can't you request the sysconf > >>>> registers from within the drivers themselves? > >>>> > >>> > >>> How would you probe the watchdog driver then? Would you had the > >>> "atmel,at91rm9200-st" compatible there? > >>> > >>> At some point in time, we should add the reset driver, would you also > >>> match it on "atmel,at91rm9200-st"? > >>> > >>> I'm fine with that as this allows to avoid the mfd driver. > >> > >> I'm sorry, I don't follow. Why can't each driver have their own > >> compatible strings? > >> > > > > The same IP provides a clocksource, a watchdog and is also the reset > > controller. I think that the DT guidelines requires that the DT > > describes the hardware and so use one compatible for that IP; > > I would add also that the registers within the IP are kind of mixed, > there is no way to separate by logical functions. How is that different from any other syscon based device? BTW, did you see "mfd: syscon: fix syscon probing from dt" It may be the solution to your problem. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
