[PATCH] spi: intel-pci: Add support for Meteor Lake-S SPI serial flash

[PATCH] spi: intel-pci: Add support for Meteor Lake-S SPI serial flash

[Mika Westerberg]

Intel Meteor Lake-S has the same SPI serial flash controller as Meteor
Lake-P. Add Meteor Lake-S PCI ID to the driver list of supported
devices.

Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
---
 drivers/spi/spi-intel-pci.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/spi/spi-intel-pci.c b/drivers/spi/spi-intel-pci.c
index 00b140903e4e..87de0e3eb451 100644
--- a/drivers/spi/spi-intel-pci.c
+++ b/drivers/spi/spi-intel-pci.c
@@ -83,6 +83,7 @@ static const struct pci_device_id intel_spi_pci_ids[] = {
 	{ PCI_VDEVICE(INTEL, 0xa2a4), (unsigned long)&cnl_info },
 	{ PCI_VDEVICE(INTEL, 0xa324), (unsigned long)&cnl_info },
 	{ PCI_VDEVICE(INTEL, 0xa3a4), (unsigned long)&cnl_info },
+	{ PCI_VDEVICE(INTEL, 0xae23), (unsigned long)&cnl_info },
 	{ },
 };
 MODULE_DEVICE_TABLE(pci, intel_spi_pci_ids);
-- 
2.39.2

Re: [PATCH] spi: intel-pci: Add support for Meteor Lake-S SPI serial flash

[Mark Brown]

On Fri, 31 Mar 2023 08:28:12 +0300, Mika Westerberg wrote:
> Intel Meteor Lake-S has the same SPI serial flash controller as Meteor
> Lake-P. Add Meteor Lake-S PCI ID to the driver list of supported
> devices.
> 
> 

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: intel-pci: Add support for Meteor Lake-S SPI serial flash
      commit: c2912d42e86e494935722669e4d9eade69649072

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark