| Message ID | 1411637529-18289-4-git-send-email-lokeshvutla@ti.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
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.
On Thursday 25 September 2014 08:41 PM, Felipe Balbi wrote: > 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. Ok..will update it and repost. Thanks and regards, Lokesh > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
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 help Say "yes" here to support the on chip real time clock - present on TI OMAP1, AM33xx and DA8xx/OMAP-L13x. + present on TI OMAP1, AM33xx, DA8xx/OMAP-L13x, AM43xx and DRA7xx. This driver can also be built as a module, if so, module will be called rtc-omap. diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c index 93c5424..f28f1fd 100644 --- a/drivers/rtc/rtc-omap.c +++ b/drivers/rtc/rtc-omap.c @@ -1,5 +1,5 @@ /* - * TI OMAP1 Real Time Clock interface for Linux + * TI OMAP Real Time Clock interface for Linux * * Copyright (C) 2003 MontaVista Software, Inc. * Author: George G. Davis <gdavis@mvista.com> or <source@mvista.com> @@ -25,7 +25,7 @@ #include <linux/pm_runtime.h> #include <linux/io.h> -/* The OMAP1 RTC is a year/month/day/hours/minutes/seconds BCD clock +/* The OMAP RTC is a year/month/day/hours/minutes/seconds BCD clock * with century-range alarm matching, driven by the 32kHz clock. * * The main user-visible ways it differs from PC RTCs are by omitting