[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241210144025.GG1888283@ziepe.ca>
Date: Tue, 10 Dec 2024 10:40:25 -0400
From: Jason Gunthorpe <jgg@...pe.ca>
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: linux-coco@...ts.linux.dev, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Huewe <peterhuewe@....de>, "H. Peter Anvin" <hpa@...or.com>,
linux-integrity@...r.kernel.org,
James Bottomley <James.Bottomley@...senpartnership.com>,
x86@...nel.org, Joerg Roedel <jroedel@...e.de>,
Jarkko Sakkinen <jarkko@...nel.org>, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Claudio Carvalho <cclaudio@...ux.ibm.com>,
Dov Murik <dovmurik@...ux.ibm.com>,
Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [PATCH 3/3] x86/sev: add a SVSM vTPM platform device
On Tue, Dec 10, 2024 at 03:34:23PM +0100, Stefano Garzarella wrote:
> + if (platform_device_add_data(&tpm_device, &pops, sizeof(pops)))
> + return -ENODEV;
> + if (platform_device_register(&tpm_device))
> + return -ENODEV;
This seems like an old fashioned way to instantiate a device. Why do
this? Just put the TPM driver here and forget about pops? Simple tpm
drivers are not very complex.
Jason
Powered by blists - more mailing lists