From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: "Rob Herring" <robh+dt@kernel.org>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-actions@lists.infradead.org
Subject: [PATCH 06/10] arm: dts: owl-s500: Add MMC nodes
Date: Fri, 26 Jun 2020 02:34:18 +0300 [thread overview]
Message-ID: <2a08075ab09975cbd1c3cee73d425e8f8fef6598.1593124368.git.cristian.ciocaltea@gmail.com> (raw)
In-Reply-To: <cover.1593124368.git.cristian.ciocaltea@gmail.com>
Add MMC controller nodes for Actions Semi S500 SoC.
Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
---
arch/arm/boot/dts/owl-s500.dtsi | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/arch/arm/boot/dts/owl-s500.dtsi b/arch/arm/boot/dts/owl-s500.dtsi
index 3b625358d786..778775ac42f7 100644
--- a/arch/arm/boot/dts/owl-s500.dtsi
+++ b/arch/arm/boot/dts/owl-s500.dtsi
@@ -241,5 +241,38 @@ dma: dma-controller@b0260000 {
clocks = <&cmu CLK_DMAC>;
power-domains = <&sps S500_PD_DMA>;
};
+
+ mmc0: mmc@b0230000 {
+ compatible = "actions,owl-mmc";
+ reg = <0xb0230000 0x38>;
+ interrupts = <GIC_SPI 42 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&cmu CLK_SD0>;
+ resets = <&cmu RESET_SD0>;
+ dmas = <&dma 2>;
+ dma-names = "mmc";
+ status = "disabled";
+ };
+
+ mmc1: mmc@b0234000 {
+ compatible = "actions,owl-mmc";
+ reg = <0xb0234000 0x38>;
+ interrupts = <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&cmu CLK_SD1>;
+ resets = <&cmu RESET_SD1>;
+ dmas = <&dma 3>;
+ dma-names = "mmc";
+ status = "disabled";
+ };
+
+ mmc2: mmc@b0238000 {
+ compatible = "actions,owl-mmc";
+ reg = <0xb0238000 0x38>;
+ interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&cmu CLK_SD2>;
+ resets = <&cmu RESET_SD2>;
+ dmas = <&dma 4>;
+ dma-names = "mmc";
+ status = "disabled";
+ };
};
};
--
2.27.0
next prev parent reply other threads:[~2020-06-25 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 23:34 [PATCH 00/10] Add CMU/RMU/DMA/MMC/I2C support for Actions Semi S500 SoCs Cristian Ciocaltea
2020-06-25 23:34 ` [PATCH 01/10] arm: dts: owl-s500: Add Clock Management Unit Cristian Ciocaltea
2020-06-25 23:34 ` [PATCH 02/10] arm: dts: owl-s500: Set UART clock refs from CMU Cristian Ciocaltea
2020-06-25 23:34 ` [PATCH 03/10] arm: dts: owl-s500: Add DMA controller Cristian Ciocaltea
2020-06-25 23:34 ` [PATCH 04/10] arm: dts: owl-s500: Add Reset Controller support Cristian Ciocaltea
2020-06-25 23:34 ` [PATCH 05/10] arm: dts: owl-s500: Add pinctrl node Cristian Ciocaltea
2020-06-25 23:34 ` Cristian Ciocaltea [this message]
2020-06-25 23:34 ` [PATCH 07/10] arm: dts: owl-s500: Add I2C nodes Cristian Ciocaltea
2020-06-25 23:34 ` [PATCH 08/10] arm: dts: owl-s500-roseapplepi: Use UART clock from CMU Cristian Ciocaltea
2020-06-25 23:34 ` [PATCH 09/10] arm: dts: owl-s500-roseapplepi: Add uSD support Cristian Ciocaltea
2020-06-25 23:34 ` [PATCH 10/10] arm: dts: owl-s500-roseapplepi: Enable I2C0 Cristian Ciocaltea
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=2a08075ab09975cbd1c3cee73d425e8f8fef6598.1593124368.git.cristian.ciocaltea@gmail.com \
--to=cristian.ciocaltea@gmail.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@kernel.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).