Santosh Shilimkar <[email protected]> writes: > cpu_class_is_omap2() contains all OMAP2+ devices. So update the DMA code > cpu checks accordingly so that there is no need to patch > the file for any future OMAP2+ devices. > > In long run, all these attributes should come from hwmod dev_attr based > on DMA IP version. > > Signed-off-by: Santosh Shilimkar <[email protected]> > --- > arch/arm/mach-omap2/dma.c | 2 +- > arch/arm/plat-omap/dma.c | 4 ++-- > 2 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/arch/arm/mach-omap2/dma.c b/arch/arm/mach-omap2/dma.c > index b19d849..2750bb9 100644 > --- a/arch/arm/mach-omap2/dma.c > +++ b/arch/arm/mach-omap2/dma.c > @@ -227,7 +227,7 @@ static int __init omap2_system_dma_init_dev(struct > omap_hwmod *oh, void *unused) > > dma_stride = OMAP2_DMA_STRIDE; > dma_common_ch_start = CSDP; > - if (cpu_is_omap3630() || cpu_is_omap44xx()) > + if (omap_rev() >= OMAP3630_REV_ES1_0)
It's not obvious (at least to me) that this is equivalent. For example, this will now be true on the TI81xx devices. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
