Skip to contentSkip to conversation

ARM: dts: AM33XX: Add device tree data

PATCH RESEND Superseded AnilKumar Ch 4 participants 14 messages Sep 19, 2012 – Sep 28, 2012

Subsystems (5)
lore
Share & tools
lore
#0 lore raw

cover ARM: dts: AM33XX: Add device tree data

Add device tree data of pinctrl, d_can, lis331dlh and tmp275 drivers for AM33XX family of devices. These patches were submitted earlier and reviewed. Re-sending to apply cleanly on linux-omap/devel-dt tree. These patches were tested on am33xx-evm and am335x-bone.

AnilKumar Ch (5):
ARM: dts: AM33XX: Add basic pinctrl device tree data
ARM: dts: AM33XX: Add D_CAN device tree data
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data
ARM: dts: AM33XX: Add lis331dlh device tree data to am335x-evm
ARM: dts: AM33XX: Add temperature sensor device tree data to

    am335x-evm
 arch/arm/boot/dts/am335x-evm.dts     |   44 ++++++++++++++++++++++++++++++++++
 arch/arm/boot/dts/am33xx.dtsi        |   27 +++++++++++++++++++++
 arch/arm/mach-omap2/clock33xx_data.c |    1 +
 3 files changed, 72 insertions(+)
Signature · 1 line
1.7.9.5
#1 lore raw

PATCH RESEND v7 1/5 ARM: dts: AM33XX: Add basic pinctrl device tree data

Adds basic pinctrl device tree data for AM33XX family of devices. This patch is based on the pinctrl-single driver.

---
 arch/arm/boot/dts/am33xx.dtsi |    9 +++++++++
 1 file changed, 9 insertions(+)
arch/arm/boot/dts/am33xx.dtsi +9 -0
index b4e3e47..894fec6 100644
@@ -55,6 +55,15 @@
 		};
 	};
 
