On Tue, Aug 14, 2018 at 04:36:03PM +0200, Alexandre Belloni wrote: > On 13/08/2018 20:18:08+0200, Sam Ravnborg wrote: > > > Would be good to have a plan to phase-out the old atmel_lcdfb fbdev > > > driver when this one addresses some TODO items that make sense. > > Agree on this. > > One approach could be to say that when all in-kernel users of atmel_lcdfb > > are ported, then the old driver could be dropped after a kernel release. > > > > I would drop it only after an LTS release. Much better, agreed. > > > > The mfd suffix seems strange to me. What about "atmel,at91sam9263-lcdc-mfd" > > > => "atmel,at91sam9263-lcd" (or "microchip,at91sam9263-lcdc"). > > The "-mfd" suffix was added to avoid clashing with the current > > compatible string used by the atmel_lcdfb driver. > > > > I susggest we do the following: > > - use the microchip prefix, as this is now owned by microchip > > - and add the driver to a drm/microchip/ directory > > (Then we can only hope that microchip do not change name or > > are purchased by someone else). > > > > The compatible string should remain the same but the drivers have to be > mutually exclusive in Kconfig. OK, will do so in v2. I had planned to keep both in the DT file but then I will just replace one with the other. Sam
