From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] clocksource: st_lpc: Add LPC timer as a clocksource.
Date: Fri, 17 Apr 2015 23:16:45 +0200 [thread overview]
Message-ID: <1429305405.16771.114.camel@x220> (raw)
In-Reply-To: <1429267823-8879-2-git-send-email-peter.griffin@linaro.org>
On Fri, 2015-04-17 at 11:50 +0100, Peter Griffin wrote:
> --- a/drivers/clocksource/Kconfig
> +++ b/drivers/clocksource/Kconfig
> +config CLKSRC_ST_LPC_CLOCK
> + bool
> + depends on ARCH_STI
> + select CLKSRC_OF if OF
> + help
> + Enable this option to use the Low Power controller timer
> + as clock source.
> +
> +config CLKSRC_ST_LPC_TIMER_SCHED_CLOCK
> + bool
> + depends on ST_LPC_CLOCK
It looks like you meant
depends on CLKSRC_ST_LPC_CLOCK
> + default y
> + help
> + Use Low Power controller timer clock source as sched_clock
> --- a/drivers/clocksource/Makefile
> +++ b/drivers/clocksource/Makefile
> +obj-$(CONFIG_CLKSRC_ST_LPC_CLOCK) += st_lpc.o
> --- /dev/null
> +++ b/drivers/clocksource/st_lpc.c
> +#ifdef CONFIG_CLKSRC_LPC_TIMER_SCHED_CLOCK
#ifdef CONFIG_CLKSRC_ST_LPC_TIMER_SCHED_CLOCK here?
> +static u64 notrace st_lpc_sched_clock_read(void)
> +{
> + return st_lpc_counter_read();
> +}
> +#endif
> +#ifdef CONFIG_CLKSRC_LPC_TIMER_SCHED_CLOCK
Again, #ifdef CONFIG_CLKSRC_ST_LPC_TIMER_SCHED_CLOCK here?
> + sched_clock_register(st_lpc_sched_clock_read, 64, rate);
> +#endif
Assuming the above suggestions are correct: checkkconfigsymbols.py, as
shipped in linux-next, helps detect stuff like this. See
scripts/checkkconfigsymbols.py --help.
Thanks,
Paul Bolle
WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, srinivas.kandagatla@gmail.com,
maxime.coquelin@st.com, patrice.chotard@st.com,
daniel.lezcano@linaro.org, tglx@linutronix.de,
lee.jones@linaro.org, devicetree@vger.kernel.org,
Ajit Pal Singh <ajitpal.singh@st.com>
Subject: Re: [PATCH 1/5] clocksource: st_lpc: Add LPC timer as a clocksource.
Date: Fri, 17 Apr 2015 23:16:45 +0200 [thread overview]
Message-ID: <1429305405.16771.114.camel@x220> (raw)
In-Reply-To: <1429267823-8879-2-git-send-email-peter.griffin@linaro.org>
On Fri, 2015-04-17 at 11:50 +0100, Peter Griffin wrote:
> --- a/drivers/clocksource/Kconfig
> +++ b/drivers/clocksource/Kconfig
> +config CLKSRC_ST_LPC_CLOCK
> + bool
> + depends on ARCH_STI
> + select CLKSRC_OF if OF
> + help
> + Enable this option to use the Low Power controller timer
> + as clock source.
> +
> +config CLKSRC_ST_LPC_TIMER_SCHED_CLOCK
> + bool
> + depends on ST_LPC_CLOCK
It looks like you meant
depends on CLKSRC_ST_LPC_CLOCK
> + default y
> + help
> + Use Low Power controller timer clock source as sched_clock
> --- a/drivers/clocksource/Makefile
> +++ b/drivers/clocksource/Makefile
> +obj-$(CONFIG_CLKSRC_ST_LPC_CLOCK) += st_lpc.o
> --- /dev/null
> +++ b/drivers/clocksource/st_lpc.c
> +#ifdef CONFIG_CLKSRC_LPC_TIMER_SCHED_CLOCK
#ifdef CONFIG_CLKSRC_ST_LPC_TIMER_SCHED_CLOCK here?
> +static u64 notrace st_lpc_sched_clock_read(void)
> +{
> + return st_lpc_counter_read();
> +}
> +#endif
> +#ifdef CONFIG_CLKSRC_LPC_TIMER_SCHED_CLOCK
Again, #ifdef CONFIG_CLKSRC_ST_LPC_TIMER_SCHED_CLOCK here?
> + sched_clock_register(st_lpc_sched_clock_read, 64, rate);
> +#endif
Assuming the above suggestions are correct: checkkconfigsymbols.py, as
shipped in linux-next, helps detect stuff like this. See
scripts/checkkconfigsymbols.py --help.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-04-17 21:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 10:50 [PATCH 0/5] Add st_lpc clocksource timer driver Peter Griffin
2015-04-17 10:50 ` Peter Griffin
2015-04-17 10:50 ` Peter Griffin
2015-04-17 10:50 ` [PATCH 1/5] clocksource: st_lpc: Add LPC timer as a clocksource Peter Griffin
2015-04-17 10:50 ` Peter Griffin
2015-04-17 21:16 ` Paul Bolle [this message]
2015-04-17 21:16 ` Paul Bolle
2015-04-20 7:14 ` Peter Griffin
2015-04-20 7:14 ` Peter Griffin
2015-04-21 9:56 ` Thomas Gleixner
2015-04-21 9:56 ` Thomas Gleixner
2015-04-21 9:56 ` Thomas Gleixner
2015-04-29 15:48 ` Maxime Coquelin
2015-04-29 15:48 ` Maxime Coquelin
2015-04-29 15:48 ` Maxime Coquelin
2015-05-02 16:36 ` Peter Griffin
2015-05-02 16:36 ` Peter Griffin
2015-05-02 16:36 ` Peter Griffin
2015-04-17 10:50 ` [PATCH 2/5] clocksource: st_lpc: Add DT bindings documentation for lpc timer Peter Griffin
2015-04-17 10:50 ` Peter Griffin
2015-04-17 10:50 ` [PATCH 3/5] MAINTAINERS: Add st_lpc.c to ARCH/STI section of maintainers Peter Griffin
2015-04-17 10:50 ` Peter Griffin
2015-04-17 10:50 ` [PATCH 4/5] ARM: sti: Always enable CLKSRC_ST_LPC_CLOCK Peter Griffin
2015-04-17 10:50 ` Peter Griffin
2015-04-17 10:50 ` Peter Griffin
2015-04-17 10:50 ` [PATCH 5/5] ARM: DT: STi: STiH407: Add DT node for st-lpc timer Peter Griffin
2015-04-17 10:50 ` Peter Griffin
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=1429305405.16771.114.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.