Displaying 6 results from an estimated 6 matches for "regulator_".
Did you mean:
regulator
2015 Jan 06
2
[PATCH 1/11] ARM: tegra: add function to control the GPU rail clamp
...y the PMC
> except the clamping control, and GK20A has its own power rail, do we really
> want to hide the power sequence in the generic powergate code? We still have
> to control the voltage level in the GK20A driver through the regulator
> framework. It seems weird to me if we put the regulator_{enable|disable}
> somewhere other than the GK20A driver.
I think we want both. The power domain to control the power partition
and the regulator in the gk20a driver for the voltage control.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not availabl...
2015 Jan 06
2
[PATCH 1/11] ARM: tegra: add function to control the GPU rail clamp
...e clamping control, and GK20A has its own power rail, do we really
> >>want to hide the power sequence in the generic powergate code? We still have
> >>to control the voltage level in the GK20A driver through the regulator
> >>framework. It seems weird to me if we put the regulator_{enable|disable}
> >>somewhere other than the GK20A driver.
> >I think we want both. The power domain to control the power partition
> >and the regulator in the gk20a driver for the voltage control.
> Do you mean excluding the power sequence of GK20A from the generic power
&g...
2015 Jan 06
0
[PATCH 1/11] ARM: tegra: add function to control the GPU rail clamp
...owered on/off by the
PMC except the clamping control, and GK20A has its own power rail, do we
really want to hide the power sequence in the generic powergate code? We
still have to control the voltage level in the GK20A driver through the
regulator framework. It seems weird to me if we put the
regulator_{enable|disable} somewhere other than the GK20A driver.
Thanks,
Vince
>
> Also adding Peter whom I had discussed this with earlier. Can we finally
> get this converted? I'd rather not keep complicating this custom API to
> avoid making the conversion even more difficult.
>
>...
2015 Jan 06
0
[PATCH 1/11] ARM: tegra: add function to control the GPU rail clamp
...t; except the clamping control, and GK20A has its own power rail, do we really
>> want to hide the power sequence in the generic powergate code? We still have
>> to control the voltage level in the GK20A driver through the regulator
>> framework. It seems weird to me if we put the regulator_{enable|disable}
>> somewhere other than the GK20A driver.
> I think we want both. The power domain to control the power partition
> and the regulator in the gk20a driver for the voltage control.
Do you mean excluding the power sequence of GK20A from the generic power
domain?
Thanks,
V...
2015 Jan 06
0
[PATCH 1/11] ARM: tegra: add function to control the GPU rail clamp
...rol, and GK20A has its own power rail, do we really
> > >>want to hide the power sequence in the generic powergate code? We still have
> > >>to control the voltage level in the GK20A driver through the regulator
> > >>framework. It seems weird to me if we put the regulator_{enable|disable}
> > >>somewhere other than the GK20A driver.
> > >I think we want both. The power domain to control the power partition
> > >and the regulator in the gk20a driver for the voltage control.
> > Do you mean excluding the power sequence of GK20A from...
2015 Jan 05
4
[PATCH 1/11] ARM: tegra: add function to control the GPU rail clamp
On Thu, Dec 25, 2014 at 10:28:08AM +0800, Vince Hsu wrote:
> On 12/24/2014 09:16 PM, Lucas Stach wrote:
> >Am Dienstag, den 23.12.2014, 18:39 +0800 schrieb Vince Hsu:
> >>The Tegra124 and later Tegra SoCs have a sepatate rail gating register
> >>to enable/disable the clamp. The original function
> >>tegra_powergate_remove_clamping() is not sufficient for the