From: Simon Horman <simon.horman@corigine.com>
To: Marek Vasut <marex@denx.de>
Cc: linux-wireless@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Arend van Spriel <aspriel@gmail.com>,
Danny van Heumen <danny@dannyvanheumen.nl>,
Eric Dumazet <edumazet@google.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Jakub Kicinski <kuba@kernel.org>, Kalle Valo <kvalo@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Paul Cercueil <paul@crapouillou.net>,
SHA-cyfmac-dev-list@infineon.com,
Ulf Hansson <ulf.hansson@linaro.org>,
brcm80211-dev-list.pdl@broadcom.com, linux-mmc@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2] wifi: brcmfmac: add Cypress 43439 SDIO ids
Date: Sat, 8 Apr 2023 21:44:35 +0200 [thread overview]
Message-ID: <ZDHEI7tbjLJiRcBr@corigine.com> (raw)
In-Reply-To: <509e4308-9164-4131-4b93-75c42568d1e4@denx.de>
On Sat, Apr 08, 2023 at 06:44:40PM +0200, Marek Vasut wrote:
> On 4/8/23 17:24, Simon Horman wrote:
> > On Fri, Apr 07, 2023 at 10:37:52PM +0200, Marek Vasut wrote:
> > > Add SDIO ids for use with the muRata 1YN (Cypress CYW43439).
> > > The odd thing about this is that the previous 1YN populated
> > > on M.2 card for evaluation purposes had BRCM SDIO vendor ID,
> > > while the chip populated on real hardware has a Cypress one.
> > > The device ID also differs between the two devices. But they
> > > are both 43439 otherwise, so add the IDs for both.
> > >
> > > On-device 1YN (43439), the new one, chip label reads "1YN":
> > > ```
> > > /sys/.../mmc_host/mmc2/mmc2:0001 # cat vendor device
> > > 0x04b4
> > > 0xbd3d
> > > ```
> > >
> > > EA M.2 evaluation board 1YN (43439), the old one, chip label reads "1YN ES1.4":
> > > ```
> > > /sys/.../mmc_host/mmc0/mmc0:0001/# cat vendor device
> > > 0x02d0
> > > 0xa9a6
> > > ```
> > >
> > > Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> > > Fixes: be376df724aa3 ("wifi: brcmfmac: add 43439 SDIO ids and initialization")
> > > Signed-off-by: Marek Vasut <marex@denx.de>
> >
> > Reviewed-by: Simon Horman <simon.horman@corigine.com>
> >
> >
> > > ---
> > > NOTE: Please drop the Fixes tag if this is considered unjustified
> >
> > <2c>
> > Feels more like enablement than a fix to me.
> > </2c>
>
> I added it because
>
> Documentation/process/stable-kernel-rules.rst
>
> L24 - New device IDs and quirks are also accepted.
Thanks. If I was aware of that, I had forgotten.
> So, really, up to the maintainer whether they are fine with it being
> backported to stable releases or not. I don't really mind either way.
Yes, I completely agree.
next prev parent reply other threads:[~2023-04-08 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 20:37 [PATCH v2] wifi: brcmfmac: add Cypress 43439 SDIO ids Marek Vasut
2023-04-08 15:24 ` Simon Horman
2023-04-08 16:44 ` Marek Vasut
2023-04-08 19:44 ` Simon Horman [this message]
2023-04-12 7:50 ` Kalle Valo
2023-04-12 18:01 ` Marek Vasut
2023-04-14 12:31 ` [v2] " 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=ZDHEI7tbjLJiRcBr@corigine.com \
--to=simon.horman@corigine.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=danny@dannyvanheumen.nl \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@crapouillou.net \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).