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>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/5] dt-bindings: net: wireless: ath12k: describe WSI properties for QCN9274
Date: Tue, 5 Nov 2024 08:24:55 +0100 [thread overview]
Message-ID: <74c84937-fa12-4ab2-922b-7889eb5dda47@kernel.org> (raw)
In-Reply-To: <cb69c30f-8230-4a8f-a538-3ec964b79084@quicinc.com>
On 04/11/2024 19:44, Raj Kumar Bhagat wrote:
>>> $id: http://devicetree.org/schemas/net/wireless/qcom,ath12k.yaml#
>>> @@ -18,10 +19,17 @@ properties:
>>> compatible:
>>> enum:
>>> - pci17cb,1107 # WCN7850
>>> + - pci17cb,1109 # QCN9274
>>
>> I asked for separate binding because it is quite a different device.
>> Unless it is not... but then commit msg is quite not precise here.
>>
>
> sure, will create a separate binding, may be "qcom,ath12k_wsi.yaml".
Underscores are not allowed in compatibles and the file name follows
compatible name, so use hyphen.
>>> + type: object
>>> + description: |
>>> + The ath12k devices (QCN9274) feature WSI support. WSI stands for
>>> + WLAN Serial Interface. It is used for the exchange of specific
>>> + control information across radios based on the doorbell mechanism.
>>> + This WSI connection is essential to exchange control information
>>> + among these devices.
>>> +
>>> + Diagram to represent one WSI connection (one WSI group) among
>>> + three devices.
>>> +
>>> + +-------+ +-------+ +-------+
>>> + | pcie2 | | pcie3 | | pcie1 |
>>> + | | | | | |
>>> + +----->| wsi |------->| wsi |------->| wsi |-----+
>>> + | | grp 0 | | grp 0 | | grp 2 | |
>>> + | +-------+ +-------+ +-------+ |
>>> + +------------------------------------------------------+
>>> +
>>> + Diagram to represent two WSI connections (two separate WSI groups)
>>> + among four devices.
>>> +
>>> + +-------+ +-------+ +-------+ +-------+
>>> + | pcie2 | | pcie3 | | pcie1 | | pcie0 |
>>> + | | | | | | | |
>>> + +-->| wsi |--->| wsi |--+ +-->| wsi |--->| wsi |--+
>>> + | | grp 0 | | grp 0 | | | | grp 1 | | grp 1 | |
>>> + | +-------+ +-------+ | | +-------+ +-------+ |
>>> + +---------------------------+ +---------------------------+
>>> +
>>> + properties:
>>> + qcom,wsi-group-id:
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + description:
>>> + It represents the identifier assigned to the WSI connection. All
>>> + the ath12k devices connected to same WSI connection have the
>>> + same wsi-group-id.
>>
>> That's not needed according to description. Entire group is defined by
>> graph.
>>
>
> So this mean "qcom,wsi-group-id" to be dropped and we can assign the
> group ID (in ath12k driver implementation) by using the graph?
Yes
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-05 7:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 17:30 [RFC PATCH v2 0/5] wifi: ath12k: Add WSI node for QCN9274 in RDP433 for MLO Raj Kumar Bhagat
2024-10-29 17:30 ` [RFC PATCH v2 1/5] dt-bindings: net: wireless: ath12k: describe WSI properties for QCN9274 Raj Kumar Bhagat
2024-10-29 17:52 ` Krzysztof Kozlowski
2024-11-04 18:44 ` Raj Kumar Bhagat
2024-11-05 7:24 ` Krzysztof Kozlowski [this message]
2024-10-30 19:04 ` Jeff Johnson
2024-10-30 20:48 ` Jeff Johnson
2024-11-04 18:55 ` Raj Kumar Bhagat
2024-10-29 17:30 ` [RFC PATCH v2 2/5] wifi: ath12k: parse multiple device information from device tree Raj Kumar Bhagat
2024-10-29 17:30 ` [RFC PATCH v2 3/5] wifi: ath12k: Send partner device details in QMI MLO capability Raj Kumar Bhagat
2024-10-29 17:30 ` [RFC PATCH v2 4/5] wifi: ath12k: assign unique hardware link IDs during QMI host cap Raj Kumar Bhagat
2024-10-29 17:30 ` [RFC PATCH v2 5/5] arm64: dts: qcom: ipq9574: Add WiFi nodes for RDP433 Raj Kumar Bhagat
2024-10-29 17:53 ` Krzysztof Kozlowski
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=74c84937-fa12-4ab2-922b-7889eb5dda47@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.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