diff options
author | Andy Green <[email protected]> | 2011-07-10 05:27:14 -0600 |
---|---|---|
committer | Paul Walmsley <[email protected]> | 2011-07-10 05:27:14 -0600 |
commit | 3e6005221138bcfc08f1a35b6f9e43b53330e851 (patch) | |
tree | 276a76ad11a879d5df020a8eceb1839ae6449a3d /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | da7cdfac1b0c58d6863532dd3b432c3fbc034978 (diff) |
I2C: OMAP2+: Set hwmod flags to only allow 16-bit accesses to i2c
Peter Maydell noticed when running under QEMU he was getting
errors reporting 32-bit access to I2C peripheral unit registers
that are documented to be 8 or 16-bit only[1][2]
The I2C driver is blameless as it wraps its accesses in a
function using __raw_writew and __raw_readw, it turned out it
is the hwmod stuff.
However the hwmod code already has a flag to force a
perhipheral unit to only be accessed using 16-bit operations.
This patch applies the 16-bit only flag to the 2430,
OMAP3xxx and OMAP44xx hwmod structs. 2420 was already
correctly marked up as 16-bit.
The 2430 change will need testing by TI as arranged
in the comments to the previous patch version.
When the 16-bit flag is or-ed with other flags, it is placed
first as requested in comments.
[1] OMAP4430 Technical reference manual section 23.1.6.2
[2] OMAP3530 Techincal reference manual section 18.6
Cc: [email protected]
Cc: Ben Dooks <[email protected]>
Reported-by: Peter Maydell <[email protected]>
Signed-off-by: Andy Green <[email protected]>
Signed-off-by: Tony Lindgren <[email protected]>
Signed-off-by: Kevin Hilman <[email protected]>
Signed-off-by: Paul Walmsley <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions