From: Sudeep Holla <sudeep.holla@arm.com>
To: Nikunj Kela <quic_nkela@quicinc.com>
Cc: cristian.marussi@arm.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] Allow parameter in smc/hvc calls
Date: Tue, 9 May 2023 17:01:00 +0100 [thread overview]
Message-ID: <20230509160100.2reb4il5enadjaum@bogus> (raw)
In-Reply-To: <20230506182428.25343-1-quic_nkela@quicinc.com>
On Sat, May 06, 2023 at 11:24:26AM -0700, Nikunj Kela wrote:
> Currently, smc/hvc calls are made with parameters set
> to zeros. We are using multiple scmi instances within
> a VM. We are sharing the same smc-id(func_id) with all
> scmi instance. The hypervisor needs a way to distinguish
> among hvc calls made from different instances.
>
> This patch series introduces new compatible string which
> can be used to pass shmem channel address as parameters
> to smc/hvc calls.
>
> ---
> v5 -> avoid computing page and offset in send function
> Link: https://lore.kernel.org/all/20230418185659.29745-1-quic_nkela@quicinc.com/
>
Thanks for the updated patch. I will pick this up for v6.5 and update
once queued.
--
Regards,
Sudeep
next prev parent reply other threads:[~2023-05-09 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 18:24 [PATCH v5 0/2] Allow parameter in smc/hvc calls Nikunj Kela
2023-05-06 18:24 ` [PATCH v5 1/2] dt-bindings: firmware: arm,scmi: support for parameter in smc/hvc call Nikunj Kela
2023-05-08 17:47 ` Florian Fainelli
2023-05-06 18:24 ` [PATCH v5 2/2] firmware: arm_scmi: Augment SMC/HVC to allow optional parameters Nikunj Kela
2023-05-08 17:46 ` Florian Fainelli
2023-05-09 16:01 ` Sudeep Holla [this message]
2023-05-31 12:26 ` [PATCH v5 0/2] Allow parameter in smc/hvc calls Sudeep Holla
[not found] ` <110da0da-211d-1a3f-e007-ddab272aece7@quicinc.com>
[not found] ` <20230630094441.fxwd4eagtj5wmbbg@bogus>
2023-06-30 15:14 ` Nikunj Kela
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=20230509160100.2reb4il5enadjaum@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_nkela@quicinc.com \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).