On 06/10/2024 13:33, Krzysztof Kozlowski wrote: > [Some people who received this message don't often get email from krzk@xxxxxxxxxx. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] > > This email is not from Hexagon’s Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email. > > > On 06/10/2024 10:49, Sherry Sun wrote: >> >>> -----Original Message----- >>> From: Catalin Popescu <catalin.popescu@xxxxxxxxxxxxxxxxxxxx> >>> Sent: Friday, October 4, 2024 7:36 PM >>> To: Amitkumar Karwar <amitkumar.karwar@xxxxxxx>; Neeraj Sanjay Kale >>> <neeraj.sanjaykale@xxxxxxx>; marcel@xxxxxxxxxxxx; >>> luiz.dentz@xxxxxxxxx; robh@xxxxxxxxxx; krzk+dt@xxxxxxxxxx; >>> conor+dt@xxxxxxxxxx; p.zabel@xxxxxxxxxxxxxx >>> Cc: linux-bluetooth@xxxxxxxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx; linux- >>> kernel@xxxxxxxxxxxxxxx; m.felsch@xxxxxxxxxxxxxx; bsp- >>> development.geo@xxxxxxxxxxxxxxxxxxxx; Catalin Popescu >>> <catalin.popescu@xxxxxxxxxxxxxxxxxxxx> >>> 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@xxxxxxxxxxxxxxxxxxxx> >>> --- >>> .../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. Hi Sherry, Regulators and reset controls being refcounted, we can then implement powerup sequence in both bluetooth/wlan drivers and have the drivers operate independently. This way bluetooth driver would has no dependance on the wlan driver for : - its power supply - its reset pin (PDn) - its firmware (being downloaded as part of the combo firmware) For the wlan driver we use mmc power sequence to drive the chip reset pin and there's another patchset that adds support for reset control into the mmc pwrseq simple driver. > Please wrap your replies. > > It seems you need power sequencing just like Bartosz did for Qualcomm WCN. Hi Krzysztof, I'm not familiar with power sequencing, but looks like way more complicated than reset controls. So, why power sequencing is recommended here ? Is it b/c a supply is involved ? > > Best regards, > Krzysztof >
