From: Kalle Valo <kvalo@codeaurora.org>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
Sven Eckelmann <sven.eckelmann@openmesh.com>
Subject: Re: [PATCH] ath10k: Limit available channels via DT ieee80211-freq-limit
Date: Tue, 28 Aug 2018 13:51:02 +0000 (UTC) [thread overview]
Message-ID: <20180828135102.EF2336044E@smtp.codeaurora.org> (raw)
In-Reply-To: <20180730153933.3771-1-sven.eckelmann@openmesh.com>
Sven Eckelmann <sven.eckelmann@openmesh.com> wrote:
> Tri-band devices (1x 2.4GHz + 2x 5GHz) often incorporate special filters in
> the RX and TX path. These filtered channel can in theory still be used by
> the hardware but the signal strength is reduced so much that it makes no
> sense.
>
> There is already a DT property to limit the available channels but ath10k
> has to manually call this functionality to limit the currrently set wiphy
> channels further.
>
> Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
34d5629d2ca8 ath10k: limit available channels via DT ieee80211-freq-limit
--
https://patchwork.kernel.org/patch/10549245/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-08-28 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 15:39 [PATCH] ath10k: Limit available channels via DT ieee80211-freq-limit Sven Eckelmann
2018-07-30 15:39 ` Sven Eckelmann
2018-07-30 18:50 ` Arend van Spriel
2018-07-30 18:50 ` Arend van Spriel
2018-08-24 11:46 ` Kalle Valo
2018-08-24 11:46 ` Kalle Valo
2018-07-30 18:54 ` Arend van Spriel
2018-07-30 18:54 ` Arend van Spriel
2018-07-30 18:56 ` Arend van Spriel
2018-07-30 18:56 ` Arend van Spriel
2018-08-28 13:51 ` Kalle Valo [this message]
2018-08-28 13:51 ` 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=20180828135102.EF2336044E@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sven.eckelmann@openmesh.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.