On 28 August 2014 18:34, jonsmirl@xxxxxxxxx <jonsmirl@xxxxxxxxx> wrote: > On Thu, Aug 28, 2014 at 12:25 PM, Michal Suchanek <hramrach@xxxxxxxxx> wrote: >> On 28 August 2014 16:33, jonsmirl@xxxxxxxxx <jonsmirl@xxxxxxxxx> wrote: >>> On Thu, Aug 28, 2014 at 10:20 AM, Geert Uytterhoeven >>> <geert@xxxxxxxxxxxxxx> wrote: >>>> On Thu, Aug 28, 2014 at 3:22 PM, jonsmirl@xxxxxxxxx <jonsmirl@xxxxxxxxx> wrote: >>>>>> 2) We don't want to hardcode these clocks into the kernel (sunxi) clk >>>>>> driver, instead the bootloader should tell the kernel about these clocks. >>>>>> >>>>>> So the only point of discussion left seems to be how to do 2... >>>>> >>>>> Wouldn't it be a lot simpler just to use existing fbdev (not KMS) and >>>>> whip together a device specific driver that claims the proper >>>>> resources? And just implement the minimal about of fbdev possible? >>>>> fbdev already is a driver library. >>>> >>>> Like... drivers/video/fbdev/offb.c? >>> >>> I'd probably reclassify drivers/video/fbdev/simplefb.c as a skeleton >>> and use it as a template for making device specific versions of it. >>> >>> I don't see why there is so much resistance to just making device >>> specific fb drivers. Whenever the KMS driver gets written just >>> disable the device specific fb driver in the build. >> >> Except that is not the goal here. The simplefb or whatever replacement >> is supposed to stay as a generic driver compiled into kernel whereas > > There is no generic solution to this problem as this entire thread has > illustrated. The clocks/regulators needed by each SOC vary. > > So there are two solutions.. > 1) modify simplefb to have some kind of heuristic that tries to guess > what needs to be protected. A heuristic that is probably going to fail > on every new SOC. You do not need a heuristic when the bootloader that enabled the clocks and regulators can tell you which. And this patch was initially about adding support to simplefb to read from DT where u-boot fills in the clocks that are needed for HDMI output to keep running on sunxi. > > 2) Spend a day implementing a device specific fbdev driver that does > the correct thing all of the time. These drivers would sit in initrd > and load before the clock/regulator clean up shuts everything off. Use > the existing simplefb code as a template for doing this. But then you need to spend a day implementing such driver for every SoC and it will not work before initrd is loaded. In contrast simplefb with resource management support can work on any platform where the bootloader enables framebuffer and then can be compiled into generic kernel and work before even initrd is loaded. Thanks Michal -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
