Message ID | 20181003143824.13059-1-ulf.hansson@linaro.org |
---|---|
Headers | show |
Series | PM / Domains: Support hierarchical CPU arrangement (PSCI/ARM) (a subset) | expand |
On Wed, Oct 3, 2018 at 4:39 PM Ulf Hansson <ulf.hansson@linaro.org> wrote: > > I have digested the review comments so far, including a recent offlist chat > with with Lorenzo Pieralisi around the debatable PSCI changes. More or less I > have a plan for how to move forward. > > However, to avoid re-posting non-changed patches over and over again, I decided > to withhold the more debatable part from this v9, hence this is not the complete > series to make things play. In v9, I have just included the trivial changes, > which are either already acked/reviewed or hopefully can be rather soon/easily. > > My hope is to get this queued for v4.20, to move things forward. I know it's > late, but there are more or less nothing new here since v8. I have no problems with the first three patches in this series, so I can apply them right away. Do you want me to do that? As for the rest, the cpuidle driver patch looks OK to me, but the PSCI-related ones need ACKs. Thanks, Rafael
On Thu, Oct 04, 2018 at 07:07:27PM +0200, Rafael J. Wysocki wrote: [...] > > > I don't see any dependency there, so I'll queue up the 1-3 in > > > pm-domains and the 4-6 in pm-cpuidle. > > > > I do not see why we should merge patches 4-6 for v4.20; they add legacy > > (DT bindings and related parsing code) with no user in the kernel; we > > may still want to tweak them, in particular PSCI DT bindings. > > My impression was that 4-6 have been agreed on due to the ACKs they > carry. I'll drop them if that's not the case. I have not expressed myself correctly: they have been agreed (even though as I said they may require some tweaking) but I see no urgency of merging them in v4.20 since they have no user. They contain DT bindings, that create ABI/legacy, I think it is better to have code that uses them in the kernel before merging them and creating a dependency that is not needed. > > Likewise, it makes no sense to merge patches 7-8 without the rest of > > the PSCI patches. > > OK > > I'll let the ARM camp sort out the PSCI material then. We will do. Thanks, Lorenzo
On 5 October 2018 at 12:47, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote: > On Thu, Oct 04, 2018 at 08:36:24PM +0200, Ulf Hansson wrote: >> On 4 October 2018 at 19:21, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote: >> > On Thu, Oct 04, 2018 at 07:07:27PM +0200, Rafael J. Wysocki wrote: >> > >> > [...] >> > >> >> > > I don't see any dependency there, so I'll queue up the 1-3 in >> >> > > pm-domains and the 4-6 in pm-cpuidle. >> >> > >> >> > I do not see why we should merge patches 4-6 for v4.20; they add legacy >> >> > (DT bindings and related parsing code) with no user in the kernel; we >> >> > may still want to tweak them, in particular PSCI DT bindings. >> >> >> >> My impression was that 4-6 have been agreed on due to the ACKs they >> >> carry. I'll drop them if that's not the case. >> > >> > I have not expressed myself correctly: they have been agreed (even >> > though as I said they may require some tweaking) but I see no urgency >> > of merging them in v4.20 since they have no user. They contain DT >> > bindings, that create ABI/legacy, I think it is better to have code >> > that uses them in the kernel before merging them and creating a >> > dependency that is not needed. >> >> There is already code using the new bindings, for the idle states. >> Please have look at patch 5, 6 and 11. > > I had a look before replying and I reiterate the point, there is > no reason to merge those patches without the rest of the series, > none. There is already a way to describe idle states in the kernel > and it works very well, we will add one when we need it not before. Okay, let's defer them. > >> Moreover, you have had plenty on time to look at the series, as those >> patches haven't changed since a very long time. > > So ? > >> May I suggest you do the review instead, so we can move things >> forward, please. The changes in the v9 series should be trivial to >> review. > > There is no reason to merge patches [4, 5, 6, 10] stand-alone, they > are not solving any problem and they do not provide any benefit > other than adding useless ABI/legacy, they make sense when we look > at the whole series. Okay, let's defer them. > >> >> > Likewise, it makes no sense to merge patches 7-8 without the rest of >> >> > the PSCI patches. >> >> Well, those patches are part of this series, because Mark wanted me to >> move the files. Is really such a big deal? I think it makes sense, no >> matter what happens afterwards. > > We can merge patches [7-8] even if there is no urgency at all to do so, > usually PSCI patches go via arm-soc whose patches queue is now closed > and I do not think that's a problem at all. Okay, let's defer them. That said, can please review the patches? Kind regards Uffe