[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e5f7ba28-65b8-30f4-78e6-b3e242054110@quicinc.com>
Date: Tue, 25 Apr 2023 07:01:43 -0700
From: Nikunj Kela <quic_nkela@...cinc.com>
To: <sudeep.holla@....com>
CC: <cristian.marussi@....com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>,
<linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 0/2] Allow parameter in smc/hvc calls
Hi Sudeep, could you please review v4 patches. Thanks!
On 4/18/2023 11:56 AM, 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.
>
> ---
> v4 -> split shmem address into 4KB-pages and offset
>
> v3 -> pass shmem channel address as parameter
>
> v2 -> fix the compilation erros on 32bit platform(see below)
> Reported-by: kernel test robot <lkp@...el.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202304100606.kUjhsRYf-lkp@intel.com/
>
> v1 -> original patches
>
> Nikunj Kela (2):
> dt-bindings: firmware: arm,scmi: support for parameter in smc/hvc call
> firmware: arm_scmi: Augment SMC/HVC to allow optional parameters
>
> .../devicetree/bindings/firmware/arm,scmi.yaml | 8 +++++++-
> drivers/firmware/arm_scmi/driver.c | 1 +
> drivers/firmware/arm_scmi/smc.c | 14 +++++++++++++-
> 3 files changed, 21 insertions(+), 2 deletions(-)
>
Powered by blists - more mailing lists