From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Aaradhana Sahu <aaradhana.sahu@oss.qualcomm.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath-next v3] wifi: ath12k: add QMI capability negotiation for dynamic memory mode
Date: Tue, 30 Jun 2026 08:53:22 -0700 [thread overview]
Message-ID: <4db87d04-2de6-4521-8da0-d80b036d216a@oss.qualcomm.com> (raw)
In-Reply-To: <20260626084327.2022076-1-aaradhana.sahu@oss.qualcomm.com>
On 6/26/2026 1:43 AM, Aaradhana Sahu wrote:
> @@ -2319,11 +2360,14 @@ static void ath12k_qmi_phy_cap_send(struct ath12k_base *ab)
>
> ab->qmi.num_radios = resp.num_phy;
>
> + if (resp.dynamic_ddr_support_valid)
> + ab->qmi.dynamic_ddr_support = resp.dynamic_ddr_support;
> +
> ath12k_dbg(ab, ATH12K_DBG_QMI,
> - "phy capability resp valid %d single_chip_mlo_support %d valid %d num_phy %d valid %d board_id %d\n",
> + "phy capability resp valid %d single_chip_mlo_support %d valid %d num_phy %d valid %d board_id %d dynamic_ddr_valid %u dynamic_ddr_support %u\n",
> resp.single_chip_mlo_support_valid, resp.single_chip_mlo_support,
> - resp.num_phy_valid, resp.num_phy,
> - resp.board_id_valid, resp.board_id);
> + resp.num_phy_valid, resp.num_phy, resp.board_id_valid, resp.board_id,
> + resp.dynamic_ddr_support_valid, resp.dynamic_ddr_support);
Your logging change conflicts with the one in:
wifi: ath12k: use %u for unsigned variables in QMI debug logs
That one is already in my pending queue, so I'll have you rebase once that one
lands in ath-next.
/jeff
next prev parent reply other threads:[~2026-06-30 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 8:43 [PATCH ath-next v3] wifi: ath12k: add QMI capability negotiation for dynamic memory mode Aaradhana Sahu
2026-06-29 2:24 ` Baochen Qiang
2026-06-29 5:42 ` Rameshkumar Sundaram
2026-06-30 15:53 ` Jeff Johnson [this message]
2026-07-01 3:15 ` Aaradhana Sahu
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=4db87d04-2de6-4521-8da0-d80b036d216a@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=aaradhana.sahu@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.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