On Mon, 27 Mar 2017 18:11:15 +0200 Christian Lamparter <chunk...@googlemail.com> wrote:
> On Monday, March 13, 2017 10:05:09 PM CEST Alban wrote: > > The current binding only cover PCI devices so extend it for SoC devices. > > > > Most SoC platforms use an MTD partition for the calibration data > > instead of an EEPROM. The qca,no-eeprom property was added to allow > > loading the EEPROM content using firmware loading. This new binding > > replace this hack with NVMEM cells, so we also mark the qca,no-eeprom > > property as deprecated in case anyone ever used it. > > Please don't mark "qca,no-eeprom" as deprecated then. > If some devices geniously need to rely on userspace for extracting > and processing the calibration data, it should be stay a > optional properties. Deprecated just mean that it shouldn't be used for new devices. But as it is not used by any board, misuse the firmware loading API and firmware loader user helper are deprecated in udev, I find we could also just drop it. > For example: A device that can't do easily without "qca,no-eeprom" is > the AVM FRITZ!WLAN Repeater 300E. For this device, the caldata > is stored in the flash, however for whatever reason the vendor > choose to "reverse" it. (like completely back to front, not byteswapped > or something). So an extra "unreversing step" is required. So, it would > require some sort of a special nvmem-provider-processor as an > alternative. Or just handle this special eeprom format in the ath9k driver. I doubt that this case is so common that it would justify adding a whole new layer to nvmem. > > Signed-off-by: Alban <al...@free.fr> > > --- > > diff --git a/Documentation/devicetree/bindings/net/wireless/qca,ath9k.txt > > b/Documentation/devicetree/bindings/net/wireless/qca,ath9k.txt > > index b7396c8..61f5f6d 100644 > > --- a/Documentation/devicetree/bindings/net/wireless/qca,ath9k.txt > > +++ b/Documentation/devicetree/bindings/net/wireless/qca,ath9k.txt > > @@ -27,16 +27,34 @@ Required properties: > > - 0034 for AR9462 > > - 0036 for AR9565 > > - 0037 for AR9485 > > + For SoC devices the compatible should be "qca,<soctype>-wmac" > > + and one of the following fallbacks: > > + - "qca,ar9100-wmac" > > + - "qca,ar9330-wmac" > > + - "qca,ar9340-wmac" > > + - "qca,qca9550-wmac" > > + - "qca,qca9530-wmac" > > - reg: Address and length of the register set for the device. > > > > +Required properties for SoC devices: > > +- interrupt-parent: phandle of the parent interrupt controller. > > +- interrupts: Interrupt specifier for the controllers interrupt. > > + > > Optional properties: > > +- mac-address: See ethernet.txt in the parent directory > > +- local-mac-address: See ethernet.txt in the parent directory > > +- clock-names: has to be "ref" > > +- clocks: phandle of the reference clock > > +- resets: phandle of the reset line > > +- nvmem-cell-names: has to be "eeprom" and/or "address" > > +- nvmem-cells: phandle to the eeprom nvmem cell and/or to the mac address > > + nvmem cell. > > + > > +Deprecated properties: > > - qca,no-eeprom: Indicates that there is no physical EEPROM > > connected to the ath9k wireless chip (in this case the calibration / > > EEPROM data will be loaded from userspace > > using the kernel firmware loader). > > -- mac-address: See ethernet.txt in the parent directory > > -- local-mac-address: See ethernet.txt in the parent directory > > - > It sounds like you want to deprecate mac-address and > local-mac-address as well. If so you sould add this to the commit as > well. From my point of view, people mostly flat-out patched the > eeprom-image if they wanted to set the mac-address. However, this was > an extra step, if nvmem does away with it, I'm completely fine with > deprecating these properties. The produced diff is very misleading because the mac-address properties get lumped with the other new optional properties. But if you look closely it just move qca,no-eeprom to the deprecated section. Alban
pgp0BJ7VscCj1.pgp
Description: OpenPGP digital signature
