From: Hector Martin <marcan@marcan.st>
To: Arend Van Spriel <aspriel@gmail.com>, "Ivan T. Ivanov" <iivanov@suse.de>
Cc: franky.lin@broadcom.com, hante.meuleman@broadcom.com,
rmk+kernel@armlinux.org.uk, stefan.wahren@i2se.com,
pbrobinson@gmail.com, jforbes@fedoraproject.org,
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, stable@vger.kernel.org
Subject: Re: [PATCH v2] brcmfmac: Prefer DT board type over DMI board type
Date: Sat, 7 Jan 2023 01:35:31 +0900 [thread overview]
Message-ID: <3cf5c1cd-1cc3-35bb-db65-e7f4a3f00527@marcan.st> (raw)
In-Reply-To: <0b277149-867b-8acf-30d8-2cd68ba24c99@gmail.com>
On 07/01/2023 01.21, Arend Van Spriel wrote:
> On 1/6/2023 2:19 PM, Ivan T. Ivanov wrote:
>> The introduction of support for Apple board types inadvertently changed
>> the precedence order, causing hybrid SMBIOS+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")
>>
>> [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1206697#c13
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Ivan T. Ivanov <iivanov@suse.de>
>
> Looks good to me. I do have a question about the devicetree node for
> brcmfmac. The driver does a compatible check against
> "brcm,bcm4329-fmac". I actually expect all devicetree specifications to
> use this. That said I noticed the check for it in brcmf_of_probe()
> should be moved so it is the first check done.
We're talking about the machine compatible in the root OF node, not the
compatible for the device itself. That's how firmware selection for
non-Apple platforms works (and has worked since before the Apple stuff
got introduced): first try the machine type which is either derived from
DMI info or the root compatible, and fall back to generic firmware.
The device compatible is indeed always brcm,bcm4329-fmac.
- Hector
next prev parent reply other threads:[~2023-01-06 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 13:19 [PATCH v2] brcmfmac: Prefer DT board type over DMI board type Ivan T. Ivanov
2023-01-06 16:21 ` Arend Van Spriel
2023-01-06 16:35 ` Hector Martin [this message]
2023-01-06 17:00 ` Peter Robinson
2023-01-16 11:18 ` Kalle Valo
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=3cf5c1cd-1cc3-35bb-db65-e7f4a3f00527@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=jforbes@fedoraproject.org \
--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=pbrobinson@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefan.wahren@i2se.com \
/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