dt-bindings: trivial-devices: Add silabs,si3210
Subsystems (2)
PATCH 1/2 dt-bindings: trivial-devices: Add silabs,si3210
Add Silicon Labs SI3210 to trivial devices.
--- Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++ 1 file changed, 2 insertions(+)
Documentation/devicetree/bindings/trivial-devices.yaml +2 -0
@@ -325,6 +325,8 @@ properties: - sgx,vz89x # Silicon Labs EM3581 Zigbee SoC with SPI interface - silabs,em3581 + # Silicon Labs SI3210 Programmable CMOS SLIC/CODEC with SPI interface + - silabs,si3210 # Relative Humidity and Temperature Sensors - silabs,si7020 # Skyworks SKY81452: Six-Channel White LED Driver with Touch Panel Bias Supply
Signature · 1 line
2.37.2
PATCH 2/2 spidev: Add Silicon Labs SI3210 device compatible
Add compatible string for Silicon Labs SI3210 device.
--- drivers/spi/spidev.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/spi/spidev.c +2 -0
@@ -703,6 +703,7 @@ static const struct spi_device_id spidev_spi_ids[] = { { .name = "spi-petra" }, { .name = "spi-authenta" }, { .name = "em3581" }, + { .name = "si3210" }, {}, };MODULE_DEVICE_TABLE (spi, spidev_spi_ids);
@@ -730,6 +731,7 @@ static const struct of_device_id spidev_dt_ids[] = { { .compatible = "cisco,spi-petra", .data = &spidev_of_check }, { .compatible = "micron,spi-authenta", .data = &spidev_of_check }, { .compatible = "silabs,em3581", .data = &spidev_of_check }, + { .compatible = "silabs,si3210", .data = &spidev_of_check }, {}, };MODULE_DEVICE_TABLE (of, spidev_dt_ids);
Signature · 1 line
2.37.2
Mark Brown
maintainerQuoted 3 lines · Vincent Tremblay
Add Silicon Labs SI3210 to trivial devices.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] dt-bindings: trivial-devices: Add silabs,si3210
commit: f7879d677e76d0c4449fa1839f948d335795f334
[2/2] spidev: Add Silicon Labs SI3210 device compatible
commit: 6c9d1fd52956c3148e847a214bae9102b1811de5All 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