From: Sven Eckelmann <se@simonwunderlich.de>
To: ih@simonwunderlich.de, Issam Hamdi <ih@simonwunderlich.de>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
mathias.kretschmer@fit.fraunhofer.de,
simon.wunderlich@open-mesh.com, sw@simonwunderlich.de
Subject: Re: [PATCH v2 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang
Date: Wed, 06 Nov 2024 11:06:03 +0100 [thread overview]
Message-ID: <5516036.Sb9uPGUboI@ripper> (raw)
In-Reply-To: <20241106090439.3487958-1-ih@simonwunderlich.de>
On Wednesday, 6 November 2024 10:04:38 CET Issam Hamdi wrote:
> +static bool ath_hw_hang_deadbeef(struct ath_softc *sc)
> +{
> + struct ath_common *common = ath9k_hw_common(sc->sc_ah);
> + u32 reg;
> +
> + /* check for stucked MAC */
> + ath9k_ps_wakeup(sc);
> + reg = REG_READ(sc->sc_ah, AR_CFG);
> + ath9k_ps_restore(sc);
> +
> + if (reg != 0xdeadbeef)
> + return false;
> +
> + ath_dbg(common, RESET,
> + "0xdeadbeef hang is detected. Schedule chip reset\n");
> + ath9k_queue_reset(sc, RESET_TYPE_DEADBEEF);
> +
> + return true;
> +}
I don't really get why this was proposed again. Can you please explain why the
reworked version of this patch [1] (by Felix) is not good enough?
If there are any deficits with Felix's version then it would be nice to know
get informed about it (in the commit message) and then work on the deficits.
Having two different checks at the same time for the same thing in upstream
Linux doesn't seem to be helpful.
I have more problems with the submission style - see next mail.
Kind regards,
Sven
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a34d0a0da1abae46a5f6ebd06fb0ec484ca099d9
prev parent reply other threads:[~2024-11-06 10:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 17:16 [PATCH 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang Issam Hamdi
2024-11-04 17:16 ` [PATCH 2/2] wifi: ath9k: Reset chip on potential deaf state Issam Hamdi
2024-11-05 10:53 ` Kalle Valo
2024-11-05 13:02 ` Toke Høiland-Jørgensen
2024-11-05 13:30 ` Simon Wunderlich
2024-11-05 15:10 ` Toke Høiland-Jørgensen
2024-11-06 10:05 ` Hamdi Issam
2024-11-05 13:34 ` Simon Wunderlich
2024-11-05 10:49 ` [PATCH 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang Kalle Valo
2024-11-05 12:31 ` Toke Høiland-Jørgensen
2024-11-06 9:04 ` [PATCH v2 " Issam Hamdi
2024-11-06 9:04 ` [PATCH v2 2/2] wifi: ath9k: Reset chip on potential deaf state Issam Hamdi
2024-11-06 10:05 ` Sven Eckelmann
2024-11-06 12:41 ` Toke Høiland-Jørgensen
2024-11-07 8:03 ` Kalle Valo
2024-11-06 10:06 ` Sven Eckelmann [this message]
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=5516036.Sb9uPGUboI@ripper \
--to=se@simonwunderlich.de \
--cc=ih@simonwunderlich.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fit.fraunhofer.de \
--cc=simon.wunderlich@open-mesh.com \
--cc=sw@simonwunderlich.de \
/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