ath9k: Remove ATH9K_BEACON_PERIOD mask

Earlier beacon_interval is used to hold interval value and
some flags (ATH9K_BEACON_ENA &ATH9K_BEACON_PERIOD). So to
extract interval ATH9K_BEACON_PERIOD is used. Those flags
were completely removed. So masking beacon_interval is
not required.

Signed-off-by: Rajkumar Manoharan <rmanoharan@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/drivers/net/wireless/ath/ath9k/beacon.c b/drivers/net/wireless/ath/ath9k/beacon.c
index d4d8ceced89..8b85d7c1d38 100644
--- a/drivers/net/wireless/ath/ath9k/beacon.c
+++ b/drivers/net/wireless/ath/ath9k/beacon.c
@@ -496,7 +496,7 @@ static void ath_beacon_config_ap(struct ath_softc *sc,
         u32 nexttbtt, intval;
 
         /* NB: the beacon interval is kept internally in TU's */
-        intval = TU_TO_USEC(conf->beacon_interval & ATH9K_BEACON_PERIOD);
+        intval = TU_TO_USEC(conf->beacon_interval);
         intval /= ATH_BCBUF;    /* for staggered beacons */
         nexttbtt = intval;
 
@@ -543,7 +543,7 @@ static void ath_beacon_config_sta(struct ath_softc *sc,
         }
 
         memset(&bs, 0, sizeof(bs));
-        intval = conf->beacon_interval & ATH9K_BEACON_PERIOD;
+        intval = conf->beacon_interval;
 
         /*
          * Setup dtim and cfp parameters according to
@@ -657,7 +657,7 @@ static void ath_beacon_config_adhoc(struct ath_softc *sc,
         ath9k_reset_beacon_status(sc);
 
         tsf = ath9k_hw_gettsf32(ah) + TU_TO_USEC(FUDGE);
-        intval = TU_TO_USEC(conf->beacon_interval & ATH9K_BEACON_PERIOD);
+        intval = TU_TO_USEC(conf->beacon_interval);
 
         if (!sc->beacon.bc_tstamp)
                 nexttbtt = tsf + intval;