Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1700620 > unrolled thread

[PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC

Started byLokesh Vutla <lokeshvutla@ti.com>
First post2017-08-01 06:50 +0200
Last post2017-08-07 15:40 +0200
Articles 7 — 5 participants

Back to article view | Back to linux.kernel

Contents

  [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC Lokesh Vutla <lokeshvutla@ti.com> - 2017-08-01 06:50 +0200
    [PATCH 3/6] ARM: dts: keystone-k2g: Add eDMA nodes Lokesh Vutla <lokeshvutla@ti.com> - 2017-08-01 06:50 +0200
    [PATCH 2/6] dt-bindings: ti,omap-hsmmc: Add 66AK2G mmc controller Lokesh Vutla <lokeshvutla@ti.com> - 2017-08-01 06:50 +0200
      Re: [PATCH 2/6] dt-bindings: ti,omap-hsmmc: Add 66AK2G mmc controller Rob Herring <robh@kernel.org> - 2017-08-10 02:10 +0200
    Re: [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC Santosh Shilimkar <santosh.shilimkar@oracle.com> - 2017-08-01 20:20 +0200
      Re: [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC Keerthy <j-keerthy@ti.com> - 2017-08-02 06:00 +0200
      Re: [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com> - 2017-08-07 15:40 +0200

#1700620 — [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC

FromLokesh Vutla <lokeshvutla@ti.com>
Date2017-08-01 06:50 +0200
Subject[PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC
Message-ID<u9xi1-768-3@gated-at.bofh.it>
This series adds DT nodes and documentation for eDMA and MMC IPs on
Keystone 66AK2G SoC. Also enable the required configs in keystone_defconfig.

This series depends on Keerthy's gpio node patches on 66AK2G:
https://patchwork.kernel.org/patch/9864311/

Tested:
k2g-evm with rootfs on mmc: http://pastebin.ubuntu.com/25217978/

Lokesh Vutla (5):
  dt-bindings: ti,edma: Add 66AK2G specific information
  dt-bindings: ti,omap-hsmmc: Add 66AK2G mmc controller
  ARM: dts: keystone-k2g: add MMC0 and MMC1 nodes
  ARM: dts: keystone-k2g-evm: Enable MMC0 and MMC1
  ARM: configs: keystone: Enable MMC and regulators

Peter Ujfalusi (1):
  ARM: dts: keystone-k2g: Add eDMA nodes

 Documentation/devicetree/bindings/dma/ti-edma.txt  | 95 +++++++++++++++++++--
 .../devicetree/bindings/mmc/ti-omap-hsmmc.txt      | 52 ++++++++----
 arch/arm/boot/dts/keystone-k2g-evm.dts             | 53 ++++++++++++
 arch/arm/boot/dts/keystone-k2g.dtsi                | 98 ++++++++++++++++++++++
 arch/arm/configs/keystone_defconfig                |  4 +
 5 files changed, 282 insertions(+), 20 deletions(-)

-- 
2.13.0

[toc] | [next] | [standalone]

#1700621 — [PATCH 3/6] ARM: dts: keystone-k2g: Add eDMA nodes

FromLokesh Vutla <lokeshvutla@ti.com>
Date2017-08-01 06:50 +0200
Subject[PATCH 3/6] ARM: dts: keystone-k2g: Add eDMA nodes
Message-ID<u9xi1-768-13@gated-at.bofh.it>
In reply to#1700620
From: Peter Ujfalusi <peter.ujfalusi@ti.com>

Add nodes for eDMA0 and eDMA1.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
---
 arch/arm/boot/dts/keystone-k2g.dtsi | 66 +++++++++++++++++++++++++++++++++++++
 1 file changed, 66 insertions(+)

diff --git a/arch/arm/boot/dts/keystone-k2g.dtsi b/arch/arm/boot/dts/keystone-k2g.dtsi
index f9ff29972295..3f1fd3df76d5 100644
--- a/arch/arm/boot/dts/keystone-k2g.dtsi
+++ b/arch/arm/boot/dts/keystone-k2g.dtsi
@@ -210,5 +210,71 @@
 			clocks = <&k2g_clks 0x001c 0x0>;
 			clock-names = "gpio";
 		};
+
+		edma0: edma@02700000 {
+			compatible = "ti,k2g-edma3-tpcc", "ti,edma3-tpcc";
+			reg =	<0x02700000 0x8000>;
+			reg-names = "edma3_cc";
+			interrupts = <GIC_SPI 200 IRQ_TYPE_EDGE_RISING>,
+					<GIC_SPI 216 IRQ_TYPE_EDGE_RISING>,
+					<GIC_SPI 217 IRQ_TYPE_EDGE_RISING>;
+			interrupt-names = "edma3_ccint", "emda3_mperr",
+					  "edma3_ccerrint";
+			dma-requests = <64>;
+			#dma-cells = <2>;
+
+			ti,tptcs = <&edma0_tptc0 7>, <&edma0_tptc1 0>;
+
+			ti,edma-memcpy-channels = <32 33 34 35>;
+
+			power-domains = <&k2g_pds 0x3f>;
+		};
+
+		edma0_tptc0: tptc@02760000 {
+			compatible = "ti,k2g-edma3-tptc", "ti,edma3-tptc";
+			reg =	<0x02760000 0x400>;
+			power-domains = <&k2g_pds 0x3f>;
+		};
+
+		edma0_tptc1: tptc@02768000 {
+			compatible = "ti,k2g-edma3-tptc", "ti,edma3-tptc";
+			reg =	<0x02768000 0x400>;
+			power-domains = <&k2g_pds 0x3f>;
+		};
+
+		edma1: edma@02728000 {
+			compatible = "ti,k2g-edma3-tpcc", "ti,edma3-tpcc";
+			reg =	<0x02728000 0x8000>;
+			reg-names = "edma3_cc";
+			interrupts = <GIC_SPI 208 IRQ_TYPE_EDGE_RISING>,
+					<GIC_SPI 219 IRQ_TYPE_EDGE_RISING>,
+					<GIC_SPI 220 IRQ_TYPE_EDGE_RISING>;
+			interrupt-names = "edma3_ccint", "emda3_mperr",
+					  "edma3_ccerrint";
+			dma-requests = <64>;
+			#dma-cells = <2>;
+
+			ti,tptcs = <&edma1_tptc0 7>, <&edma1_tptc1 0>;
+
+			/*
+			 * memcpy is disabled, can be enabled with:
+			 * ti,edma-memcpy-channels = <12 13 14 15>;
+			 * for example.
+			 */
+
+			power-domains = <&k2g_pds 0x4f>;
+		};
+
+		edma1_tptc0: tptc@027b0000 {
+			compatible = "ti,k2g-edma3-tptc", "ti,edma3-tptc";
+			reg =	<0x027b0000 0x400>;
+			power-domains = <&k2g_pds 0x4f>;
+		};
+
+		edma1_tptc1: tptc@027b8000 {
+			compatible = "ti,k2g-edma3-tptc", "ti,edma3-tptc";
+			reg =	<0x027b8000 0x400>;
+			power-domains = <&k2g_pds 0x4f>;
+		};
 	};
 };
-- 
2.13.0

[toc] | [prev] | [next] | [standalone]

#1700622 — [PATCH 2/6] dt-bindings: ti,omap-hsmmc: Add 66AK2G mmc controller

FromLokesh Vutla <lokeshvutla@ti.com>
Date2017-08-01 06:50 +0200
Subject[PATCH 2/6] dt-bindings: ti,omap-hsmmc: Add 66AK2G mmc controller
Message-ID<u9xi1-768-9@gated-at.bofh.it>
In reply to#1700620
Update the ti,omap-hsmmc.txt to include information about
66AK2G specific mmc controller. Also cleanup the entries
under optional properties to look a bit nicer.

Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
---
 .../devicetree/bindings/mmc/ti-omap-hsmmc.txt      | 52 +++++++++++++++-------
 1 file changed, 37 insertions(+), 15 deletions(-)

diff --git a/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt b/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
index 0e026c151c1c..016741402e37 100644
--- a/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
+++ b/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
@@ -1,33 +1,55 @@
-* TI Highspeed MMC host controller for OMAP
+* TI Highspeed MMC host controller for OMAP and 66AK2G family.
 
-The Highspeed MMC Host Controller on TI OMAP family
+The Highspeed MMC Host Controller on TI OMAP and 66AK2G family
 provides an interface for MMC, SD, and SDIO types of memory cards.
 
 This file documents differences between the core properties described
 by mmc.txt and the properties used by the omap_hsmmc driver.
 
 Required properties:
+--------------------
 - compatible:
  Should be "ti,omap2-hsmmc", for OMAP2 controllers
  Should be "ti,omap3-hsmmc", for OMAP3 controllers
  Should be "ti,omap3-pre-es3-hsmmc" for OMAP3 controllers pre ES3.0
  Should be "ti,omap4-hsmmc", for OMAP4 controllers
  Should be "ti,am33xx-hsmmc", for AM335x controllers
-- ti,hwmods: Must be "mmc<n>", n is controller instance starting 1
+ Should be "ti,k2g-hsmmc", "ti,omap4-hsmmc" for 66AK2G controllers.
+
+SoC specific required properties:
+---------------------------------
+The following are mandatory properties for OMAPs, AM33xx and AM43xx SoCs only:
+- ti,hwmods: Must be "mmc<n>", n is controller instance starting 1.
+
+The following are mandatory properties for 66AK2G SoCs only:
+- power-domains:Should contain a phandle to a PM domain provider node
+		and an args specifier containing the MMC device id
+		value. This property is as per the binding,
+		Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
+- clocks:	Must contain an entry for each entry in clock-names. Should
+		be defined as per the he appropriate clock bindings consumer
+		usage in Documentation/devicetree/bindings/clock/ti,sci-clk.txt
+- clock-names:	Shall be "fck" for the functional clock,
+		and "mmchsdb_fck" for the debounce clock.
+
 
 Optional properties:
-ti,dual-volt: boolean, supports dual voltage cards
-<supply-name>-supply: phandle to the regulator device tree node
-"supply-name" examples are "vmmc", "vmmc_aux"(deprecated)/"vqmmc" etc
-ti,non-removable: non-removable slot (like eMMC)
-ti,needs-special-reset: Requires a special softreset sequence
-ti,needs-special-hs-handling: HSMMC IP needs special setting for handling High Speed
-dmas: List of DMA specifiers with the controller specific format
-as described in the generic DMA client binding. A tx and rx
-specifier is required.
-dma-names: List of DMA request names. These strings correspond
-1:1 with the DMA specifiers listed in dmas. The string naming is
-to be "rx" and "tx" for RX and TX DMA requests, respectively.
+--------------------
+- ti,dual-volt:		boolean, supports dual voltage cards
+- <supply-name>-supply:	phandle to the regulator device tree node
+			  "supply-name" examples are "vmmc",
+			  "vmmc_aux"(deprecated)/"vqmmc" etc
+- ti,non-removable:	non-removable slot (like eMMC)
+- ti,needs-special-reset:	Requires a special softreset sequence
+- ti,needs-special-hs-handling:	HSMMC IP needs special setting
+				  for handling High Speed
+- dmas:			List of DMA specifiers with the controller specific
+			format as described in the generic DMA client
+			binding. A tx and rx specifier is required.
+- dma-names:		List of DMA request names. These strings correspond
+			1:1 with the DMA specifiers listed in dmas.
+			The string naming is to be "rx" and "tx" for
+			RX and TX DMA requests, respectively.
 
 Examples:
 
-- 
2.13.0

[toc] | [prev] | [next] | [standalone]

#1708082 — Re: [PATCH 2/6] dt-bindings: ti,omap-hsmmc: Add 66AK2G mmc controller

FromRob Herring <robh@kernel.org>
Date2017-08-10 02:10 +0200
SubjectRe: [PATCH 2/6] dt-bindings: ti,omap-hsmmc: Add 66AK2G mmc controller
Message-ID<ucJcZ-6lV-5@gated-at.bofh.it>
In reply to#1700622
On Tue, Aug 01, 2017 at 10:11:15AM +0530, Lokesh Vutla wrote:
> Update the ti,omap-hsmmc.txt to include information about
> 66AK2G specific mmc controller. Also cleanup the entries
> under optional properties to look a bit nicer.
> 
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
>  .../devicetree/bindings/mmc/ti-omap-hsmmc.txt      | 52 +++++++++++++++-------
>  1 file changed, 37 insertions(+), 15 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt b/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
> index 0e026c151c1c..016741402e37 100644
> --- a/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
> +++ b/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
> @@ -1,33 +1,55 @@
> -* TI Highspeed MMC host controller for OMAP
> +* TI Highspeed MMC host controller for OMAP and 66AK2G family.
>  
> -The Highspeed MMC Host Controller on TI OMAP family
> +The Highspeed MMC Host Controller on TI OMAP and 66AK2G family
>  provides an interface for MMC, SD, and SDIO types of memory cards.
>  
>  This file documents differences between the core properties described
>  by mmc.txt and the properties used by the omap_hsmmc driver.
>  
>  Required properties:
> +--------------------
>  - compatible:
>   Should be "ti,omap2-hsmmc", for OMAP2 controllers
>   Should be "ti,omap3-hsmmc", for OMAP3 controllers
>   Should be "ti,omap3-pre-es3-hsmmc" for OMAP3 controllers pre ES3.0
>   Should be "ti,omap4-hsmmc", for OMAP4 controllers
>   Should be "ti,am33xx-hsmmc", for AM335x controllers
> -- ti,hwmods: Must be "mmc<n>", n is controller instance starting 1
> + Should be "ti,k2g-hsmmc", "ti,omap4-hsmmc" for 66AK2G controllers.

Same comment here.

> +
> +SoC specific required properties:
> +---------------------------------
> +The following are mandatory properties for OMAPs, AM33xx and AM43xx SoCs only:
> +- ti,hwmods: Must be "mmc<n>", n is controller instance starting 1.
> +
> +The following are mandatory properties for 66AK2G SoCs only:
> +- power-domains:Should contain a phandle to a PM domain provider node
> +		and an args specifier containing the MMC device id
> +		value. This property is as per the binding,
> +		Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
> +- clocks:	Must contain an entry for each entry in clock-names. Should
> +		be defined as per the he appropriate clock bindings consumer
> +		usage in Documentation/devicetree/bindings/clock/ti,sci-clk.txt
> +- clock-names:	Shall be "fck" for the functional clock,
> +		and "mmchsdb_fck" for the debounce clock.
> +
>  
>  Optional properties:
> -ti,dual-volt: boolean, supports dual voltage cards
> -<supply-name>-supply: phandle to the regulator device tree node
> -"supply-name" examples are "vmmc", "vmmc_aux"(deprecated)/"vqmmc" etc
> -ti,non-removable: non-removable slot (like eMMC)
> -ti,needs-special-reset: Requires a special softreset sequence
> -ti,needs-special-hs-handling: HSMMC IP needs special setting for handling High Speed
> -dmas: List of DMA specifiers with the controller specific format
> -as described in the generic DMA client binding. A tx and rx
> -specifier is required.
> -dma-names: List of DMA request names. These strings correspond
> -1:1 with the DMA specifiers listed in dmas. The string naming is
> -to be "rx" and "tx" for RX and TX DMA requests, respectively.
> +--------------------
> +- ti,dual-volt:		boolean, supports dual voltage cards
> +- <supply-name>-supply:	phandle to the regulator device tree node
> +			  "supply-name" examples are "vmmc",
> +			  "vmmc_aux"(deprecated)/"vqmmc" etc
> +- ti,non-removable:	non-removable slot (like eMMC)
> +- ti,needs-special-reset:	Requires a special softreset sequence
> +- ti,needs-special-hs-handling:	HSMMC IP needs special setting
> +				  for handling High Speed
> +- dmas:			List of DMA specifiers with the controller specific
> +			format as described in the generic DMA client
> +			binding. A tx and rx specifier is required.
> +- dma-names:		List of DMA request names. These strings correspond
> +			1:1 with the DMA specifiers listed in dmas.
> +			The string naming is to be "rx" and "tx" for
> +			RX and TX DMA requests, respectively.

Is there some change here or just reformatting? Please make reformatting 
a separate patch.

Rob

[toc] | [prev] | [next] | [standalone]

#1701324

FromSantosh Shilimkar <santosh.shilimkar@oracle.com>
Date2017-08-01 20:20 +0200
Message-ID<u9JVU-7qE-41@gated-at.bofh.it>
In reply to#1700620
On 7/31/2017 9:41 PM, Lokesh Vutla wrote:
> This series adds DT nodes and documentation for eDMA and MMC IPs on
> Keystone 66AK2G SoC. Also enable the required configs in keystone_defconfig.
> 
> This series depends on Keerthy's gpio node patches on 66AK2G:
Am waiting for Keerthy to send refresh series. Thanks for
note about the deps.

Regards,
Santosh

[toc] | [prev] | [next] | [standalone]

#1701689

FromKeerthy <j-keerthy@ti.com>
Date2017-08-02 06:00 +0200
Message-ID<u9SZb-4CX-3@gated-at.bofh.it>
In reply to#1701324

On Tuesday 01 August 2017 11:40 PM, Santosh Shilimkar wrote:
> 
> On 7/31/2017 9:41 PM, Lokesh Vutla wrote:
>> This series adds DT nodes and documentation for eDMA and MMC IPs on
>> Keystone 66AK2G SoC. Also enable the required configs in
>> keystone_defconfig.
>>
>> This series depends on Keerthy's gpio node patches on 66AK2G:
> Am waiting for Keerthy to send refresh series. Thanks for
> note about the deps.

Thanks Santosh. I am waiting for a response from Rob H on Suman's
question on whether to include power-domains property.

> 
> Regards,
> Santosh

[toc] | [prev] | [next] | [standalone]

#1705523

From"santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
Date2017-08-07 15:40 +0200
Message-ID<ubQqd-nB-1@gated-at.bofh.it>
In reply to#1701324
On 8/1/17 11:10 AM, Santosh Shilimkar wrote:
> 
> On 7/31/2017 9:41 PM, Lokesh Vutla wrote:
>> This series adds DT nodes and documentation for eDMA and MMC IPs on
>> Keystone 66AK2G SoC. Also enable the required configs in 
>> keystone_defconfig.
>>
>> This series depends on Keerthy's gpio node patches on 66AK2G:
> Am waiting for Keerthy to send refresh series. Thanks for
> note about the deps.
> 
Series applied !!

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web