public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jeff Johnson <jjohnson@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 00/13] wifi: ath12k: add Ath12k AHB driver support for IPQ5332
Date: Tue, 28 Jan 2025 10:20:13 +0100	[thread overview]
Message-ID: <1df7ff9d-d63a-44f5-a67d-8f20973c7b57@kernel.org> (raw)
In-Reply-To: <af926bd7-730c-4465-a206-4168bb93d01a@quicinc.com>

On 28/01/2025 10:16, Raj Kumar Bhagat wrote:
> On 12/10/2024 8:42 PM, Krzysztof Kozlowski wrote:
>> On 10/12/2024 16:08, Krzysztof Kozlowski wrote:
>>> On 10/12/2024 08:41, Raj Kumar Bhagat wrote:
>>>> Currently, Ath12k driver only supports WiFi devices that are based on
>>>> PCI bus. New Ath12k device IPQ5332 is based on AHB bus. Hence, add
>>>> Ath12k AHB support for IPQ5332.
>>>>
>>>> IPQ5332 is IEEE802.11be 2 GHz 2x2 Wifi device. To bring-up IPQ5332
>>>> device:
>>>> - Add hardware parameters for IPQ5332.
>>>> - CE register address space in IPQ5332 is separate from WCSS register
>>>>   space. Hence, add logic to remap CE register address.
>>>> - Add support for fixed QMI firmware memory for IPQ5332.
>>>> - Support userPD handling for WCSS secure PIL driver to enable ath12k
>>>>   AHB support.
>>>>
>>>> v4:
>>>> - Missed to include some review list in v3. Hence sending v4 with
>>>>   all review list as per - scripts/get_maintainers.pl
>>>>
>>> The amount of undocumented ABI you add here, points to the problem that
>>> either your drivers don't work or your drivers would never work with
>>> upstream. Why? Because either you would have wrong DTS or drivers not
>>> matching DTS, thus not working.
>>>
>>> Please point us to your upstream DTS implementing (and working 100%)
>>> this ABI, so we can review that you do not sneak more broken or
>>> undocumented things. I will NAK also future submissions without above,
>>> because I believe you usptream something which will not work.
>>
>>
>> I dug a bit and I found your earlier v2:
>> https://lore.kernel.org/all/20241015182637.955753-3-quic_rajkbhag@quicinc.com/
>>
>> which confirms:
>> 1. DTS not following coding style, so not possible to accept
>> 2. Driver relying on that exact DTS, so not really working.
>>
>> Please post in separate series updated DTS, after fixing all the issues
>> pointed out by DTS coding style.
>>
> 
> To fix all the issues in DTS (including undocumented ABIs) we did changes in
> dt-binding as well.
> 
> The dt-binding and working DTS are now posted as separate series -
> https://lore.kernel.org/lkml/20250128091012.2574478-1-quic_rajkbhag@quicinc.com/


You replied 1.5 months after, so entire context is gone. Anyway, your
DTS does not work.

Best regards,
Krzysztof

      reply	other threads:[~2025-01-28  9:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10  7:41 [PATCH v4 00/13] wifi: ath12k: add Ath12k AHB driver support for IPQ5332 Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 01/13] dt-bindings: net: wireless: describe the ath12k AHB module Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 02/13] wifi: ath12k: fix incorrect CE addresses Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 03/13] wifi: ath12k: refactor ath12k_hw_regs structure Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 04/13] wifi: ath12k: add ath12k_hw_params for IPQ5332 Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 05/13] wifi: ath12k: avoid m3 firmware download in AHB device IPQ5332 Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 06/13] wifi: ath12k: Add hw_params to remap CE register space for IPQ5332 Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 07/13] wifi: ath12k: add support for fixed QMI firmware memory Raj Kumar Bhagat
2024-12-10 14:43   ` Krzysztof Kozlowski
2024-12-10 17:00     ` Raj Kumar Bhagat
2024-12-11  8:52       ` Krzysztof Kozlowski
2024-12-10  7:41 ` [PATCH v4 08/13] wifi: ath12k: add AHB driver support for IPQ5332 Raj Kumar Bhagat
2024-12-10 14:47   ` Krzysztof Kozlowski
2025-01-29 18:28     ` Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 09/13] wifi: ath12k: Power up root PD Raj Kumar Bhagat
2024-12-10 14:50   ` Krzysztof Kozlowski
2025-01-29 18:32     ` Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 10/13] wifi: ath12k: Register various userPD interrupts and save SMEM entries Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 11/13] wifi: ath12k: Power up userPD Raj Kumar Bhagat
2024-12-10 14:52   ` Krzysztof Kozlowski
2025-01-29 18:34     ` Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 12/13] wifi: ath12k: Power down userPD Raj Kumar Bhagat
2024-12-10  7:41 ` [PATCH v4 13/13] wifi: ath12k: enable ath12k AHB support Raj Kumar Bhagat
2024-12-10 15:08 ` [PATCH v4 00/13] wifi: ath12k: add Ath12k AHB driver support for IPQ5332 Krzysztof Kozlowski
2024-12-10 15:12   ` Krzysztof Kozlowski
2025-01-28  9:16     ` Raj Kumar Bhagat
2025-01-28  9:20       ` Krzysztof Kozlowski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1df7ff9d-d63a-44f5-a67d-8f20973c7b57@kernel.org \
    --to=krzk@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jjohnson@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_rajkbhag@quicinc.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox