From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 11/12] ARM: EXYNOS: add support device tree enabled board file for EXYNOS5
Date: Wed, 14 Mar 2012 15:37:15 -0700 [thread overview]
Message-ID: <20120314223715.GA13872@quad.lixom.net> (raw)
In-Reply-To: <1331736138-28964-12-git-send-email-kgene.kim@samsung.com>
On Wed, Mar 14, 2012 at 07:42:17AM -0700, Kukjin Kim wrote:
> This patch adds a new EXYNOS5 compatible device tree enabled board
> When using this, a corresponding device tree blob which describes the
> board's properties should be supplied at boot time to the kernel.
Hi,
Sorry, missed this last time around:
> diff --git a/arch/arm/mach-exynos/Kconfig b/arch/arm/mach-exynos/Kconfig
> index a2ed05c..ac24386 100644
> --- a/arch/arm/mach-exynos/Kconfig
> +++ b/arch/arm/mach-exynos/Kconfig
> @@ -362,7 +362,18 @@ config MACH_SMDK4412
> Machine support for Samsung SMDK4412
> endif
>
> -comment "Flattened Device Tree based board for Exynos4 based SoC"
> +if ARCH_EXYNOS5
> +
> +comment "EXYNOS5250 Boards"
> +
> +config MACH_SMDK5250
> + bool "SMDK5250"
> + select SOC_EXYNOS5250
> + help
> + Machine support for Samsung SMDK5250
> +endif
There's no board file for SMDK5250 in this series (and there shouldn't be since
it should all be covered by MACH_EXYNOS5_DT. So the above config option can go
away.
-Olof
next prev parent reply other threads:[~2012-03-14 22:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 14:42 [PATCH v4 00/12] ARM: EXYNOS: add support new EXYNOS5250 Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 01/12] ARM: EXYNOS: to declare static for mach-exynos/common.c Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 02/12] ARM: EXYNOS: use exynos_init_uarts() instead of exynos4_init_uarts() Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 03/12] ARM: EXYNOS: add clock part for EXYNOS5250 SoC Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 04/12] ARM: EXYNOS: add initial setup-i2c0 for EXYNOS5 Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 05/12] ARM: EXYNOS: add support uart for EXYNOS4 and EXYNOS5 Kukjin Kim
2012-03-21 9:13 ` Thomas Abraham
2012-03-21 10:45 ` Marek Szyprowski
2012-03-22 14:08 ` Kukjin Kim
2012-03-22 15:31 ` Marek Szyprowski
2012-03-26 14:12 ` Thomas Abraham
2012-03-29 2:05 ` Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 06/12] ARM: EXYNOS: add support for EXYNOS5250 SoC Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 07/12] ARM: EXYNOS: add interrupt definitions for EXYNOS5250 Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 08/12] ARM: EXYNOS: support EINT for EXYNOS4 and EXYNOS5 Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 09/12] ARM: EXYNOS: add support get_core_count() for EXYNOS5250 Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 10/12] ARM: EXYNOS: add support ARCH_EXYNOS5 for EXYNOS5 SoCs Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 11/12] ARM: EXYNOS: add support device tree enabled board file for EXYNOS5 Kukjin Kim
2012-03-14 22:37 ` Olof Johansson [this message]
2012-03-14 23:18 ` Kukjin Kim
2012-03-14 14:42 ` [PATCH v4 12/12] ARM: dts: add initial dts file for EXYNOS5250, SMDK5250 Kukjin Kim
2012-03-14 22:40 ` [PATCH v4 00/12] ARM: EXYNOS: add support new EXYNOS5250 Olof Johansson
2012-03-14 23:20 ` 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=20120314223715.GA13872@quad.lixom.net \
--to=olof@lixom.net \
--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