All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Benjamin Berg <benjamin@sipsolutions.net>, ath10k@lists.infradead.org
Cc: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>,
	Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>,
	Michal Kazior <michal.kazior@tieto.com>,
	Sebastian Gottschall <s.gottschall@dd-wrt.com>,
	Simon Wunderlich <sw@simonwunderlich.de>
Subject: Re: [PATCHv3 2/2] ath10k: Allow setting coverage class
Date: Mon, 16 Oct 2017 10:57:51 -0700	[thread overview]
Message-ID: <6cbadf5a-4289-640c-eb46-694a7da8ea44@candelatech.com> (raw)
In-Reply-To: <20160825132522.30994-3-benjamin@sipsolutions.net>

On 08/25/2016 06:25 AM, Benjamin Berg wrote:
> Unfortunately ath10k does not generally allow modifying the coverage class
> with the stock firmware and Qualcomm has so far refused to implement this
> feature so that it can be properly supported in ath10k. If we however know
> the registers that need to be modified for proper operation with a higher
> coverage class, then we can do these modifications from the driver.
>
> This patch implements this hack for first generation cards which are based
> on a core that is similar to ath9k. The registers are modified in place and
> need to be re-written every time the firmware sets them. To achieve this
> the register status is verified after certain WMI events from the firmware.
>
> The coverage class may not be modified temporarily right after the card
> re-initializes the registers. This is for example the case during scanning.
>
> Thanks to Sebastian Gottschall <s.gottschall@dd-wrt.com> for initially
> working on a userspace support for this. This patch wouldn't have been
> possible without this documentation.

Hello,

Do you happen to know the maximum distance that can work with this
patch enabled?  The register value maximum seems to be 0x3FFF, but I
am not sure of the units (nor how exactly that applies to distance).

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2017-10-16 17:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 13:25 [PATCHv3 0/2] ath10k: Allow setting coverage class Benjamin Berg
2016-08-25 13:25 ` [PATCHv3 1/2] ath10k: Rename hw_rx_desc_ops to hw_ops to use it for other purposes Benjamin Berg
2016-08-25 13:25 ` [PATCHv3 2/2] ath10k: Allow setting coverage class Benjamin Berg
2016-08-25 14:28   ` Ben Greear
2016-08-25 14:33     ` Benjamin Berg
2016-08-25 15:10       ` Sebastian Gottschall
2017-10-16 17:57   ` Ben Greear [this message]
2017-10-16 17:59     ` Adrian Chadd
2017-10-16 19:10       ` Sebastian Gottschall
2017-10-16 19:12         ` Adrian Chadd
2017-10-16 19:55           ` Ben Greear
2017-10-17  7:57             ` Sebastian Gottschall
2017-10-17  7:56           ` Sebastian Gottschall

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=6cbadf5a-4289-640c-eb46-694a7da8ea44@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=benjamin@sipsolutions.net \
    --cc=mathias.kretschmer@fit.fraunhofer.de \
    --cc=michal.kazior@tieto.com \
    --cc=s.gottschall@dd-wrt.com \
    --cc=sw@simonwunderlich.de \
    --cc=vthiagar@qti.qualcomm.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 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.