linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Stromdahl <erik.stromdahl@gmail.com>
To: kvalo@qca.qualcomm.com, linux-wireless@vger.kernel.org,
	ath10k@lists.infradead.org
Cc: Erik Stromdahl <erik.stromdahl@gmail.com>
Subject: [RFC v2 01/10] ath10k: high_latency detection
Date: Mon, 12 Jun 2017 17:03:02 +0200	[thread overview]
Message-ID: <1497279791-9598-2-git-send-email-erik.stromdahl@gmail.com> (raw)
In-Reply-To: <1497279791-9598-1-git-send-email-erik.stromdahl@gmail.com>

The setup of high latency chips (USB and SDIO) is
sometimes different than for chips using low latency
interfaces.

The bus type is used to determine if the interface is
a high latency interface.

Signed-off-by: Erik Stromdahl <erik.stromdahl@gmail.com>
---
 drivers/net/wireless/ath/ath10k/core.c | 1 +
 drivers/net/wireless/ath/ath10k/core.h | 7 +++++++
 2 files changed, 8 insertions(+)

diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c
index 3fb1429..d3bf5c4 100644
--- a/drivers/net/wireless/ath/ath10k/core.c
+++ b/drivers/net/wireless/ath/ath10k/core.c
@@ -2455,6 +2455,7 @@ struct ath10k *ath10k_core_create(size_t priv_size, struct device *dev,
 	ar->hw_rev = hw_rev;
 	ar->hif.ops = hif_ops;
 	ar->hif.bus = bus;
+	ar->is_high_latency = ath10k_is_high_latency(bus);
 
 	switch (hw_rev) {
 	case ATH10K_HW_QCA988X:
diff --git a/drivers/net/wireless/ath/ath10k/core.h b/drivers/net/wireless/ath/ath10k/core.h
index 1efe0a1..90069b8 100644
--- a/drivers/net/wireless/ath/ath10k/core.h
+++ b/drivers/net/wireless/ath/ath10k/core.h
@@ -789,6 +789,8 @@ struct ath10k {
 
 	bool p2p;
 
+	bool is_high_latency;
+
 	struct {
 		enum ath10k_bus bus;
 		const struct ath10k_hif_ops *ops;
@@ -1008,6 +1010,11 @@ static inline bool ath10k_peer_stats_enabled(struct ath10k *ar)
 	return false;
 }
 
+static inline bool ath10k_is_high_latency(enum ath10k_bus bus)
+{
+	return ((bus == ATH10K_BUS_SDIO) || (bus == ATH10K_BUS_USB));
+}
+
 struct ath10k *ath10k_core_create(size_t priv_size, struct device *dev,
 				  enum ath10k_bus bus,
 				  enum ath10k_hw_rev hw_rev,
-- 
2.7.4

  reply	other threads:[~2017-06-12 15:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 15:03 [RFC v2 00/10] ath10k high latency Erik Stromdahl
2017-06-12 15:03 ` Erik Stromdahl [this message]
2017-06-12 15:03 ` [RFC v2 02/10] ath10k: htt: RX ring config HL support Erik Stromdahl
2017-06-12 15:03 ` [RFC v2 03/10] ath10k: per target configurablity of various items Erik Stromdahl
2017-06-12 15:03 ` [RFC v2 04/10] ath10k: add start_once support Erik Stromdahl
2017-06-12 15:03 ` [RFC v2 05/10] ath10k: htt: High latency TX support Erik Stromdahl
2017-06-13 17:38   ` Peter Oh
2017-06-17 17:59     ` Erik Stromdahl
2017-06-19 15:37       ` Kalle Valo
2017-06-12 15:03 ` [RFC v2 06/10] ath10k: htt: High latency RX support Erik Stromdahl
2017-06-13 17:39   ` Peter Oh
2017-06-12 15:03 ` [RFC v2 07/10] ath10k: dma fixes for high latency devices Erik Stromdahl
2017-06-12 15:03 ` [RFC v2 08/10] ath10k: add QCA9377 usb hw_param item Erik Stromdahl
2017-06-12 15:03 ` [RFC v2 09/10] ath10k: add QCA9377 sdio " Erik Stromdahl
2017-06-12 15:03 ` [RFC v2 10/10] ath10k: wmi: disable softirq's while calling ieee80211_rx Erik Stromdahl

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=1497279791-9598-2-git-send-email-erik.stromdahl@gmail.com \
    --to=erik.stromdahl@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).