summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorBen Cahill <ben.m.cahill@intel.com>2009-11-20 12:04:53 -0800
committerJohn W. Linville <linville@tuxdriver.com>2009-11-23 17:05:30 -0500
commit74ba67edfcb235c0415a62d37493866c8380dc1d (patch)
treecadd766c992a8ac760443ecb25f4819123b9733b /tools
parent4e03185fb8e85d5624d3a68feced70cc9c9e2136 (diff)
downloadop-kernel-dev-74ba67edfcb235c0415a62d37493866c8380dc1d.zip
op-kernel-dev-74ba67edfcb235c0415a62d37493866c8380dc1d.tar.gz
iwlagn: Use iwl_write8() for CSR_INT_COALESCING register
CSR_INT_COALESCING previously had only one, but now has two single-byte fields. With only one single-byte field (lowest order byte) it was okay to write via iwl_write32(), but now with two, an iwl_write32() to the lower order field clobbers the other field (odd-address CSR_INT_PERIODIC_REG, offset 0x5), and an iwl_write32() to CSR_INT_PERIODIC_REG could clobber the lowest byte of the next-higher register (CSR_INT, offset 0x8). Fortunately, no bad side effects have been produced by the iwl_write32() usage, due to order of execution (low order byte was always written before higher order byte), and the fact that writing "0" to the low byte of the next higher register has no effect (only action is when writing "1"s). Nonetheless, this cleans up the accesses so no bad side effects might occur in the future, if execution order changes, or more bit fields get added to CSR_INT_COALESCING. Add some comments regarding periodic interrupt usage. Signed-off-by: Ben Cahill <ben.m.cahill@intel.com> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud