[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c624bc95-1369-b6ef-5c98-15988955937e@gmail.com>
Date: Tue, 1 Jun 2021 21:00:50 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Thierry Reding <thierry.reding@...il.com>
Cc: Jonathan Hunter <jonathanh@...dia.com>,
Michał Mirosław <mirq-linux@...e.qmqm.pl>,
Nikola Milosavljević <mnidza@...look.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Peter Geis <pgwipeout@...il.com>,
Nicolas Chauvet <kwizart@...il.com>,
Viresh Kumar <vireshk@...nel.org>,
Stephen Boyd <sboyd@...nel.org>,
Matt Merhar <mattmerhar@...tonmail.com>,
Paul Fertser <fercerpav@...il.com>,
Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Mikko Perttunen <mperttunen@...dia.com>,
linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org,
devicetree@...r.kernel.org, linux-pm@...r.kernel.org,
Nathan Chancellor <nathan@...nel.org>,
linux-clk@...r.kernel.org
Subject: Re: [PATCH v6 00/14] NVIDIA Tegra memory and power management changes
for 5.14
01.06.2021 20:10, Thierry Reding пишет:
> On Tue, Jun 01, 2021 at 06:51:33PM +0300, Dmitry Osipenko wrote:
>> 01.06.2021 14:27, Thierry Reding пишет:
>>> On Tue, Jun 01, 2021 at 05:31:05AM +0300, Dmitry Osipenko wrote:
>>>> This series:
>>>>
>>>> 1. Adds CPU/core voltage bump before system is rebooted.
>>>> 2. Adds new devm_tegra_core_dev_init_opp_table() helper and switches
>>>> Tegra memory drivers to use it.
>>>> 3. Adds compile-testing support to the Tegra memory drivers.
>>>> 4. Adds Tegra SoC core power domain support.
>>>>
>>>> Changelog:
>>>>
>>>> v6: - Fixed another compile-test trouble reported for v5. I double checked
>>>> the clk stubs this time and compiled them locally.
>>>
>>> Heh... I just fixed those locally on top of your v5. Let me see if I can
>>> roll back the changes and apply this new set instead.
>>
>> Thank you! You probably saw already that Ulf Hansson suggested to remove
>> the lockdep annotation for now from the core PD, I'll make a v7 with
>> this small change.
>
> Can you perhaps post this change as a follow-up? That way I can just
> merge it into the corresponding branch, which may be easier than backing
> out all the changes spread over four branches and applying basically the
> same thing again.
Alright, I'll make a follow-up. Thank you.
Powered by blists - more mailing lists