From: rjw@rjwysocki.net (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: tegra: add regulator dependency for T124
Date: Sat, 12 Dec 2015 03:26:57 +0100 [thread overview]
Message-ID: <1834718.KShzbrV9CD@vostro.rjw.lan> (raw)
In-Reply-To: <2194927.eV2s2QmZs0@wuerfel>
On Tuesday, December 08, 2015 10:52:45 PM Arnd Bergmann wrote:
> This driver is the only one that calls regulator_sync_voltage(), but it
> can currently be built with CONFIG_REGULATOR disabled, producing
> this build error:
>
> drivers/cpufreq/tegra124-cpufreq.c: In function 'tegra124_cpu_switch_to_pllx':
> drivers/cpufreq/tegra124-cpufreq.c:68:2: error: implicit declaration of function 'regulator_sync_voltage' [-Werror=implicit-function-declaration]
> regulator_sync_voltage(priv->vdd_cpu_reg);
>
> My first attempt was to implement a helper for this function
> for regulator_sync_voltage, but Mark Brown explained:
>
> We don't do this for *all* regulator API functions - there's some where
> using them strongly suggests that there is actually a dependency on
> the regulator API. This does seem like it might be falling into the
> specialist category [...]
> Looking at the code I'm pretty unclear on what the authors think the
> use of _sync_voltage() is doing in the first place so it may be even
> better to just remove the call. It seems to have been included in the
> first commit so there's not changelog explaining things and there's
> no comment either. I'd *expect* it to be a noop as far as I can see.
>
> This adds the dependency to make the driver always build successfully
> or not be enabled at all. Alternatively, we could investigate if the
> driver should stop calling regulator_sync_voltage instead.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied, thanks!
Rafael
prev parent reply other threads:[~2015-12-12 2:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 21:52 [PATCH] cpufreq: tegra: add regulator dependency for T124 Arnd Bergmann
2015-12-09 2:16 ` Viresh Kumar
2015-12-09 12:03 ` Jon Hunter
2015-12-09 14:47 ` Mark Brown
2015-12-09 17:33 ` Jon Hunter
2015-12-09 20:10 ` Mark Brown
2015-12-10 10:07 ` Jon Hunter
2015-12-10 11:35 ` Mark Brown
2015-12-10 12:12 ` Jon Hunter
2015-12-12 2:26 ` Rafael J. Wysocki [this message]
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=1834718.KShzbrV9CD@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--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 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).