From: Hector Martin <marcan@marcan.st>
To: "Ivan T. Ivanov" <iivanov@suse.de>, aspriel@gmail.com
Cc: franky.lin@broadcom.com, hante.meuleman@broadcom.com,
rmk+kernel@armlinux.org.uk, kvalo@kernel.org,
davem@davemloft.net, devicetree@vger.kernel.org,
edumazet@google.com, krzysztof.kozlowski+dt@linaro.org,
kuba@kernel.org, pabeni@redhat.com, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com
Subject: Re: [PATCH] brcmfmac: of: Use board compatible string for board type
Date: Fri, 6 Jan 2023 18:27:35 +0900 [thread overview]
Message-ID: <fc6d3c3b-1352-4f75-cbef-d29bd74c0e40@marcan.st> (raw)
In-Reply-To: <20230106072746.29516-1-iivanov@suse.de>
On 2023/01/06 16:27, Ivan T. Ivanov wrote:
> 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 <iivanov@suse.de>
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.
Fixes: 7682de8b3351 ("wifi: brcmfmac: of: Fetch Apple properties")
===
An also add a Cc: stable@vger.kernel.org to make sure this gets backported.
With the fixed description,
Reviewed-by: Hector Martin <marcan@marcan.st>
- Hector
next prev parent reply other threads:[~2023-01-06 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 7:27 [PATCH] brcmfmac: of: Use board compatible string for board type Ivan T. Ivanov
2023-01-06 9:27 ` Hector Martin [this message]
2023-01-06 12:13 ` Hector Martin
2023-01-06 12:20 ` Ivan T. Ivanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc6d3c3b-1352-4f75-cbef-d29bd74c0e40@marcan.st \
--to=marcan@marcan.st \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=iivanov@suse.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox