[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed6aceb6-4954-43ad-b631-6c6fda209411@kernel.org>
Date: Thu, 19 Sep 2024 12:00:53 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Kalle Valo <kvalo@...nel.org>
Cc: Bartosz Golaszewski <brgl@...ev.pl>,
"David S . Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Jeff Johnson <jjohnson@...nel.org>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org, ath11k@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH net-next v2] dt-bindings: net: ath11k: document the inputs
of the ath11k on WCN6855
On 19/09/2024 09:48, Kalle Valo wrote:
> Krzysztof Kozlowski <krzk@...nel.org> writes:
>
>> On 14/08/2024 10:23, Bartosz Golaszewski wrote:
>>> From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>>>
>>> Describe the inputs from the PMU of the ath11k module on WCN6855.
>>>
>>> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>>> ---
>>> v1 -> v2:
>>> - update the example
>>
>> I don't understand why this patch is no being picked up. The code
>> correct represents the piece of hardware. The supplies should be
>> required, because this one particular device - the one described in this
>> binding - cannot work without them.
>
> I have already explained the situation. With supplies changed to
> optional I'm happy take the patch.
You did not provide any relevant argument to this case. Your concerns
described quite different case and are no applicable to DT based platforms.
Best regards,
Krzysztof
Powered by blists - more mailing lists