Searched refs:generations (Results 1 – 11 of 11) sorted by relevance
14 Tegra generations later than Tegra30 the compatible value should
13 available in later generations such as fab code, lot code, wafer id,..
5 Mediatek SMI have two generations of HW architecture, here is the list
1708 cdm->pos.generations[CAM_BUS_GENERATION]= in xptedtbusfunc()1741 if ((cdm->pos.generations[CAM_TARGET_GENERATION] != in xptedtbusfunc()1777 if (cdm->pos.generations[CAM_DEV_GENERATION] != in xptedttargetfunc()1842 cdm->pos.generations[CAM_BUS_GENERATION]= in xptedtdevicefunc()1845 cdm->pos.generations[CAM_TARGET_GENERATION] = in xptedtdevicefunc()1848 cdm->pos.generations[CAM_DEV_GENERATION] = in xptedtdevicefunc()1901 if (cdm->pos.generations[CAM_PERIPH_GENERATION] != in xptedtdevicefunc()1956 cdm->pos.generations[CAM_BUS_GENERATION]= in xptedtperiphfunc()1959 cdm->pos.generations[CAM_TARGET_GENERATION] = in xptedtperiphfunc()1962 cdm->pos.generations[CAM_DEV_GENERATION] = in xptedtperiphfunc()[all …]
556 u_int generations[4]; member
4 this M4U have two generations of HW architecture. Generation one uses flat
242 // Patterns for optimizing code generations for HVX.
222 // Encoding changes between subtarget generations.
529 This allows new file generations to be activated simply
263 This allows new file generations to be activated simply
7820 of size_t on 32-bit versus 64-bit generations. Lin Ming.