On Fri, Feb 21, 2020 at 11:41:47AM -0800, Julius Werner wrote: > > Because the ATF does not define standard wdt index, each vendor defines > > its own index. > > So I don't think that the current driver[0] can fully cover my usecases. > > I think the best way to solve this would be to put the SMC function ID > as another field into the device tree, so that multiple vendors could > share the same driver even if their firmware interface uses a > different SMC. But they still have to implement the same API for that > SMC, of course, not sure if the Meson driver is suitable for that (but > if it is then I think merging those drivers would be a good idea). More common would be to have a single driver and multiple compatible strings. The driver would then pick the SMC function ID from the compatible string. After all, we'd not only need the SMC function ID; parameters are also different. Guenter
