linux-kernel - Re: [PATCH 1/2] dt-bindings: net: bluetooth: nxp: add support for supply and reset

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241028090028.x6rzopvpcdvgouqv@pengutronix.de>
Date: Mon, 28 Oct 2024 10:00:28 +0100
From: Marco Felsch <m.felsch@...gutronix.de>
To: Sherry Sun <sherry.sun@....com>
Cc: POPESCU Catalin <catalin.popescu@...ca-geosystems.com>,
	Amitkumar Karwar <amitkumar.karwar@....com>,
	Neeraj Sanjay Kale <neeraj.sanjaykale@....com>,
	"marcel@...tmann.org" <marcel@...tmann.org>,
	"luiz.dentz@...il.com" <luiz.dentz@...il.com>,
	"robh@...nel.org" <robh@...nel.org>,
	"krzk+dt@...nel.org" <krzk+dt@...nel.org>,
	"conor+dt@...nel.org" <conor+dt@...nel.org>,
	"p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
	"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	GEO-CHHER-bsp-development <bsp-development.geo@...ca-geosystems.com>,
	Krzysztof Kozlowski <krzk@...nel.org>
Subject: Re: [PATCH 1/2] dt-bindings: net: bluetooth: nxp: add support for
 supply and reset

Hi,

On 24-10-28, Sherry Sun wrote:
> 
> > From: POPESCU Catalin <catalin.popescu@...ca-geosystems.com>
> >
> > We use the NXP downstream driver mwifiex which doesn't have support for
> > regulator or PDn.
> >
> > However, regulator is already supported by the MMC core (vmmc-supply).
> >
> > For PDn, we use mmc pwrseq simple driver that has been patched to add
> > support for reset-control.
> 
> Ok, thanks, the mmc change looks good for me, so there is no problem
> with the NXP SDIO wifi.
>
> But how do you plan to handle the NXP PCIe wifi? We also need to make
> sure the BT patch won't break the PCIe wifi function.

Can you please elaborate how this could break the PCIe use-case?

Regards,
  Marco