From: boris brezillon <b.brezillon@overkiz.com>
To: "Mike Turquette" <mturquette@linaro.org>,
"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>,
"Nicolas Ferre" <nicolas.ferre@atmel.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] clk: add clk accuracy retrieval support
Date: Thu, 19 Dec 2013 09:54:07 +0100 [thread overview]
Message-ID: <52B2B42F.9010202@overkiz.com> (raw)
In-Reply-To: <20131219060431.18119.64699@quantum>
Hello Mike,
On 19/12/2013 07:04, Mike Turquette wrote:
> Quoting Boris BREZILLON (2013-12-17 06:36:22)
>> +unsigned long __clk_get_accuracy(struct clk *clk)
>> +{
>> + unsigned long ret;
>> +
>> + if (!clk)
>> + return 0;
>> +
>> + return clk->accuracy;
>> +}
>> +EXPORT_SYMBOL_GPL(__clk_get_accuracy);
> Any reason for exporting this?
This might be used by clk drivers to choose the most accurate clk
among its parent clks (within the determinate_rate callback).
And as some clk drivers might be compiled as modules we need
to export the symbol (__clk_get_name helper function is exported
too).
Best Regards,
Boris
>
> Regards,
> Mike
next prev parent reply other threads:[~2013-12-19 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 14:36 [PATCH v3 0/2] clk: add clk accuracy support Boris BREZILLON
2013-12-17 14:36 ` [PATCH v3 1/2] clk: add clk accuracy retrieval support Boris BREZILLON
[not found] ` <20131219060431.18119.64699@quantum>
2013-12-19 8:54 ` boris brezillon [this message]
[not found] ` <20131219193633.18119.57678@quantum>
2013-12-19 19:41 ` boris brezillon
2013-12-17 14:36 ` [PATCH v3 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=52B2B42F.9010202@overkiz.com \
--to=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=mturquette@linaro.org \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.org \
--cc=u.kleine-koenig@pengutronix.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).