From: Arend Van Spriel <aspriel@gmail.com>
To: Jacobe Zang <jacobe.zang@wesion.com>,
kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: nick@khadas.com, arend@broadcom.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: net: wireless: BCM4329 binding: add pci14e4,449d
Date: Tue, 18 Jun 2024 13:09:07 +0200 [thread overview]
Message-ID: <b6b06a15-b7de-4351-ab9e-5234d2b91496@gmail.com> (raw)
In-Reply-To: <20240617024341.3106240-1-jacobe.zang@wesion.com>
On 6/17/2024 4:43 AM, Jacobe Zang wrote:
> It's a Broadcom Wi-Fi module connected via the PCIe interface and also
> add prefix in vendor-prefix.yaml
>
> Link:https://lore.kernel.org/linux-devicetree/20240617023517.3104427-1-jacobe.zang@wesion.com/T/#u
> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> ---
> .../devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml b/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
> index e564f20d8f415..0477566acd72a 100644
> --- a/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
> +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
> @@ -53,6 +53,7 @@ properties:
> - pci14e4,4488 # BCM4377
> - pci14e4,4425 # BCM4378
> - pci14e4,4433 # BCM4387
> + - pci14e4,449d # BCM4329
I can not find that device id. Can you provide more information where
you came across this device. The BCM4329 as I know it is an 802.11n
*SDIO* device. Not a PCI device.
Regards,
Arend
next prev parent reply other threads:[~2024-06-18 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 2:43 Jacobe Zang
2024-06-17 6:18 ` Krzysztof Kozlowski
2024-06-17 6:30 ` Jacobe Zang
2024-06-18 11:09 ` Arend Van Spriel [this message]
2024-06-18 14:47 ` Sebastian Reichel
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=b6b06a15-b7de-4351-ab9e-5234d2b91496@gmail.com \
--to=aspriel@gmail.com \
--cc=arend@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jacobe.zang@wesion.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick@khadas.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®