spi: Use of_property_present() for non-boolean properties
Subsystems (2)
PATCH 1/1 spi: Use of_property_present() for non-boolean properties
The use of of_property_read_bool() for non-boolean properties is deprecated in favor of of_property_present() when testing for property presence.
--- drivers/spi/spi-qcom-qspi.c | 2 +- drivers/spi/spi-ti-qspi.c | 2 +- drivers/spi/spi.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
drivers/spi/spi-qcom-qspi.c +1 -1
@@ -771,7 +771,7 @@ static int qcom_qspi_probe(struct platform_device *pdev) host->prepare_message = qcom_qspi_prepare_message; host->transfer_one = qcom_qspi_transfer_one; host->handle_err = qcom_qspi_handle_err; -if (of_property_read_bool (pdev->dev.of_node,"iommus" )) +if (of_property_present (pdev->dev.of_node,"iommus" )) host->can_dma = qcom_qspi_can_dma; host->auto_runtime_pm = true; host->mem_ops = &qcom_qspi_mem_ops;
drivers/spi/spi-ti-qspi.c +1 -1
@@ -824,7 +824,7 @@ static int ti_qspi_probe(struct platform_device *pdev) } -if (of_property_read_bool (np,"syscon-chipselects" )) { +if (of_property_present (np,"syscon-chipselects" )) { qspi->ctrl_base =syscon_regmap_lookup_by_phandle (np,"syscon-chipselects" );
drivers/spi/spi.c +1 -1
@@ -2454,7 +2454,7 @@ static int of_spi_parse_dt(struct spi_controller *ctlr, struct spi_device *spi, nc, rc);return rc; } -if ((of_property_read_bool (nc,"parallel-memories" )) && +if ((of_property_present (nc,"parallel-memories" )) && (!(ctlr->flags &SPI_CONTROLLER_MULTI_CS ))) {dev_err (&ctlr->dev,"SPI controller doesn't support multi CS\n" );return -EINVAL ;
Signature · 1 line
2.45.2
Mark Brown
maintainerQuoted 5 lines · Rob Herring (Arm)
The use of
of_property_read_bool()for non-boolean properties is deprecated in favor ofof_property_present()when testing for property presence.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: Use of_property_present() for non-boolean properties
commit: 270ddc23914ed79aa117373f4b3413c34cdabf12
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