From: Arnd Bergmann <arnd@arndb.de> To: Kukjin Kim <kgene.kim@samsung.com> Cc: Olof Johansson <olof@lixom.net>, "linux-samsung-soc@vger.kernel.org" <linux-samsung-soc@vger.kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Ilho Lee <ilho215.lee@samsung.com>, Thomas Abraham <thomas.ab@samsung.com>, Kumar Gala <galak@codeaurora.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 2/3] arm64: Add Kconfig option for Samsung GH7 SoC family Date: Tue, 18 Feb 2014 11:53:49 +0100 [thread overview] Message-ID: <2152943.isBRrxZ7xx@wuerfel> (raw) In-Reply-To: <5302B306.8090503@samsung.com> On Tuesday 18 February 2014 10:10:30 Kukjin Kim wrote: > On 02/15/14 02:06, Arnd Bergmann wrote: > > On Thursday 13 February 2014, Olof Johansson wrote: > >> On Mon, Feb 10, 2014 at 6:52 PM, Kukjin Kim<kgene.kim@samsung.com> wrote: > >>> On 02/13/14 04:14, Arnd Bergmann wrote: > >>>> On Wednesday 12 February 2014 13:04:40 Kumar Gala wrote: > >>> Basically, I agreed with Arnd's suggestion to use ARCH_SBSA. Or we need to > >>> define level in Kconfig like ARCH_SBSA_L1 for level1. BTW, how about > >>> compliant with SBSA Level1 and having some specific features? > > > Well, how about ARMv8 mobile SoC? I think, it is not compatible with > SBSA. For example, you know MCT can be used for ARMv8 cores instead of > ARCH Timer. So I'm not sure ARCH_SBSA is really good choice... Sure, if you are talking about an embedded SoC that is not SBSA compliant, we shouldn't try to make it work with ARCH_SBSA and instead give it its own Kconfig symbol. > > My feeling is that we don't need to use the levels for Kconfig, although > > we might want to use them DT compatible strings, even if it ends up looking > > a little funny when you do > > > > compatible = "arm,sbsa-l3", "arm,sbsa-l2", "arm,sbsa-l1"; > > > >> What kind of features are you expecting though? More IP > >> blocks/devices? Those are just kernel config options to enable, > >> ideally as modules. > > > > Right, I think we can just put them into defconfig. No need to > > "select" them from Kconfig since the extra options wouldn't be > > required for booting or using the system. > > > As I commented above, how about MCT? Samsung has a plan to use MCT on > ARMv8, it is not for used for GH7 though... If it's just one driver that is needed in addition to the usual stuff, we can also just make it a standalone option and turn it on in the generic defconfig. We won't need a per-platform option in that case. Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/3] arm64: Add Kconfig option for Samsung GH7 SoC family Date: Tue, 18 Feb 2014 11:53:49 +0100 [thread overview] Message-ID: <2152943.isBRrxZ7xx@wuerfel> (raw) In-Reply-To: <5302B306.8090503@samsung.com> On Tuesday 18 February 2014 10:10:30 Kukjin Kim wrote: > On 02/15/14 02:06, Arnd Bergmann wrote: > > On Thursday 13 February 2014, Olof Johansson wrote: > >> On Mon, Feb 10, 2014 at 6:52 PM, Kukjin Kim<kgene.kim@samsung.com> wrote: > >>> On 02/13/14 04:14, Arnd Bergmann wrote: > >>>> On Wednesday 12 February 2014 13:04:40 Kumar Gala wrote: > >>> Basically, I agreed with Arnd's suggestion to use ARCH_SBSA. Or we need to > >>> define level in Kconfig like ARCH_SBSA_L1 for level1. BTW, how about > >>> compliant with SBSA Level1 and having some specific features? > > > Well, how about ARMv8 mobile SoC? I think, it is not compatible with > SBSA. For example, you know MCT can be used for ARMv8 cores instead of > ARCH Timer. So I'm not sure ARCH_SBSA is really good choice... Sure, if you are talking about an embedded SoC that is not SBSA compliant, we shouldn't try to make it work with ARCH_SBSA and instead give it its own Kconfig symbol. > > My feeling is that we don't need to use the levels for Kconfig, although > > we might want to use them DT compatible strings, even if it ends up looking > > a little funny when you do > > > > compatible = "arm,sbsa-l3", "arm,sbsa-l2", "arm,sbsa-l1"; > > > >> What kind of features are you expecting though? More IP > >> blocks/devices? Those are just kernel config options to enable, > >> ideally as modules. > > > > Right, I think we can just put them into defconfig. No need to > > "select" them from Kconfig since the extra options wouldn't be > > required for booting or using the system. > > > As I commented above, how about MCT? Samsung has a plan to use MCT on > ARMv8, it is not for used for GH7 though... If it's just one driver that is needed in addition to the usual stuff, we can also just make it a standalone option and turn it on in the generic defconfig. We won't need a per-platform option in that case. Arnd
next prev parent reply other threads:[~2014-02-18 10:54 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-11 6:29 [PATCH 0/3] arm64: add new support Samsung GH7 SoC and SSDK board Kukjin Kim 2014-02-11 6:29 ` Kukjin Kim 2014-02-11 6:29 ` [PATCH 1/3] arm64: dts: add initial dts for Samsung GH7 SoC and SSDK-GH7 board Kukjin Kim 2014-02-11 6:29 ` Kukjin Kim 2014-02-11 18:15 ` Mark Rutland 2014-02-11 18:15 ` Mark Rutland 2014-02-11 3:16 ` Kukjin Kim 2014-02-11 3:16 ` Kukjin Kim 2014-02-18 10:30 ` Mark Rutland 2014-02-18 10:30 ` Mark Rutland 2014-02-24 23:56 ` Kukjin Kim 2014-02-24 23:56 ` Kukjin Kim 2014-02-11 23:36 ` Olof Johansson 2014-02-11 23:36 ` Olof Johansson 2014-02-11 3:25 ` Kukjin Kim 2014-02-11 3:25 ` Kukjin Kim 2014-02-12 11:13 ` Marc Zyngier 2014-02-12 11:13 ` Marc Zyngier 2014-02-12 11:29 ` Mark Rutland 2014-02-12 11:29 ` Mark Rutland 2014-02-12 11:40 ` Marc Zyngier 2014-02-12 11:40 ` Marc Zyngier 2014-02-11 3:03 ` Kukjin Kim 2014-02-11 3:03 ` Kukjin Kim 2014-02-11 6:29 ` [PATCH 2/3] arm64: Add Kconfig option for Samsung GH7 SoC family Kukjin Kim 2014-02-11 6:29 ` Kukjin Kim 2014-02-11 23:39 ` Olof Johansson 2014-02-11 23:39 ` Olof Johansson 2014-02-12 10:38 ` Catalin Marinas 2014-02-12 10:38 ` Catalin Marinas 2014-02-12 16:25 ` Kumar Gala 2014-02-12 16:25 ` Kumar Gala 2014-02-12 18:12 ` Catalin Marinas 2014-02-12 18:12 ` Catalin Marinas 2014-02-12 19:04 ` Kumar Gala 2014-02-12 19:04 ` Kumar Gala 2014-02-12 19:14 ` Arnd Bergmann 2014-02-12 19:14 ` Arnd Bergmann 2014-02-11 2:52 ` Kukjin Kim 2014-02-11 2:52 ` Kukjin Kim 2014-02-13 19:26 ` Olof Johansson 2014-02-13 19:26 ` Olof Johansson 2014-02-14 17:06 ` Arnd Bergmann 2014-02-14 17:06 ` Arnd Bergmann 2014-02-18 1:10 ` Kukjin Kim 2014-02-18 1:10 ` Kukjin Kim 2014-02-18 10:53 ` Arnd Bergmann [this message] 2014-02-18 10:53 ` Arnd Bergmann 2014-02-18 16:16 ` Olof Johansson 2014-02-18 16:16 ` Olof Johansson 2014-02-18 18:13 ` Arnd Bergmann 2014-02-18 18:13 ` Arnd Bergmann 2014-02-18 19:52 ` John Stultz 2014-02-18 19:52 ` John Stultz 2014-02-18 20:00 ` Olof Johansson 2014-02-18 20:00 ` Olof Johansson 2014-02-18 20:06 ` John Stultz 2014-02-18 20:06 ` John Stultz 2014-02-20 9:03 ` Olof Johansson 2014-02-20 9:03 ` Olof Johansson 2014-02-20 11:22 ` Catalin Marinas 2014-02-20 11:22 ` Catalin Marinas 2014-02-20 12:07 ` Arnd Bergmann 2014-02-20 12:07 ` Arnd Bergmann 2014-02-20 17:09 ` Olof Johansson 2014-02-20 17:09 ` Olof Johansson 2014-02-20 18:58 ` Catalin Marinas 2014-02-20 18:58 ` Catalin Marinas 2014-02-25 0:19 ` Kukjin Kim 2014-02-25 0:19 ` Kukjin Kim 2014-02-25 0:20 ` Kukjin Kim 2014-02-25 0:20 ` Kukjin Kim 2014-02-25 0:10 ` Kukjin Kim 2014-02-25 0:10 ` Kukjin Kim 2014-02-18 16:40 ` Catalin Marinas 2014-02-18 16:40 ` Catalin Marinas 2014-02-13 20:08 ` Rob Herring 2014-02-13 20:08 ` Rob Herring 2014-02-13 20:19 ` Olof Johansson 2014-02-13 20:19 ` Olof Johansson 2014-02-11 6:29 ` [PATCH 3/3] Documentation: DT: add new entry for Samsung GH7 SoC and SSDK board Kukjin Kim 2014-02-11 6:29 ` Kukjin Kim
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=2152943.isBRrxZ7xx@wuerfel \ --to=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=galak@codeaurora.org \ --cc=ilho215.lee@samsung.com \ --cc=kgene.kim@samsung.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=olof@lixom.net \ --cc=thomas.ab@samsung.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.