From: Alex Elder <elder@linaro.org>
To: Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>
Cc: linux-remoteproc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] remoteproc: some bug fixes
Date: Fri, 28 Feb 2020 12:33:55 -0600 [thread overview]
Message-ID: <20200228183359.16229-1-elder@linaro.org> (raw)
This series fixes some bugs in the remoteproc code.
- The first patch moves some checks of the remoteproc state inside
the protection of the mutex.
- The second just eliminates an unsafe state check before calling
a function, because the function will make the same check safely.
- The third does proper recovery in the q6v5_probe() error path.
- The last returns EINVAL if an unrecognized value is written
into the "recovery" debugfs file.
This series is available (based on v5.6-rc3) in branch "remoteproc-v1"
in this git repository:
https://git.linaro.org/people/alex.elder/linux.git
-Alex
Alex Elder (4):
remoteproc: re-check state in rproc_trigger_recovery()
remoteproc: remoteproc debugfs file fixes
remoteproc: qcom: fix q6v5 probe error paths
remoteproc: return error for bad "recovery" debugfs input
drivers/remoteproc/qcom_q6v5_mss.c | 23 +++++++++++++++--------
drivers/remoteproc/remoteproc_core.c | 12 ++++++++----
drivers/remoteproc/remoteproc_debugfs.c | 14 +++++++-------
3 files changed, 30 insertions(+), 19 deletions(-)
--
2.20.1
next reply other threads:[~2020-02-28 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 18:33 Alex Elder [this message]
2020-02-28 18:33 ` [PATCH 1/4] remoteproc: re-check state in rproc_trigger_recovery() Alex Elder
2020-03-09 20:56 ` Mathieu Poirier
2020-03-11 23:44 ` Bjorn Andersson
2020-03-12 2:58 ` Alex Elder
2020-02-28 18:33 ` [PATCH 2/4] remoteproc: remoteproc debugfs file fixes Alex Elder
2020-02-28 18:33 ` [PATCH 3/4] remoteproc: qcom: fix q6v5 probe error paths Alex Elder
2020-02-28 18:33 ` [PATCH 4/4] remoteproc: return error for bad "recovery" debugfs input Alex Elder
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=20200228183359.16229-1-elder@linaro.org \
--to=elder@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.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