From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
To: "wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Tx power for slave devices in ETSI DFS region
Date: Tue, 11 Dec 2018 02:30:58 +0000 [thread overview]
Message-ID: <423eaa39-fc06-6a5a-a8fd-5e15d503dff5@quantenna.com> (raw)
Hello,
according to ETSI
https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
section 4.2.3.2.2, table 2
Note 3 states:
>Slave devices without a Radar Interference Detection function shall
>comply with the limits for the frequency range 5 250 MHz to 5 350 MHz.
And Tx power limits are defined as following:
5150 to 5350: 20 dbm
5470 to 5725: 27 dbm
Which means that if STA device can not do radar detection, it must use
20dbm Tx powers on all channels (can not use 27 dbm limit).
Looking at regdb
https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt,
power limit for frequency range 5470 to 5725 is defined at 27 dbm.
Question is: does wireless core assumes that each device can do radar
detection in slave modes (eg acting as a STA) and it is enabled by
default? I couldn't find any logic in kernel which would limit 27 dbm
power to 20 for STA devices.
next reply other threads:[~2018-12-11 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 2:30 Igor Mitsyanko [this message]
2019-01-15 13:45 ` Tx power for slave devices in ETSI DFS region Johannes Berg
2019-01-16 3:58 ` Igor Mitsyanko
2019-01-16 10:26 ` [wireless-regdb] " Petko Bordjukov
2019-01-16 12:49 ` Bjørn Mork
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=423eaa39-fc06-6a5a-a8fd-5e15d503dff5@quantenna.com \
--to=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.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).