drivers: spi_ll_stm32: Add LOG to indicate that DMA cannot be enabled

[Freey0]

Add LOG to indicate the reason why DMA cannot be enabled

When using the stm32h7 and W5500 network card driver, configuring CONFIG_SPI_STM32_DMA will silently fail.

[JarmouniA]

CI compliance issues to be fixed

LONG_LINE_STRING: line length of 102 exceeds 100 columns
File:drivers/spi/spi_ll_stm32.c

UC5 Commit title exceeds max length (79>75): "drivers: spi_ll_stm32: Add LOG to indicate the reason why DMA cannot be enabled"

author email ([email protected]) needs to match one of the signed-off-by entries.
Compliance error, check for error messages in the "Run Compliance Tests" step

You can run this step locally with the ./scripts/ci/check_compliance.py script.

[Freey0]

CI compliance issues to be fixed

LONG_LINE_STRING: line length of 102 exceeds 100 columns
File:drivers/spi/spi_ll_stm32.c

UC5 Commit title exceeds max length (79>75): "drivers: spi_ll_stm32: Add LOG to indicate the reason why DMA cannot be enabled"

author email ([email protected]) needs to match one of the signed-off-by entries.
Compliance error, check for error messages in the "Run Compliance Tests" step

You can run this step locally with the ./scripts/ci/check_compliance.py script.

Fixed CI compliance issues

[JarmouniA]

Squash the 2nd commit

[etienne-lms]

Suggested change

	LOG_ERR("SPI buffers are not in non-cacheable memory,"
	" SPI DMA transfer is not supported");
	LOG_ERR("SPI buffers are not in non-cacheable memory, SPI DMA transfer is not supported");

Prefer trace message in a single line so that one can easier grep the message in the source file tree, see Linux kernel coding style directives:

However, never break user-visible strings such as printk messages because that breaks the ability to grep for them.

Maybe trace message can be shortened, e.g.:

		LOG_ERR("SPI DMA transfers not supported on cached memory");

[Freey0]

Done. Accept the suggestion and use short messages.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud