APPLIED Re: [PATCH 00/13][SRU][OEM-5.17] Add support for Raptor Lake
Timo Aaltonen
tjaalton at ubuntu.com
Tue Jun 28 10:28:53 UTC 2022
On 15.6.2022 11.29, Koba Ko wrote:
> BugLink: https://bugs.launchpad.net/bugs/1978794
>
> [Comment]
> Add support for Raptor Lake on the multiple subsystems.
>
> [Where problems could occur]
> Low
>
> Andy Shevchenko (1):
> pinctrl: alderlake: Add Raptor Lake-S ACPI ID
>
> Even Xu (1):
> HID: intel-ish-hid: ipc: add ADL and RPL device id
>
> Jarkko Nikula (3):
> i2c: i801: Add support for Intel Raptor Lake PCH-S
> spi: pxa2xx: Add support for Intel Raptor Lake PCH-S
> mfd: intel-lpss: Add Intel Raptor Lake PCH-S PCI IDs
>
> Kan Liang (5):
> perf/x86: Add new Alder Lake and Raptor Lake support
> perf/x86/msr: Add new Alder Lake and Raptor Lake support
> perf/x86/cstate: Add new Alder Lake and Raptor Lake support
> perf/x86/uncore: Clean up uncore_pci_ids[]
> perf/x86/uncore: Add new Alder Lake and Raptor Lake support
>
> Mika Westerberg (1):
> spi: intel: Add support for Raptor Lake-S SPI serial flash
>
> Tony Luck (1):
> x86/cpu: Add new Alderlake and Raptorlake CPU model numbers
>
> Zhang Rui (1):
> powercap: intel_rapl: add support for RaptorLake
>
> Documentation/i2c/busses/i2c-i801.rst | 1 +
> arch/x86/events/intel/core.c | 3 +
> arch/x86/events/intel/cstate.c | 3 +
> arch/x86/events/intel/uncore.c | 3 +
> arch/x86/events/intel/uncore_snb.c | 440 +++++++---------------
> arch/x86/events/msr.c | 3 +
> arch/x86/include/asm/intel-family.h | 3 +
> debian.oem/config/annotations | 1 -
> drivers/hid/intel-ish-hid/ipc/hw-ish.h | 2 +
> drivers/hid/intel-ish-hid/ipc/pci-ish.c | 2 +
> drivers/i2c/busses/Kconfig | 1 +
> drivers/i2c/busses/i2c-i801.c | 3 +
> drivers/mfd/intel-lpss-pci.c | 15 +
> drivers/pinctrl/intel/pinctrl-alderlake.c | 1 +
> drivers/powercap/intel_rapl_common.c | 1 +
> drivers/spi/spi-intel-pci.c | 96 +++++
> drivers/spi/spi-pxa2xx.c | 5 +
> 17 files changed, 282 insertions(+), 301 deletions(-)
> create mode 100644 drivers/spi/spi-intel-pci.c
>
applied to to oem-5.17, although if the SRU header has a question "where
problems could occur", the answer can't be "low" ;)
also, since they are cherry-picks I'm assuming they are already
upstream, but the bug should be clear about it so that we don't miss
anything from kinetic (and hwe-k kernel)
--
t
More information about the kernel-team
mailing list