[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251015121533.GF3938986@ziepe.ca>
Date: Wed, 15 Oct 2025 09:15:33 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@...nel.org>,
Jeremy Linton <jeremy.linton@....com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Dan Williams <dan.j.williams@...el.com>, linux-coco@...ts.linux.dev,
kvmarm@...ts.linux.dev, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, aik@....com, lukas@...ner.de,
Samuel Ortiz <sameo@...osinc.com>,
Xu Yilun <yilun.xu@...ux.intel.com>,
Suzuki K Poulose <Suzuki.Poulose@....com>,
Steven Price <steven.price@....com>,
Catalin Marinas <catalin.marinas@....com>,
Marc Zyngier <maz@...nel.org>, Will Deacon <will@...nel.org>,
Oliver Upton <oliver.upton@...ux.dev>
Subject: Re: [RFC PATCH v1 11/38] KVM: arm64: CCA: register host tsm platform
device
On Wed, Oct 15, 2025 at 01:57:38PM +0200, Greg KH wrote:
> If this really is a firmware thing, and you have a firmware device, then
> I am confused why this was even brought up at all? Use a real platform
> device, with the resources that are needed to talk to this platform
> device and you should be fine.
I think the issue today is the PSCI does not always get a
platform_device, fixing that seems straightforward then all the
downstream things can switch from using more platform devices to using
an aux device with the PSCI as the parent..
> BUT, if you are making child devices that are NOT actually talking to
> the firmware,
This thread is about how to bind various subsystems to this shared
firmware interface.
Jason
Powered by blists - more mailing lists