On Thu, 2010-08-05 at 09:06 +0200, ext Taneja, Archit wrote: > Hi, > > > > > Also, we should think how to reduce if (cpu_is_omap44xx()) > > lines. There should be some kind of DSS capability list > > somewhere, which would tell the features available. I haven't > > thought this more, but it'd be very nice if we could use the > > DSS HW version number to decide what features there are. > > > > However, TI answered that information about DSS HW version > > numbers is not available, and thus cannot be used =(. Perhaps > > you could try to dig out some information from inside TI? > > > > I read the DSS_REVISON, DISPC_REVISION etc registers on 3430, 3630, 4430: > > 3430: DSS rev 2.0, DISPC rev 3.0, RFBI rev 1.0, DSI rev 1.0, VENC rev 2 > 3630: DSS rev 2.0, DISPC rev 3.0, RFBI rev 1.0, DSI rev 1.0, VENC rev 2 > 4430: DSS rev 4.0, DISPC rev 4.0, DSI rev 3.0, RFBI rev 3.5 > > I haven't tried on OMAP2 yet.. > > Don't you think these revision numbers are enough to differentiate the > features of each IP block? Perhaps. The problem is, I don't know what the version numbers mean, ie. when are they changed, what are the changes. I would hope you that you could find some internal info inside TI that would explain the differences =). We can of course reverse engineer the version numbers, and hope that we decipher them correctly. For OMAP3430/3630/4430 the differences look clear. But how about OMAP rev changes? For example, at some 3430 revision the bitfield lengths of video timing registers were changed. Does it show on DSS/DISPC version numbers? I don't think I have boards with those revs, so I can't check. Tomi -- 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