+	am33xx_pinmux: pinmux at 44e10800 {
+		compatible = "pinctrl-single";
+		reg = <0x44e10800 0x0238>;
+		#address-cells = <1>;
+		#size-cells = <0>;
+		pinctrl-single,register-width = <32>;
+		pinctrl-single,function-mask = <0x7f>;
+	};
+
 	/*
 	 * XXX: Use a flat representation of the AM33XX interconnect.
 	 * The real AM33XX interconnect network is quite complex.Since
Signature · 1 line
1.7.9.5
#2 lore raw

PATCH RESEND v7 2/5 ARM: dts: AM33XX: Add D_CAN device tree data

In reply to AnilKumar Ch

Add Bosch D_CAN controller device tree data to AM33XX dtsi file by adding d_can device nodes with all the necessary parameters.

---
 arch/arm/boot/dts/am33xx.dtsi |   18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
arch/arm/boot/dts/am33xx.dtsi +18 -0
index 894fec6..64c2efe 100644
@@ -234,5 +234,23 @@
 			interrupt-parent = <&intc>;
 			interrupts = <91>;
 		};
+
+		dcan0: d_can at 481cc000 {
+			compatible = "bosch,d_can";
+			ti,hwmods = "d_can0";
+			reg = <0x481cc000 0x2000>;
+			interrupts = <52>;
+			interrupt-parent = <&intc>;
+			status = "disabled";
+		};
+
+		dcan1: d_can at 481d0000 {
+			compatible = "bosch,d_can";
+			ti,hwmods = "d_can1";
+			reg = <0x481d0000 0x2000>;
+			interrupts = <55>;
+			interrupt-parent = <&intc>;
+			status = "disabled";
+		};
 	};
 };
Signature · 1 line
1.7.9.5
#3 lore raw

PATCH RESEND 3/5 ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

In reply to AnilKumar Ch

Add AM335x cpu0 clock entry to the corresponding clock data file. This is useful in getting the correct mpu clock pointer to change the cpu frequency in cpufreq driver.

---
 arch/arm/mach-omap2/clock33xx_data.c |    1 +
 1 file changed, 1 insertion(+)
arch/arm/mach-omap2/clock33xx_data.c +1 -0
index a4006b2..4933993 100644
@@ -1013,6 +1013,7 @@ static struct omap_clk am33xx_clks[] = {
 	CLK(NULL,	"dpll_core_m5_ck",	&dpll_core_m5_ck,	CK_AM33XX),
 	CLK(NULL,	"dpll_core_m6_ck",	&dpll_core_m6_ck,	CK_AM33XX),
 	CLK(NULL,	"dpll_mpu_ck",		&dpll_mpu_ck,	CK_AM33XX),
+	CLK("cpu0",	NULL,			&dpll_mpu_ck,		CK_AM33XX),
 	CLK(NULL,	"dpll_mpu_m2_ck",	&dpll_mpu_m2_ck,	CK_AM33XX),
 	CLK(NULL,	"dpll_ddr_ck",		&dpll_ddr_ck,	CK_AM33XX),
 	CLK(NULL,	"dpll_ddr_m2_ck",	&dpll_ddr_m2_ck,	CK_AM33XX),
Signature · 1 line
1.7.9.5
maintainer
#4 lore raw

PATCH RESEND 3/5 ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

Hi

Quoted 5 lines · AnilKumar Ch

Add AM335x cpu0 clock entry to the corresponding clock data file. This is useful in getting the correct mpu clock pointer to change the cpu frequency in cpufreq driver.

Looks like this one is unrelated to the DTS changes, so I'll queue it separately here for 3.7.

- Paul

#5 lore raw

PATCH RESEND 3/5 ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

Quoted 4 lines · Paul Walmsley

Hi

On Thu, 20 Sep 2012, AnilKumar Ch wrote:

Quoted 9 lines
Quoted 5 lines

Add AM335x cpu0 clock entry to the corresponding clock data file. This is useful in getting the correct mpu clock pointer to change the cpu frequency in cpufreq driver.

Looks like this one is unrelated to the DTS changes, so I'll queue it separately here for 3.7.

Thanks Paul

Thanks
AnilKumar

#6 lore raw

PATCH RESEND v3 4/5 ARM: dts: AM33XX: Add lis331dlh device tree data to am335x-evm

In reply to AnilKumar Ch

Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM lis331dlh accelerometer is connected to I2C2 bus. So this patch change the status of I2C2 node to "okay" to use I2C2 bus. Also added all the required platform data to am335x-evm.

---
 arch/arm/boot/dts/am335x-evm.dts |   39 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)
arch/arm/boot/dts/am335x-evm.dts +39 -0
index 4707cda..d25d1b3 100644
@@ -37,6 +37,39 @@
 				reg = <0x2d>;
 			};
 		};
+
+		i2c2: i2c at 4802a000 {
+			status = "okay";
+			clock-frequency = <400000>;
+
+			lis331dlh: lis331dlh at 18 {
+				compatible = "st,lis331dlh", "st,lis3lv02d";
+				reg = <0x18>;
+				Vdd-supply = <&lis3_reg>;
+				Vdd_IO-supply = <&lis3_reg>;
+
+				st,click-single-x;
+				st,click-single-y;
+				st,click-single-z;
+				st,click-thresh-x = <10>;
+				st,click-thresh-y = <10>;
+				st,click-thresh-z = <10>;
+				st,irq1-click;
+				st,irq2-click;
+				st,wakeup-x-lo;
+				st,wakeup-x-hi;
+				st,wakeup-y-lo;
+				st,wakeup-y-hi;
+				st,wakeup-z-lo;
+				st,wakeup-z-hi;
+				st,min-limit-x = <120>;
+				st,min-limit-y = <120>;
+				st,min-limit-z = <140>;
+				st,max-limit-x = <550>;
+				st,max-limit-y = <550>;
+				st,max-limit-z = <750>;
+			};
+		};
 	};
 
 	vbat: fixedregulator at 0 {
@@ -46,6 +79,12 @@
 		regulator-max-microvolt = <5000000>;
 		regulator-boot-on;
 	};
+
+	lis3_reg: fixedregulator at 1 {
+		compatible = "regulator-fixed";
+		regulator-name = "lis3_reg";
+		regulator-boot-on;
+	};
 };
 
 /include/ "tps65910.dtsi"
Signature · 1 line
1.7.9.5
#7 lore raw

PATCH RESEND 5/5 ARM: dts: AM33XX: Add temperature sensor device tree data to am335x-evm

In reply to AnilKumar Ch

Add temperature sensor DT data to am335x-evm.dts. In AM335x EVM tmp275 temperature sensor is connected to I2C2 bus. So this patch adds child node inside i2c2 node with i2c slave address. This patch is tested on AM335x EVM.

---
 arch/arm/boot/dts/am335x-evm.dts |    5 +++++
 1 file changed, 5 insertions(+)
arch/arm/boot/dts/am335x-evm.dts +5 -0
index d25d1b3..a5c4c62 100644
@@ -69,6 +69,11 @@
 				st,max-limit-y = <550>;
 				st,max-limit-z = <750>;
 			};
+
+			tmp275: tmp275 at 48 {
+				compatible = "ti,tmp275";
+				reg = <0x48>;
+			};
 		};
 	};
 
Signature · 1 line
1.7.9.5
#8 lore raw

cover ARM: dts: AM33XX: Add device tree data

In reply to AnilKumar Ch

+ Paul

Hi Anil,

Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

Paul,
Is that OK?

Regards,
Benoit

Quoted 1 line

Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 12.654.784

-----Original Message-----

Quoted 28 lines

From: AnilKumar, Chimata
Sent: Wednesday, September 19, 2012 4:19 PM
To: tony at atomide.com
Cc: Cousson, Benoit; linux-arm-kernel at lists.infradead.org; linux- omap at vger.kernel.org; AnilKumar, Chimata
Subject: [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data

Add device tree data of pinctrl, d_can, lis331dlh and tmp275 drivers for AM33XX family of devices. These patches were submitted earlier and reviewed. Re-sending to apply cleanly on linux-omap/devel-dt tree. These patches were tested on am33xx-evm and am335x-bone.

AnilKumar Ch (5):
ARM: dts: AM33XX: Add basic pinctrl device tree data
ARM: dts: AM33XX: Add D_CAN device tree data
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data
ARM: dts: AM33XX: Add lis331dlh device tree data to am335x-evm
ARM: dts: AM33XX: Add temperature sensor device tree data to
am335x-evm

arch/arm/boot/dts/am335x-evm.dts | 44
++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/am33xx.dtsi | 27 +++++++++++++++++++++
arch/arm/mach-omap2/clock33xx_data.c | 1 +

3 files changed, 72 insertions(+)

--
1.7.9.5

maintainer
#9 lore raw

cover ARM: dts: AM33XX: Add device tree data

Hi Beno?t

Quoted 5 lines · Benoit

Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

Paul,
Is that OK?

Looks to me like the clock change is unrelated to the DTS changes? Best thing would be if you could just take the DTS changes and I'll take the clkdev alias change.

Otherwise if that doesn't work I can ack it, but there might be some conflicts with other clkdev data changes.

- Paul

#10 lore raw

cover ARM: dts: AM33XX: Add device tree data

Quoted 7 lines · Paul Walmsley

Hi Beno?t

Quoted 3 lines · Benoit

Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

Quoted 6 lines
Quoted 2 lines

Paul,
Is that OK?

Looks to me like the clock change is unrelated to the DTS changes? Best thing would be if you could just take the DTS changes and I'll take the clkdev alias change.

Good point, it can be separated.

Quoted 2 lines

Otherwise if that doesn't work I can ack it, but there might be some conflicts with other clkdev data changes.

No problem, that's fine for me.

Regards,
Benoit

#11 lore raw

cover ARM: dts: AM33XX: Add device tree data

In reply to Cousson, Benoit
Quoted 7 lines · Benoit

+ Paul

Hi Anil,

Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

Thanks Benoit,

Thanks
AnilKumar

#12 lore raw

cover ARM: dts: AM33XX: Add device tree data

+ Matt

Quoted 8 lines · Chimata
Quoted 7 lines · Benoit

+ Paul

Hi Anil,

Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

What about Matt's series to fix the I2C number? Should it be applied on top of that one?

Regards,
Benoit

#13 lore raw

cover ARM: dts: AM33XX: Add device tree data

Quoted 6 lines · Benoit Cousson

+ Matt

Quoted 3 lines · Chimata
Quoted 2 lines · Benoit

+ Paul

Quoted 8 lines
Quoted 5 lines
Quoted 5 lines

Hi Anil,

Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data

What about Matt's series to fix the I2C number? Should it be applied on top of that one?

I had the series to fix the GPIO numbering [1]. It's dependent on this series which carries the led dts patch. Pantelis has a patch for i2c dts numbering in his i2c series [2]. A hunk in that patch has support for his i2c pinctrl series mixed in (not sure where that one is due to the change to early init) so it doesn't apply cleanly alone on top of for_3.7/dts_part2. If you're willing to pick up that i2c renumbering by itself I can drop you a patch just for that part.

-Matt

[1] https://patchwork.kernel.org/patch/1433481/

    https://patchwork.kernel.org/patch/1433471/

[2] https://patchwork.kernel.org/patch/1474001/

Quoted 7 lines

Regards,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html