> -----Original Message----- > From: Paul Walmsley [mailto:paul@xxxxxxxxx] > Sent: Tuesday, September 13, 2011 11:33 PM > To: Premi, Sanjeev > Cc: notasas@xxxxxxxxx; tony@xxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx > Subject: OMAP3505 revisions? > > > Hi Sanjeev > > Am looking at your commit 4cac6018, which touches > arch/arm/mach-omap2/id.c. That commit implements SoC > detection for the > 3505 in a different way than the implementations for other > OMAP2+ devices: > it doesn't enumerate the possible TAP revisions for OMAP3505. > The TRM Paul, In the function omap3_check_revision(), the revision is being extracted from the TAP register for AM3505/AM3517 devices thru same code used for OMAP34xx registers. OR, Am I missing something? ~sanjeev > doesn't seem to list those, either. And unfortunately that > is blocking > some of the omap_chip removal work. > > Could you send me a list of the possible revision values for the > 3505/3517, along with mappings to ES levels, please? > > thanks > > - Paul > -- 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
