[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v4 1/6] xen/arm: firmware: Add SCMI over SMC calls handling layer


  • To: "Andrei Cherechesu (OSS)" <andrei.cherechesu@xxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Michal Orzel <michal.orzel@xxxxxxx>
  • Date: Thu, 19 Dec 2024 12:48:08 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=oss.nxp.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Zyby56vWh5zGB3Pcac1H9OfoizXcHv8RILeAHEZ+O+Q=; b=okpMcGjPN8fe7aXjWJTqQXK7C5q17TsBhLGujk4plCOnsA1KdDNjNSF9dJTP4KzFDDZeqs27PqZVd3AhW9rdSlK5lRM2enjfdIIPTl0HB64rR6AzdCf9YkK8Wu/hQCw1aSWoyek/Mhzl7IeQ2b10YBDwiofjVxeH2kwZZl972CU+lsZvS4iVcaNMjtw6OATp4A1HbR4bBjRguF7hEidcqYSAgdSyLUaMEk/zWboqhbWPacmY4OvDmb5tf4OLGJ5GmdMAd9UcqcO4Hu9IJgFmfBPvnng3hKP6K3k/fgmp/qGbYUv/SpUq886o9WatrwvN2fx7hm3aRuNaEbkEGwL1WQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=TAPvNruc73mLo9i/lTjYNVO9VEisvy1fKxl5BXVxDAwKHxIRqISLdxl0QTQgJNSuw+IoINbq4wwuIEl0sjWQIL9Q3X/OWG0su5po6v9HUIV/4/HEdCr9h8CYEoozoyhxT/KsbFdwwBEC8aA1Hx9CHZ/n4dfBvhc9aZ63Y4D/ELmRrPgNOZreJdgbYJNFyKleNPqLsoo4BbjNnuTRU6+mQOmv9Xartqz4b9ZL54yTZDFoftT4Zky+5U8Qiux2Q+NO+G8HvwQaF0/KLkuA8vju0OONpuwxxfA4lhHNFPE3jG8Gq0TAnmdqrTcY19iDwv7mpGZHrNye7Yds3te/woctOw==
  • Cc: <S32@xxxxxxx>, Andrei Cherechesu <andrei.cherechesu@xxxxxxx>, "Stefano Stabellini" <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, "Bertrand Marquis" <bertrand.marquis@xxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>
  • Delivery-date: Thu, 19 Dec 2024 11:48:35 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>


On 19/12/2024 12:23, Andrei Cherechesu (OSS) wrote:
> 
> 
> From: Andrei Cherechesu <andrei.cherechesu@xxxxxxx>
> 
> Introduce the SCMI-SMC layer to have some basic degree of
> awareness about SCMI calls that are based on the ARM System
> Control and Management Interface (SCMI) specification (DEN0056E).
> 
> The SCMI specification includes various protocols for managing
> system-level resources, such as: clocks, pins, reset, system power,
> power domains, performance domains, etc. The clients are named
> "SCMI agents" and the server is named "SCMI platform".
> 
> Only support the shared-memory based transport with SMCs as
> the doorbell mechanism for notifying the platform. Also, this
> implementation only handles the "arm,scmi-smc" compatible,
> requiring the following properties:
>         - "arm,smc-id" (unique SMC ID)
>         - "shmem" (one or more phandles pointing to shmem zones
>         for each channel)
> 
> The initialization is done as initcall, since we need
> SMCs, and PSCI should already probe EL3 FW for SMCCC support.
> If no "arm,scmi-smc" compatible node is found in the host
> DT, the initialization fails silently, as it's not mandatory.
> Otherwise, we get the 'arm,smc-id' DT property from the node,
> to know the SCMI SMC ID we handle. The 'shmem' memory ranges
> are not validated, as the SMC calls are only passed through
> to EL3 FW if coming from the hardware domain.
> 
> Create a new 'firmware' folder to keep the SCMI code separate
> from the generic ARM code.
> 
> Signed-off-by: Andrei Cherechesu <andrei.cherechesu@xxxxxxx>
> Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
NIT for the future. If there are changes in-between the revisions, in general 
you should
drop the Rb/Ab tags. Here you incorporated my feedback, so:
Acked-by: Michal Orzel <michal.orzel@xxxxxxx>

The series is ready to go in. I'll commit it today or tomorrow as I'm waiting 
for
staging to become "green" again. Thanks.

~Michal




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.