1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>wiphy_apply_custom_regulatory</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="The 802.11 subsystems &#8211; for kernel developers"><link rel="up" href="bk01ch06.html" title="Chapter&#160;6.&#160;Regulatory enforcement infrastructure"><link rel="prev" href="API-regulatory-hint.html" title="regulatory_hint"><link rel="next" href="API-freq-reg-info.html" title="freq_reg_info"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">wiphy_apply_custom_regulatory</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="API-regulatory-hint.html">Prev</a>&#160;</td><th width="60%" align="center">Chapter&#160;6.&#160;Regulatory enforcement infrastructure</th><td width="20%" align="right">&#160;<a accesskey="n" href="API-freq-reg-info.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API-wiphy-apply-custom-regulatory"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>wiphy_apply_custom_regulatory &#8212; 
2  apply a custom driver regulatory domain
3 </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="funcsynopsis"><table border="0" class="funcprototype-table" summary="Function synopsis" style="cellspacing: 0; cellpadding: 0;"><tr><td><code class="funcdef">void <b class="fsfunc">wiphy_apply_custom_regulatory </b>(</code></td><td>struct wiphy * <var class="pdparam">wiphy</var>, </td></tr><tr><td>&#160;</td><td>const struct ieee80211_regdomain * <var class="pdparam">regd</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer">&#160;</div></div></div><div class="refsect1"><a name="idp1113202628"></a><h2>Arguments</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>wiphy</code></em></span></dt><dd><p>
4     the wireless device we want to process the regulatory domain on
5    </p></dd><dt><span class="term"><em class="parameter"><code>regd</code></em></span></dt><dd><p>
6     the custom regulatory domain to use for this wiphy
7    </p></dd></dl></div></div><div class="refsect1"><a name="idp1113205340"></a><h2>Description</h2><p>
8   Drivers can sometimes have custom regulatory domains which do not apply
9   to a specific country. Drivers can use this to apply such custom regulatory
10   domains. This routine must be called prior to wiphy registration. The
11   custom regulatory domain will be trusted completely and as such previous
12   default channel settings will be disregarded. If no rule is found for a
13   channel on the regulatory domain the channel will be disabled.
14   Drivers using this for a wiphy should also set the wiphy flag
15   REGULATORY_CUSTOM_REG or cfg80211 will set it for the wiphy
16   that called this helper.
17</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="API-regulatory-hint.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="bk01ch06.html">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="API-freq-reg-info.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="phrase">regulatory_hint</span>&#160;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&#160;<span class="phrase">freq_reg_info</span></td></tr></table></div></body></html>
18