[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a3ad8a6-90a9-45c5-bbdf-7b91d3c18e51@oss.qualcomm.com>
Date: Fri, 20 Jun 2025 08:27:30 -0700
From: Jeff Johnson <jeff.johnson@....qualcomm.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, Rosen Penev <rosenp@...il.com>,
linux-wireless@...r.kernel.org
Cc: Toke Høiland-Jørgensen <toke@...e.dk>, nbd@....name,
Johannes Berg <johannes@...solutions.net>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:MIPS" <linux-mips@...r.kernel.org>
Subject: Re: [PATCHv5 0/5] wifi: ath9k: add ahb OF support
On 6/19/2025 10:39 PM, Krzysztof Kozlowski wrote:
> On 20/06/2025 07:32, Krzysztof Kozlowski wrote:
>> On 20/06/2025 02:33, Jeff Johnson wrote:
>>> On 6/8/2025 8:08 PM, Rosen Penev wrote:
>>>> First two commits are small cleanups to make the changes of the third
>>>> simpler. The fourth actually adds dts definitions to use ahb.
>>>>
>>>> v2: Add documentation, use kernel_ulong_t, and of_device_get_match_data
>>>> v3: Use qcom prefix and wifi suffix as in other ath drivers.
>>>> v4: fix up dts example in Documentation
>>>> v5: move back to using qca prefix. It makes no sense to diverge between
>>>> all the other drivers for MIPS based qualcomm devices. qcom as a prefix
>>>> is used for Quallcomm's ARM(64) stuff.
>>>>
>>>> Rosen Penev (5):
>>>> wifi: ath9k: ahb: reorder declarations
>>>> wifi: ath9k: ahb: reorder includes
>>>> wifi: ath9k: ahb: replace id_table with of
>>>> dt-bindings: net: wireless: ath9k: add OF bindings
>>>> mips: dts: qca: add wmac support
>>>>
>>>> .../bindings/net/wireless/qca,ath9k.yaml | 23 ++++++-
>>>> arch/mips/boot/dts/qca/ar9132.dtsi | 9 +++
>>>> .../boot/dts/qca/ar9132_tl_wr1043nd_v1.dts | 4 ++
>>>> arch/mips/boot/dts/qca/ar9331.dtsi | 9 +++
>>>> arch/mips/boot/dts/qca/ar9331_dpt_module.dts | 4 ++
>>>> .../mips/boot/dts/qca/ar9331_dragino_ms14.dts | 4 ++
>>>> arch/mips/boot/dts/qca/ar9331_omega.dts | 4 ++
>>>> .../qca/ar9331_openembed_som9331_board.dts | 4 ++
>>>> arch/mips/boot/dts/qca/ar9331_tl_mr3020.dts | 4 ++
>>>> drivers/net/wireless/ath/ath9k/ahb.c | 60 +++++++------------
>>>> 10 files changed, 84 insertions(+), 41 deletions(-)
>>>>
>>>
>>> DT team, should I take this series through my tree?
>>> Toke, Ack?
>> No, of course not. The same as you asked some time ago: DTS never, NEVER
>> goes via driver subsystem tree.
>>
>
> Heh, you do not have any subsystem maintainers acks or reviews on DTS,
> so this should not be considered. It's like me taking wireless patches
> without your acks.
That is why I was looking for clarification.
All the DT stuff had your R-B and hence why I asked Toke for his Ack.
Will DT team take the entire series (I'm ok with that)?
Or just the DTS and I should take the rest?
/jeff
Powered by blists - more mailing lists