On 3/3/2011 6:56 PM, Andy Green wrote:
On 03/03/2011 05:42 PM, Somebody in the thread at some point said:
On 3/3/2011 2:50 PM, Andy Green wrote:
Hi -
Thanks for the reply.
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]
Well, in that case, it is more a QEMU bug since the HW is working fine
with 32 bits access to sysconfig :-)
Actually it's documented in TI documentation, as noted:
>> [1] OMAP4430 Technical reference manual section 23.1.6.2
>> [2] OMAP3530 Techincal reference manual section 18.6
With the following warning in a nice big grey box -->
''CAUTION
The I2Ci registers are limited to 16 bit and 8 bit data accesses, 32 bit
data access is not allowed and can corrupt register content.''
So, as a side-issue it can be worth confirming with the author of the
warning if it still holds or not and letting Qemu guys know if it's not
actually true what is written in the TI docs about that.
I was able to check for OMAP4, and in fact since the I2C bus is using
only the 16 LSB of the 32 bits interconnect, doing 32 bits access is
harmless.
But OMAP2 & 3 were using a different interconnect, so it was probably
not done like that, hence the big CAUTION in the TRM.
In fact that flag was added because 32 bits access to I2C sysconfig was
generating bus abort on 2420 only:
(2004290f55f03c52e22044a5843928cf0f6cc56a).
Since 2430, OMAP3 and OMAP4 are working fine with 32 bits, we were lazy
and didn't add that flag.
There is no bus abort. However if the warning in the documentation is
true, it'd be better that there was a bus abort.
Did you check this patch on a real HW? Since this was reported using
QEMU only.
I checked my patched code works OK on both IGEP2 (OMAP3) and Panda
(OMAP4), there's no visible symptom without the patch it's true.
Even if starting from OMAP4 generation we can do 32 bits access, since
the whole IP is documented with 16 bits registers, it is cleaner to
prevent hwmod access in 32 bits.
I will still report that to the TRM team in order to avoid unnecessary
scary notes.
Otherwise, I'm fine with that patch, it will not change anything but
will improve the consistency across SoC version.
BTW, It will be good if you could update the omap_hwmod_2430_data.c file
as well.
I left it because I can't test it, but I'll happily do it additionally
if you can test it on some OMAP2 hardware.
Don't hesitate to do it, and clearly add in the cover-letter that it was
tested on 3430 and 4430 only.
Someone from TI should be able to test it on 2430.
Thanks,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
