From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
<linux-wireless@vger.kernel.org>,
Brett Rudley <brudley@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Hante Meuleman <meuleman@broadcom.com>,
<brcm80211-dev-list@broadcom.com>
Subject: Re: [PATCH] brcmfmac: support NVRAMs containing pci devpaths (instead of pcie)
Date: Mon, 1 Jun 2015 13:59:10 +0200 [thread overview]
Message-ID: <556C490E.90509@broadcom.com> (raw)
In-Reply-To: <1432815561-6639-1-git-send-email-zajec5@gmail.com>
On 05/28/15 14:19, Rafał Miłecki wrote:
> Recently Broadcom added support for NVRAMs with entries for multiple
> PCIe devices. One of the supported formats is based on prefixes defined
> like: devpath0=pcie/1/4/ and entries like 0:foo=bar 0:baz=qux etc.
>
> Unfortunately there are also a bit older devices using different way of
> defining prefixes, e.g. SmartRG SR400ac (2 x BCM43602) with entries:
> devpath0=pci/1/1/
> devpath1=pci/2/1
> Broadcom stated this old format will never be used/supported by brcmfmac
> but given the simplicity of this patch I'll insist on supporting it.
Well, if you insist :-p
Acked-by: Arend van Spriel <arend@broadcom.com>
> Signed-off-by: Rafał Miłecki<zajec5@gmail.com>
> ---
> drivers/net/wireless/brcm80211/brcmfmac/firmware.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/brcm80211/brcmfmac/firmware.c b/drivers/net/wireless/brcm80211/brcmfmac/firmware.c
> index b72df87..743f16b 100644
> --- a/drivers/net/wireless/brcm80211/brcmfmac/firmware.c
> +++ b/drivers/net/wireless/brcm80211/brcmfmac/firmware.c
> @@ -232,6 +232,8 @@ static void brcmf_fw_strip_multi_v1(struct nvram_parser *nvp, u16 domain_nr,
> u16 bus_nr)
> {
> /* Device path with a leading '=' key-value separator */
> + char pci_path[] = "=pci/?/?";
> + size_t pci_len;
> char pcie_path[] = "=pcie/?/?";
> size_t pcie_len;
>
> @@ -251,6 +253,9 @@ static void brcmf_fw_strip_multi_v1(struct nvram_parser *nvp, u16 domain_nr,
> /* First search for the devpathX and see if it is the configuration
> * for domain_nr/bus_nr. Search complete nvp
> */
> + snprintf(pci_path, sizeof(pci_path), "=pci/%d/%d", domain_nr,
> + bus_nr);
> + pci_len = strlen(pci_path);
> snprintf(pcie_path, sizeof(pcie_path), "=pcie/%d/%d", domain_nr,
> bus_nr);
> pcie_len = strlen(pcie_path);
> @@ -260,8 +265,9 @@ static void brcmf_fw_strip_multi_v1(struct nvram_parser *nvp, u16 domain_nr,
> /* Format: devpathX=pcie/Y/Z/
> * Y = domain_nr, Z = bus_nr, X = virtual ID
> */
> - if ((strncmp(&nvp->nvram[i], "devpath", 7) == 0)&&
> - (strncmp(&nvp->nvram[i + 8], pcie_path, pcie_len) == 0)) {
> + if (strncmp(&nvp->nvram[i], "devpath", 7) == 0&&
> + (!strncmp(&nvp->nvram[i + 8], pci_path, pci_len) ||
> + !strncmp(&nvp->nvram[i + 8], pcie_path, pcie_len))) {
> id = nvp->nvram[i + 7] - '0';
> found = true;
> break;
next prev parent reply other threads:[~2015-06-01 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 12:19 [PATCH] brcmfmac: support NVRAMs containing pci devpaths (instead of pcie) Rafał Miłecki
2015-06-01 11:59 ` Arend van Spriel [this message]
2015-06-01 12:32 ` Rafał Miłecki
2015-06-08 11:26 ` 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=556C490E.90509@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.