# \[PATCH v2\] dt: bindings: Make compatible optional for mmc function nodes

- From: Rob Herring \<robh@kernel.org\>
- Date: 2016-08-01 16:41:56 
- List: linux-arm-kernel
- Page: https://ratatoskr.run/linux-arm-kernel/2016/08/8126071
- Thread: https://ratatoskr.run/linux-devicetree/2016/07/8126005/t.md

```text
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@arndb.de>
> Cc: Maxime Ripard <redacted>
> Signed-off-by: Hans de Goede <redacted>
> ---
> 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@kernel.org>
```
