mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Puranjay Mohan <puranjay12@gmail.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
Cc: Puranjay Mohan <p-mohan@ti.com>
Subject: [PATCH 2/2] remoteproc: wkup_m3: Set deny_sysfs_ops flag
Date: Mon, 31 Jan 2022 19:41:52 +0530	[thread overview]
Message-ID: <1643638312-3912-3-git-send-email-p-mohan@ti.com> (raw)
In-Reply-To: <1643638312-3912-1-git-send-email-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 'deny_sysfs_ops' flag
to not allow any overriding of the remoteproc firmware or state
from userspace.

Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Puranjay Mohan <p-mohan@ti.com>
---
 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..bbb84bb28af8 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->deny_sysfs_ops = true;
 
 	wkupm3 = rproc->priv;
 	wkupm3->rproc = rproc;
-- 
2.24.3


      parent reply	other threads:[~2022-01-31 14:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 14:11 [PATCH 0/2] remoteproc sysfs fixes/improvements Puranjay Mohan
2022-01-31 14:11 ` [PATCH 1/2] remoteproc: Introduce deny_sysfs_ops flag Puranjay Mohan
2022-02-03 18:37   ` Mathieu Poirier
2022-02-03 20:10     ` Puranjay Mohan
2022-02-04 17:03       ` Mathieu Poirier
2022-02-03 20:43     ` Bjorn Andersson
2022-02-04 13:17       ` Puranjay Mohan
2022-01-31 14:11 ` 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=1643638312-3912-3-git-send-email-p-mohan@ti.com \
    --to=puranjay12@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=p-mohan@ti.com \
    --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

all inboxes | Powered by JetHome®