From: Denzeel Oliva <wachiturroxd150@gmail.com>
To: andi.shyti@kernel.org, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, alim.akhtar@samsung.com,
peter.griffin@linaro.org, andre.draszik@linaro.org,
tudor.ambarus@linaro.org, linux-spi@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Denzeel Oliva <wachiturroxd150@gmail.com>
Subject: [PATCH v1 1/2] spi: dt-bindings: samsung: add samsung,exynos990-spi compatible
Date: Wed, 12 Feb 2025 19:12:40 +0000 [thread overview]
Message-ID: <20250212191241.280-2-wachiturroxd150@gmail.com> (raw)
In-Reply-To: <20250212191241.280-1-wachiturroxd150@gmail.com>
Add "samsung,exynos990-spi" dedicated compatible for the SPI controller
on Exynos990 SoC. This ensures proper representation of the hardware
in the device tree.
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.48.1
next prev parent reply other threads:[~2025-02-12 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 19:12 [PATCH v1 0/2] spi: s3c64xx: add support for samsung,exynos990-spi Denzeel Oliva
2025-02-12 19:12 ` Denzeel Oliva [this message]
2025-02-12 19:12 ` [PATCH v1 2/2] spi: s3c64xx: add support exynos990-spi to new port config data Denzeel Oliva
2025-02-13 7:10 ` Tudor Ambarus
2025-02-13 7:05 ` [PATCH v1 0/2] spi: s3c64xx: add support for samsung,exynos990-spi Tudor Ambarus
2025-02-13 19:47 ` Denzeel Oliva
2025-02-14 6:14 ` Tudor Ambarus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250212191241.280-2-wachiturroxd150@gmail.com \
--to=wachiturroxd150@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).