public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Nishanth Menon <nm@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Sekhar Nori <nsekhar@ti.com>, Rob Herring <robh+dt@kernel.org>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/4] arm64: Initial support for Texas Instrument's J7200 Platform
Date: Tue, 8 Sep 2020 12:55:29 +0300	[thread overview]
Message-ID: <d89cf38a-da57-b1ca-dc80-0c2cca2ada38@ti.com> (raw)
In-Reply-To: <20200907234833.r376hhl64q55gd7o@akan>

On 08/09/2020 02:48, Nishanth Menon wrote:
> On 19:53-20200907, Lokesh Vutla wrote:
> 
> [... I should have responded to the correct patch..]
>>> Besides yaml and compatibility acks, there are a few ancillary
>>> comments to fix up.. Kconfig -> I think we should either stay with
>>> status quo and create a new config option per SoC OR rename the
>>> config to be generic (using j7200 with j721e SoC config is not very
>>
>> Please suggest your preference here. I guess separate defconfig for J7200?
> 
> 
> I was just scanning through remaining arm64 additions to see what others have
> done. We seem to have two options here:
> a) Just use ARCH_K3 and no specific SoC configs
> b) Specific SoC configs
> In both cases, use += instead of \ to incrementally add dtbs
> 
> We have been going with (b) so far, Tero: any specific preference here?
> 
> (a) has the aspect of simplicity and reduced dependencies.
> (b) Allows downstream kernels to save just a little bit and focus purely
>      on SoC of interest.

If possible, I think we should aim for a) at least for now. We have the 
soc type detection code in place anyways that can be used on driver 
level. Creating compile time flags should be avoided imo as much as 
possible and just go with runtime detection. I can't see why saving 
maybe a megabyte of memory with SoC specific kernels would be of any 
importance on K3 arch with the memory amounts we have in our disposal.

-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-09-08  9:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27  6:51 [PATCH v2 0/4] arm64: Initial support for Texas Instrument's J7200 Platform Lokesh Vutla
2020-08-27  6:51 ` [PATCH v2 1/4] dt-bindings: arm: ti: Convert K3 board/soc bindings to DT schema Lokesh Vutla
2020-08-28  0:41   ` Nishanth Menon
2020-08-28  3:14     ` Lokesh Vutla
2020-08-28  3:47       ` Suman Anna
2020-08-28 13:07       ` Nishanth Menon
2020-09-04 11:55       ` Nishanth Menon
2020-09-04  7:15   ` Lokesh Vutla
2020-08-27  6:51 ` [PATCH v2 2/4] dt-bindings: arm: ti: Add bindings for J7200 SoC Lokesh Vutla
2020-08-27  6:51 ` [PATCH v2 3/4] arm64: dts: ti: Add support " Lokesh Vutla
2020-08-27 17:04   ` Suman Anna
2020-09-08 11:47     ` Nishanth Menon
2020-08-31  9:13   ` Peter Ujfalusi
2020-09-02  3:51     ` Lokesh Vutla
2020-08-27  6:51 ` [PATCH v2 4/4] arm64: dts: ti: Add support for J7200 Common Processor Board Lokesh Vutla
2020-09-08 11:57   ` Nishanth Menon
2020-08-27  9:09 ` [PATCH v2 0/4] arm64: Initial support for Texas Instrument's J7200 Platform Grygorii Strashko
2020-09-07 12:02 ` Lokesh Vutla
2020-09-07 14:14   ` Nishanth Menon
2020-09-07 14:23     ` Lokesh Vutla
2020-09-07 23:48       ` Nishanth Menon
2020-09-08  9:55         ` Tero Kristo [this message]
2020-09-08 11:25           ` Nishanth Menon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d89cf38a-da57-b1ca-dc80-0c2cca2ada38@ti.com \
    --to=t-kristo@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox