From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Kozlowski Subject: Re: [PATCH] ARM: exynos_defconfig: Make S3C2410_WATCHDOG as loadable module Date: Fri, 04 Sep 2015 15:42:50 +0900 Message-ID: <55E93D6A.8030301@samsung.com> References: <1441253429-3264-1-git-send-email-linux.amoon@gmail.com> <55E7D478.2020200@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mailout1.w1.samsung.com ([210.118.77.11]:34247 "EHLO mailout1.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757869AbbIDGm4 (ORCPT ); Fri, 4 Sep 2015 02:42:56 -0400 In-reply-to: Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: Anand Moon Cc: Russell King , Kukjin Kim , Javier Martinez Canillas , Andreas Faerber , Lukasz Majewski , linux-arm-kernel@lists.infradead.org, "linux-samsung-soc@vger.kernel.org" , Linux Kernel On 03.09.2015 14:20, Anand Moon wrote: > Hi Krzysztof > > On 3 September 2015 at 10:32, Krzysztof Kozlowski > wrote: >> On 03.09.2015 13:10, Anand Moon wrote: >>> S3C2410_WATCHDOG watchdog drivers should not be loaded automatically, >>> but only if a watchdog daemon is installed. >> >> First of all: why? >> >> Secondly: even as a module driver could be loaded automatically to match >> enabled device (it has MODULE_DEVICE_TABLE). In the same time loading it >> does not hurt - watchdog should be inactive: >> >> s3c2410-wdt 10060000.watchdog: watchdog inactive, reset disabled, irq >> disabled >> >> Best regards, >> Krzysztof >> >>> >>> Signed-off-by: Anand Moon >>> --- >>> arch/arm/configs/exynos_defconfig | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig >>> index aaf7aa4..b5d382e 100644 >>> --- a/arch/arm/configs/exynos_defconfig >>> +++ b/arch/arm/configs/exynos_defconfig >>> @@ -101,7 +101,7 @@ CONFIG_CPU_THERMAL=y >>> CONFIG_THERMAL_EMULATION=y >>> CONFIG_EXYNOS_THERMAL=y >>> CONFIG_WATCHDOG=y >>> -CONFIG_S3C2410_WATCHDOG=y >>> +CONFIG_S3C2410_WATCHDOG=m >>> CONFIG_MFD_CROS_EC=y >>> CONFIG_MFD_CROS_EC_I2C=y >>> CONFIG_MFD_CROS_EC_SPI=y >>> > > All the watchdog drivers are blacklisted not to be loaded by the ubuntu. > Their are some configurable parameters which get configured while > loading of the module using watchdog daemon. > Watchdog service will reconfigure watchdog driver while loading. Thank you for clarification. First of all such information (that Ubuntu requires it) should be put in commit message. This looks like a requirement specific for Ubuntu. For example on Arch these modules are not blacklisted. I don't know how this is handled on Debian or Fedora. Other defconfigs (including multi_v7) make these modules built-in. Summarizing I am not convinced that the change is necessary. Having everything built-in makes testing exynos defconfig easier because some you just upload zImage and DTB to the testing board. With modules you have to prepare the initramfs/initrd (e.g. for network boot). Best regards, Krzysztof From mboxrd@z Thu Jan 1 00:00:00 1970 From: k.kozlowski@samsung.com (Krzysztof Kozlowski) Date: Fri, 04 Sep 2015 15:42:50 +0900 Subject: [PATCH] ARM: exynos_defconfig: Make S3C2410_WATCHDOG as loadable module In-Reply-To: References: <1441253429-3264-1-git-send-email-linux.amoon@gmail.com> <55E7D478.2020200@samsung.com> Message-ID: <55E93D6A.8030301@samsung.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 03.09.2015 14:20, Anand Moon wrote: > Hi Krzysztof > > On 3 September 2015 at 10:32, Krzysztof Kozlowski > wrote: >> On 03.09.2015 13:10, Anand Moon wrote: >>> S3C2410_WATCHDOG watchdog drivers should not be loaded automatically, >>> but only if a watchdog daemon is installed. >> >> First of all: why? >> >> Secondly: even as a module driver could be loaded automatically to match >> enabled device (it has MODULE_DEVICE_TABLE). In the same time loading it >> does not hurt - watchdog should be inactive: >> >> s3c2410-wdt 10060000.watchdog: watchdog inactive, reset disabled, irq >> disabled >> >> Best regards, >> Krzysztof >> >>> >>> Signed-off-by: Anand Moon >>> --- >>> arch/arm/configs/exynos_defconfig | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig >>> index aaf7aa4..b5d382e 100644 >>> --- a/arch/arm/configs/exynos_defconfig >>> +++ b/arch/arm/configs/exynos_defconfig >>> @@ -101,7 +101,7 @@ CONFIG_CPU_THERMAL=y >>> CONFIG_THERMAL_EMULATION=y >>> CONFIG_EXYNOS_THERMAL=y >>> CONFIG_WATCHDOG=y >>> -CONFIG_S3C2410_WATCHDOG=y >>> +CONFIG_S3C2410_WATCHDOG=m >>> CONFIG_MFD_CROS_EC=y >>> CONFIG_MFD_CROS_EC_I2C=y >>> CONFIG_MFD_CROS_EC_SPI=y >>> > > All the watchdog drivers are blacklisted not to be loaded by the ubuntu. > Their are some configurable parameters which get configured while > loading of the module using watchdog daemon. > Watchdog service will reconfigure watchdog driver while loading. Thank you for clarification. First of all such information (that Ubuntu requires it) should be put in commit message. This looks like a requirement specific for Ubuntu. For example on Arch these modules are not blacklisted. I don't know how this is handled on Debian or Fedora. Other defconfigs (including multi_v7) make these modules built-in. Summarizing I am not convinced that the change is necessary. Having everything built-in makes testing exynos defconfig easier because some you just upload zImage and DTB to the testing board. With modules you have to prepare the initramfs/initrd (e.g. for network boot). Best regards, Krzysztof