Skip to contentSkip to conversation

spi: Respect DataBitLength field of SpiSerialBusV2() ACPI resource

PATCH Applied Andy Shevchenko 2 participants 3 messages Apr 13, 2020 – Apr 17, 2020 SPI

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 spi: Respect DataBitLength field of SpiSerialBusV2() ACPI resource

By unknown reason the commit 64bee4d28c9e
("spi / ACPI: add ACPI enumeration support")
missed the DataBitLength property to encounter when parse SPI slave device data from ACPI.

Fill the gap here.

Fixes 64bee4d28c9e ("spi / ACPI: add ACPI enumeration support")
---
 drivers/spi/spi.c | 1 +
 1 file changed, 1 insertion(+)
drivers/spi/spi.c +1 -0
index c92c89467e7e..e0e27fe06878 100644
@@ -2111,6 +2111,7 @@ static int acpi_spi_add_resource(struct acpi_resource *ares, void *data)
 			}
 
 			lookup->max_speed_hz = sb->connection_speed;
+			lookup->bits_per_word = sb->data_bit_length;
 
 			if (sb->clock_phase == ACPI_SPI_SECOND_PHASE)
 				lookup->mode |= SPI_CPHA;
Signature · 1 line
2.25.1
maintainer
#1 lore raw

Applied "spi: Respect DataBitLength field of SpiSerialBusV2() ACPI resource" to the spi tree

The patch

spi: Respect DataBitLength field of SpiSerialBusV2() ACPI resource

has been applied to the spi tree at

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git

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

From 0dadde344d965566589cd82797893d5aa06557a3 Mon Sep 17 00:00:00 2001
From: Andy Shevchenko <[email protected]>
Date: Mon, 13 Apr 2020 21:04:06 +0300
Subject: [PATCH] spi: Respect DataBitLength field of SpiSerialBusV2() ACPI
resource

By unknown reason the commit 64bee4d28c9e
("spi / ACPI: add ACPI enumeration support")
missed the DataBitLength property to encounter when parse SPI slave device data from ACPI.

Fill the gap here.

Fixes 64bee4d28c9e ("spi / ACPI: add ACPI enumeration support")
---
 drivers/spi/spi.c | 1 +
 1 file changed, 1 insertion(+)
drivers/spi/spi.c +1 -0
index 0996d238f61e..531d1de85f7f 100644
@@ -2111,6 +2111,7 @@ static int acpi_spi_add_resource(struct acpi_resource *ares, void *data)
 			}
 
 			lookup->max_speed_hz = sb->connection_speed;
+			lookup->bits_per_word = sb->data_bit_length;
 
 			if (sb->clock_phase == ACPI_SPI_SECOND_PHASE)
 				lookup->mode |= SPI_CPHA;
Signature · 1 line
2.20.1
maintainer Applied
#2 lore raw
In reply to Andy Shevchenko
Quoted 8 lines · Andy Shevchenko

By unknown reason the commit 64bee4d28c9e
("spi / ACPI: add ACPI enumeration support")
missed the DataBitLength property to encounter when parse SPI slave device data from ACPI.

Fill the gap here.

[...]

Applied, thanks!

[1/1] spi: Respect DataBitLength field of SpiSerialBusV2() ACPI resource

      commit: 0dadde344d965566589cd82797893d5aa06557a3

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