public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, sudeep.holla@arm.com,
	james.quinlan@broadcom.com, Jonathan.Cameron@huawei.com,
	f.fainelli@gmail.com, etienne.carriere@linaro.org,
	vincent.guittot@linaro.org, souvik.chakravarty@arm.com,
	wleavitt@marvell.com, peter.hilber@opensynergy.com,
	nicola.mazzucato@arm.com, tarek.el-sherbiny@arm.com
Subject: Re: [RFC PATCH 5/6] firmware: arm_scmi: Add raw transmission support
Date: Tue, 16 Aug 2022 19:03:21 +0100	[thread overview]
Message-ID: <Yvvb6Y+lzuABT1fy@sirena.org.uk> (raw)
In-Reply-To: <20220816072450.3120959-6-cristian.marussi@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 830 bytes --]

On Tue, Aug 16, 2022 at 08:24:49AM +0100, Cristian Marussi wrote:
> Add SCMI Raw mode support which exposes a userspace interface rooted under
> /sys/kernel/debug/scmi_raw.

> Raw mode can be enabled/disabled at runtime via ./scmi_raw/enable.
> Once enabled, all the regular SCMI drivers activity is inhibited and a
> userspace application can then inject and read back bare SCMI messages
> writing and reading to/from ./scmi_raw/message* entries.

Is there a strong reason to have the runtime enable/disable?  Given that
this is going to be used in special kernel builds rather than something
people have as standard it feels like the transition to/from raw mode is
opening up a set of extra use cases that wouldn't normally come up for
the SCMI drivers (especially if the testing ends up leaving the firmware
in a weird state).

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-08-16 18:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  7:24 [RFC PATCH 0/6] Introduce a unified API for SCMI Server testing Cristian Marussi
2022-08-16  7:24 ` [RFC PATCH 1/6] firmware: arm_scmi: Refactor xfer in-flight registration routines Cristian Marussi
2022-08-16  7:24 ` [RFC PATCH 2/6] firmware: arm_scmi: Add bus helpers to enter raw mode Cristian Marussi
2022-08-16  7:24 ` [RFC PATCH 3/6] firmware: arm_scmi: Add xfer raw helpers Cristian Marussi
2022-08-16  7:24 ` [RFC PATCH 4/6] firmware: arm_scmi: Move errors defs and code to common.h Cristian Marussi
2022-08-16  7:24 ` [RFC PATCH 5/6] firmware: arm_scmi: Add raw transmission support Cristian Marussi
2022-08-16 18:03   ` Mark Brown [this message]
2022-08-17  8:38     ` Cristian Marussi
2022-08-17 13:42       ` Mark Brown
2022-08-17 14:21         ` Cristian Marussi
2022-08-16  7:24 ` [RFC PATCH 6/6] firmware: arm_scmi: Call Raw mode hooks from the core stack Cristian Marussi

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=Yvvb6Y+lzuABT1fy@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=cristian.marussi@arm.com \
    --cc=etienne.carriere@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=james.quinlan@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicola.mazzucato@arm.com \
    --cc=peter.hilber@opensynergy.com \
    --cc=souvik.chakravarty@arm.com \
    --cc=sudeep.holla@arm.com \
    --cc=tarek.el-sherbiny@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=wleavitt@marvell.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