From: Samuel Ortiz <sameo@linux.intel.com>
To: Ulf Hansson <ulf.hansson@stericsson.com>
Cc: linux-arm-kernel@lists.infradead.org,
Mike Turquette <mturquette@ti.com>,
Mike Turquette <mturquette@linaro.org>,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Philippe Begnic <philippe.begnic@st.com>,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
Michel Jaouen <michel.jaouen@stericsson.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rickard Andersson <rickard.andersson@stericsson.com>
Subject: Re: [PATCH 3/4] mfd: dbx500: Provide a more accurate smp_twd clock
Date: Wed, 19 Sep 2012 18:02:51 +0200 [thread overview]
Message-ID: <20120919160251.GM28670@sortiz-mobl> (raw)
In-Reply-To: <1346415691-13371-4-git-send-email-ulf.hansson@stericsson.com>
Hi Ulf,
On Fri, Aug 31, 2012 at 02:21:30PM +0200, Ulf Hansson wrote:
> From: Michel Jaouen <michel.jaouen@stericsson.com>
>
> The local timer clock is based on ARM subsystem clock. This patch
> obtains a more exact value of that clock by reading PRCMU registers.
> Using this increases the accuracy of the local timer events.
>
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
> Signed-off-by: Rickard Andersson <rickard.andersson@stericsson.com>
> Signed-off-by: Michel Jaouen <michel.jaouen@stericsson.com>
> ---
> drivers/mfd/db8500-prcmu.c | 42 ++++++++++++++++++++++++++++++++++++++
> drivers/mfd/dbx500-prcmu-regs.h | 4 +++-
> include/linux/mfd/dbx500-prcmu.h | 1 +
> 3 files changed, 46 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/db8500-prcmu.c b/drivers/mfd/db8500-prcmu.c
> index 4f74529..e7f9539 100644
> --- a/drivers/mfd/db8500-prcmu.c
> +++ b/drivers/mfd/db8500-prcmu.c
> @@ -418,6 +418,9 @@ static struct {
>
> static atomic_t ac_wake_req_state = ATOMIC_INIT(0);
>
> +/* Functions definition */
> +static void compute_armss_rate(void);
> +
I'm not a big fan of forward declarations, but I still applied your patch to
my for-next branch. Thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-09-19 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 12:21 [PATCH 0/4] clk: Support for smp_twd clock for ux500 Ulf Hansson
2012-08-31 12:21 ` [PATCH 1/4] clk: Provide option for clk_get_rate to issue hw for new rate Ulf Hansson
2012-08-31 19:29 ` Mike Turquette
2012-09-06 9:09 ` Ulf Hansson
[not found] ` <20120907001927.20289.41627@nucleus>
2012-09-07 1:00 ` Turquette, Mike
2012-09-07 8:21 ` Linus Walleij
2012-09-07 12:29 ` Ulf Hansson
2012-09-07 21:34 ` Linus Walleij
2012-08-31 12:21 ` [PATCH 2/4] clk: ux500: Support for prmcu_rate clock Ulf Hansson
2012-08-31 12:21 ` [PATCH 3/4] mfd: dbx500: Provide a more accurate smp_twd clock Ulf Hansson
2012-09-19 16:02 ` Samuel Ortiz [this message]
2012-09-19 16:42 ` Mike Turquette
2012-09-19 16:56 ` Samuel Ortiz
2012-08-31 12:21 ` [PATCH 4/4] clk: ux500: Define smp_twd clock for u8500 Ulf Hansson
2012-08-31 23:32 ` [PATCH 0/4] clk: Support for smp_twd clock for ux500 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=20120919160251.GM28670@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel.jaouen@stericsson.com \
--cc=mturquette@linaro.org \
--cc=mturquette@ti.com \
--cc=philippe.begnic@st.com \
--cc=rickard.andersson@stericsson.com \
--cc=srinidhi.kasagar@stericsson.com \
--cc=ulf.hansson@linaro.org \
--cc=ulf.hansson@stericsson.com \
/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).