public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Paweł Owoc" <frut3k7@gmail.com>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
	 Jeff Johnson <jjohnson@kernel.org>,
	 linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] wifi: ath10k: add channel 177 for 5 GHz band
Date: Fri, 18 Oct 2024 14:49:44 +0300	[thread overview]
Message-ID: <87ed4dr5pj.fsf@kernel.org> (raw)
In-Reply-To: <CAKEyCaDUfn4jtCdTt9JJ-Qe+CCudORPwcjj5i5=G28ANc+eCRg@mail.gmail.com> ("Paweł Owoc"'s message of "Fri, 18 Oct 2024 00:51:59 +0200")

Paweł Owoc <frut3k7@gmail.com> writes:

> On Fri, Oct 11, 2024 at 6:51 PM Jeff Johnson <quic_jjohnson@quicinc.com> wrote:
>>
>> On 10/8/2024 11:49 PM, Paweł Owoc wrote:> Add support for channel 177 (5885
>> MHz ) for the 5 GHz band.
>> >
>> > Tested-on: qca988x hw2.0 firmware ver 10.2.4-1.0-00047
>>
>> Can you elaborate on what was tested in your commit text? And more
>> importantly, what is the impact on existing devices, especially given that
>> existing devices would not have calibration data for this channel in the board
>> files? Does the QCA988x board file even have calibration data for this channel?
>>
> In the case of ath10k we use an external regulatory database.
> For the country "US" channels 169, 173 and 177 are marked as NO-IR and
> we cannot run AP on them.
> Even if channels are not disabled in the board files:
>             * 5845.0 MHz [169] (27.0 dBm) (no IR)
>             * 5865.0 MHz [173] (27.0 dBm) (no IR)
>             * 5885.0 MHz [177] (27.0 dBm) (no IR)
>
> I only tested the use as a client on channel 177:
> root@OpenWrt:~# iwinfo phy1 scan
> Cell 01 - Address: XX:XX:XX:XX:XX:XX
>           ESSID: "ch177"
>           Mode: Master  Frequency: 5.885 GHz  Band: 5 GHz  Channel: 177
>           Signal: -43 dBm  Quality: 67/70
>           Encryption: mixed WPA2/WPA3 PSK/SAE (CCMP)
>           HT Operation:
>                     Primary Channel: 177
>                     Secondary Channel Offset: no secondary
>                     Channel Width: 20 MHz

I wonder how this works with QCA6174, unfortunately I'm not able to test
that.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2024-10-18 11:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 20:23 [PATCH] wifi: ath10k: add channel 177 for 5 GHz band Paweł Owoc
2024-10-09  6:49 ` [PATCH v2] " Paweł Owoc
2024-10-11 16:51   ` Jeff Johnson
2024-10-17 22:51     ` Paweł Owoc
2024-10-18 11:49       ` Kalle Valo [this message]
2024-10-19 15:32         ` Paweł Owoc
2025-09-17 16:17           ` Paweł Owoc
2026-03-19 12:26             ` Paweł Owoc

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=87ed4dr5pj.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=frut3k7@gmail.com \
    --cc=jjohnson@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_jjohnson@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox