From: Marek Vasut <marex@denx.de>
To: Conor Dooley <conor@kernel.org>
Cc: linux-bluetooth@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Conor Dooley <conor+dt@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding
Date: Tue, 19 Mar 2024 19:07:42 +0100 [thread overview]
Message-ID: <878e72e6-8a75-4593-8080-e3d9b3f7f523@denx.de> (raw)
In-Reply-To: <20240317-spotter-imminent-1a29a152648b@spud>
On 3/17/24 4:03 PM, Conor Dooley wrote:
> On Sat, Mar 09, 2024 at 04:15:12AM +0100, Marek Vasut wrote:
>> CYW43439 is a Wi-Fi + Bluetooth combo device from Infineon.
>> The Bluetooth part is capable of Bluetooth 5.2 BR/EDR/LE .
>> This chip is present e.g. on muRata 1YN module. Extend the
>> binding with its DT compatible.
>
> How come there's no fallback here? Looking at the binding patch there's
> no device-specific handling done, what's incompatibly different between
> this device and some of the other ones supported by the hci_bcm driver?
For posterity, should be addressed in V2.
prev parent reply other threads:[~2024-03-19 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 3:15 [PATCH 1/2] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding Marek Vasut
2024-03-09 3:15 ` [PATCH 2/2] Bluetooth: hci_bcm: Add CYW43439 support Marek Vasut
2024-03-09 11:39 ` [PATCH 1/2] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding Krzysztof Kozlowski
2024-03-17 15:03 ` Conor Dooley
2024-03-19 18:07 ` Marek Vasut [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=878e72e6-8a75-4593-8080-e3d9b3f7f523@denx.de \
--to=marex@denx.de \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--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