From: Rishabh Bhatnagar <rishabhb@codeaurora.org>
To: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: bjorn.andersson@linaro.org, mathieu.poirier@linaro.org,
tsoni@codeaurora.org, psodagud@codeaurora.org,
sidgup@codeaurora.org,
Rishabh Bhatnagar <rishabhb@codeaurora.org>
Subject: [PATCH 0/2] Move recovery and coredump interface to sysfs
Date: Tue, 28 Jul 2020 16:08:15 -0700 [thread overview]
Message-ID: <1595977697-15389-1-git-send-email-rishabhb@codeaurora.org> (raw)
From Android R onwards Google has restricted access to debugfs in user
and user-debug builds. This restricts access to most of the features
exposed through debugfs. 'Coredump' and 'Recovery' are critical interfaces
that are required for remoteproc to work on Qualcomm Chipsets. Coredump
configuration needs to be set to "inline" in debug/test builds and
"disabled" in production builds. Whereas recovery needs to be "disabled"
for debugging purposes and "enabled" on production builds. Moving these
interfaces to sysfs will allow usage for these interfaces for
production and debug builds.
Rishabh Bhatnagar (2):
remoteproc: Move coredump entry from debugfs to sysfs.
remoteproc: Move recovery debugfs entry to sysfs
Documentation/ABI/testing/sysfs-class-remoteproc | 76 +++++++++++
drivers/remoteproc/remoteproc_debugfs.c | 167 -----------------------
drivers/remoteproc/remoteproc_sysfs.c | 123 +++++++++++++++++
3 files changed, 199 insertions(+), 167 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2020-07-28 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 23:08 Rishabh Bhatnagar [this message]
2020-07-28 23:08 ` [PATCH 1/2] remoteproc: Move coredump entry from debugfs to sysfs Rishabh Bhatnagar
2020-08-18 20:02 ` Mathieu Poirier
2020-07-28 23:08 ` [PATCH 2/2] remoteproc: Move recovery debugfs entry " Rishabh Bhatnagar
2020-08-18 20:12 ` Mathieu Poirier
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=1595977697-15389-1-git-send-email-rishabhb@codeaurora.org \
--to=rishabhb@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=psodagud@codeaurora.org \
--cc=sidgup@codeaurora.org \
--cc=tsoni@codeaurora.org \
/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