From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 01/18] dt-bindings: net: wireless: describe the ath12k AHB module
Date: Wed, 4 Sep 2024 09:38:45 +0200 [thread overview]
Message-ID: <1e2a2974-b78b-483f-9190-34d5dae69f7d@kernel.org> (raw)
In-Reply-To: <cecf0e32-b84c-423e-89c3-61eab9f1928a@quicinc.com>
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.
> on WiFi frequency bands capability. For example, 2 GHz, 5 GHz, 6 GHz, or multi-band
> variants of ath12k devices have different qcom,board_id values.
>
> In the next version, I will include the above information in the qcom,board_id
> description.
Please follow DTS coding style. And style of existing properties like
this. Did you look for them? I claim you just sent whatever you had in
downstream.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-04 7:38 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 [this message]
2024-09-04 11:28 ` Raj Kumar Bhagat
2024-09-04 11:42 ` Krzysztof Kozlowski
2024-09-05 18:33 ` Kalle Valo
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=1e2a2974-b78b-483f-9190-34d5dae69f7d@kernel.org \
--to=krzk@kernel.org \
--cc=ath12k@lists.infradead.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