[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YV86cX/omlQa3kpq@orome.fritz.box>
Date: Thu, 7 Oct 2021 20:20:33 +0200
From: Thierry Reding <thierry.reding@...il.com>
To: Mikko Perttunen <mperttunen@...dia.com>
Cc: rafael@...nel.org, viresh.kumar@...aro.org, 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 1/5] thermal: tegra-bpmp: Handle errors in BPMP response
On Wed, Sep 15, 2021 at 11:55:13AM +0300, 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.
>
> Signed-off-by: Mikko Perttunen <mperttunen@...dia.com>
> ---
> drivers/thermal/tegra/tegra-bpmp-thermal.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
Perhaps this should be moved into tegra_bpmp_transfer() or some new
helper to make sure we can keep this consistent across all callers.
For instance, I'm not sure -EINVAL is the right (or best) error code in
all the cases. Either way, seems fine in this case and this is certainly
an improvement, so:
Acked-by: Thierry Reding <treding@...dia.com>
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists