Lorenzo, Sudeep, Mark On 15 August 2018 at 12:44, Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx> wrote: > On Fri, Aug 10, 2018 at 02:18:15PM -0600, Lina Iyer wrote: > > [...] > >> >>But, the OSI feature is critical for QCOM mobile platforms. The >> >>last man activities during cpuidle save quite a lot of power. >> > >> >What I expressed above was that, in PSCI based systems (OSI or PC >> >alike), it is up to firmware/hardware to detect "the last man" not >> >the kernel. >> > >> >I need to understand what you mean by "last man activities" to >> >provide feedback here. >> > >> When the last CPU goes down during deep sleep, the following would be >> done >> - Lower resource requirements for shared resources such as clocks, >> busses and regulators that were used by drivers in AP. These shared >> resources when not used by other processors in the SoC may be turned >> off and put in low power state by a remote processor. [1][2] >> - Enable and setup wakeup capable interrupts on an always-on interrupt >> controller, so the GIC and the GPIO controllers may be put in low >> power state. [3][4] >> - Write next known wakeup value to the timer, so the blocks that were >> powered off, may be brought back into operational before the wakeup. >> [4][5] >> >> These are commonly done during suspend, but to achieve a good power >> efficiency, we have to do this when all the CPUs are just executing CPU >> idle. Also, they cannot be done from the firmware (because the data >> required for all this is part of Linux). OSI plays a crucial role in >> determining when to do all this. > > No it does not. It is the power domain cpumasks that allow this code to > make an educated guess on the last cpu running (the kernel), PSCI OSI is > not crucial at all (it is crucial in QC platforms because that's the > only mode supported but that's not a reason I accept as valid since it > does not comply with the PSCI specifications). We can keep argue on this back and forward, but it seems to lead nowhere. As a matter of fact I am also surprised that this kind of discussion pops up, again. I thought we had sorted this out, especially since we have also met face to face, discussing this in detail, several times by now. Well, well, let's try again. :-) First, in regards to complying with the PSCI spec, to me, that sounds like nonsense, sorry! Is the spec stating that the PSCI FW needs to support all the idle states in PC mode, when the optional OSI mode also is supported? To me, it looks like the QCOM PSCI FW supports PC mode, but in that mode only a subset of the idle states can be reached, so that should be fine, no? Moving forward, I am wondering if a more detailed technical description, comparing the benefits from OSI mode vs the benefits from PC mode could help? Or is just a waste of everybody time, as you all already know this? Anyway I am willing to try, just tell me and I provide you with the best details I can give, about why OSI is better suited for these kind of QCOM SoCs. I trust Lina to help to fill in, if/when needed. Why? Simply because I doubt we ever see the QCOM FW for the battery driven embedded devices to support all idles states in the PC mode, so doing a comparison on for example the 410c platform, just doesn't seems to be possible, sorry! I also have another, quite important, concern. That is, ARM decided to put the OSI mode into the PSCI spec, I assume there were reasons for it. Then, when the ARM community wants to implement support for OSI mode, you are now requiring us to proof the justification of it in the spec. To me, that is, nicely stated, weird. :-) But it also worries me, ARM vendors observes the behavior. That said, in the end we are discussing a quite limited amount of lines of code to support PSCI OSI (some which may not even be considered as OSI specific). It's ~200 lines of code, where most of the code lives in a separate new c-file (psci_pm_domain.c). Additionally, existing PC mode only platforms should still work as before, without drawbacks. Really, why are we arguing about this at all? > > As I mentioned in another thread[1] the generic part of this > series may be applicable in a platform agnostic way to the > CPUidle framework, whether that's beneficial it has to be proven > and it is benchmark specific anyway. I don't think this can be made fully platform agnostic. Or maybe you are suggesting another helper layer above the new genpd infrastructure? Anyway, my point is, the genpd backend driver requires knowledge about the FW and the last man standing algorithm, hence a platform agnostic backend doesn't sound feasible to me. > > Lorenzo > > [1]: https://marc.info/?l=linux-pm&m=153382916513032&w=2 Kind regards Uffe
