Re: [PATCH 0/4] OMAP 3 and 4 i2c fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



To summarize my comments on your series.

On 3/3/2011 2:50 PM, Andy Green wrote:
The following series fixes two issues with OMAP 3 and 4 i2c support.

First, hwmod tables don't have the i2c units marked up as being
for 16-bit access only, which is mandatory.

That part is OK, and should just be extended to 2430 for the sake of completeness. A rev attribute should be added as well for the second part.

Second, the i2c peripheral unit init code is confused about using
cpu_is...() and probed peripheral unit version, leading to OMAP3
i2c code doing the wrong thing and accessing nonexistant registers.

That part should be revisited to use a better way to identify the IP revision.

Most of the code is there, you just have to copy the correct information during I2C device init.

Just let me know if you are not comfortable with that latest part, some l-o folks, including me, can help you.

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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux