On Tue, Aug 29, 2017 at 06:58:23AM -0700, Tony Lindgren wrote: > * Sebastian Reichel <sebastian.reichel@xxxxxxxxxxxxxxx> [170829 04:51]: > > On Tue, Aug 29, 2017 at 04:50:22PM +0530, Kishon Vijay Abraham I wrote: > > > On Thursday 24 August 2017 04:59 PM, Ulf Hansson wrote: > > > > I guess we have two options. > > > > > > > > 1) Allow us to invent and use new bindings - and a new compatible. > > > > When everything is implemented in sdhci-omap, we can deprecate the old > > > > omap_hsmmc driver and its corresponding compatible/bindings. At some > > > > point later we can remove the legacy driver/bindings altogether - of > > > > course that might take a while. This option allows us to re-think some > > > > of the old bindings and really clean up some if its related code. For > > > > example, I think "ti,dual-volt" is a bad binding. Instead it would be > > > > better to use the existing mmc bindings about which speed mode the > > > > controller/board supports (as the voltage level comes with it). > > > > > > > > 2) Invent only a new compatible, but stick to use the old omap hsmmc > > > > bindings and thus also deploy the similar code dealing with them. When > > > > everything is implemented move the old omap_hsmmc compatibles into the > > > > new sdhci-omap driver and them remove the old omap_hsmmc driver. At > > > > that point we could also deprecate the old omap hsmmc compatibles, but > > > > to me that is rather pointless. > > > > > > > > The two options has different advantages, feel free to pick any of them! > > > > > > Okay. I'll send a new version with option '1' (new compatible/new bindings). > > Agreed. > > > > And when we deprecate the omap_hsmmc driver (some time later), we'll add > > > support for the legacy bindings in sdhci-omap driver (so that old dtbs continue > > > to work). Tony, are you okay with this? > > > > I think you should Cc Rob Herring and Mark Rutland (DT binding > > maintainers). This sounds like "I use DT to describe driver > > behaviour" instead of "I use DT to describe hardware". Indeed... > > Yes please. > > > I would expect the conversion to look like the one done for UART, > > see CONFIG_SERIAL_OMAP vs CONFIG_SERIAL_8250_OMAP. Both use the > > same compatible value and you can choose using kernel configuration. > > That does not work unfortunately :( We are now stuck in a situation > where two drivers are attempting to probe with the same compatible > and we can't enable 8250_OMAP because of the user space breakage > with the device names. And I'm actuallly thinking we should add a > new compatible for 8250-omap to be able to start enabling it one > board at a time. Is that the only problem? Presumably, the SD driver doesn't have a userspace facing issue. > It's best to enable devices to use the new compatible as things are > tested rather than hope for some magic "flag day" flip that might > never happen. Having two days attempting to probe with the same > binding just won't work. Aren't you just picking whether the flag day is in DT or the kernel? I guess you're assuming one kernel build and it would be switching all boards at one. > So yeah, I agree with Kishon that we should stick with generic > and sdhci bindings. And then we can start already using it for > boards that can use it, then eventually when we're ready, start > parsing also the legacy bindings and maybe drop the old driver. I assume there are some other common properties you would switch to in the transition? You could make the legacy driver bail from probe based on presence or absence of other properties. Or you could just blacklist converted platforms in the legacy driver. The point is that the problems are solvable in the kernel. But if your really want a new compatible, I don't really care. It's only one device. Rob -- 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
