Hi Rafał, On Thu, 27 Nov 2014, Rafał Miłecki wrote:
> On 27 November 2014 at 20:56, Paul Walmsley <[email protected]> wrote: > > On Tue, 25 Nov 2014, Rafał Miłecki wrote: > >> I understand your arguments against drivers/soc/, but on the other hand > >> I have no idea where else this driver could go. > > > > After looking around the tree to find out where similar code is located, > > it looks like drivers/firmware is the right place. These days, > > drivers/firmware is mainly used for drivers that parse EFI bootloader > > data, DMI data, that sort of thing. Quite similar to the CFE-provided > > data that the bcm47xx-nvram code deals with. So, by functional analogy, > > drivers/firmware appears to be the right place to stash this device > > data-probing code. > > > >> I guess DT is older than CFE, but Broadcom decided to invent own > >> solution called NVRAM anyway. This is a bit messy, because it actually > >> stores hardware details (CPU, RAM, switch) as well as user settings > >> (e.g. LEDs behavior). I can't say why Broadcom decided to implement it > >> this way. > > > > Yep, based on what the other drivers in drivers/firmware are used for, I > > think drivers/firmware is the right place for the CFE parsing code. > > The problem is I can't find MAINTAINER of the drivers/firmware/. Is > there someone responsible for that? Some mailing list maybe? Who could > give us an ACK to move bcm47xx_nvram there? The list of folks who have committed patches that touch drivers/firmware is large. I did this as a first-order approximation: $ git log --format=fuller drivers/firmware/* | grep Commit: | sort -u Commit: Adrian Bunk <[email protected]> Commit: Adrian Bunk <[email protected]> Commit: Al Viro <[email protected]> Commit: Andi Kleen <[email protected]> Commit: Benjamin Herrenschmidt <[email protected]> Commit: David S. Miller <[email protected]> Commit: David Woodhouse <[email protected]> Commit: Dmitry Torokhov <[email protected]> Commit: Greg Kroah-Hartman <[email protected]> Commit: Greg Kroah-Hartman <[email protected]> Commit: H. Peter Anvin <[email protected]> Commit: H. Peter Anvin <[email protected]> Commit: Ingo Molnar <[email protected]> Commit: Ingo Molnar <[email protected]> Commit: James Bottomley <[email protected]> Commit: James Bottomley <[email protected]> Commit: Jean Delvare <[email protected]> Commit: Jeff Garzik <[email protected]> Commit: Jeff Garzik <[email protected]> Commit: Jesse Barnes <[email protected]> Commit: Jiri Kosina <[email protected]> Commit: Konrad Rzeszutek Wilk <[email protected]> Commit: Konrad Rzeszutek Wilk <[email protected]> Commit: Len Brown <[email protected]> Commit: Linus Torvalds <[email protected]> Commit: Linus Torvalds <[email protected]> Commit: Linus Torvalds <[email protected]> Commit: Linus Torvalds <[email protected]> Commit: Linus Torvalds <[email protected]> Commit: Mark Brown <[email protected]> Commit: Mark M. Hoffman <[email protected]> Commit: Matt Fleming <[email protected]> Commit: Matthew Wilcox <[email protected]> Commit: Paul Gortmaker <[email protected]> Commit: Rafael J. Wysocki <[email protected]> Commit: Russell King <[email protected]> Commit: Tejun Heo <[email protected]> Commit: Theodore Ts'o <[email protected]> Commit: Thomas Gleixner <[email protected]> Commit: Tony Luck <[email protected]> If I were in your shoes, I would suggest either 1. asking Ralf to merge your patches that touch drivers/firmware, since he'll also presumably be merging the parts that touch arch/mips or 2. asking Greg KH to merge those patches And of course it would not hurt to collect some Reviewed-By:s from other folks. (See below...) > >> > It sounds to me like this code is a combination of three > >> > pieces: > >> > > >> > 1. code that autoprobes the size of the "nvram" partition in the Broadcom > >> > platform flash, by reading various locations in the MMIO flash aperture, > >> > configured by some other system entity > >> > >> That's right, on MIPS we simply detect flash type (drivers/ssb & > >> driver/bcma) and using that we init NVRAM passing memory offset where > >> the flash is mapped. > > > > OK. > > > > So (as a side issue), I would suggest that when you move this code out of > > arch/mips, the MIPS-isms in it should be removed, like KSEG1ADDR(), etc., > > and replaced by the standard ioremap()-type approach. After all, Broadcom > > could build CFE for ARM, and then we'd want to use this same code to parse > > the CFE-provided data. > > > > Also I would suggest getting rid of the #ifdefs for the flash type, and > > probing it dynamically instead. The flash setup code under drivers/ssb/ > > and drivers/bcma/ sets up platform_devices for the flash, right? If so > > then it would be best if this code could run after the bus setup code, > > query the Linux device model for the type of platform flash in use, and > > then extract the appropriate address space to probe from that data. > > I'm pretty sure you look at some old version of arch/bcm47xx/nvram.c. > I wouldn't dare to move such a MIPS-focused driver to some common > place ;) > > Please check for the version of nvram.c in Ralf's upstream-sfr tree. I > think you'll like it much more. Hopefully you will even consider it > ready for moving to the drivers/firmware/ or whatever :) OK I will take a look at this, and will either send comments, or will send a Reviewed-By:. Thanks for all of the good discussion on this :-) - Paul
