Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1303595 > unrolled thread

Re: [PATCH] soc: qcom: Add support for SAW2 regulators

Started byGeorgi Djakov <georgi.djakov@linaro.org>
First post2016-01-07 14:50 +0100
Last post2016-01-12 03:40 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] soc: qcom: Add support for SAW2 regulators Georgi Djakov <georgi.djakov@linaro.org> - 2016-01-07 14:50 +0100
    Re: [PATCH] soc: qcom: Add support for SAW2 regulators Stephen Boyd <sboyd@codeaurora.org> - 2016-01-12 03:40 +0100

#1303595 — Re: [PATCH] soc: qcom: Add support for SAW2 regulators

FromGeorgi Djakov <georgi.djakov@linaro.org>
Date2016-01-07 14:50 +0100
SubjectRe: [PATCH] soc: qcom: Add support for SAW2 regulators
Message-ID<qOj6W-kZ-7@gated-at.bofh.it>
On 12/18/2015 07:22 PM, Mark Brown wrote:
> On Fri, Dec 18, 2015 at 06:14:58PM +0200, Georgi Djakov wrote:
>> The SAW2 (Subsystem Power Manager and Adaptive Voltage Scaling Wrapper)
>> is part of the SPM subsystem. It is a hardware block found on some of the
>> Qualcomm chipsets, which regulates the power to the CPU cores. Add some
>> basic support for it, so that we can do dynamic voltage scaling.
>>
>> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
>> ---
>>  drivers/soc/qcom/spm.c |  149 +++++++++++++++++++++++++++++++++++++++++++++++-
> 
> Please don't implement regualtors outside of the regulator driver
> directory unless there is a really strong reason to do so, it makes it
> much easier to maintain the subsystem and keep track of what's going on.
> 

The reason of implementing the regulator functionality in drivers/soc is
that it is part of the same hardware. The saw2 hardware manages the power
controls - switching to low-power sleep modes, adaptive voltage scaling,
voltage control and messaging to the PMIC. Keeping all the functionality
of this hardware into a single driver seemed the suitable approach to me.
But if you think this is not a strong reason, then the approach probably
would be to export parts of the existing driver and use syscon from a
separate driver in drivers/regulator?

Thanks,
Georgi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1306939

FromStephen Boyd <sboyd@codeaurora.org>
Date2016-01-12 03:40 +0100
Message-ID<qPX2i-2Wn-5@gated-at.bofh.it>
In reply to#1303595
On 01/07, Georgi Djakov wrote:
> On 12/18/2015 07:22 PM, Mark Brown wrote:
> > On Fri, Dec 18, 2015 at 06:14:58PM +0200, Georgi Djakov wrote:
> >> The SAW2 (Subsystem Power Manager and Adaptive Voltage Scaling Wrapper)
> >> is part of the SPM subsystem. It is a hardware block found on some of the
> >> Qualcomm chipsets, which regulates the power to the CPU cores. Add some
> >> basic support for it, so that we can do dynamic voltage scaling.
> >>
> >> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
> >> ---
> >>  drivers/soc/qcom/spm.c |  149 +++++++++++++++++++++++++++++++++++++++++++++++-
> > 
> > Please don't implement regualtors outside of the regulator driver
> > directory unless there is a really strong reason to do so, it makes it
> > much easier to maintain the subsystem and keep track of what's going on.
> > 
> 
> The reason of implementing the regulator functionality in drivers/soc is
> that it is part of the same hardware. The saw2 hardware manages the power
> controls - switching to low-power sleep modes, adaptive voltage scaling,
> voltage control and messaging to the PMIC. Keeping all the functionality
> of this hardware into a single driver seemed the suitable approach to me.

It's also weird because sometimes we need to configure something
for the regulator that lives on the PMIC with SSBI or SPMI
transactions. So we get this split bus driver where we want to do
some stuff over the pmic bus (SSBI/SPMI) and then change voltages
with MMIO writes in the SAW IP block. Plus we can't figure out
the initial voltage for the regulator without reading the voltage
out over the pmic bus. A plain MMIO regulator through the SAW
hardware is pretty much limited to setting voltages and on/off.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web