[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpo=4gY42TJ0CcUBarHRnUvFKkXTykTYCfGUnAZ+CFwYE9g@mail.gmail.com>
Date: Mon, 2 Jun 2014 22:25:18 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arvind Chauhan <arvind.chauhan@....com>,
Eduardo Valentin <edubezval@...il.com>,
Pavel Machek <pavel@....cz>,
Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH 1/2] regulators: Add definition of regulator_set_voltage_time()
for !CONFIG_REGULATOR
On 2 June 2014 20:50, Mark Brown <broonie@...nel.org> wrote:
> No, not at all and I don't think it applies to the clock API either -
> it's got similar issues with real physical clocks not always supporting
> all operations. Consider for a moment what happens if we try to set and
> then use a clock rate ona fixed clock.
Okay, so the patch 1/3 isn't enough as we need to fix other drivers as
well which are expected to work with CONFIG_REGULATOR=n. That
would be some work and will try to send a patchset for that..
As Rafael has asked you to apply the patches, can you please apply
patch 2-3 for now?
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists