From: Mike Turquette <mturquette@linaro.org>
To: Rob Landley <rob@landley.net>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Russell King <linux@arm.linux.org.uk>
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Boris BREZILLON <b.brezillon@overkiz.com>
Subject: Re: [RFC PATCH RESEND 1/2] clk: add clk accuracy retrieval support
Date: Fri, 15 Nov 2013 17:59:46 -0800 [thread overview]
Message-ID: <20131116015946.19193.29895@quantum> (raw)
In-Reply-To: <1381684631-10835-2-git-send-email-b.brezillon@overkiz.com>
Quoting Boris BREZILLON (2013-10-13 10:17:10)
> diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
> index 73bdb69..942811d 100644
> --- a/include/linux/clk-provider.h
> +++ b/include/linux/clk-provider.h
...
> @@ -194,6 +204,7 @@ struct clk_hw {
> struct clk_fixed_rate {
> struct clk_hw hw;
> unsigned long fixed_rate;
> + unsigned long fixed_accuracy;
This change belongs in patch #2. Please also update the kerneldoc above
this struct definition.
Regards,
Mike
> u8 flags;
> };
>
> diff --git a/include/linux/clk.h b/include/linux/clk.h
> index 9a6d045..2fe3b54 100644
> --- a/include/linux/clk.h
> +++ b/include/linux/clk.h
> @@ -85,6 +85,23 @@ int clk_notifier_unregister(struct clk *clk, struct notifier_block *nb);
> #endif
>
> /**
> + * clk_get_accuracy - obtain the clock accuracy in ppb (parts per billion)
> + * for a clock source.
> + * @clk: clock source
> + *
> + * This gets the clock source accuracy expressed in ppb.
> + * A perfect clock returns 0.
> + */
> +#ifdef CONFIG_HAVE_CLK_GET_ACCURACY
> +unsigned long clk_get_accuracy(struct clk *clk);
> +#else
> +static inline unsigned long clk_get_accuracy(struct clk *clk)
> +{
> + return 0;
> +}
> +#endif
> +
> +/**
> * clk_prepare - prepare a clock source
> * @clk: clock source
> *
> --
> 1.7.9.5
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2013-11-16 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 17:17 [RFC PATCH RESEND 0/2] clk: add clk accuracy support Boris BREZILLON
2013-10-13 17:17 ` [RFC PATCH RESEND 1/2] clk: add clk accuracy retrieval support Boris BREZILLON
2013-11-08 0:51 ` Mike Turquette
2013-11-08 8:54 ` boris brezillon
2013-11-16 0:50 ` Mike Turquette
2013-11-17 15:33 ` boris brezillon
2013-11-17 15:42 ` boris brezillon
2013-11-16 1:59 ` Mike Turquette [this message]
2013-11-18 13:20 ` boris brezillon
2013-10-13 17:17 ` [RFC PATCH RESEND 2/2] clk: add accuracy support for fixed clock Boris BREZILLON
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=20131116015946.19193.29895@quantum \
--to=mturquette@linaro.org \
--cc=b.brezillon@overkiz.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).