drivers/char/tpm/tpm_svsm.c
Source file repositories/reference/linux-study-clean/drivers/char/tpm/tpm_svsm.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/char/tpm/tpm_svsm.c- Extension
.c- Size
- 3051 bytes
- Lines
- 122
- Domain
- Driver Families
- Bucket
- drivers/char
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/kernel.hlinux/platform_device.hlinux/tpm_svsm.hasm/sev.htpm.h
Detected Declarations
struct tpm_svsm_privfunction tpm_svsm_sendfunction tpm_svsm_probefunction tpm_svsm_remove
Annotated Snippet
struct tpm_svsm_priv {
void *buffer;
};
static int tpm_svsm_send(struct tpm_chip *chip, u8 *buf, size_t bufsiz,
size_t cmd_len)
{
struct tpm_svsm_priv *priv = dev_get_drvdata(&chip->dev);
int ret;
ret = svsm_vtpm_cmd_request_fill(priv->buffer, 0, buf, cmd_len);
if (ret)
return ret;
/*
* The SVSM call uses the same buffer for the command and for the
* response, so after this call, the buffer will contain the response.
*
* Note: we have to use an internal buffer because the device in SVSM
* expects the svsm_vtpm header + data to be physically contiguous.
*/
ret = snp_svsm_vtpm_send_command(priv->buffer);
if (ret)
return ret;
return svsm_vtpm_cmd_response_parse(priv->buffer, buf, bufsiz);
}
static struct tpm_class_ops tpm_chip_ops = {
.flags = TPM_OPS_AUTO_STARTUP,
.send = tpm_svsm_send,
};
static int __init tpm_svsm_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
struct tpm_svsm_priv *priv;
struct tpm_chip *chip;
int err;
priv = devm_kmalloc(dev, sizeof(*priv), GFP_KERNEL);
if (!priv)
return -ENOMEM;
/*
* The maximum buffer supported is one page (see SVSM_VTPM_MAX_BUFFER
* in tpm_svsm.h).
*/
priv->buffer = (void *)devm_get_free_pages(dev, GFP_KERNEL, 0);
if (!priv->buffer)
return -ENOMEM;
chip = tpmm_chip_alloc(dev, &tpm_chip_ops);
if (IS_ERR(chip))
return PTR_ERR(chip);
dev_set_drvdata(&chip->dev, priv);
chip->flags |= TPM_CHIP_FLAG_SYNC;
err = tpm2_probe(chip);
if (err)
return err;
err = tpm_chip_register(chip);
if (err)
return err;
dev_info(dev, "SNP SVSM vTPM %s device\n",
(chip->flags & TPM_CHIP_FLAG_TPM2) ? "2.0" : "1.2");
return 0;
}
static void __exit tpm_svsm_remove(struct platform_device *pdev)
{
struct tpm_chip *chip = platform_get_drvdata(pdev);
tpm_chip_unregister(chip);
}
/*
* tpm_svsm_remove() lives in .exit.text. For drivers registered via
* module_platform_driver_probe() this is ok because they cannot get unbound
* at runtime. So mark the driver struct with __refdata to prevent modpost
* triggering a section mismatch warning.
*/
static struct platform_driver tpm_svsm_driver __refdata = {
.remove = __exit_p(tpm_svsm_remove),
.driver = {
.name = "tpm-svsm",
Annotation
- Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/platform_device.h`, `linux/tpm_svsm.h`, `asm/sev.h`, `tpm.h`.
- Detected declarations: `struct tpm_svsm_priv`, `function tpm_svsm_send`, `function tpm_svsm_probe`, `function tpm_svsm_remove`.
- Atlas domain: Driver Families / drivers/char.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.