From: Felipe Balbi <balbi@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: a.zummo@towertech.it, rtc-linux@googlegroups.com,
devicetree@vger.kernel.org, tony@atomide.com, j-keerthy@ti.com,
nsekhar@ti.com, balbi@ti.com, t-kristo@ti.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/4] rtc: omap: Update Kconfig for OMAP RTC
Date: Thu, 25 Sep 2014 10:11:18 -0500 [thread overview]
Message-ID: <20140925151117.GL28045@saruman> (raw)
In-Reply-To: <1411637529-18289-4-git-send-email-lokeshvutla@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 1153 bytes --]
On Thu, Sep 25, 2014 at 03:02:08PM +0530, Lokesh Vutla wrote:
> From: Tero Kristo <t-kristo@ti.com>
>
> RTC is present in AM43xx and DRA7xx also. Updating the
> same in Kconfig.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
> Changes since v1:
> - New patch
> drivers/rtc/Kconfig | 6 +++---
> drivers/rtc/rtc-omap.c | 4 ++--
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
> index a168e96..b092e2f 100644
> --- a/drivers/rtc/Kconfig
> +++ b/drivers/rtc/Kconfig
> @@ -971,11 +971,11 @@ config RTC_DRV_IMXDI
> will be called "rtc-imxdi".
>
> config RTC_DRV_OMAP
> - tristate "TI OMAP1"
> - depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX
> + tristate "TI OMAP Real Time Clock"
> + depends on ARCH_OMAP15XX || ARCH_OMAP16XX || ARCH_OMAP730 || ARCH_DAVINCI_DA8XX || SOC_AM33XX || SOC_DRA7XX || SOC_AM43XX
do you mind if we just make this "depends on ARCH_OMAP || ARCH_DAVINCI" ? Pretty much
every incarnation has this anyway.
--
balbi
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-09-25 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 9:32 [PATCH v2 0/4] rtc: omap: Add support for regulator supply Lokesh Vutla
2014-09-25 9:32 ` [PATCH v2 1/4] rtc: omap: Introduce rtc_omap_dev structure to include per device data Lokesh Vutla
2014-10-08 17:36 ` Johan Hovold
2014-09-25 9:32 ` [PATCH v2 2/4] rtc: omap: Adopt driver to support probe deferral Lokesh Vutla
2014-10-08 17:38 ` Johan Hovold
2014-09-25 9:32 ` [PATCH v2 3/4] rtc: omap: Update Kconfig for OMAP RTC Lokesh Vutla
2014-09-25 15:11 ` Felipe Balbi [this message]
2014-09-29 5:25 ` Lokesh Vutla
2014-09-29 5:25 ` [PATCH v3 " Lokesh Vutla
2014-09-29 14:44 ` Felipe Balbi
2014-09-25 9:32 ` [PATCH v2 4/4] rtc: omap: Support regulator supply for RTC Lokesh Vutla
2014-10-08 17:40 ` Johan Hovold
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=20140925151117.GL28045@saruman \
--to=balbi@ti.com \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=rtc-linux@googlegroups.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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 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).