diff options
Diffstat (limited to 'include/net/regulatory.h')
| -rw-r--r-- | include/net/regulatory.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/include/net/regulatory.h b/include/net/regulatory.h index c96a0b86f342..b07cdc9fa454 100644 --- a/include/net/regulatory.h +++ b/include/net/regulatory.h | |||
| @@ -96,6 +96,10 @@ struct regulatory_request { | |||
| 96 | * initiator is %REGDOM_SET_BY_CORE). Drivers that use | 96 | * initiator is %REGDOM_SET_BY_CORE). Drivers that use |
| 97 | * wiphy_apply_custom_regulatory() should have this flag set | 97 | * wiphy_apply_custom_regulatory() should have this flag set |
| 98 | * or the regulatory core will set it for the wiphy. | 98 | * or the regulatory core will set it for the wiphy. |
| 99 | * If you use regulatory_hint() *after* using | ||
| 100 | * wiphy_apply_custom_regulatory() the wireless core will | ||
| 101 | * clear the REGULATORY_CUSTOM_REG for your wiphy as it would be | ||
| 102 | * implied that the device somehow gained knowledge of its region. | ||
| 99 | * @REGULATORY_STRICT_REG: tells us that the wiphy for this device | 103 | * @REGULATORY_STRICT_REG: tells us that the wiphy for this device |
| 100 | * has regulatory domain that it wishes to be considered as the | 104 | * has regulatory domain that it wishes to be considered as the |
| 101 | * superset for regulatory rules. After this device gets its regulatory | 105 | * superset for regulatory rules. After this device gets its regulatory |