On Sat, Jul 30, 2016 at 05:03:50PM +0200, Hans de Goede wrote: > On some boards (android tablets) different batches use different sdio > wifi modules. This is not a problem since mmc/sdio is an enumerable bus, > so we only need to describe and activate the mmc controller in dt and > then the kernel will automatically load the right driver. > > Sometimes it is useful to specify certain ethernet properties for these > "unknown" sdio devices, specifically we want the boot-loader to be able > to set "local-mac-address" as some of these sdio wifi modules come without > an eeprom / without a factory programmed mac address. > > Since the exact device is unknown (differs per batch) we cannot use > a wifi-chip specific compatible, thus sometimes it is desirable to have a > mmc function node, without having to make up an otherwise unused compatible > for the node, so make the compatible property optional. > > Cc: Arnd Bergmann <arnd@xxxxxxxx> > Cc: Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx> > Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx> > --- > Changes in v2: > -Change the commit-msg to explain why it sometimes is desirable to have a > mmc function node without a compatible > --- > Documentation/devicetree/bindings/mmc/mmc.txt | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) Acked-by: Rob Herring <robh@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
