[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d237c089-88d7-32ec-04cf-f04417b0ef4b@kapsi.fi>
Date: Mon, 4 Oct 2021 09:51:29 +0300
From: Mikko Perttunen <cyndis@...si.fi>
To: Viresh Kumar <viresh.kumar@...aro.org>,
Mikko Perttunen <mperttunen@...dia.com>
Cc: rafael@...nel.org, thierry.reding@...il.com, jonathanh@...dia.com,
krzysztof.kozlowski@...onical.com, lorenzo.pieralisi@....com,
robh@...nel.org, kw@...ux.com, p.zabel@...gutronix.de,
rui.zhang@...el.com, daniel.lezcano@...aro.org, amitk@...nel.org,
linux-pm@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH 4/5] cpufreq: tegra186/tegra194: Handle errors in BPMP
response
On 10/4/21 9:37 AM, Viresh Kumar wrote:
> On 15-09-21, 11:55, Mikko Perttunen wrote:
>> The return value from tegra_bpmp_transfer indicates the success or
>> failure of the IPC transaction with BPMP. If the transaction
>> succeeded, we also need to check the actual command's result code.
>> Add code to do this.
>>
>> While at it, explicitly handle missing CPU clusters, which can
>> occur on floorswept chips. This worked before as well, but
>> possibly only by accident.
>>
>> Signed-off-by: Mikko Perttunen <mperttunen@...dia.com>
>> ---
>> drivers/cpufreq/tegra186-cpufreq.c | 4 ++++
>> drivers/cpufreq/tegra194-cpufreq.c | 8 +++++++-
>> 2 files changed, 11 insertions(+), 1 deletion(-)
>
> Should I apply it alone ?
>
Yes please, all of these patches are independent of each other.
Mikko
Powered by blists - more mailing lists