Re: [PATCH] omap: Fix 35xx detection (Re: [PATCH] [RFC] omap: 3630: default cpu_is_omap3630 to zero)

[Nishanth Menon <nm@ti.com>]

Tony Lindgren had written, on 10/13/2009 12:32 PM, the following:
> * Tony Lindgren <tony@atomide.com> [091013 10:18]:
>> * Vikram Pandita <vikram.pandita@ti.com> [091012 14:31]:
>>> make default cpu_is_omap3630() return zero
>>>
>>> Signed-off-by: Vikram Pandita <vikram.pandita@ti.com>
>>> ---
>>>  arch/arm/plat-omap/include/mach/cpu.h |    2 ++
>>>  1 files changed, 2 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/arch/arm/plat-omap/include/mach/cpu.h b/arch/arm/plat-omap/include/mach/cpu.h
>>> index da9e8f8..940946e 100644
>>> --- a/arch/arm/plat-omap/include/mach/cpu.h
>>> +++ b/arch/arm/plat-omap/include/mach/cpu.h
>>> @@ -322,6 +322,7 @@ IS_OMAP_TYPE(3430, 0x3430)
>>>  #define cpu_is_omap2423()		0
>>>  #define cpu_is_omap2430()		0
>>>  #define cpu_is_omap3430()		0
>>> +#define cpu_is_omap3630()		0
>>>  
>>>  /*
>>>   * Whether we have MULTI_OMAP1 or not, we still need to distinguish
>>> @@ -386,6 +387,7 @@ IS_OMAP_TYPE(3430, 0x3430)
>>>  						(omap3_has_sgx()) &	\
>>>  						(!omap3_has_iva()))
>>>  # define cpu_is_omap3530		(cpu_is_omap3430())
>>> +# undef cpu_is_omap3630()
>>>  # define cpu_is_omap3630()		is_omap363x()
wondering what the standard is:
  # define cpu_is_omap3430()		is_omap3430()
so is it
  #define cpu_is_omapXXXX() 		blah blah
or
  #define cpu_is_omapXXXX		blah blah
would have though it is  cpu_is_omapXXXX()

Regards,
Nishanth Menon