From: Guenter Roeck <linux@roeck-us.net>
To: Jean-Baptiste Theou <jtheou@adeneo-embedded.us>,
Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] gpio_wdt: Add option for early registration
Date: Fri, 05 Jun 2015 21:31:28 -0700 [thread overview]
Message-ID: <557277A0.4060801@roeck-us.net> (raw)
In-Reply-To: <1433555212-4729-3-git-send-email-jtheou@adeneo-embedded.us>
On 06/05/2015 06:46 PM, Jean-Baptiste Theou wrote:
> In some situation, mainly when it's not possible to disable a
> watchdog, you may want the watchdog driver to be started as soon
> as possible.
>
> Adding GPIO_WATCHDOG_ARCH_INITCALL to raise initcall from
> module_init to arch_initcall. This is only for a built-in
> module.
>
> This patch require watchdog registration deferral mechanism
>
> Signed-off-by: Jean-Baptiste Theou <jtheou@adeneo-embedded.us>
> ---
> drivers/watchdog/Kconfig | 14 ++++++++++++++
> drivers/watchdog/gpio_wdt.c | 13 +++++++++++++
> 2 files changed, 27 insertions(+)
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index e5e7c55..a9655a9 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -1,3 +1,4 @@
> +
> #
> # Watchdog device configuration
> #
> @@ -114,6 +115,19 @@ config MENF21BMC_WATCHDOG
> This driver can also be built as a module. If so the module
> will be called menf21bmc_wdt.
>
> +config GPIO_WATCHDOG_ARCH_INITCALL
> + bool "Register the watchdog as early as possible"
> + depends on GPIO_WATCHDOG
depends on GPIO_WATCHDOG=y
> + help
> + This option make sense only on a built-in situation.
> +
and then you can drop this sentence.
> + In some situation, the default initcall level (module_init)
situations
> + in not early enough on the boot process to avoid the watchdog
in the boot process
> + to be trigger.
triggered.
> + If you say yes here, the initcall level would be raise to
will be raised to ...
> + arch_initcall.
> + "If in doubt, leave it out" - say N.
If in doubt, say N.
> +
> config WM831X_WATCHDOG
> tristate "WM831x watchdog"
> depends on MFD_WM831X
> diff --git a/drivers/watchdog/gpio_wdt.c b/drivers/watchdog/gpio_wdt.c
> index cbc313d..07a39cd 100644
> --- a/drivers/watchdog/gpio_wdt.c
> +++ b/drivers/watchdog/gpio_wdt.c
> @@ -267,8 +267,21 @@ static struct platform_driver gpio_wdt_driver = {
> .probe = gpio_wdt_probe,
> .remove = gpio_wdt_remove,
> };
> +#ifndef GPIO_WATCHDOG_ARCH_INITCALL
> module_platform_driver(gpio_wdt_driver);
> +#else
> +static int __init gpio_wdt_init(void)
> +{
> + return platform_driver_register(&gpio_wdt_driver);
> +}
> +arch_initcall(gpio_wdt_init);
>
> +static void __exit gpio_wdt_exit(void)
> +{
> + platform_driver_unregister(&gpio_wdt_driver);
> +}
> +module_exit(gpio_wdt_exit);
> +#endif
If you change the dependency as suggested above, you don't need
the exit function at all, and you can simplify this code to
#ifdef GPIO_WATCHDOG_ARCH_INITCALL
arch_initcall(gpio_wdt_init);
#else
module_platform_driver(gpio_wdt_driver);
#endif
which would look much nicer.
Thanks,
Guenter
> MODULE_AUTHOR("Alexander Shiyan <shc_work@mail.ru>");
> MODULE_DESCRIPTION("GPIO Watchdog");
> MODULE_LICENSE("GPL");
>
next prev parent reply other threads:[~2015-06-06 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 1:46 [PATCH v2 1/3] watchdog_core: Add watchdog registration deferral mechanism Jean-Baptiste Theou
2015-06-06 1:46 ` [PATCH v2 2/3] watchdog-kernel-api: Add " Jean-Baptiste Theou
2015-06-06 4:26 ` Guenter Roeck
2015-06-06 1:46 ` [PATCH v2 3/3] gpio_wdt: Add option for early registration Jean-Baptiste Theou
2015-06-06 4:31 ` Guenter Roeck [this message]
2015-06-06 4:24 ` [PATCH v2 1/3] watchdog_core: Add watchdog registration deferral mechanism Guenter Roeck
2015-06-06 6:39 ` Jean-Baptiste Theou
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=557277A0.4060801@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jtheou@adeneo-embedded.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/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
Powered by JetHome