[PATCH v1 5/9] spi: dt-bindings: samsung: add samsung,exynos990-spi compatible

Denzeel Oliva posted 9 patches 10 months, 1 week ago
[PATCH v1 5/9] spi: dt-bindings: samsung: add samsung,exynos990-spi compatible
Posted by Denzeel Oliva 10 months, 1 week ago
According to the Exynos 990 downstream kernel,
almost all of them do not use the same 64 bytes depth.
Some SPI nodes using a depth of 256 bytes (SPI 9/8/10).
But in the end these nodes work.

Signed-off-by: Denzeel Oliva <wachiturroxd150@gmail.com>
---
 Documentation/devicetree/bindings/spi/samsung,spi.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/spi/samsung,spi.yaml b/Documentation/devicetree/bindings/spi/samsung,spi.yaml
index 3c206a64d..1d3c95bd2 100644
--- a/Documentation/devicetree/bindings/spi/samsung,spi.yaml
+++ b/Documentation/devicetree/bindings/spi/samsung,spi.yaml
@@ -24,6 +24,7 @@ properties:
           - samsung,exynos4210-spi
           - samsung,exynos5433-spi
           - samsung,exynos850-spi
+          - samsung,exynos990-spi
           - samsung,exynosautov9-spi
           - tesla,fsd-spi
       - items:
-- 
2.47.1
Re: [PATCH v1 5/9] spi: dt-bindings: samsung: add samsung,exynos990-spi compatible
Posted by Krzysztof Kozlowski 10 months, 1 week ago
On 05/02/2025 23:22, Denzeel Oliva wrote:
> According to the Exynos 990 downstream kernel,
> almost all of them do not use the same 64 bytes depth.
> Some SPI nodes using a depth of 256 bytes (SPI 9/8/10).
> But in the end these nodes work.
> 
> Signed-off-by: Denzeel Oliva <wachiturroxd150@gmail.com>
> ---
<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.

Please kindly resend and include all necessary To/Cc entries.
</form letter>

Best regards,
Krzysztof