{"push_id":826644940,"size":4,"distinct_size":4,"ref":"refs/heads/for-peter-v44","head":"694a0bc832c7d281749f3fcb62eabb8b1dcb2d41","before":"af585cec49920c974f5027b896f42a96f2c8d507","commits":[{"sha":"11edb5034194cfb870225eca0ad6cba9e5651613","author":{"email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com","name":"Jarkko Sakkinen"},"message":"tpm, tpm_tis: fix tpm_tis ACPI detection issue with TPM 2.0\n\nBoth for FIFO and CRB interface TCG has decided to use the same HID\nMSFT0101. They can be differentiated by looking at the start method from\nTPM2 ACPI table. This patches makes necessary fixes to tpm_tis and\ntpm_crb modules in order to correctly detect, which module should be\nused.\n\nFor MSFT0101 we must use struct acpi_driver because struct pnp_driver\nhas a 7 character limitation.\n\nIt turned out that the root cause in b371616b8 was not correct for\nhttps://bugzilla.kernel.org/show_bug.cgi?id=98181.\n\nv2:\n\n* One fixup was missing from v1: is_tpm2_fifo -> is_fifo\n\nv3:\n\n* Use pnp_driver for existing HIDs and acpi_driver only for MSFT0101 in\n  order ensure backwards compatibility.\n\nv4:\n\n* Check for FIFO before doing *anything* in crb_acpi_add().\n* There was return immediately after acpi_bus_unregister_driver() in\n  cleanup_tis(). This caused pnp_unregister_driver() not to be called.\n\nReported-by: Michael Saunders <mick.saunders@gmail.com>\nReported-by: Michael Marley <michael@michaelmarley.com>\nReported-by: Jethro Beekman <kernel@jbeekman.nl>\nReported-by: Matthew Garrett <mjg59@srcf.ucam.org>\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nTested-by: Michael Marley <michael@michaelmarley.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine/linux-tpm2/commits/11edb5034194cfb870225eca0ad6cba9e5651613"},{"sha":"7b135df6675ecf0ee874b66c46103402ddbfea01","author":{"email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com","name":"Jarkko Sakkinen"},"message":"sysfs: added __compat_only_sysfs_link_entry_to_kobj()\n\nAdded a new function __compat_only_sysfs_link_group_to_kobj() that adds\na symlink from attribute or group to a kobject. This needed for\nmaintaining backwards compatibility with PPI attributes in the TPM\ndriver.\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine/linux-tpm2/commits/7b135df6675ecf0ee874b66c46103402ddbfea01"},{"sha":"f0db64c2625e776d46e67acc8f7977a7fa4e4678","author":{"email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com","name":"Jarkko Sakkinen"},"message":"tpm: move the PPI attributes to character device directory.\n\nMoved PPI attributes to the character device directory. This aligns with\nthe sysfs guidelines and makes them race free because they are created\natomically with the character device as part of device_register().The\ncharacter device and the sysfs attributes appear at the same time to the\nuser space.\n\nAs part of this change we enable PPI attributes also for TPM 2.0\ndevices. In order to retain backwards compatibility with TPM 1.x\ndevices, a symlink is created to the platform device directory.\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nReviewed-by: Jason Gunthorpe <jason.gunthorpe@obsidianresearch.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine/linux-tpm2/commits/f0db64c2625e776d46e67acc8f7977a7fa4e4678"},{"sha":"694a0bc832c7d281749f3fcb62eabb8b1dcb2d41","author":{"email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com","name":"Jarkko Sakkinen"},"message":"tpm: update PPI documentation to address the location change.\n\nUpdated Documentation/ABI/testing/sysfs-driver-ppi in order to explain\nwhere PPI attributes are located and how backwards compatibility is\naddressed.\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine/linux-tpm2/commits/694a0bc832c7d281749f3fcb62eabb8b1dcb2d41"}]}