From: Janusz Dziedzic <janusz.dziedzic@gmail.com>
To: ath12k@lists.infradead.org
Subject: qcn9274 hw2.0 in banana pi r64 - LTSSM read fail
Date: Mon, 29 Jan 2024 12:34:51 +0100 [thread overview]
Message-ID: <CAFED-jma7ZB17Rcgx9H+eVZ=N6Pty4__gz3B+O2V34XtcEzOGg@mail.gmail.com> (raw)
Hello,
I have this card in bpi-r64 board. Need to hash: ath12k_pci_enable_ltssm()
While board hang here (next board restart):
val = ath12k_pci_read32(ab, PCIE_PCIE_PARF_LTSSM);
Is it a 12k bug/MTK pci controller bug?
When hash it works correctly.
root@OpenWrt:~# lspci -nn
00:00.0 PCI bridge [0604]: MEDIATEK Corp. Device [14c3:3258]
01:00.0 Network controller [0280]: Qualcomm Device [17cb:1109] (rev 01)
root@OpenWrt:~#
BR
Janusz
next reply other threads:[~2024-01-29 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 11:34 Janusz Dziedzic [this message]
2024-01-29 13:04 ` qcn9274 hw2.0 in banana pi r64 - LTSSM read fail Kalle Valo
2024-01-29 15:09 ` Janusz Dziedzic
2024-01-31 17:08 ` Janusz Dziedzic
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='CAFED-jma7ZB17Rcgx9H+eVZ=N6Pty4__gz3B+O2V34XtcEzOGg@mail.gmail.com' \
--to=janusz.dziedzic@gmail.com \
--cc=ath12k@lists.infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).