brcmfmac: of: Use board compatible string for board type
PATCH 1/1 brcmfmac: of: Use board compatible string for board type
When "brcm,board-type" is not explicitly set in devicetree fallback to board compatible string for board type.
Some of the existing devices rely on the most compatible device string to find best firmware files, including Raspberry PI's[1].
[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1206697#c13
--- drivers/net/wireless/broadcom/brcm80211/brcmfmac/of.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/net/wireless/broadcom/brcm80211/brcmfmac/of.c +3 -2
@@ -79,7 +79,8 @@ void brcmf_of_probe(struct device *dev, enum brcmf_bus_type bus_type,/* Apple ARM64 platforms have their own idea of board type, passed in * via the device tree. They also have an antenna SKU parameter */ -if (!of_property_read_string (np,"brcm,board-type" , &prop)) + err =of_property_read_string (np,"brcm,board-type" , &prop); +if (!err) settings->board_type = prop;if (!of_property_read_string (np,"apple,antenna-sku" , &prop))
@@ -87,7 +88,7 @@ void brcmf_of_probe(struct device *dev, enum brcmf_bus_type bus_type,/* Set board-type to the first string of the machine compatible prop */ root =of_find_node_by_path ("/" ); -if (root && !settings->board_type) { +if (root && err) {char *board_type;const char *tmp;
Signature · 1 line
2.35.3
Quoted 11 lines · Ivan T. Ivanov
When "brcm,board-type" is not explicitly set in devicetree fallback to board compatible string for board type.
Some of the existing devices rely on the most compatible device string to find best firmware files, including Raspberry PI's[1].
Fixes 7682de8b3351 ("wifi: brcmfmac: of: Fetch Apple properties")[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1206697#c13
Signed-off-by Ivan T. Ivanov <[email protected]>
The existing code already falls back to the compatible string, *as long as there is no board_type set already*.
As far as I can tell, the only way the board_type can get another value first is if it comes from DMI. This behavior was inadvertently changed by commit 7682de8b3351 (since I was not expecting platforms to have *both* DT and DMI information).
I'm guessing the Raspberry Pi is one such platform, and /sys/devices/virtual/dmi exists? Hybrid UEFI+ACPI+DT platform I take it?
If so, your commit description should probably be something like:
===
brcmfmac: Prefer DT board type over DMI board type
The introduction of support for Apple board types inadvertently changed the precedence order, causing hybrid ACPI+DT platforms to look up the firmware using the DMI information instead of the device tree compatible to generate the board type. Revert back to the old behavior, as affected platforms use firmwares named after the DT compatible.
===
An also add a Cc: [email protected] to make sure this gets backported.
With the fixed description,
- Hector
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 38 lines · Hector Martin
Quoted 11 lines · Ivan T. Ivanov
When "brcm,board-type" is not explicitly set in devicetree fallback to board compatible string for board type.
Some of the existing devices rely on the most compatible device string to find best firmware files, including Raspberry PI's[1].
Fixes 7682de8b3351 ("wifi: brcmfmac: of: Fetch Apple properties")[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1206697#c13
Signed-off-by Ivan T. Ivanov <[email protected]>The existing code already falls back to the compatible string, *as long as there is no
board_typeset already*.As far as I can tell, the only way the
board_typecan get another value first is if it comes from DMI. This behavior was inadvertently changed by commit7682de8b3351(since I was not expecting platforms to have *both* DT and DMI information).I'm guessing the Raspberry Pi is one such platform, and
/sys/devices/virtual/dmiexists? Hybrid UEFI+ACPI+DT platform I take it?If so, your commit description should probably be something like:
===
brcmfmac: Prefer DT board type over DMI board typeThe introduction of support for Apple board types inadvertently changed the precedence order, causing hybrid ACPI+DT platforms to look up the firmware using the DMI information instead of the device tree compatible to generate the board type. Revert back to the old behavior, as affected platforms use firmwares named after the DT compatible.
Fixes 7682de8b3351 ("wifi: brcmfmac: of: Fetch Apple properties")===
Quoted 7 lines
An also add a Cc: [email protected] to make sure this gets backported.
With the fixed description,
Reviewed-by Hector Martin <[email protected]>- Hector
Looking into this a bit more from what was mentioned in the linked bug, the DMI data comes from the SMBIOS table. We don't have that on Apple platforms even though we also boot via U-Boot+EFI, but I'm guessing you build U-Boot with CONFIG_GENERATE_SMBIOS_TABLE and provide that stuff in the DT? So s/ACPI/SMBIOS/ would be more accurate in the commit message.
- Hector
Quoted 46 lines · Hector Martin
Quoted 44 lines · Hector Martin
Quoted 11 lines · Ivan T. Ivanov
When "brcm,board-type" is not explicitly set in devicetree fallback to board compatible string for board type.
Some of the existing devices rely on the most compatible device string to find best firmware files, including Raspberry PI's[1].
Fixes 7682de8b3351 ("wifi: brcmfmac: of: Fetch Apple properties")[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1206697#c13
Signed-off-by Ivan T. Ivanov <[email protected]>The existing code already falls back to the compatible string, *as long as there is no
board_typeset already*.As far as I can tell, the only way the
board_typecan get another value first is if it comes from DMI. This behavior was inadvertently changed by commit7682de8b3351(since I was not expecting platforms to have *both* DT and DMI information).I'm guessing the Raspberry Pi is one such platform, and
/sys/devices/virtual/dmiexists? Hybrid UEFI+ACPI+DT platform I take it?If so, your commit description should probably be something like:
===
brcmfmac: Prefer DT board type over DMI board typeThe introduction of support for Apple board types inadvertently changed the precedence order, causing hybrid ACPI+DT platforms to look up the firmware using the DMI information instead of the device tree compatible to generate the board type. Revert back to the old behavior, as affected platforms use firmwares named after the DT compatible.
Fixes 7682de8b3351 ("wifi: brcmfmac: of: Fetch Apple properties")===
An also add a Cc: [email protected] to make sure this gets backported.
With the fixed description,
Reviewed-by Hector Martin <[email protected]>
Quoted 7 lines
Quoted 1 line
- Hector
Looking into this a bit more from what was mentioned in the linked bug, the DMI data comes from the SMBIOS table. We don't have that on Apple platforms even though we also boot via U-Boot+EFI, but I'm guessing you build U-Boot with
CONFIG_GENERATE_SMBIOS_TABLEand provide that stuff in the DT?
Yes, that is the way in openSUSE case.
Quoted 1 line
So s/ACPI/SMBIOS/ would be more accurate in the commit message.
Sure, I will rewrite commit message and repost.
Thanks!