From: Kalle Valo <kvalo@kernel.org>
To: Hamid Zamani <hzamani.cs91@gmail.com>
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Shawn Guo <shawn.guo@linaro.org>,
Hans de Goede <hdegoede@redhat.com>, Soeren Moch <smoch@web.de>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hamid Zamani <hzamani.cs91@gmail.com>
Subject: Re: [PATCH] brcmfmac: use ISO3166 country code and 0 rev as fallback on brcmfmac43602 chips
Date: Wed, 27 Apr 2022 05:03:47 +0000 (UTC) [thread overview]
Message-ID: <165103582533.18987.15646969582351051016.kvalo@kernel.org> (raw)
In-Reply-To: <20220423111237.60892-1-hzamani.cs91@gmail.com>
Hamid Zamani <hzamani.cs91@gmail.com> wrote:
> This uses ISO3166 country code and 0 rev on brcmfmac43602 chips.
> Without this patch 80 MHz width is not selected on 5 GHz channels.
>
> Commit a21bf90e927f ("brcmfmac: use ISO3166 country code and 0 rev as
> fallback on some devices") provides a way to specify chips for using the
> fallback case.
>
> Before commit 151a7c12c4fc ("Revert "brcmfmac: use ISO3166 country code
> and 0 rev as fallback"") brcmfmac43602 devices works correctly and for
> this specific case 80 MHz width is selected.
>
> Signed-off-by: Hamid Zamani <hzamani.cs91@gmail.com>
Patch applied to wireless-next.git, thanks.
21947f3a74d6 brcmfmac: use ISO3166 country code and 0 rev as fallback on brcmfmac43602 chips
--
https://patchwork.kernel.org/project/linux-wireless/patch/20220423111237.60892-1-hzamani.cs91@gmail.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-04-27 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 11:12 Hamid Zamani
2022-04-27 5:03 ` Kalle Valo [this message]
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=165103582533.18987.15646969582351051016.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=hzamani.cs91@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=smoch@web.de \
/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
all inboxes | Powered by JetHome®