From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>,
Catalin Popescu <catalin.popescu@leica-geosystems.com>,
Amitkumar Karwar <amitkumar.karwar@nxp.com>,
Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"m.felsch@pengutronix.de" <m.felsch@pengutronix.de>,
"bsp-development.geo@leica-geosystems.com"
<bsp-development.geo@leica-geosystems.com>
Subject: Re: [PATCH 1/2] dt-bindings: net: bluetooth: nxp: add support for supply and reset
Date: Sun, 6 Oct 2024 13:33:00 +0200 [thread overview]
Message-ID: <3fa35cd2-e52c-4873-8a7f-db459b016a97@kernel.org> (raw)
In-Reply-To: <DB9PR04MB8429B4535422D3AE07D8EE79927C2@DB9PR04MB8429.eurprd04.prod.outlook.com>
On 06/10/2024 10:49, Sherry Sun wrote:
>
>
>> -----Original Message-----
>> From: Catalin Popescu <catalin.popescu@leica-geosystems.com>
>> Sent: Friday, October 4, 2024 7:36 PM
>> To: Amitkumar Karwar <amitkumar.karwar@nxp.com>; Neeraj Sanjay Kale
>> <neeraj.sanjaykale@nxp.com>; marcel@holtmann.org;
>> luiz.dentz@gmail.com; robh@kernel.org; krzk+dt@kernel.org;
>> conor+dt@kernel.org; p.zabel@pengutronix.de
>> Cc: linux-bluetooth@vger.kernel.org; devicetree@vger.kernel.org; linux-
>> kernel@vger.kernel.org; m.felsch@pengutronix.de; bsp-
>> development.geo@leica-geosystems.com; Catalin Popescu
>> <catalin.popescu@leica-geosystems.com>
>> Subject: [PATCH 1/2] dt-bindings: net: bluetooth: nxp: add support for supply
>> and reset
>>
>> Add support for chip power supply and chip reset/powerdown.
>>
>> Signed-off-by: Catalin Popescu <catalin.popescu@leica-geosystems.com>
>> ---
>> .../bindings/net/bluetooth/nxp,88w8987-bt.yaml | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987-
>> bt.yaml b/Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987-
>> bt.yaml
>> index 37a65badb448..8520b3812bd2 100644
>> --- a/Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987-
>> bt.yaml
>> +++ b/Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987-
>> bt.yaml
>> @@ -34,6 +34,14 @@ properties:
>> firmware-name:
>> maxItems: 1
>>
>> + vcc-supply:
>> + description:
>> + phandle of the regulator that provides the supply voltage.
>> +
>> + reset-gpios:
>> + description:
>> + Chip powerdown/reset signal (PDn).
>> +
>
> Hi Catalin,
>
> For NXP WIFI/BT chip, WIFI and BT share the one PDn pin, which means that both wifi and BT controller will be powered on and off at the same time.
> Taking the M.2 NXP WIFI/BT module as an example, pin56(W_DISABLE1) is connected to the WIFI/BT chip PDn pin, we has already controlled this pin in the corresponding PCIe/SDIO controller dts nodes.
> It is not clear to me what exactly pins for vcc-supply and reset-gpios you describing here. Can you help understand the corresponding pins on M.2 interface as an example? Thanks.
Please wrap your replies.
It seems you need power sequencing just like Bartosz did for Qualcomm WCN.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-06 11:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 11:35 [PATCH 1/2] dt-bindings: net: bluetooth: nxp: add support for supply and reset Catalin Popescu
2024-10-04 11:35 ` [PATCH 2/2] Bluetooth: btnxpuart: implement powerup sequence Catalin Popescu
2024-10-06 9:04 ` Sherry Sun
2024-10-07 12:45 ` POPESCU Catalin
2024-11-20 4:48 ` Neeraj Sanjay Kale
2024-10-04 15:24 ` [PATCH 1/2] dt-bindings: net: bluetooth: nxp: add support for supply and reset Conor Dooley
2024-10-06 8:49 ` Sherry Sun
2024-10-06 11:33 ` Krzysztof Kozlowski [this message]
2024-10-07 12:58 ` POPESCU Catalin
2024-10-07 14:54 ` Krzysztof Kozlowski
2024-10-21 6:41 ` Marco Felsch
2024-10-21 7:50 ` Krzysztof Kozlowski
2024-10-21 10:25 ` Marco Felsch
2024-10-22 5:11 ` Krzysztof Kozlowski
2024-10-22 7:12 ` Marco Felsch
2024-10-22 7:30 ` Krzysztof Kozlowski
2024-10-22 7:32 ` Krzysztof Kozlowski
2024-10-22 8:13 ` Marco Felsch
2024-10-22 8:23 ` Krzysztof Kozlowski
2024-10-22 5:13 ` Sherry Sun
2024-10-22 7:23 ` Marco Felsch
2024-10-22 8:09 ` Sherry Sun
2024-10-22 8:21 ` POPESCU Catalin
2024-10-22 8:22 ` Marco Felsch
2024-10-22 14:24 ` Sherry Sun
2024-10-22 15:49 ` POPESCU Catalin
2024-10-23 14:16 ` Sherry Sun
2024-10-23 14:38 ` POPESCU Catalin
2024-10-28 4:27 ` Sherry Sun
2024-10-28 9:00 ` Marco Felsch
2024-10-28 9:59 ` Sherry Sun
2024-10-28 11:51 ` Marco Felsch
2024-10-28 13:16 ` Sherry Sun
2024-10-28 15:00 ` Marco Felsch
2024-11-18 22:17 ` Marco Felsch
2024-11-19 10:09 ` Sherry Sun
2024-11-19 12:51 ` Marco Felsch
2024-11-20 3:14 ` ttyRe: " Sherry Sun
2024-11-20 4:44 ` Neeraj Sanjay Kale
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=3fa35cd2-e52c-4873-8a7f-db459b016a97@kernel.org \
--to=krzk@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=bsp-development.geo@leica-geosystems.com \
--cc=catalin.popescu@leica-geosystems.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=m.felsch@pengutronix.de \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sherry.sun@nxp.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 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).