Re: [patch 2.6.19-git] RTC Kconfig sorted by type
> > +if RTC_CLASS != n > > + > > > if RTC_CLASS > > > because otherwise Thanks for the clarification. I think Alessandro was going to redo this one soon, since the Kconfig changed so much the patch would no longer apply. I trust he'll remember your comments! - Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.19-git] RTC Kconfig sorted by type
On Wed, Dec 06, 2006 at 04:52:44PM -0800, David Brownell wrote: > This reorders the RTC driver menu into separate sections, splitting out > the SOC, I2C, and SPI support to help make the menu easier to navigate. > (We got some feedback a while ago that it was "a mess" and hard to make > sense of...) > > Signed-off-by: David Brownell <[EMAIL PROTECTED]> > > --- > Assumes the rtc-omap patch has been merged, and no other RTC drivers > have been added to this Kconfig menu. > > Index: at91/drivers/rtc/Kconfig > === > --- at91.orig/drivers/rtc/Kconfig 2006-12-05 03:25:20.0 -0800 > +++ at91/drivers/rtc/Kconfig 2006-12-05 03:46:53.0 -0800 > @@ -1,4 +1,4 @@ > -\# > +# > # RTC class/drivers configuration > # > > @@ -20,6 +20,8 @@ config RTC_CLASS > This driver can also be built as a module. If so, the module > will be called rtc-class. > > +if RTC_CLASS != n > + if RTC_CLASS because otherwise > config RTC_HCTOSYS > bool "Set system time from RTC on startup" > depends on RTC_CLASS = y > @@ -45,11 +47,10 @@ config RTC_DEBUG > and individual RTC drivers. > > comment "RTC interfaces" > - depends on RTC_CLASS > > config RTC_INTF_SYSFS > tristate "sysfs" > - depends on RTC_CLASS && SYSFS > + depends on SYSFS >... RTC_CLASS=m, RTC_INTF_SYSFS=y would be an allowed configuration. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.19-git] RTC Kconfig sorted by type
On Wed, Dec 06, 2006 at 04:52:44PM -0800, David Brownell wrote: This reorders the RTC driver menu into separate sections, splitting out the SOC, I2C, and SPI support to help make the menu easier to navigate. (We got some feedback a while ago that it was a mess and hard to make sense of...) Signed-off-by: David Brownell [EMAIL PROTECTED] --- Assumes the rtc-omap patch has been merged, and no other RTC drivers have been added to this Kconfig menu. Index: at91/drivers/rtc/Kconfig === --- at91.orig/drivers/rtc/Kconfig 2006-12-05 03:25:20.0 -0800 +++ at91/drivers/rtc/Kconfig 2006-12-05 03:46:53.0 -0800 @@ -1,4 +1,4 @@ -\# +# # RTC class/drivers configuration # @@ -20,6 +20,8 @@ config RTC_CLASS This driver can also be built as a module. If so, the module will be called rtc-class. +if RTC_CLASS != n + if RTC_CLASS because otherwise config RTC_HCTOSYS bool Set system time from RTC on startup depends on RTC_CLASS = y @@ -45,11 +47,10 @@ config RTC_DEBUG and individual RTC drivers. comment RTC interfaces - depends on RTC_CLASS config RTC_INTF_SYSFS tristate sysfs - depends on RTC_CLASS SYSFS + depends on SYSFS ... RTC_CLASS=m, RTC_INTF_SYSFS=y would be an allowed configuration. cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.19-git] RTC Kconfig sorted by type
+if RTC_CLASS != n + if RTC_CLASS because otherwise Thanks for the clarification. I think Alessandro was going to redo this one soon, since the Kconfig changed so much the patch would no longer apply. I trust he'll remember your comments! - Dave - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.19-git] RTC Kconfig sorted by type
On Wed, 6 Dec 2006 16:52:44 -0800 David Brownell <[EMAIL PROTECTED]> wrote: > This reorders the RTC driver menu into separate sections, splitting out > the SOC, I2C, and SPI support to help make the menu easier to navigate. > (We got some feedback a while ago that it was "a mess" and hard to make > sense of...) > > Signed-off-by: David Brownell <[EMAIL PROTECTED]> Thanks David, I was planning to do that myself.. you saved me some work! :) Acked-by: Alessandro Zummo <[EMAIL PROTECTED]> -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.19-git] RTC Kconfig sorted by type
On Wed, 6 Dec 2006 16:52:44 -0800 David Brownell [EMAIL PROTECTED] wrote: This reorders the RTC driver menu into separate sections, splitting out the SOC, I2C, and SPI support to help make the menu easier to navigate. (We got some feedback a while ago that it was a mess and hard to make sense of...) Signed-off-by: David Brownell [EMAIL PROTECTED] Thanks David, I was planning to do that myself.. you saved me some work! :) Acked-by: Alessandro Zummo [EMAIL PROTECTED] -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[patch 2.6.19-git] RTC Kconfig sorted by type
This reorders the RTC driver menu into separate sections, splitting out the SOC, I2C, and SPI support to help make the menu easier to navigate. (We got some feedback a while ago that it was "a mess" and hard to make sense of...) Signed-off-by: David Brownell <[EMAIL PROTECTED]> --- Assumes the rtc-omap patch has been merged, and no other RTC drivers have been added to this Kconfig menu. Index: at91/drivers/rtc/Kconfig === --- at91.orig/drivers/rtc/Kconfig 2006-12-05 03:25:20.0 -0800 +++ at91/drivers/rtc/Kconfig2006-12-05 03:46:53.0 -0800 @@ -1,4 +1,4 @@ -\# +# # RTC class/drivers configuration # @@ -20,6 +20,8 @@ config RTC_CLASS This driver can also be built as a module. If so, the module will be called rtc-class. +if RTC_CLASS != n + config RTC_HCTOSYS bool "Set system time from RTC on startup" depends on RTC_CLASS = y @@ -45,11 +47,10 @@ config RTC_DEBUG and individual RTC drivers. comment "RTC interfaces" - depends on RTC_CLASS config RTC_INTF_SYSFS tristate "sysfs" - depends on RTC_CLASS && SYSFS + depends on SYSFS default RTC_CLASS help Say yes here if you want to use your RTCs using sysfs interfaces, @@ -60,7 +61,7 @@ config RTC_INTF_SYSFS config RTC_INTF_PROC tristate "proc" - depends on RTC_CLASS && PROC_FS + depends on PROC_FS default RTC_CLASS help Say yes here if you want to use your first RTC through the proc @@ -72,7 +73,6 @@ config RTC_INTF_PROC config RTC_INTF_DEV tristate "dev" - depends on RTC_CLASS default RTC_CLASS help Say yes here if you want to use your RTCs using the /dev @@ -92,129 +92,121 @@ config RTC_INTF_DEV_UIE_EMUL driver does not expose RTC_UIE ioctls. Those requests generate once-per-second update interrupts, used for synchronization. +## + comment "RTC drivers" - depends on RTC_CLASS -config RTC_DRV_X1205 - tristate "Xicor/Intersil X1205" - depends on RTC_CLASS && I2C +config RTC_DRV_DS1553 + tristate "Dallas DS1553" help If you say yes here you get support for the - Xicor/Intersil X1205 RTC chip. + Dallas DS1553 timekeeping chip. This driver can also be built as a module. If so, the module - will be called rtc-x1205. + will be called rtc-ds1553. -config RTC_DRV_DS1307 - tristate "Dallas/Maxim DS1307 and similar I2C RTC chips" - depends on RTC_CLASS && I2C +config RTC_DRV_DS1742 + tristate "Dallas DS1742" help - If you say yes here you get support for various compatible RTC - chips (often with battery backup) connected with I2C. This driver - should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, - and probably other chips. In some cases the RTC must already - have been initialized (by manufacturing or a bootloader). - - The first seven registers on these chips hold an RTC, and other - registers may add features such as NVRAM, a trickle charger for - the RTC/NVRAM backup power, and alarms. This driver may not - expose all those available chip features. + If you say yes here you get support for the + Dallas DS1742 timekeeping chip. This driver can also be built as a module. If so, the module - will be called rtc-ds1307. + will be called rtc-ds1742. -config RTC_DRV_DS1553 - tristate "Dallas DS1553" - depends on RTC_CLASS +config RTC_DRV_V3020 + tristate "EM Microelectronic V3020" help - If you say yes here you get support for the - Dallas DS1553 timekeeping chip. + If you say yes here you will get support for the + EM Microelectronic v3020 RTC chip. This driver can also be built as a module. If so, the module - will be called rtc-ds1553. + will be called rtc-v3020. -config RTC_DRV_ISL1208 - tristate "Intersil 1208" - depends on RTC_CLASS && I2C +config RTC_DRV_M48T86 + tristate "ST M48T86/Dallas DS12887" help - If you say yes here you get support for the - Intersil 1208 RTC chip. + If you say Y here you will get support for the + ST M48T86 and Dallas DS12887 RTC chips. This driver can also be built as a module. If so, the module - will be called rtc-isl1208. + will be called rtc-m48t86. -config RTC_DRV_DS1672 - tristate "Dallas/Maxim DS1672" - depends on RTC_CLASS && I2C +config RTC_DRV_TEST + tristate "Test driver/device" help If you say yes here you get support for the - Dallas/Maxim DS1672 timekeeping chip. + RTC test
[patch 2.6.19-git] RTC Kconfig sorted by type
This reorders the RTC driver menu into separate sections, splitting out the SOC, I2C, and SPI support to help make the menu easier to navigate. (We got some feedback a while ago that it was a mess and hard to make sense of...) Signed-off-by: David Brownell [EMAIL PROTECTED] --- Assumes the rtc-omap patch has been merged, and no other RTC drivers have been added to this Kconfig menu. Index: at91/drivers/rtc/Kconfig === --- at91.orig/drivers/rtc/Kconfig 2006-12-05 03:25:20.0 -0800 +++ at91/drivers/rtc/Kconfig2006-12-05 03:46:53.0 -0800 @@ -1,4 +1,4 @@ -\# +# # RTC class/drivers configuration # @@ -20,6 +20,8 @@ config RTC_CLASS This driver can also be built as a module. If so, the module will be called rtc-class. +if RTC_CLASS != n + config RTC_HCTOSYS bool Set system time from RTC on startup depends on RTC_CLASS = y @@ -45,11 +47,10 @@ config RTC_DEBUG and individual RTC drivers. comment RTC interfaces - depends on RTC_CLASS config RTC_INTF_SYSFS tristate sysfs - depends on RTC_CLASS SYSFS + depends on SYSFS default RTC_CLASS help Say yes here if you want to use your RTCs using sysfs interfaces, @@ -60,7 +61,7 @@ config RTC_INTF_SYSFS config RTC_INTF_PROC tristate proc - depends on RTC_CLASS PROC_FS + depends on PROC_FS default RTC_CLASS help Say yes here if you want to use your first RTC through the proc @@ -72,7 +73,6 @@ config RTC_INTF_PROC config RTC_INTF_DEV tristate dev - depends on RTC_CLASS default RTC_CLASS help Say yes here if you want to use your RTCs using the /dev @@ -92,129 +92,121 @@ config RTC_INTF_DEV_UIE_EMUL driver does not expose RTC_UIE ioctls. Those requests generate once-per-second update interrupts, used for synchronization. +## + comment RTC drivers - depends on RTC_CLASS -config RTC_DRV_X1205 - tristate Xicor/Intersil X1205 - depends on RTC_CLASS I2C +config RTC_DRV_DS1553 + tristate Dallas DS1553 help If you say yes here you get support for the - Xicor/Intersil X1205 RTC chip. + Dallas DS1553 timekeeping chip. This driver can also be built as a module. If so, the module - will be called rtc-x1205. + will be called rtc-ds1553. -config RTC_DRV_DS1307 - tristate Dallas/Maxim DS1307 and similar I2C RTC chips - depends on RTC_CLASS I2C +config RTC_DRV_DS1742 + tristate Dallas DS1742 help - If you say yes here you get support for various compatible RTC - chips (often with battery backup) connected with I2C. This driver - should handle DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00, - and probably other chips. In some cases the RTC must already - have been initialized (by manufacturing or a bootloader). - - The first seven registers on these chips hold an RTC, and other - registers may add features such as NVRAM, a trickle charger for - the RTC/NVRAM backup power, and alarms. This driver may not - expose all those available chip features. + If you say yes here you get support for the + Dallas DS1742 timekeeping chip. This driver can also be built as a module. If so, the module - will be called rtc-ds1307. + will be called rtc-ds1742. -config RTC_DRV_DS1553 - tristate Dallas DS1553 - depends on RTC_CLASS +config RTC_DRV_V3020 + tristate EM Microelectronic V3020 help - If you say yes here you get support for the - Dallas DS1553 timekeeping chip. + If you say yes here you will get support for the + EM Microelectronic v3020 RTC chip. This driver can also be built as a module. If so, the module - will be called rtc-ds1553. + will be called rtc-v3020. -config RTC_DRV_ISL1208 - tristate Intersil 1208 - depends on RTC_CLASS I2C +config RTC_DRV_M48T86 + tristate ST M48T86/Dallas DS12887 help - If you say yes here you get support for the - Intersil 1208 RTC chip. + If you say Y here you will get support for the + ST M48T86 and Dallas DS12887 RTC chips. This driver can also be built as a module. If so, the module - will be called rtc-isl1208. + will be called rtc-m48t86. -config RTC_DRV_DS1672 - tristate Dallas/Maxim DS1672 - depends on RTC_CLASS I2C +config RTC_DRV_TEST + tristate Test driver/device help If you say yes here you get support for the - Dallas/Maxim DS1672 timekeeping chip. + RTC test driver. It's a software RTC which can be +
