> > + /* Append OMAP3 IDCODE, Production ID and Die ID to system_soc_info */ > > + sz = strlen(system_soc_info); > > + snprintf(system_soc_info + sz, SYSTEM_SOC_INFO_SIZE - sz, > > + "\n\tIDCODE\t: %08x\n\tPr. ID\t: %08x %08x %08x %08x\n" > > + "\tDie ID\t: %08x %08x %08x %08x\n", > > + read_tap_reg(OMAP_TAP_IDCODE), > > + read_tap_reg(OMAP_TAP_PROD_ID_0), > > + read_tap_reg(OMAP_TAP_PROD_ID_1), > > + read_tap_reg(OMAP_TAP_PROD_ID_2), > > + read_tap_reg(OMAP_TAP_PROD_ID_3), > > + read_tap_reg(OMAP_TAP_DIE_ID_0), > > + read_tap_reg(OMAP_TAP_DIE_ID_1), > > + read_tap_reg(OMAP_TAP_DIE_ID_2), > > + read_tap_reg(OMAP_TAP_DIE_ID_3)); > > } > Just a query here. > Since we have already code to decode all above information > And convert it into a meaningful data like , OMAP3430 ES2.0 , OMAP3630 ES1.0 > , OMAP4430 ES1.0 etc. > > Can we export that itself. Ofcourse with above data also some one can refer TRM > and do the decoding. > Ignore the previous comment since looks like you are already doing that. Regards, Santosh -- 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
