On Thu, Nov 10, 2022 at 01:45:05PM +0000, Sudeep Holla wrote: > FFH Operation Region space can be used to trigger SMC or HVC calls, > using the Arm SMC Calling Convention (SMCCC). The choice of conduit > (SMC or HVC) is based on what the kernel choose based on PSCI as with > any other users of SMCCC within the kernel. > > Function identifiers only in the SMCCC SiP Service, OEM Service and FF-A > specific call range are allowed in FFH Opregions. > > Offset can be either 0(32 bit calling convention) or 1(64 bit calling > convention). The length must be set with the range applicable based > on the value of the offset. > > Acked-by: Catalin Marinas <catalin.marinas@xxxxxxx> > Cc: Will Deacon <will@xxxxxxxxxx> > Signed-off-by: Sudeep Holla <sudeep.holla@xxxxxxx> > --- > Hi Will, > > Catalin had acked the changes to be routed via PM tree for last or the > one previous merge window. Since we were waiting for ACPICA changes, it > was not merged. Now that ACPICA changes are queued(via PM tree), I will > ask Rafael to take these patches now. Just thought I will let you know > since you are handling upcoming merge window and I do see few ACPI related > changes there. I don't see any conflict with this, so it should be fine. > > Please let me know if you are fine with that and ack is an add-on :). I'm happy either way, so I'll leave this for Rafael but just poke me if you want me to queue them instead. Will
