From: Kalle Valo <kvalo@codeaurora.org>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-mmc@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com,
linux-wireless@vger.kernel.org, ulf.hansson@linaro.org,
arend.vanspriel@broadcom.com, franky.lin@broadcom.com,
hante.meuleman@broadcom.com,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: brcmfmac: add support for BCM43455 with modalias sdio:c00v02D0dA9BF
Date: Fri, 20 Jan 2017 09:48:14 +0000 (UTC) [thread overview]
Message-ID: <20170120094814.E2D30607CD@smtp.codeaurora.org> (raw)
In-Reply-To: <20170116101757.20483-1-martin.blumenstingl@googlemail.com>
Martin Blumenstingl <martin.blumenstingl@googlemail.com> wrote:
> BCM43455 is a more recent revision of the BCM4345. Some of the BCM43455
> got a dedicated SDIO device ID which is currently not supported by
> brcmfmac.
> Adding the new sdio_device_id to brcmfmac is enough to get the BCM43455
> supported because the chip itself is already supported (due to BCM4345
> support in the driver).
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Reviewed-by: Andreas Färber <afaerber@suse.de>
> Tested-by: Andreas Färber <afaerber@suse.de>
Patch applied to wireless-drivers-next.git, thanks.
a62a77881b1b brcmfmac: add support for BCM43455 with modalias sdio:c00v02D0dA9BF
--
https://patchwork.kernel.org/patch/9518447/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-01-20 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 10:17 [PATCH] brcmfmac: add support for BCM43455 with modalias sdio:c00v02D0dA9BF Martin Blumenstingl
2017-01-16 10:50 ` Arend Van Spriel
2017-01-17 0:19 ` Andreas Färber
2017-01-20 9:48 ` Kalle Valo [this message]
2017-01-20 10:29 ` [PATCH] " Ulf Hansson
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=20170120094814.E2D30607CD@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--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).