* Paul Walmsley <p...@pwsan.com> [120523 17:55]: > On Tue, 22 May 2012, Tony Lindgren wrote: > > > > Unfortunately for many of the older boards these values will probably > > remain unknown. > > > > So the better approach here is to just disable frequency scaling > > for these cases. Otherwise we'll be breaking old boards with smsc911x > > where the timings for the FPGA controlling smsc911x are unknown. > > > > If we somehow manage to get those values without breaking support for > > these boards, then yes I agree we should deprecate hardcoded and > > bootloader values. > > I was thinking that if we log the register values supplied by the > bootloader to the console, then someone can write a patch to the board > file or DT data to set those register values explicitly in the kernel, > once they're known. Or at least just report them to the l-o list. > > So then that should reduce the problem cases down to boards which no one > reports the data to the mailing list within a few mainline kernel releases > -- i.e., boards which are unmaintained. For those boards, I'd suggest > that we just drop GPMC support until someone shows up who has a board and > can test-boot it. Or just drop the board completely ;-)
OK seems fair to me. It still allows us to boot the older boards with minimal changes (but without L3 frequency scaling). Sounds like those registers should be dumped only if no configuration is specified to avoid spamming the console. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
