linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: krzk@kernel.org (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 3/8] ARM64: EXYNOS: enable exynos_chipid for ARCH_EXYNOS
Date: Fri, 16 Dec 2016 19:38:50 +0200	[thread overview]
Message-ID: <20161216173850.GB3746@kozik-lap> (raw)
In-Reply-To: <1481375323-29724-4-git-send-email-pankaj.dubey@samsung.com>

On Sat, Dec 10, 2016 at 06:38:38PM +0530, Pankaj Dubey wrote:
> This patch enables exynos_chipid driver for ARCH_EXYNOS
> based SoC.
> 
> Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> ---
>  arch/arm64/Kconfig.platforms | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 72f4eac..e6aa5c2 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -53,6 +53,7 @@ config ARCH_BRCMSTB
>  
>  config ARCH_EXYNOS
>  	bool "ARMv8 based Samsung Exynos SoC family"
> +	select EXYNOS_CHIPID

You allowed CHIPID only on ARMv7, not ARMv8.

Best regards,
Krzysztof

>  	select COMMON_CLK_SAMSUNG
>  	select HAVE_S3C2410_WATCHDOG if WATCHDOG
>  	select HAVE_S3C_RTC if RTC_CLASS
> -- 
> 2.7.4
> 

  reply	other threads:[~2016-12-16 17:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20161210130616epcas1p2ce44d503ae03854e7b36b4d37d54900a@epcas1p2.samsung.com>
2016-12-10 13:08 ` [PATCH v8 0/8] Introducing Exynos ChipId driver Pankaj Dubey
2016-12-10 13:08   ` [PATCH v8 1/8] soc: samsung: add exynos chipid driver support Pankaj Dubey
2016-12-16 17:37     ` Krzysztof Kozlowski
2016-12-17  4:06       ` Pankaj Dubey
2016-12-17 12:03         ` Krzysztof Kozlowski
2016-12-19 11:59     ` Markus Reichl
2016-12-19 13:29       ` pankaj.dubey
2016-12-19 18:03         ` Krzysztof Kozlowski
2016-12-21  7:52           ` pankaj.dubey
2016-12-21 14:08     ` Andrzej Hajda
     [not found]     ` <CGME20161227140255epcas1p1a2c2b50ede0e9b2378c8ac052b1617f6@epcas1p1.samsung.com>
2016-12-27 14:02       ` Bartlomiej Zolnierkiewicz
2016-12-28  2:38         ` Pankaj Dubey
2016-12-10 13:08   ` [PATCH v8 2/8] ARM: EXYNOS: enable exynos_chipid for ARCH_EXYNOS Pankaj Dubey
2016-12-16 18:04     ` Krzysztof Kozlowski
2016-12-17  4:15       ` Pankaj Dubey
2016-12-10 13:08   ` [PATCH v8 3/8] ARM64: " Pankaj Dubey
2016-12-16 17:38     ` Krzysztof Kozlowski [this message]
2016-12-10 13:08   ` [PATCH v8 4/8] ARM: EXYNOS: refactor firmware specific routines Pankaj Dubey
2016-12-16 18:25     ` Krzysztof Kozlowski
2016-12-17  3:50       ` Pankaj Dubey
2016-12-10 13:08   ` [PATCH v8 5/8] ARM: EXYNOS: refactor power management " Pankaj Dubey
2016-12-17 14:54     ` Krzysztof Kozlowski
2016-12-10 13:08   ` [PATCH v8 6/8] ARM: EXYNOS: remove secondary startup initialization from smp_prepare_cpus Pankaj Dubey
2016-12-17 18:48     ` Krzysztof Kozlowski
2016-12-17 22:06       ` Chanwoo Choi
2016-12-10 13:08   ` [PATCH v8 7/8] ARM: EXYNOS: refactor smp specific code and routines Pankaj Dubey
2016-12-17 18:59     ` Krzysztof Kozlowski
2016-12-10 13:08   ` [PATCH v8 8/8] ARM: EXYNOS: refactor of mach-exynos to use chipid information Pankaj Dubey
2016-12-17 19:03     ` Krzysztof Kozlowski
2016-12-16 13:11   ` [PATCH v8 0/8] Introducing Exynos ChipId driver Marek Szyprowski
2016-12-19 13:25     ` pankaj.dubey

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=20161216173850.GB3746@kozik-lap \
    --to=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).