From: Rob Herring <robh@kernel.org>
To: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 01/12] dt: bindings: net: add bindings of WCN6750 for ath11k
Date: Tue, 29 Mar 2022 18:37:50 -0500 [thread overview]
Message-ID: <YkOYTpTMXTEx5mAU@robh.at.kernel.org> (raw)
In-Reply-To: <20220328094838.14093-2-quic_mpubbise@quicinc.com>
On Mon, 28 Mar 2022 15:18:27 +0530, Manikanta Pubbisetty wrote:
> WCN6750 is the WLAN chip on Qualcomm Snapdragon SoC SC7280;
> Though being a PCIe based solution, it is not attached to
> the APSS processor (Application Processor SubSystem), it is
> instead attached to another tiny processor called WPSS Q6
> processor (Wireless Processor SubSystem) on the SC7280 MSM,
> where the WLAN firmware runs, and it is the WLAN firmware
> running on the Q6 processor which enumerates WCN6750, as a
> result APPS processor would never know such a device being
> present in the system and would not detect the WCN6750
> hardware unless and otherwise WCN6750 is registered as a
> platform device. This is the reason behind adding WCN6750
> WLAN node in the device tree.
>
> Add WCN6750 wireless driver support, its based on ath11k driver.
>
> Signed-off-by: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
> ---
> .../bindings/net/wireless/qcom,ath11k.yaml | 361 ++++++++++++------
> 1 file changed, 252 insertions(+), 109 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-03-29 23:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 9:48 [PATCH v3 00/12] add support for WCN6750 Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 01/12] dt: bindings: net: add bindings of WCN6750 for ath11k Manikanta Pubbisetty
2022-03-29 23:37 ` Rob Herring [this message]
2022-03-30 5:19 ` Manikanta Pubbisetty
2022-04-04 19:11 ` Matthias Kaehlcke
2022-04-05 6:25 ` Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 02/12] ath11k: Add HW params for WCN6750 Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 03/12] ath11k: Add bus " Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 04/12] ath11k: Add register access logic " Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 05/12] ath11k: Fetch device information via QMI " Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 06/12] ath11k: Add QMI changes " Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 07/12] ath11k: HAL changes to support WCN6750 Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 08/12] ath11k: Datapath " Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 09/12] ath11k: Do not put HW in DBS mode for WCN6750 Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 10/12] ath11k: WMI changes to support WCN6750 Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 11/12] ath11k: Update WBM idle ring HP after FW mode on Manikanta Pubbisetty
2022-03-28 9:48 ` [PATCH v3 12/12] ath11k: Add support for WCN6750 device Manikanta Pubbisetty
[not found] <20220328060937.16738-1-quic_mpubbise@quicinc.com>
[not found] ` <20220328060937.16738-2-quic_mpubbise@quicinc.com>
2022-03-28 6:13 ` [PATCH v3 01/12] dt: bindings: net: add bindings of WCN6750 for ath11k Manikanta Pubbisetty
2022-03-28 9:18 ` Kalle Valo
2022-03-28 9:19 ` Kalle Valo
2022-03-28 9:46 ` Manikanta Pubbisetty
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=YkOYTpTMXTEx5mAU@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_mpubbise@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;
as well as URLs for NNTP newsgroup(s).