[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <31ddcb1f-4606-4c5b-893a-179718ed6339@kernel.org>
Date: Tue, 24 Dec 2024 14:27:09 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Janaki Ramaiah Thota <quic_janathot@...cinc.com>
Cc: Marcel Holtmann <marcel@...tmann.org>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>, Rob Herring
<robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Balakrishna Godavarthi <quic_bgodavar@...cinc.com>,
Rocky Liao <quic_rjliao@...cinc.com>, quic_mohamull@...cinc.com,
quic_hbandi@...cinc.com, quic_anubhavg@...cinc.com,
linux-bluetooth@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 1/1] dt-bindings: bluetooth: update the wcn6750
required properties
On 24/12/2024 12:51, Janaki Ramaiah Thota wrote:
>
>
> On 12/24/2024 2:46 PM, Krzysztof Kozlowski wrote:
>> On Mon, Dec 23, 2024 at 07:27:00PM +0530, Janaki Ramaiah Thota wrote:
>>
>> Subject: everything is an update... say something useful, e.g. use PMU
>> abstraction for WCN6750
>>
>
> Sure will correct it in next patch.
>
>>> Drop the inputs from the host and instead expect the Bluetooth node to
>>> consume the outputs of the internal PMU.
>>
>> On which device?
>>
>
> It is for BT module wcn6750 attached on qcs6490-rb3gen2 board.
> will update same on next commit message.
>
>> But anyway I have doubts this is correct. enable GPIO is a pin going
>> from the host, not from PMU.
>>
>
> Yes you are correct, enable GPIO is out pin of host, but here updated
> the entries required for Bluetooth node from PMU, not from host to PMU.
Hm? No, you removed for example enable-gpios, which is input from the
host. Sorry, I don't understand the reason behind this patch and commit
msg does not help me there.
Best regards,
Krzysztof
Powered by blists - more mailing lists