Re: Adding new ARC platforms (was Re: Handling stub code for new platforms)

2017-08-13 Thread Vineet Gupta

On 08/11/2017 10:55 PM, Alexandru Gagniuc wrote:

Does that work for you ?


I was hoping to avoid the addition of extra source files for zero code gain, 
though your proposal does work. However, since the platform would be added 
unconditionally, would it make more sense to add the

.compatible = "adaptrum,anarion"
binding to plat-nsim instead of creating new files?


Yeah that is indeed better.

But we have a convention to name SoC binding starting with arc-*.
Look at other ARC SoC bindings.

-Vineet

___
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc


Re: Adding new ARC platforms (was Re: Handling stub code for new platforms)

2017-08-13 Thread Vineet Gupta

On 08/11/2017 10:55 PM, Alexandru Gagniuc wrote:
I was hoping to avoid the addition of extra source files for zero code gain, 
though your proposal does work. However, since the platform would be added 
unconditionally, would it make more sense to add the

.compatible = "adaptrum,anarion"


Actual Abilis TB10x is similar in terms of need for special platform callbacks, 
but they do need Kconfig glue to pull in bunch of drivers, your platform doesn't ?


-Vineet

___
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc