From: Ben Dooks <ben@simtec.co.uk>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, rtc-linux@googlegroups.com,
p_gortmaker@yahoo.com, Atul Dahiya <atul.dahiya@samsung.com>,
ben-linux@fluff.org, a.zummo@towertech.it
Subject: Re: [PATCH 3/5] ARM: S5P6440: Add RTC support for S5P6440
Date: Wed, 28 Jul 2010 19:13:59 +0100 [thread overview]
Message-ID: <4C507367.1000206@simtec.co.uk> (raw)
In-Reply-To: <1279702814-14929-4-git-send-email-kgene.kim@samsung.com>
On 21/07/10 10:00, Kukjin Kim wrote:
> From: Atul Dahiya <atul.dahiya@samsung.com>
>
> This patch adds support RTC driver for Samsung S5P6440.
>
> Signed-off-by: Atul Dahiya <atul.dahiya@samsung.com>
> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> ---
> arch/arm/mach-s5p6440/Kconfig | 2 ++
> arch/arm/mach-s5p6440/include/mach/map.h | 2 +-
> arch/arm/mach-s5p6440/mach-smdk6440.c | 1 +
> 3 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-s5p6440/Kconfig b/arch/arm/mach-s5p6440/Kconfig
> index f066fae..b2d4716 100644
> --- a/arch/arm/mach-s5p6440/Kconfig
> +++ b/arch/arm/mach-s5p6440/Kconfig
> @@ -18,7 +18,9 @@ config MACH_SMDK6440
> select CPU_S5P6440
> select SAMSUNG_DEV_TS
> select SAMSUNG_DEV_ADC
> + select S3C_DEV_RTC
> select S3C_DEV_WDT
> + select HAVE_S3C_RTC
> select HAVE_S3C2410_WATCHDOG
> help
> Machine support for the Samsung SMDK6440
I'm considering we shoudl just set HAVE_S3C_RTC for
each SOC, as allowing it to compile isn't going to
end up causing a problem. Adding it to each machine
will end up with large Kconfig entries for each.
--
Ben
WARNING: multiple messages have this Message-ID (diff)
From: ben@simtec.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: S5P6440: Add RTC support for S5P6440
Date: Wed, 28 Jul 2010 19:13:59 +0100 [thread overview]
Message-ID: <4C507367.1000206@simtec.co.uk> (raw)
In-Reply-To: <1279702814-14929-4-git-send-email-kgene.kim@samsung.com>
On 21/07/10 10:00, Kukjin Kim wrote:
> From: Atul Dahiya <atul.dahiya@samsung.com>
>
> This patch adds support RTC driver for Samsung S5P6440.
>
> Signed-off-by: Atul Dahiya <atul.dahiya@samsung.com>
> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> ---
> arch/arm/mach-s5p6440/Kconfig | 2 ++
> arch/arm/mach-s5p6440/include/mach/map.h | 2 +-
> arch/arm/mach-s5p6440/mach-smdk6440.c | 1 +
> 3 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-s5p6440/Kconfig b/arch/arm/mach-s5p6440/Kconfig
> index f066fae..b2d4716 100644
> --- a/arch/arm/mach-s5p6440/Kconfig
> +++ b/arch/arm/mach-s5p6440/Kconfig
> @@ -18,7 +18,9 @@ config MACH_SMDK6440
> select CPU_S5P6440
> select SAMSUNG_DEV_TS
> select SAMSUNG_DEV_ADC
> + select S3C_DEV_RTC
> select S3C_DEV_WDT
> + select HAVE_S3C_RTC
> select HAVE_S3C2410_WATCHDOG
> help
> Machine support for the Samsung SMDK6440
I'm considering we shoudl just set HAVE_S3C_RTC for
each SOC, as allowing it to compile isn't going to
end up causing a problem. Adding it to each machine
will end up with large Kconfig entries for each.
--
Ben
next prev parent reply other threads:[~2010-07-28 18:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 9:00 [PATCH 0/5] Add RTC support SMDK6410, SMDKC100, SMDKC110 and SMDKV210 Kukjin Kim
2010-07-21 9:00 ` Kukjin Kim
2010-07-21 9:00 ` [PATCH 1/5] ARM: S3C64XX: Add RTC support for S3C64XX Kukjin Kim
2010-07-21 9:00 ` Kukjin Kim
2010-07-21 9:00 ` [PATCH 2/5] rtc: rtc-s3c: Add extra option to include RTC for Samsung SoCs Kukjin Kim
2010-07-21 9:00 ` Kukjin Kim
2010-07-21 9:00 ` [PATCH 3/5] ARM: S5P6440: Add RTC support for S5P6440 Kukjin Kim
2010-07-21 9:00 ` Kukjin Kim
2010-07-28 18:13 ` Ben Dooks [this message]
2010-07-28 18:13 ` Ben Dooks
2010-07-29 1:37 ` Kukjin Kim
2010-07-29 1:37 ` Kukjin Kim
2010-07-21 9:00 ` [PATCH 4/5] ARM: S5PC100: Add RTC support for S5PC100 Kukjin Kim
2010-07-21 9:00 ` Kukjin Kim
2010-07-21 9:00 ` [PATCH 5/5] ARM: S5PV210: Add RTC support for S5PV210 and S5PC110 Kukjin Kim
2010-07-21 9:00 ` 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=4C507367.1000206@simtec.co.uk \
--to=ben@simtec.co.uk \
--cc=a.zummo@towertech.it \
--cc=atul.dahiya@samsung.com \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
--cc=rtc-linux@googlegroups.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: link
Be 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.