From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Peter Zijlstra <peterz@infradead.org>,
Richard Purdie <rpurdie@rpsys.net>,
Thomas Gleixner <tglx@linutronix.de>,
linux-leds@vger.kernel.org, rt@linutronix.de
Subject: Re: [PATCH] leds/trigger/cpu: move from CPU_STARTING to ONLINE level
Date: Thu, 21 Jul 2016 08:48:49 +0200 [thread overview]
Message-ID: <57907051.5090200@samsung.com> (raw)
In-Reply-To: <1469028295-14702-1-git-send-email-bigeasy@linutronix.de>
Hi Sebastian,
On 07/20/2016 05:24 PM, Sebastian Andrzej Siewior wrote:
> There is no need the ledtriger to be called *that* early in the hotplug
> process (+ with disabled interrupts). As explained by Jacek Anaszewski [0]
> there is no need for it.
> Therefore this patch moves it to the ONLINE/PREPARE_DOWN level using the
> dynamic registration for the id.
>
> [0] https://lkml.kernel.org/r/578C92BC.2070603@samsung.com
>
> Cc: Jacek Anaszewski <j.anaszewski@samsung.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Richard Purdie <rpurdie@rpsys.net>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: linux-leds@vger.kernel.org
> Cc: rt@linutronix.de
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> drivers/leds/trigger/ledtrig-cpu.c | 16 ++++++++--------
> include/linux/cpuhotplug.h | 1 -
> 2 files changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/leds/trigger/ledtrig-cpu.c b/drivers/leds/trigger/ledtrig-cpu.c
> index 4a6a182d0a88..22f0634dd3fa 100644
> --- a/drivers/leds/trigger/ledtrig-cpu.c
> +++ b/drivers/leds/trigger/ledtrig-cpu.c
> @@ -92,13 +92,13 @@ static struct syscore_ops ledtrig_cpu_syscore_ops = {
> .resume = ledtrig_cpu_syscore_resume,
> };
>
> -static int ledtrig_starting_cpu(unsigned int cpu)
> +static int ledtrig_online_cpu(unsigned int cpu)
> {
> ledtrig_cpu(CPU_LED_START);
> return 0;
> }
>
> -static int ledtrig_dying_cpu(unsigned int cpu)
> +static int ledtrig_prepare_down_cpu(unsigned int cpu)
> {
> ledtrig_cpu(CPU_LED_STOP);
> return 0;
> @@ -107,6 +107,7 @@ static int ledtrig_dying_cpu(unsigned int cpu)
> static int __init ledtrig_cpu_init(void)
> {
> int cpu;
> + int ret;
>
> /* Supports up to 9999 cpu cores */
> BUILD_BUG_ON(CONFIG_NR_CPUS > 9999);
> @@ -126,12 +127,11 @@ static int __init ledtrig_cpu_init(void)
>
> register_syscore_ops(&ledtrig_cpu_syscore_ops);
>
> - /*
> - * FIXME: Why needs this to happen in the interrupt disabled
> - * low level bringup phase of a cpu?
> - */
> - cpuhp_setup_state(CPUHP_AP_LEDTRIG_STARTING, "AP_LEDTRIG_STARTING",
> - ledtrig_starting_cpu, ledtrig_dying_cpu);
> + ret = cpuhp_setup_state(CPUHP_AP_ONLINE_DYN, "AP_LEDTRIG_STARTING",
> + ledtrig_online_cpu, ledtrig_prepare_down_cpu);
> + if (ret < 0)
> + pr_err("CPU hotplug notifier for ledtrig-cpu could not be registered: %d\n",
> + ret);
>
> pr_info("ledtrig-cpu: registered to indicate activity on CPUs\n");
>
> diff --git a/include/linux/cpuhotplug.h b/include/linux/cpuhotplug.h
> index 09ef54bcba39..282800b42627 100644
> --- a/include/linux/cpuhotplug.h
> +++ b/include/linux/cpuhotplug.h
> @@ -65,7 +65,6 @@ enum cpuhp_state {
> CPUHP_AP_ARM_CORESIGHT_STARTING,
> CPUHP_AP_ARM_CORESIGHT4_STARTING,
> CPUHP_AP_ARM64_ISNDEP_STARTING,
> - CPUHP_AP_LEDTRIG_STARTING,
> CPUHP_AP_SMPCFD_DYING,
> CPUHP_AP_X86_TBOOT_DYING,
> CPUHP_AP_NOTIFY_STARTING,
>
Acked-by: Jacek Anaszewski <j.anaszewski@samsung.com>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2016-07-21 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 15:24 Sebastian Andrzej Siewior
2016-07-21 6:48 ` Jacek Anaszewski [this message]
2016-07-22 15:24 ` Linus Walleij
2016-07-22 19:58 ` [tip:smp/hotplug] leds/trigger/cpu: Move " tip-bot for Sebastian Andrzej Siewior
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=57907051.5090200@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=bigeasy@linutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rpurdie@rpsys.net \
--cc=rt@linutronix.de \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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