All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamdi Issam <ih@simonwunderlich.de>
To: akolli@codeaurora.org
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	periyasa@codeaurora.org
Subject: Re: [PATCH 06/11] ath11k: add static window support for register access
Date: Mon, 28 Mar 2022 18:44:00 +0200	[thread overview]
Message-ID: <4c708ea3-d027-aa01-e157-17a29889ac44@simonwunderlich.de> (raw)
In-Reply-To: <1612946530-28504-7-git-send-email-akolli@codeaurora.org>

Hello,

I was trying to read values of timers from some offsets on the QCN9074, 
but I get every time an invalid values (0xffffffff):
This is example of my code:

#define QCN9000_WLAON_GLOBAL_COUNTER_CTRL3      0x1F80118
#define QCN9000_WLAON_GLOBAL_COUNTER_CTRL4      0x1F8011C
#define QCN9000_WLAON_GLOBAL_COUNTER_CTRL5      0x1F80120

#define QCN9000_TIME_SYNC_ENABLE                0x80000000
#define QCN9000_TIME_SYNC_CLEAR                 0x0
.
.
.
ath11k_pci_write32(ab, QCN9000_WLAON_GLOBAL_COUNTER_CTRL5, 
QCN9000_TIME_SYNC_CLEAR);
ath11k_pci_write32(ab, QCN9000_WLAON_GLOBAL_COUNTER_CTRL5, 
QCN9000_TIME_SYNC_ENABLE);
low = ath11k_pci_read32(ab, QCN9000_WLAON_GLOBAL_COUNTER_CTRL3);
high = ath11k_pci_read32(ab, QCN9000_WLAON_GLOBAL_COUNTER_CTRL4);
.
.

The low and the high parameters always equal to "0xffffffff".

When I made some debugging. I found that the issue is related to 
"static_window_map" developed in the commit 
"480a73610c95511e42fb7d0359b523f66883e51a: ath11k: add static window 
support for register access" and enabled for QCN9074 in this commit 
"4e80946197a83a6115e308334618449b77696d6a: ath11k: add qcn9074 pci 
device support".
When I disabled the "static_window_map" 
(ab->bus_params.static_window_map = false;) for QCN9074, in that case I 
was able to get the correct values.
So it seems that there's an issue of reading some reg when 
static_window_map is enabled.
I need your help to solve this issue.

Regards,
Issam


WARNING: multiple messages have this Message-ID (diff)
From: Hamdi Issam <ih@simonwunderlich.de>
To: akolli@codeaurora.org
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	periyasa@codeaurora.org
Subject: Re: [PATCH 06/11] ath11k: add static window support for register access
Date: Mon, 28 Mar 2022 18:44:00 +0200	[thread overview]
Message-ID: <4c708ea3-d027-aa01-e157-17a29889ac44@simonwunderlich.de> (raw)
In-Reply-To: <1612946530-28504-7-git-send-email-akolli@codeaurora.org>

Hello,

I was trying to read values of timers from some offsets on the QCN9074, 
but I get every time an invalid values (0xffffffff):
This is example of my code:

#define QCN9000_WLAON_GLOBAL_COUNTER_CTRL3      0x1F80118
#define QCN9000_WLAON_GLOBAL_COUNTER_CTRL4      0x1F8011C
#define QCN9000_WLAON_GLOBAL_COUNTER_CTRL5      0x1F80120

#define QCN9000_TIME_SYNC_ENABLE                0x80000000
#define QCN9000_TIME_SYNC_CLEAR                 0x0
.
.
.
ath11k_pci_write32(ab, QCN9000_WLAON_GLOBAL_COUNTER_CTRL5, 
QCN9000_TIME_SYNC_CLEAR);
ath11k_pci_write32(ab, QCN9000_WLAON_GLOBAL_COUNTER_CTRL5, 
QCN9000_TIME_SYNC_ENABLE);
low = ath11k_pci_read32(ab, QCN9000_WLAON_GLOBAL_COUNTER_CTRL3);
high = ath11k_pci_read32(ab, QCN9000_WLAON_GLOBAL_COUNTER_CTRL4);
.
.

The low and the high parameters always equal to "0xffffffff".

When I made some debugging. I found that the issue is related to 
"static_window_map" developed in the commit 
"480a73610c95511e42fb7d0359b523f66883e51a: ath11k: add static window 
support for register access" and enabled for QCN9074 in this commit 
"4e80946197a83a6115e308334618449b77696d6a: ath11k: add qcn9074 pci 
device support".
When I disabled the "static_window_map" 
(ab->bus_params.static_window_map = false;) for QCN9074, in that case I 
was able to get the correct values.
So it seems that there's an issue of reading some reg when 
static_window_map is enabled.
I need your help to solve this issue.

Regards,
Issam


-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  parent reply	other threads:[~2022-03-28 16:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10  8:41 [PATCH 00/11] ath11k: Add support for QCN9074 Anilkumar Kolli
2021-02-10  8:41 ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 01/11] ath11k: Refactor ath11k_msi_config Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-17  9:38   ` Kalle Valo
2021-02-17  9:38   ` Kalle Valo
2021-02-10  8:42 ` [PATCH 02/11] ath11k: Move qmi service_ins_id to hw_params Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 03/11] ath11k: qmi: increase the number of fw segments Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 04/11] ath11k: Update memory segment count for qcn9074 Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 05/11] ath11k: Add qcn9074 mhi controller config Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 06/11] ath11k: add static window support for register access Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-16 16:45   ` Kalle Valo
2021-02-16 16:45     ` Kalle Valo
2021-02-17  2:28     ` akolli
2021-02-17  2:28       ` akolli
2021-02-17  9:28       ` Kalle Valo
2021-02-17  9:28         ` Kalle Valo
2022-03-28 16:44   ` Hamdi Issam [this message]
2022-03-28 16:44     ` Hamdi Issam
2022-06-23 10:44     ` Karthikeyan Periyasamy (QUIC)
2022-06-23 10:44       ` Karthikeyan Periyasamy (QUIC)
2021-02-10  8:42 ` [PATCH 07/11] ath11k: add hal support for QCN9074 Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 08/11] ath11k: add data path " Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 09/11] ath11k: add CE interrupt " Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 10/11] ath11k: add extended " Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-10  8:42 ` [PATCH 11/11] ath11k: add qcn9074 pci device support Anilkumar Kolli
2021-02-10  8:42   ` Anilkumar Kolli
2021-02-16 16:36   ` Kalle Valo
2021-02-16 16:36     ` Kalle Valo

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=4c708ea3-d027-aa01-e157-17a29889ac44@simonwunderlich.de \
    --to=ih@simonwunderlich.de \
    --cc=akolli@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=periyasa@codeaurora.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 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.