From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Walleij <linus.walleij@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sudeep Holla <Sudeep.Holla@arm.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>
Subject: Re: [PATCH 2/3] clocksource: versatile: adapt for Versatile AB and PB boards
Date: Thu, 29 Jan 2015 10:28:59 +0000 [thread overview]
Message-ID: <20150129102859.GR956@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <1422467792-2065-3-git-send-email-robh@kernel.org>
On Wed, Jan 28, 2015 at 05:56:31PM +0000, Rob Herring wrote:
> The same 24MHz counter is also present on Versatile AB and PB boards, so
> add the compatible string for them.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> Cc: Liviu Dudau <liviu.dudau@arm.com>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> ---
> drivers/clocksource/versatile.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/versatile.c b/drivers/clocksource/versatile.c
> index 2798e74..0a26d3d 100644
> --- a/drivers/clocksource/versatile.c
> +++ b/drivers/clocksource/versatile.c
> @@ -36,5 +36,7 @@ static void __init versatile_sched_clock_init(struct device_node *node)
>
> sched_clock_register(versatile_sys_24mhz_read, 32, 24000000);
> }
> -CLOCKSOURCE_OF_DECLARE(versatile, "arm,vexpress-sysreg",
> +CLOCKSOURCE_OF_DECLARE(vexpress, "arm,vexpress-sysreg",
> + versatile_sched_clock_init);
> +CLOCKSOURCE_OF_DECLARE(versatile, "arm,versatile-sysreg",
> versatile_sched_clock_init);
Acked-by: Liviu Dudau <Liviu.Dudau@arm.com>
> --
> 2.1.0
>
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
next prev parent reply other threads:[~2015-01-29 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 17:56 [PATCH 0/3] Versatile AB/PB clocksource support Rob Herring
2015-01-28 17:56 ` [PATCH 1/3] dt/bindings: Add binding for Versatile system registers Rob Herring
2015-02-03 13:23 ` Linus Walleij
2015-01-28 17:56 ` [PATCH 2/3] clocksource: versatile: adapt for Versatile AB and PB boards Rob Herring
2015-01-29 10:28 ` Liviu Dudau [this message]
2015-01-28 17:56 ` [PATCH 3/3] dts: versatile: add sysregs node Rob Herring
[not found] ` <1422467792-2065-4-git-send-email-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-02-03 13:23 ` Linus Walleij
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=20150129102859.GR956@e106497-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).