Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751714AbeAHRfu (ORCPT + 1 other); Mon, 8 Jan 2018 12:35:50 -0500 Received: from terminus.zytor.com ([65.50.211.136]:53933 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750797AbeAHRfq (ORCPT ); Mon, 8 Jan 2018 12:35:46 -0500 Date: Mon, 8 Jan 2018 09:31:21 -0800 From: tip-bot for Daniel Lezcano Message-ID: Cc: alexandre.torgue@st.com, peterz@infradead.org, torvalds@linux-foundation.org, daniel.lezcano@linaro.org, mingo@kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, hpa@zytor.com, mcoquelin.stm32@gmail.com, benjamin.gaignard@st.com Reply-To: mcoquelin.stm32@gmail.com, benjamin.gaignard@st.com, mingo@kernel.org, tglx@linutronix.de, linux-kernel@vger.kernel.org, hpa@zytor.com, torvalds@linux-foundation.org, daniel.lezcano@linaro.org, alexandre.torgue@st.com, peterz@infradead.org In-Reply-To: <1515418139-23276-13-git-send-email-daniel.lezcano@linaro.org> References: <1515418139-23276-13-git-send-email-daniel.lezcano@linaro.org> To: linux-tip-commits@vger.kernel.org Subject: [tip:timers/core] clocksource/drivers/stm32: Use the node name as timer name Git-Commit-ID: f2ed8ef1cea41c7e7e5d52199db9c822951ab101 X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: Commit-ID: f2ed8ef1cea41c7e7e5d52199db9c822951ab101 Gitweb: https://git.kernel.org/tip/f2ed8ef1cea41c7e7e5d52199db9c822951ab101 Author: Daniel Lezcano AuthorDate: Mon, 8 Jan 2018 14:28:52 +0100 Committer: Ingo Molnar CommitDate: Mon, 8 Jan 2018 17:57:25 +0100 clocksource/drivers/stm32: Use the node name as timer name As there are different timers on the stm32, use the node name for the timer name in order to give the indication of which timer the kernel is using. /proc/timer_list gives all the information with the right name, otherwise we end up digging in the kernel log and /proc/interrupt to do the connection between the used timer. Tested-by: Benjamin Gaignard Signed-off-by: Daniel Lezcano Acked-by: Benjamin Gaignard Cc: Alexandre Torgue Cc: Linus Torvalds Cc: Maxime Coquelin Cc: Peter Zijlstra Cc: Thomas Gleixner Link: http://lkml.kernel.org/r/1515418139-23276-13-git-send-email-daniel.lezcano@linaro.org Signed-off-by: Ingo Molnar --- drivers/clocksource/timer-stm32.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clocksource/timer-stm32.c b/drivers/clocksource/timer-stm32.c index 3e4ab07..14b7a2b 100644 --- a/drivers/clocksource/timer-stm32.c +++ b/drivers/clocksource/timer-stm32.c @@ -85,7 +85,7 @@ static void __init stm32_clockevent_init(struct timer_of *to) unsigned long max_delta; int prescaler; - to->clkevt.name = "stm32_clockevent"; + to->clkevt.name = to->np->full_name; to->clkevt.features = CLOCK_EVT_FEAT_PERIODIC; to->clkevt.set_state_shutdown = stm32_clock_event_shutdown; to->clkevt.set_state_periodic = stm32_clock_event_set_periodic;