All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] firmware: scmi: fix sandbox and related test since clock discovery
Date: Sat, 15 May 2021 09:20:05 -0600	[thread overview]
Message-ID: <CAPnjgZ2Ybw_WLMymMcYtxQszm2d+Mv8PKV3SVvTScwHPQOxDFw@mail.gmail.com> (raw)
In-Reply-To: <20210512145424.13184-2-etienne.carriere@linaro.org>

On Wed, 12 May 2021 at 08:55, Etienne Carriere
<etienne.carriere@linaro.org> wrote:
>
> Since SCMI clock are discovered because of integration in the CCF,
> update SCMI emulation in sandbox accordingly. Sandbox must emulate all
> clocks exposed by SCMI server since CCF clock discovery will query all
> of them even if some clocks have no consumer. This change adds clock
> discovery support in the sandbox and changes clock IDs so that less
> clock shall be managed as each SCMI clock ID is actually an index
> identifier.
>
> For consistency, update also sandbox SCMI reset controller test to
> conform with the IDs being also indices of exposed resources as per
> SCMI specification.
>
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
> ---
>  arch/sandbox/dts/test.dts                  |   4 +-
>  arch/sandbox/include/asm/scmi_test.h       |   2 -
>  drivers/firmware/scmi/sandbox-scmi_agent.c | 102 ++++++++++++++++++---
>  test/dm/scmi.c                             |  29 ++++--
>  4 files changed, 113 insertions(+), 24 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

  reply	other threads:[~2021-05-15 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 14:54 [PATCH 1/2] clk: scmi: register all scmi clock by name with CCF Etienne Carriere
2021-05-12 14:54 ` [PATCH 2/2] firmware: scmi: fix sandbox and related test since clock discovery Etienne Carriere
2021-05-15 15:20   ` Simon Glass [this message]
2021-05-15 15:20 ` [PATCH 1/2] clk: scmi: register all scmi clock by name with CCF Simon Glass

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=CAPnjgZ2Ybw_WLMymMcYtxQszm2d+Mv8PKV3SVvTScwHPQOxDFw@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.