From: Timo Alho <talho@nvidia.com>
To: <thierry.reding@gmail.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Timo Alho <talho@nvidia.com>
Subject: [PATCH 0/4] firmware: tegra: add checks for BPMP error return code
Date: Thu, 7 Sep 2017 12:31:00 +0300 [thread overview]
Message-ID: <cover.1504776489.git.talho@nvidia.com> (raw)
Hi Thierry,
There is a bug in the BPMP driver as error code in response message is
not being checked.
Patch 1 adds the error code as part of tegra_bpmp_message struct and
propagates that code to callers
Patches 2 through 4 add code to client drivers to check the error code
appropriately
BR,
Timo
Timo Alho (4):
firmware: tegra: propagate error code to caller
clk: tegra: check BPMP response return code
reset: tegra: check BPMP response return code
soc/tegra: bpmp: check BPMP response return code
drivers/clk/tegra/clk-bpmp.c | 15 ++++++++++-----
drivers/firmware/tegra/bpmp.c | 22 ++++++++++++++++------
drivers/reset/tegra/reset-bpmp.c | 9 ++++++++-
drivers/soc/tegra/powergate-bpmp.c | 15 +++++++++++++--
include/soc/tegra/bpmp.h | 1 +
5 files changed, 48 insertions(+), 14 deletions(-)
--
2.7.4
next reply other threads:[~2017-09-07 9:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 9:31 Timo Alho [this message]
2017-09-07 9:31 ` [PATCH 1/4] firmware: tegra: propagate error code to caller Timo Alho
2017-09-21 11:19 ` Jon Hunter
2017-10-17 10:41 ` Thierry Reding
2017-09-07 9:31 ` [PATCH 2/4] clk: tegra: check BPMP response return code Timo Alho
2017-09-21 11:21 ` Jon Hunter
2017-09-29 13:46 ` Timo Alho
2017-09-29 14:53 ` Jon Hunter
2017-10-02 8:43 ` Timo Alho
2017-10-02 20:23 ` Jon Hunter
2017-10-17 10:37 ` Thierry Reding
2017-10-21 14:10 ` Stephen Boyd
2017-09-07 9:31 ` [PATCH 3/4] reset: " Timo Alho
2017-10-02 20:24 ` Jon Hunter
2017-10-17 10:40 ` Thierry Reding
2017-10-17 10:52 ` Philipp Zabel
2017-10-17 11:49 ` Thierry Reding
2017-09-07 9:31 ` [PATCH 4/4] soc/tegra: bpmp: " Timo Alho
2017-10-02 20:26 ` Jon Hunter
2017-10-17 10:41 ` Thierry Reding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1504776489.git.talho@nvidia.com \
--to=talho@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).