On Wed, Jan 07, 2015 at 10:19:52PM +0800, Vince Hsu wrote: > On 04:12:54PM Jan 07, Peter De Schrijver wrote: > > On Wed, Jan 07, 2015 at 06:49:27PM +0800, Vince Hsu wrote: > > > > > > On 01/07/2015 06:19 PM, Peter De Schrijver wrote: > > > >On Mon, Jan 05, 2015 at 04:09:33PM +0100, Thierry Reding wrote: > > > >>* PGP Signed by an unknown key > > > >> > > > >>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 enable > > > >>>>>function. So add a new function which is dedicated to the GPU rail > > > >>>>>gating. Also don't refer to the powergate ID since the GPU ID makes > > > >>>>>no > > > >>>>>sense here. > > > >>>>> > > > >>>>>Signed-off-by: Vince Hsu <vin...@nvidia.com> > > > >>>>To be honest I don't see the point of this patch. > > > >>>>You are bloating the PMC interface by introducing another exported > > > >>>>function that does nothing different than what the current function > > > >>>>already does. > > > >>>> > > > >>>>If you need a way to assert the clamp I would have expected you to > > > >>>>introduce a common function to do this for all power partitions. > > > >>>I thought about adding an tegra_powergate_assert_clamping(), but that > > > >>>doesn't make sense to all the power partitions except GPU. Note the > > > >>>difference in TRM. Any suggestion for the common function? > > > >>I don't think extending the powergate API is useful at this point. We've > > > >>long had an open TODO item to replace this with a generic API. I did > > > >>some prototyping a while ago to use generic power domains for this, that > > > >>way all the details and dependencies between the partitions could be > > > >>properly modeled. > > > >> > > > >>Can you take a look at my staging/powergate branch here: > > > >> > > > >> https://github.com/thierryreding/linux/commits/staging/powergate > > > >> > > > >>and see if you can use that instead? The idea is to completely hide the > > > >>details of power partitions from drivers and use runtime PM instead. > > > >> > > > >>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. > > > >Conceptually I fully agree that we should use runtime PM and > > > >powerdomains. > > > >However I don't think the implementation you mentioned is correct. The > > > >resets > > > >of all modules in a domain need to be asserted and the memory clients > > > >need to > > > >be flushed. All this needs to be done with module clocks enabled (resets > > > >are > > > >synchronous). Then all module clocks need to be disabled and then the > > > >partition can be powergated. After ungating, the module resets need to be > > > >deasserted and the FLUSH bit cleared with clocks enabled. > > > Yeah. I plan to have the information of all the clock client of the > > > partitions and > > > the memory clients be defined statically in c source, e.g. pmc-tegra124.c. > > > All modules can declare which domain they belong to in DT. One domain can > > > be really power gated only when no module is awake. Note the clock > > > clients of > > > one domain might not equal to the clocks of the module. The reset is > > > not either. > > > So I don't get the clock and reset from module. How do you think? > > > > > > > I think it's indeed better to have a direct reference to the required clocks > > to powergate/ungate a domain. As you said, there is no easy way to derive > > the > > required clocks from the DT module declarations. My suggestion would be to > > have powerdomain definitions in DT and for each domain have references to > > the required clocks and resets. > > > And specify the dependencies between domains in DT?
I think the dependencies could be in the driver. Of course the power
domains are per-SoC data, so really shouldn't be in the DTS either (the
data is all implied by the compatible value) but there's no good way to
get at the clocks and resets without DT, so I think that's a reasonable
trade-off.
It seems to me like there are only two dependencies:
DIS and DISB depend on SOR
VE depends on DIS
That's according to 5.6.6 "Programming Guide for Power Gating and
Ungating" of the Tegra K1 TRM. It also seems like a bunch of modules are
part of seemingly unrelated domains. Especially SOR seems to cover a
large range of modules (MIPI-CAL, DPAUX, SOR, HDMI, DSI, DSIB and
HDA2HDMI).
Given that we may want to more fine-grainedly control clocks to save
power, don't we need to control clocks and resets within the drivers? I
think the runtime PM framework makes sure to call this in the right
order, so for suspend, the sequence would be:
1) device->suspend
2) domain->suspend
and for resume:
1) domain->resume
2) device->resume
But then we're back to square one, namely that the MC flush doesn't work
properly, since it needs to be implemented in domain->suspend. Does that
mean we can't clock-gate modules? In order to ensure a proper powergate
sequence, the domain code would need to clk_enable() the module clock to
make sure it stays on during the reset sequence. But if the domain code
has a reference to the clock, then the driver can't clock-gate the
module anymore by calling clk_disable().
Am I missing something?
Thierry
pgpje3cVjArye.pgp
Description: PGP signature
