···105105106106Manual fan control on the other hand, is not exposed directly by the AWCC107107interface. Instead it let's us control a fan `boost` value. This `boost` value108108-has the following aproximate behavior over the fan pwm:108108+has the following approximate behavior over the fan pwm:109109110110::111111
+2-2
Documentation/arch/x86/amd_hsmp.rst
···14141515More details on the interface can be found in chapter1616"7 Host System Management Port (HSMP)" of the family/model PPR1717-Eg: https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/programmer-references/55898_B1_pub_0_50.zip1717+Eg: https://docs.amd.com/v/u/en-US/55898_B1_pub_0_50181819192020HSMP interface is supported on EPYC line of server CPUs and MI300A (APU).···185185186186More details on the interface and message definitions can be found in chapter187187"7 Host System Management Port (HSMP)" of the respective family/model PPR188188-eg: https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/programmer-references/55898_B1_pub_0_50.zip188188+eg: https://docs.amd.com/v/u/en-US/55898_B1_pub_0_50189189190190User space C-APIs are made available by linking against the esmi library,191191which is provided by the E-SMS project https://www.amd.com/en/developer/e-sms.html.
+1-1
Documentation/misc-devices/amd-sbi.rst
···1515More details on the interface can be found in chapter1616"5 Advanced Platform Management Link (APML)" of the family/model PPR [1]_.17171818-.. [1] https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/programmer-references/55898_B1_pub_0_50.zip1818+.. [1] https://docs.amd.com/v/u/en-US/55898_B1_pub_0_50191920202121SBRMI device
···80808181/**8282 * struct pmt_callbacks - Callback infrastructure for PMT devices8383- * ->read_telem() when specified, called by client driver to access PMT data (instead8484- * of direct copy).8585- * @pdev: PCI device reference for the callback's use8686- * @guid: ID of data to acccss8787- * @data: buffer for the data to be copied8888- * @off: offset into the requested buffer8989- * @count: size of buffer8383+ * @read_telem: when specified, called by client driver to access PMT8484+ * data (instead of direct copy).8585+ * * pdev: PCI device reference for the callback's use8686+ * * guid: ID of data to acccss8787+ * * data: buffer for the data to be copied8888+ * * off: offset into the requested buffer8989+ * * count: size of buffer9090 */9191struct pmt_callbacks {9292 int (*read_telem)(struct pci_dev *pdev, u32 guid, u64 *data, loff_t off, u32 count);···120120};121121122122/**123123- * struct intel_sec_device - Auxbus specific device information123123+ * struct intel_vsec_device - Auxbus specific device information124124 * @auxdev: auxbus device struct for auxbus access125125 * @pcidev: pci device associated with the device126126 * @resource: any resources shared by the parent···128128 * @num_resources: number of resources129129 * @id: xarray id130130 * @priv_data: any private data needed131131+ * @priv_data_size: size of private data area131132 * @quirks: specified quirks132133 * @base_addr: base address of entries (if specified)133134 * @cap_id: the enumerated id of the vsec feature