On 24 November 2014 at 11:02, Paul Walmsley <paul@xxxxxxxxx> wrote: > Hi Rafał. > > On Sun, 23 Nov 2014, Rafał Miłecki wrote: > >> After Broadcom switched from MIPS to ARM for their home routers we need >> to have NVRAM driver in some common place (not arch/mips/). > > So this is a driver for a chunk of NVRAM that's embedded in the SoC, > hanging off an I/O bus? > > Is this actually some kind of RAM, or is it flash, or something else? I think you missed my description (help section) in Kconfig file :) As it says, NVRAM is a special partition on flash. >> We were thinking about putting it in bus directory, however there are >> two possible buses for MIPS: drivers/ssb/ and drivers/bcma/. So this >> won't fit there neither. >> This is why I would like to move this driver to the drivers/soc/ > > Can't speak for anyone else, but I personally consider drivers/soc to be > primarily intended for so-called "integration" IP blocks. Those are used > for SoC control functions. > > So low-level NVRAM drivers would probably go somewhere else. Here are > some likely possibilities, where it can live with others of its kind > (assuming it is something similar to RAM): > > 1. the PC "CMOS memory" NVRAM driver appears to be under drivers/char, as > drivers/char/nvram.c. > > 2. there's a generic SRAM driver, drivers/misc/sram.c > > 3. while people have put some of the eFuse code under drivers/soc, in my > opinion, the low-level fuse access code should really go under > drivers/misc/fuse. I don't think NVRAM can be treated as a standard char device. Also, in my V1 I tried moving it to the drivers/misc/, but then drivers/soc/ was suggested as a better place, see Arnd's reply: http://www.linux-mips.org/archives/linux-mips/2014-11/msg00238.html > Looking at arch/mips/bcm47xx/nvram.c: if the low-level NVRAM probe code > were moved elsewhere, the higher-level NVRAM "interpretation" functions > still remain: bcm47xx_nvram_getenv() and bcm47xx_nvram_gpio_pin(). Those > seem to be intended to parse device configuration data, yes? And this > device configuration data is organized this way by platform software > convention -- there's no hardware requirement to store data this way in > the NVRAM, right? This bcm47xx_nvram driver has two ways of reading NVRAM content: 1) Using a standard MTD API to access "nvram" partition. In such case flash driver is a low-level thing if you call it so. 2) Using memory-mapped flash access window. In such case there isn't any extra low-level driver. The "nvram" partition is required by the bootloader (CFE). It contains some important info like CPU clock, RAM configuration, switch ports layout. Then it's used by system drivers (like Ethernet driver bgmac) to get info about some particular hardware parts (like PHY address, MAC, etc.). > So if the answer to the above two questions is "yes," meaning that this > NVRAM is used to store device probing data by software convention, then it > would seem to me that proposing some place like > drivers/devicedata/bcm47xx-nvram is a better bet (where "bcm47xx-nvram" is > just some kind of opaque token). Looking at those two functions, it > doesn't seem like there's really anything MIPS or Broadcom or NVRAM or > even SoC-specific about key-value pair parsing and GPIO device data? Or > am I missing something? > > Actually, considering that bcm47xx_nvram_gpio_pin() isn't even used, can > we just drop it and save the hassle? :-) We need this function to easily find GPIO responsible for "something". For example during switch initialization we need to reset it toggling GPIO. NVRAM contains info which GPIO should be toggled, e.g.: gpio4=robo_reset (robo means roboswitch) bcm47xx_nvram_gpio_pin is needed by out-of-tree "b53" driver that some tried to push upstream, but was rejected because of API. I'll also send a patch to USB host driver soon that will require bcm47xx_nvram_gpio_pin. -- Rafał -- To unsubscribe from this list: send the line "unsubscribe linux-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
