/openbmc/linux/drivers/net/wireless/ath/ath9k/ |
H A D | ar9002_calib.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | ar9002_phy.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | eeprom_4k.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | ar9002_hw.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | ani.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | calib.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | mac.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | ar5008_phy.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | htc_drv_init.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | hw.h | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | hw.c | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
/openbmc/linux/drivers/net/wireless/ath/ |
H A D | ath.h | diff 435c1610f46dc4d86a6633adb037b18109e6ffdc Tue Oct 05 05:03:42 CDT 2010 Felix Fietkau <nbd@openwrt.org> ath9k_hw: clean up register write buffering
Throughout the code, DISABLE_REGWRITE_BUFFER is always called right after REGWRITE_BUFFER_FLUSH. Since that's unlikely to change any time soon, that makes keeping those ops separate rather pointless, as it only increases code size and line number counts.
Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|