why is this 2600? omap3 could do 3.3Mhz.
There is a silicon issue reported on TWL5030 which says that it can
not operate at the stipulated highest frequency of 3.3MHz.
The information I got is this:
I2C data hold time in HS mode is higher than specification when
reading I2C registers. This
IMO, The regs do not need to move to a separate header unless they will
be used outside of i2c-omap.c.
Would it not be cleaner to move them to a separate header file,
especially considering the fact that we have some 19 registers for
OMAP3 I2C and when we redefine them for OMAP4, there would be
assuming that Ben has picked up this for his
queue, so not adding it to any of my ustream queues.
Acked-by: Tony Lindgren t...@atomide.com
Regards,
Tony
Is this patch applied?
--
With Regards,
Jagadeesh Bhaskar Pakaravoor
--
To unsubscribe from this list: send the line unsubscribe linux-omap
The i2c_driver in twl4030-core.c and platform_driver of twl4030-usb.c
both has the name twl4030_driver. This leads to unnecessary confusion.
So rename the usb platform_driver appropriately to:
twl4030_usb_driver.
Signed-off-by: Jagadeesh Bhaskar Pakaravoor [EMAIL PROTECTED]
Index: linux-omap-git
