From: Goran Sustek <gsustek@gmail.com>
To: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>,
Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org,
Nazar Mokrynskyi <nazar@mokrynskyi.com>
Subject: Re: [PATCH ath-next v2 1/2] wifi: ath12k: report no AFC memory region to firmware
Date: Tue, 10 Nov 2026 01:21:07 +0100 [thread overview]
Message-ID: <20261110002108.89933-1-gsustek@gmail.com> (raw)
In-Reply-To: <8a301454-a8b8-427a-883f-cddcf31a4879@oss.qualcomm.com>
On 11/3/2026 6:17 AM, Rameshkumar Sundaram wrote:
> What do you mean by "bus address" here? Do you mean the DMA address
> provided in chunk->paddr?
Yes, the DMA address in chunk->paddr. v3 says that.
> Also, the paragraph below makes it sound like without this change the
> firmware doesn't send the memory ready indication and the radios don't
> come up, which isn't the case. There is no visible functional issue
> being fixed here. Please update the commit message to precisely describe
> what changes with this patch.
Agreed, there is none. v3 states that the firmware comes up with or
without the change, and describes only what changes in the response:
size 0 instead of the requested size for a segment the host does not
provide.
> I'd rather move chunk->size = 0 to the default: case. That way, all
> unsupported memory region types are consistently reported with size 0.
Done in v3: one line in the default case, no AFC case and no new enum
value. I also restored the existing warning. v2 had moved it to debug
level, which hides a request the driver does not implement; that was
wrong.
Thanks for the review.
Goran
next prev parent reply other threads:[~2026-11-10 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 20:02 [PATCH ath-next v2 0/2] wifi: ath12k: accept what newer QCN9274 firmware requests at boot Goran Sustek
2026-11-02 20:02 ` [PATCH ath-next v2 1/2] wifi: ath12k: report no AFC memory region to firmware Goran Sustek
2026-11-03 5:17 ` Rameshkumar Sundaram
2026-11-10 0:21 ` Goran Sustek [this message]
2026-11-02 20:02 ` [PATCH ath-next v2 2/2] wifi: ath12k: skip unknown direct buffer ring module IDs Goran Sustek
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=20261110002108.89933-1-gsustek@gmail.com \
--to=gsustek@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nazar@mokrynskyi.com \
--cc=rameshkumar.sundaram@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.