public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: Florian Fainelli <f.fainelli@gmail.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,
	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, quic_kshivnan@quicinc.com
Subject: Re: [PATCH v8 00/17] Introduce a unified API for SCMI Server testing
Date: Fri, 20 Jan 2023 09:53:14 +0000	[thread overview]
Message-ID: <Y8pkfJ11iaBiLCQh@e120937-lin> (raw)
In-Reply-To: <e0a09ca8-2ad8-c519-c47e-4707bfb4fe93@gmail.com>

On Thu, Jan 19, 2023 at 01:47:04PM -0800, Florian Fainelli wrote:
> Hi Christian,
> 
Hi Florian,

> On 1/18/23 04:14, Cristian Marussi wrote:
> > Hi all,
> > 
> > This series aims to introduce a new SCMI unified userspace interface meant
> > to ease testing an SCMI Server implementation for compliance, fuzzing etc.,
> > from the perspective of the OSPM agent (non-secure world only ...)
> > 
> > It is proposed as a testing/development facility, it is NOT meant to be a
> > feature to use in production, but only enabled in Kconfig for test
> > deployments.
> > 
> > Currently an SCMI Compliance Suite like the one at [1] can only work by
> > injecting SCMI messages at the SCMI transport layer using the mailbox test
> > driver (CONFIG_MAILBOX_TEST) via its few debugfs entries and looking at
> > the related replies from the SCMI backend Server.
> 
> Took a while but finally:
> 
> Tested-by: Florian Fainelli <f.fainelli@gmail.com>
> 

Thanks for giving it a go.

> Any idea when the raw_mode_support or the acs_raw_mode_support will hit your
> master branch in the scmi-tests repository?

I was holding off waiting for this series to be merged to be sure the
debugfs ABI was not changing anymore, so now, soon-ish, I'll move to request
merge the Raw support in the ACS too; the only further delay regarding this,
that I can think of, could be that I know QA is also adding v3.1 tests to the
ACS and they are too going for the MR in these days, so this could delay a bit
further the Raw support merge.

Thanks,
Cristian


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

  reply	other threads:[~2023-01-20 10:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 12:14 [PATCH v8 00/17] Introduce a unified API for SCMI Server testing Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 01/17] firmware: arm_scmi: Refactor xfer in-flight registration routines Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 02/17] firmware: arm_scmi: Refactor polling helpers Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 03/17] firmware: arm_scmi: Refactor scmi_wait_for_message_response Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 04/17] firmware: arm_scmi: Add flags field to xfer Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 05/17] firmware: arm_scmi: Add xfer Raw helpers Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 06/17] firmware: arm_scmi: Move errors defs and code to common.h Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 07/17] firmware: arm_scmi: Add internal platform/channel IDs Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 08/17] include: trace: Add platform and channel instance references Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 09/17] debugfs: Export debugfs_create_str symbol Cristian Marussi
2023-01-18 13:01   ` Greg Kroah-Hartman
2023-01-18 12:14 ` [PATCH v8 10/17] firmware: arm_scmi: Populate a common SCMI debugsfs root Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 11/17] firmware: arm_scmi: Add debugfs ABI documentation for common entries Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 12/17] firmware: arm_scmi: Add core Raw transmission support Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 13/17] firmware: arm_scmi: Add debugfs ABI documentation for Raw mode Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 14/17] firmware: arm_scmi: Reject SCMI drivers while in " Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 15/17] firmware: arm_scmi: Call Raw mode hooks from the core stack Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 16/17] firmware: arm_scmi: Add Raw mode coexistence support Cristian Marussi
2023-01-18 12:14 ` [PATCH v8 17/17] firmware: arm_scmi: Add per-channel Raw injection support Cristian Marussi
2023-01-19 19:32 ` [PATCH v8 00/17] Introduce a unified API for SCMI Server testing Sudeep Holla
2023-01-19 21:47 ` Florian Fainelli
2023-01-20  9:53   ` Cristian Marussi [this message]
2023-01-20  8:11 ` Vincent Guittot
2023-01-20  9:56   ` Cristian Marussi
2023-01-20 11:38     ` Sudeep Holla
2023-01-20 11:52 ` Sudeep Holla

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=Y8pkfJ11iaBiLCQh@e120937-lin \
    --to=cristian.marussi@arm.com \
    --cc=Jonathan.Cameron@huawei.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=quic_kshivnan@quicinc.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