From: Kalle Valo <kvalo@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>,
ath12k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 01/18] dt-bindings: net: wireless: describe the ath12k AHB module
Date: Thu, 05 Sep 2024 21:33:51 +0300 [thread overview]
Message-ID: <874j6uhrw0.fsf@kernel.org> (raw)
In-Reply-To: <a782bd91-6d8a-4d3a-8df2-c8aebebc00f9@kernel.org> (Krzysztof Kozlowski's message of "Wed, 4 Sep 2024 13:42:25 +0200")
Krzysztof Kozlowski <krzk@kernel.org> writes:
> On 04/09/2024 13:28, Raj Kumar Bhagat wrote:
>
>> On 9/4/2024 1:08 PM, Krzysztof Kozlowski wrote:
>>> On 04/09/2024 09:23, Raj Kumar Bhagat wrote:
>>>>>> + qcom,board_id:
>>>>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>>>>> + description:
>>>>>> + Board id value, it identifies the variant of ath12k WiFi device.
>>>>>
>>>>> Please do not upstream whatever you have in your vendor tree... You even
>>>>> copied its style! There is no such property in upstream.
>>>>>
>>>>> NAK, you are duplicating compatibles.
>>>>>
>>>>>
>>>>
>>>> qcom,board_id is a new parameter introduced to distinguish between different variants
>>>> of ath12k devices that share the same compatible value. This differentiation is crucial
>>>> as these variants have different qcom,board_id values (with the same compatible) based
>>>
>>> You must explain why compatible cannot be used for that.
>>>
>>
>> The compatible property is used to define the variant of the Ath12k device. However, the
>> Ath12k device variant does not change with different capabilities or configurations
>> (e.g., operating band). The qcom,board_id parameter is introduced to define these
>> configurations, not the device variant itself.
>
> operating aspects are run-time, so not suitable here. It's all still
> vague for me.
Yeah, this is weird and I would hope there is a better way to do it.
Unfortunately I'm not able to study this in detail right now but, like
you said, most likely this is just directly copied from QSDK (their
downstream).
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-09-05 18:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 9:43 [RFC PATCH 00/18] wifi: ath12k: add Ath12k AHB driver support for IPQ5332 Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 01/18] dt-bindings: net: wireless: describe the ath12k AHB module Raj Kumar Bhagat
2024-08-16 5:42 ` Krzysztof Kozlowski
2024-09-04 7:23 ` Raj Kumar Bhagat
2024-09-04 7:38 ` Krzysztof Kozlowski
2024-09-04 11:28 ` Raj Kumar Bhagat
2024-09-04 11:42 ` Krzysztof Kozlowski
2024-09-05 18:33 ` Kalle Valo [this message]
2024-08-16 5:44 ` Krzysztof Kozlowski
2024-09-04 7:27 ` Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 02/18] arm64: dts: qcom: add wifi node for IPQ5332 based RDP441 Raj Kumar Bhagat
2024-08-16 5:44 ` Krzysztof Kozlowski
2024-08-14 9:43 ` [RFC PATCH 03/18] wifi: ath12k: add ath12k_hw_params for IPQ5332 Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 04/18] wifi: ath12k: refactor ath12k_hw_regs structure Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 05/18] wifi: ath12k: add ath12k_hw_regs for IPQ5332 Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 06/18] wifi: ath12k: add ath12k_hw_ring_mask " Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 07/18] wifi: ath12k: add CE configurations " Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 08/18] wifi: ath12k: add ath12k_hw_hal_params " Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 09/18] wifi: ath12k: avoid m3 firmware download in AHB device IPQ5332 Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 10/18] wifi: ath12k: add new CMEM read-write ath12k_hif_ops Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 11/18] wifi: ath12k: remap CMEM register space for IPQ5332 Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 12/18] wifi: ath12k: fix incorrect CE addresses Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 13/18] wifi: ath12k: remap CE register space for IPQ5332 Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 14/18] wifi: ath12k: add support for fixed QMI firmware memory Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 15/18] wifi: ath12k: add support to read board_id from device-tree Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 16/18] wifi: ath12k: convert tasklet to BH workqueue for CE interrupts Raj Kumar Bhagat
2024-08-14 9:43 ` [RFC PATCH 17/18] wifi: ath12k: add AHB driver support for IPQ5332 Raj Kumar Bhagat
2024-08-16 5:47 ` Krzysztof Kozlowski
2024-08-14 9:43 ` [RFC PATCH 18/18] wifi: ath12k: enable ath12k AHB support Raj Kumar Bhagat
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=874j6uhrw0.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=krzk@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rajkbhag@quicinc.com \
/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