Paul Walmsley <paul@xxxxxxxxx> writes: > These patches add several OMAP3430 ES2 clocks and clock rates. To do > so in a way that works on either ES1 or ES2 at runtime, we need to > specially mark the clocks and rates that are specific to one or the > other revision. This allows us to skip configuring those clocks at > boot. > > This series has been updated to apply cleanly against e8bf9d5, which > involved changing the MMC3 struct clks to match the latest MMCHS driver > changes. > > Vikram Pandita <vikram.pandita@xxxxxx> found a bug in an earlier > version; also, Kevin Hilman <khilman@xxxxxxxxxx> boot-tested an > earlier version of this patch set on 3430ES2. Thanks to both Vikram > and Kevin. > > Boot-tested on 3430SDP ES1. Unfortunately, still no 3430ES2 here, > so any testing that ES2 users can provide is quite welcome. Still OK on my ES2 (and ES1 for that matter.) However, I still also need a fix you sent a while back for the wait-for-ready problems I was seeing in the DM timer code. I'm not seeing that on a boot of the vanilla OMAP git + your patches, but in my tree where I also have the -rt patch, kgdb, etc., I'm seeing the faults during DM timer init. Kevin - 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
