mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "André Valentin" <avalentin@marcant.net>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: Manikanta Pubbisetty <manikanta.pubbisetty@oss.qualcomm.com>,
	linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] wifi: ath11k: run ahb shutdown() teardown only on WCN6750
Date: Fri, 21 Aug 2026 08:50:41 +0200	[thread overview]
Message-ID: <a1ff9ecb-7338-4b14-848c-d4034a584b4d@marcant.net> (raw)
In-Reply-To: <20260810192859.949348-1-avalentin@marcant.net>

Hi Jeff,

gentle ping on v3, sent 2026-08-10. It is still marked "new" in patchwork
(https://patchwork.kernel.org/project/linux-wireless/patch/20260810192859.949348-1-avalentin@marcant.net/),
so I want to make sure it did not simply fall through the cracks rather
than that you are waiting on something from me.

v3 addresses all three points from your v2 review:

- ahb.c and hw.h use the /* on its own line block comment style.
- The comments in the generic code describe the behaviour only; no
chipset is named there any more. Only the ath11k_hw_params initializer
correlates the feature with the hardware.
- .shutdown_teardown is now initialized explicitly in every
ath11k_hw_params record (= false on all but WCN6750).

Is there anything else you would like changed, or should I resend as v4
with a fresh base?

For context on the impact: without this, a plain reboot on the IPQ AHB
targets (IPQ8074/IPQ6018/IPQ5018) stops in the boot ROM during DDR
training and only a physical power cycle recovers, so the affected
devices cannot be rebooted remotely at all.

Kind regards,
André

           reply	other threads:[~2026-08-21  6:51 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260810192859.949348-1-avalentin@marcant.net>]

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=a1ff9ecb-7338-4b14-848c-d4034a584b4d@marcant.net \
    --to=avalentin@marcant.net \
    --cc=ath11k@lists.infradead.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=manikanta.pubbisetty@oss.qualcomm.com \
    --cc=stable@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

all inboxes | Powered by JetHome®