public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: Parth Panchoil <parth105105@gmail.com>,
	"ath12k@lists.infradead.org" <ath12k@lists.infradead.org>
Subject: Re: wifi: ath12k: start-up crash with WCN7850 hw2.0 on TI AM69-SK board
Date: Thu, 15 May 2025 16:23:05 +0200	[thread overview]
Message-ID: <20250515142305.GA74294@francesco-nb> (raw)
In-Reply-To: <6ee296a1-1cb9-4187-9c74-222bea54843b@quicinc.com>

Hello,

On Tue, May 06, 2025 at 01:56:11PM +0800, Baochen Qiang wrote:
> On 4/30/2025 8:50 PM, Parth Panchoil wrote:
> > On Wed, 2025-02-19 at 18:18 +0800, Baochen Qiang wrote:
> >> On 2/5/2025 10:20 AM, Baochen Qiang wrote:
> >>> On 1/27/2025 10:01 PM, Parth Panchoil wrote:
> >>>> I am currently debugging the ath12k_pci_enable_ltssm start up
> >>>> crash/bug
> >>>> with the mainline kernel on my system and would like to share my
> >>>> observations so far:
> >>>>
> >>>> The ath12k mainline driver gets stuck at this specific line: 
> >>>> https://github.com/torvalds/linux/blob/9c5968db9e625019a0ee5226c7eebef5519d366a/drivers/net/wireless/ath/ath12k/pci.c#L295
> >>>> in the ath12k_pci_enable_ltssm  which attempts to read
> >>>> GCC_GCC_PCIE_HOT_RST, particularly
> >>>> https://github.com/torvalds/linux/blob/9c5968db9e625019a0ee5226c7eebef5519d366a/drivers/net/wireless/ath/ath12k/pci.c#L1209

...

> >>
> >> -#define GCC_GCC_PCIE_HOT_RST                   0x1e38338
> >> +#define GCC_GCC_PCIE_HOT_RST                   0x1e40304

...

> 
> GCC_GCC_PCIE_HOT_RST is wrongly defined, normally this should not cause any critical
> issue, because IMO the RC is expected to return 0xffffffff when accessing a non-exist
> register. However in your case kernel crashes, so seems RC does not behave well, maybe not
> following spec?
> 
> anyway I will submit a patch to fix it.

Any update on this? I can easily submit a patch myself, just let me
know. Because of this bug we have a crash that is preventing us to use
the device.

Francesco



  reply	other threads:[~2025-05-15 14:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 14:19 wifi: ath12k: start-up crash with WCN7850 hw2.0 on TI AM69-SK board Parth Panchoil
2025-01-22  7:20 ` Baochen Qiang
2025-01-24 10:02   ` Parth Pancholi
2025-01-27 14:01     ` Parth Panchoil
2025-01-29 16:20       ` Parth Panchoil
2025-02-05  2:20       ` Baochen Qiang
2025-02-19 10:18         ` Baochen Qiang
2025-04-30 12:50           ` Parth Panchoil
2025-05-06  5:56             ` Baochen Qiang
2025-05-15 14:23               ` Francesco Dolcini [this message]
2025-05-16  1:36                 ` Baochen Qiang

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=20250515142305.GA74294@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=ath12k@lists.infradead.org \
    --cc=parth105105@gmail.com \
    --cc=quic_bqiang@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