Re: [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration

[Denys Dmytriyenko <denys@ti.com>]

On Tue, Mar 19, 2013 at 03:29:55PM -0400, Maupin, Chase wrote:
> > -----Original Message-----
> > From: Dmytriyenko, Denys
> > Sent: Tuesday, March 19, 2013 12:13 PM
> > To: Maupin, Chase
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [PATCH 2/2] omap5-evm: Add OMAP5 EVM
> > configuration
> > 
> > On Tue, Mar 19, 2013 at 10:10:41AM -0500, Chase Maupin wrote:
> > > * Add the machine configuration for the OMAP5 EVM device.
> > 
> > Overall looks good.
> > 
> > > * Create the omap-a15.inc file to be shared with all Cortex-A15
> > >   derivative devices.
> > 
> > Is the omap-a15 a preferred name? I didn't see it used internally
> > anywhere.
> > It's not like I object specifically to this name, but was
> > wondering if there
> > was something else other people are more familiar with? Another
> > option would
> > be just simple "omap5", but I guess you are planning for few of
> > those new
> > derivative platforms that don't really have omap5 in the name...
> > :)
> > 
> > Moreover, the comment above implies omap-a15 SoC file will be
> > used for all
> > Cortex-A15 devices, which is not exactly correct, as Keystone has
> > nothing to
> > do with omap5 and shouldn't share that SoC file.
> 
> Good point.  I'll change the comment.  I was thinking of this because of the 
> DRA7xx.  I'm open to other SOC_FAMILY names though.

The more I think about it, the more omap-a15 feels appropriate - basically 
highlighting and grouping OMAP-drived Cortex-A15 SoCs. Just make sure the 
comment makes it clear, as there are other non-OMAP Cortex-A15 SoCs from TI.

-- 
Denys