From: Puranjay Mohan <p-mohan@ti.com>
To: <kishon@ti.com>, <vigneshr@ti.com>, <s-anna@ti.com>,
<bjorn.andersson@linaro.org>, <mathieu.poirier@linaro.org>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: Puranjay Mohan <p-mohan@ti.com>
Subject: [PATCH v5 2/2] remoteproc: wkup_m3: Set sysfs_read_only flag
Date: Wed, 16 Feb 2022 13:42:24 +0530 [thread overview]
Message-ID: <20220216081224.9956-3-p-mohan@ti.com> (raw)
In-Reply-To: <20220216081224.9956-1-p-mohan@ti.com>
From: Suman Anna <s-anna@ti.com>
The Wakeup M3 remote processor is controlled by the wkup_m3_ipc
client driver, so set the newly introduced 'sysfs_read_only' flag
to not allow any overriding of the remoteproc firmware, state,
recovery, or coredump from userspace.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Puranjay Mohan <p-mohan@ti.com>
Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
---
Changes in v4->v5
rename deny_sysfs_ops to sysfs_read_only
---
drivers/remoteproc/wkup_m3_rproc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/remoteproc/wkup_m3_rproc.c b/drivers/remoteproc/wkup_m3_rproc.c
index 484f7605823e..a0c204cb0979 100644
--- a/drivers/remoteproc/wkup_m3_rproc.c
+++ b/drivers/remoteproc/wkup_m3_rproc.c
@@ -163,6 +163,7 @@ static int wkup_m3_rproc_probe(struct platform_device *pdev)
}
rproc->auto_boot = false;
+ rproc->sysfs_read_only = true;
wkupm3 = rproc->priv;
wkupm3->rproc = rproc;
--
2.17.1
prev parent reply other threads:[~2022-02-16 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 8:12 [PATCH v5 0/2] remoteproc sysfs fixes/improvements Puranjay Mohan
2022-02-16 8:12 ` [PATCH v5 1/2] remoteproc: Introduce sysfs_read_only flag Puranjay Mohan
2022-02-16 20:04 ` Bjorn Andersson
2022-02-17 6:14 ` Puranjay Mohan
2022-02-18 5:00 ` Kishon Vijay Abraham I
2022-02-18 5:54 ` Bjorn Andersson
2022-03-03 8:00 ` [EXTERNAL] " Puranjay Mohan
2022-03-04 16:53 ` Mathieu Poirier
2022-02-16 8:12 ` Puranjay Mohan [this message]
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=20220216081224.9956-3-p-mohan@ti.com \
--to=p-mohan@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=s-anna@ti.com \
--cc=vigneshr@ti.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