Re: [PATCH V2] arm:DTS Correct audio input route & set mic bias
On Tue, Jul 14, 2015 at 11:17 AM, Adam YH Lee wrote:
> Audio-in was incorrectly routed to Line In. It should be Mic3L as per
> schematic.
>
> Using mic-bias voltage at 2.0v (<0x1>) does not work for some reason. There
> is no voltage seen on micbias (R127). Mic-bias voltage of 2.5v (<0x2>) works.
> I see voltage of 2.475v across GND and micbias.
>
> With these changes, I can record audio with a pair of proliferate TRRS
> earbuds.
>
> Signed-off-by: Adam YH Lee
> ---
> arch/arm/boot/dts/am335x-pepper.dts | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/am335x-pepper.dts
> b/arch/arm/boot/dts/am335x-pepper.dts
> index d627dc6..73b4cc3 100644
> --- a/arch/arm/boot/dts/am335x-pepper.dts
> +++ b/arch/arm/boot/dts/am335x-pepper.dts
> @@ -74,6 +74,7 @@
> audio_codec: tlv320aic3106@1b {
> compatible = "ti,tlv320aic3106";
> reg = <0x1b>;
> + ai3x-micbias-vg = <0x2>;
> };
>
> accel: lis331dlh@1d {
> @@ -152,7 +153,7 @@
> ti,audio-routing =
> "Headphone Jack", "HPLOUT",
> "Headphone Jack", "HPROUT",
> - "LINE1L", "Line In";
> + "MIC3L","Mic3L Switch";
> };
>
> &mcasp0 {
Note, this is getting resent to correct the sign-offs as requested
https://lkml.org/lkml/2015/7/14/56
Acked-by: Ash Charles
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/3] ARM: dts: configure regulators for Gumstix Pepper
On Sun, Jun 28, 2015 at 11:47 PM, Tony Lindgren wrote: >> Signed-off-by: Ash Charles > > From Adam, sent by Arun, signed by Ash? Can you please check > that too. I reviewed Adam's original patch internally at Gumstix and my Signed-off-by got carried along. In future, would an 'Acked-by' from me be more appropriate? --Ash -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 0/5] Device Tree Fixes for Overo
This series updates the device trees for Gumstix Overo COMs with some minor fixes and support for NAND, the TobiDuo expansion baords, and the Palo35 board. Adam YH Lee (3): omap3: overo: Update LCD panel names omap3: overo: Enable McBSP2 for all Overo COMs omap3: overo: Add device tree for Palo35 board Ash Charles (2): omap3: dts: Add DTS for Gumstix TobiDuo expansion board omap3: overo: Support PoP NAND arch/arm/boot/dts/Makefile| 4 ++ arch/arm/boot/dts/omap3-overo-base.dtsi | 55 +++ arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi | 5 +- arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi | 2 +- arch/arm/boot/dts/omap3-overo-palo35-common.dtsi | 54 +++ arch/arm/boot/dts/omap3-overo-palo35.dts | 38 + arch/arm/boot/dts/omap3-overo-storm-palo35.dts| 38 + arch/arm/boot/dts/omap3-overo-storm-tobiduo.dts | 22 arch/arm/boot/dts/omap3-overo-tobiduo-common.dtsi | 66 +++ arch/arm/boot/dts/omap3-overo-tobiduo.dts | 22 arch/arm/boot/dts/omap3-overo.dtsi| 4 -- 11 files changed, 303 insertions(+), 7 deletions(-) create mode 100644 arch/arm/boot/dts/omap3-overo-palo35-common.dtsi create mode 100644 arch/arm/boot/dts/omap3-overo-palo35.dts create mode 100644 arch/arm/boot/dts/omap3-overo-storm-palo35.dts create mode 100644 arch/arm/boot/dts/omap3-overo-storm-tobiduo.dts create mode 100644 arch/arm/boot/dts/omap3-overo-tobiduo-common.dtsi create mode 100644 arch/arm/boot/dts/omap3-overo-tobiduo.dts -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 5/5] omap3: overo: Add device tree for Palo35 board
From: Adam YH Lee
Also, reduce the maximum SPI device speed to the max. supported by the
LCD controller used on the LGPhilips LB035Q02 panel for this board.
Signed-off-by: Ash Charles
---
arch/arm/boot/dts/Makefile | 2 +
arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi | 3 +-
arch/arm/boot/dts/omap3-overo-palo35-common.dtsi | 54
arch/arm/boot/dts/omap3-overo-palo35.dts | 38 +
arch/arm/boot/dts/omap3-overo-storm-palo35.dts | 38 +
5 files changed, 134 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/omap3-overo-palo35-common.dtsi
create mode 100644 arch/arm/boot/dts/omap3-overo-palo35.dts
create mode 100644 arch/arm/boot/dts/omap3-overo-storm-palo35.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index ac7c6f6bd719..219f5ab1b585 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -387,10 +387,12 @@ dtb-$(CONFIG_ARCH_OMAP3) += \
omap3-overo-alto35.dtb \
omap3-overo-chestnut43.dtb \
omap3-overo-gallop43.dtb \
+ omap3-overo-palo35.dtb \
omap3-overo-palo43.dtb \
omap3-overo-storm-alto35.dtb \
omap3-overo-storm-chestnut43.dtb \
omap3-overo-storm-gallop43.dtb \
+ omap3-overo-storm-palo35.dtb \
omap3-overo-storm-palo43.dtb \
omap3-overo-storm-summit.dtb \
omap3-overo-storm-tobi.dtb \
diff --git a/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
b/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
index df8908adb0cb..80d236ac64a5 100644
--- a/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
+++ b/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
@@ -62,6 +62,7 @@
OMAP3_CORE1_IOPAD(0x21ca, PIN_INPUT | MUX_MODE0)
/* mcspi1_simo.mcspi1_simo */
OMAP3_CORE1_IOPAD(0x21cc, PIN_INPUT | MUX_MODE0)
/* mcspi1_somi.mcspi1_somi */
OMAP3_CORE1_IOPAD(0x21ce, PIN_INPUT | MUX_MODE0)
/* mcspi1_cs0.mcspi1_cs0 */
+ OMAP3_CORE1_IOPAD(0x21d0, PIN_INPUT | MUX_MODE0)
/* mcspi1_cs1.mcspi1_cs1 */
>;
};
@@ -123,7 +124,7 @@
label = "lcd35";
reg = <1>; /* CS1 */
- spi-max-frequency = <1000>;
+ spi-max-frequency = <50>;
spi-cpol;
spi-cpha;
diff --git a/arch/arm/boot/dts/omap3-overo-palo35-common.dtsi
b/arch/arm/boot/dts/omap3-overo-palo35-common.dtsi
new file mode 100644
index ..eab94c13634f
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-overo-palo35-common.dtsi
@@ -0,0 +1,54 @@
+/*
+ * Copyright (C) 2015 Ash Charles, Gumstix Inc.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+/*
+ * Palo35 expansion board is manufactured by Gumstix Inc.
+ */
+
+#include "omap3-overo-common-peripherals.dtsi"
+#include "omap3-overo-common-lcd35.dtsi"
+
+#include
+
+/ {
+ leds {
+ compatible = "gpio-leds";
+ pinctrl-names = "default";
+ pinctrl-0 = <&led_pins>;
+ heartbeat {
+ label = "overo:red:gpio21";
+ gpios = <&gpio1 21 GPIO_ACTIVE_LOW>;/*
gpio_21 */
+ linux,default-trigger = "heartbeat";
+ };
+ gpio22 {
+ label = "overo:blue:gpio22";
+ gpios = <&gpio1 22 GPIO_ACTIVE_LOW>;/*
gpio_22 */
+ };
+ };
+
+ gpio_keys {
+ compatible = "gpio-keys";
+ pinctrl-names = "default";
+ pinctrl-0 = <&button_pins>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ button0@23 {
+ label = "button0";
+ linux,code = ;
+ gpios = <&gpio1 23 GPIO_ACTIVE_LOW>;/*
gpio_23 */
+ gpio-key,wakeup;
+ };
+ button1@14 {
+ label = "button1";
+ linux,code = ;
+ gpios = <&gpio1 14 GPIO_ACTIVE_LOW>;/*
gpio_14 */
+ gpio-key,wakeup;
+ };
+ };
+};
+
diff --git a/arch/arm/boot/dts/omap3-overo-palo35.dts
b/arch/arm/boot/dts/omap3-overo-palo35.dts
new file mode 100644
index ..880101977d43
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-overo-palo35.dts
@@ -0,0 +1,38 @@
+/*
+ * Copyright (C) 2015 Ash C
[PATCH 4/5] omap3: overo: Support PoP NAND
Some Overo COM models include NAND flash in the on-board
package-on-package (PoP) chip. Add this to the base Overo devicetree.
Most commonly, this is 512MB NAND from the Micron MT29C4G96MAZ family
but, as discussed [1], several different sized are possible. To
support different sizes, the last partition should fill to the end of
the chip (i.e. MTDPART_SIZ_FULL).
With thanks to Florian Vaussard for the original patch [2] and Adam Lee for
updating it here.
Signed-off-by: Ash Charles
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/175760.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/175449.html
---
arch/arm/boot/dts/omap3-overo-base.dtsi | 51 +
1 file changed, 51 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-overo-base.dtsi
b/arch/arm/boot/dts/omap3-overo-base.dtsi
index 029e5feb65b4..28430f1596f2 100644
--- a/arch/arm/boot/dts/omap3-overo-base.dtsi
+++ b/arch/arm/boot/dts/omap3-overo-base.dtsi
@@ -222,3 +222,54 @@
status = "okay";
};
+&gpmc {
+ ranges = <0 0 0x 0x2000>;
+
+ nand@0,0 {
+ linux,mtd-name= "micron,mt29c4g96maz";
+ reg = <0 0 0>;
+ nand-bus-width = <16>;
+ gpmc,device-width = <2>;
+ ti,nand-ecc-opt = "bch8";
+
+ gpmc,sync-clk-ps = <0>;
+ gpmc,cs-on-ns = <0>;
+ gpmc,cs-rd-off-ns = <44>;
+ gpmc,cs-wr-off-ns = <44>;
+ gpmc,adv-on-ns = <6>;
+ gpmc,adv-rd-off-ns = <34>;
+ gpmc,adv-wr-off-ns = <44>;
+ gpmc,we-off-ns = <40>;
+ gpmc,oe-off-ns = <54>;
+ gpmc,access-ns = <64>;
+ gpmc,rd-cycle-ns = <82>;
+ gpmc,wr-cycle-ns = <82>;
+ gpmc,wr-access-ns = <40>;
+ gpmc,wr-data-mux-bus-ns = <0>;
+
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ partition@0 {
+ label = "SPL";
+ reg = <0 0x8>; /* 512KiB */
+ };
+ partition@8 {
+ label = "U-Boot";
+ reg = <0x8 0x1C>; /* 1792KiB */
+ };
+ partition@1c {
+ label = "Environment";
+ reg = <0x24 0x4>; /* 256KiB */
+ };
+ partition@28 {
+ label = "Kernel";
+ reg = <0x28 0x80>; /* 8192KiB */
+ };
+ partition@78 {
+ label = "Filesystem";
+ reg = <0xA8 0>;
+ /* HACK: MTDPART_SIZ_FULL=0 so fill to end */
+ };
+ };
+};
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 2/5] omap3: dts: Add DTS for Gumstix TobiDuo expansion board
The Gumstix "Tobi-Duo" expansion board [1] can be used with either
OMAP3 Overo or Overo Storm COMs. It provides two NICs using LAN9221
chips.
It is necessary to duplicate the interface information for the
second SMSC9221 chip as discussed [2].
[1] https://store.gumstix.com/index.php/products/241/
[2] http://www.spinics.net/lists/linux-omap/msg115282.html
Signed-off-by: Ash Charles
---
arch/arm/boot/dts/Makefile| 2 +
arch/arm/boot/dts/omap3-overo-storm-tobiduo.dts | 22
arch/arm/boot/dts/omap3-overo-tobiduo-common.dtsi | 66 +++
arch/arm/boot/dts/omap3-overo-tobiduo.dts | 22
4 files changed, 112 insertions(+)
create mode 100644 arch/arm/boot/dts/omap3-overo-storm-tobiduo.dts
create mode 100644 arch/arm/boot/dts/omap3-overo-tobiduo-common.dtsi
create mode 100644 arch/arm/boot/dts/omap3-overo-tobiduo.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 992736b5229b..ac7c6f6bd719 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -394,8 +394,10 @@ dtb-$(CONFIG_ARCH_OMAP3) += \
omap3-overo-storm-palo43.dtb \
omap3-overo-storm-summit.dtb \
omap3-overo-storm-tobi.dtb \
+ omap3-overo-storm-tobiduo.dtb \
omap3-overo-summit.dtb \
omap3-overo-tobi.dtb \
+ omap3-overo-tobiduo.dtb \
omap3-pandora-600mhz.dtb \
omap3-pandora-1ghz.dtb \
omap3-sbc-t3517.dtb \
diff --git a/arch/arm/boot/dts/omap3-overo-storm-tobiduo.dts
b/arch/arm/boot/dts/omap3-overo-storm-tobiduo.dts
new file mode 100644
index ..0c7d5a70e5e5
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-overo-storm-tobiduo.dts
@@ -0,0 +1,22 @@
+/*
+ * Copyright (C) 2015 Ash Charles, Gumstix, Inc.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+/*
+ * TobiDuo expansion board is manufactured by Gumstix Inc.
+ */
+
+/dts-v1/;
+
+#include "omap3-overo-storm.dtsi"
+#include "omap3-overo-tobiduo-common.dtsi"
+
+/ {
+ model = "OMAP36xx/AM37xx/DM37xx Gumstix Overo on TobiDuo";
+ compatible = "gumstix,omap3-overo-tobiduo", "gumstix,omap3-overo",
"ti,omap36xx", "ti,omap3";
+};
+
diff --git a/arch/arm/boot/dts/omap3-overo-tobiduo-common.dtsi
b/arch/arm/boot/dts/omap3-overo-tobiduo-common.dtsi
new file mode 100644
index ..05788aab3cd3
--- /dev/null
+++ b/arch/arm/boot/dts/omap3-overo-tobiduo-common.dtsi
@@ -0,0 +1,66 @@
+/*
+ * Copyright (C) 2015 Ash Charles, Gumstix, Inc.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+/*
+ * TobiDuo expansion board is manufactured by Gumstix Inc.
+ */
+
+#include "omap3-overo-common-peripherals.dtsi"
+
+#include "omap-gpmc-smsc9221.dtsi"
+
+&gpmc {
+ ranges = <4 0 0x2b00 0x100>,/* CS4 */
+<5 0 0x2c00 0x100>;/* CS5 */
+
+ smsc1: ethernet@gpmc {
+ reg = <5 0 0xff>;
+ interrupt-parent = <&gpio6>;
+ interrupts = <16 IRQ_TYPE_LEVEL_LOW>; /* GPIO 176 */
+ };
+
+ smsc2: ethernet@4,0 {
+ compatible = "smsc,lan9221","smsc,lan9115";
+ bank-width = <2>;
+
+ gpmc,mux-add-data;
+ gpmc,cs-on-ns = <0>;
+ gpmc,cs-rd-off-ns = <42>;
+ gpmc,cs-wr-off-ns = <36>;
+ gpmc,adv-on-ns = <6>;
+ gpmc,adv-rd-off-ns = <12>;
+ gpmc,adv-wr-off-ns = <12>;
+ gpmc,oe-on-ns = <0>;
+ gpmc,oe-off-ns = <42>;
+ gpmc,we-on-ns = <0>;
+ gpmc,we-off-ns = <36>;
+ gpmc,rd-cycle-ns = <60>;
+ gpmc,wr-cycle-ns = <54>;
+ gpmc,access-ns = <36>;
+ gpmc,page-burst-access-ns = <0>;
+ gpmc,bus-turnaround-ns = <0>;
+ gpmc,cycle2cycle-delay-ns = <0>;
+ gpmc,wr-data-mux-bus-ns = <18>;
+ gpmc,wr-access-ns = <42>;
+ gpmc,cycle2cycle-samecsen;
+ gpmc,cycle2cycle-diffcsen;
+ vddvario-supply = <&vddvario>;
+ vdd33a-supply = <&vdd33a>;
+ reg-io-width = <4>;
+ smsc,save-mac-address;
+
+ reg = <4 0 0xff>;
+ interrupt-parent = <&gpio3>;
+ interrupts = <1 IRQ_TYPE_LEVEL_LOW>;/* GPIO 65 */
+ };
+};
+
+&lis33de {
+ st
[PATCH 3/5] omap3: overo: Enable McBSP2 for all Overo COMs
From: Adam YH Lee
Both Gumstix Overo and Overo Storm COMs use TWL4030 audio module
connected to the McBSP2. As such, enable the McBSP2 module in the
common device tree file, omap3-overo-base.dtsi, rather than in the
processor-specific device tree files, omap3-overo.dtsi and
omap3-overo-storm.dtsi. This corrects audio on the Storm COMs where
the setting was accidentally missing from the device tree.
Signed-off-by: Ash Charles
---
arch/arm/boot/dts/omap3-overo-base.dtsi | 4
arch/arm/boot/dts/omap3-overo.dtsi | 4
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-overo-base.dtsi
b/arch/arm/boot/dts/omap3-overo-base.dtsi
index 18e1649681c1..029e5feb65b4 100644
--- a/arch/arm/boot/dts/omap3-overo-base.dtsi
+++ b/arch/arm/boot/dts/omap3-overo-base.dtsi
@@ -218,3 +218,7 @@
pinctrl-0 = <&uart2_pins>;
};
+&mcbsp2 {
+ status = "okay";
+};
+
diff --git a/arch/arm/boot/dts/omap3-overo.dtsi
b/arch/arm/boot/dts/omap3-overo.dtsi
index 69ca7c45bca2..932a02ff552a 100644
--- a/arch/arm/boot/dts/omap3-overo.dtsi
+++ b/arch/arm/boot/dts/omap3-overo.dtsi
@@ -32,7 +32,3 @@
>;
};
};
-
-&mcbsp2 {
- status = "okay";
-};
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 1/5] omap3: overo: Update LCD panel names
From: Adam YH Lee
For Gumstix Overo COMs, the u-boot bootloader typically passes an
argument specifying the default display via the omapdss.def_disp
parameter. When a default display is specified, DSS2 tries to match
this name with either the device tree label (e.g. label=dvi) or,
failing this, the device tree alias (e.g. label=display0). Update the
panel names for the 'lcd43' and 'lcd35' displays in the device tree
such that they match the names passed by u-boot.
Signed-off-by: Ash Charles
---
arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi | 2 +-
arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
b/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
index 233c69e50ae3..df8908adb0cb 100644
--- a/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
+++ b/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
@@ -120,7 +120,7 @@
lcd0: display@0 {
compatible = "lgphilips,lb035q02";
- label = "lcd";
+ label = "lcd35";
reg = <1>; /* CS1 */
spi-max-frequency = <1000>;
diff --git a/arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi
b/arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi
index f5395b7da912..048fd216970a 100644
--- a/arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi
+++ b/arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi
@@ -98,7 +98,7 @@
lcd0: display@0 {
compatible = "samsung,lte430wq-f0c", "panel-dpi";
- label = "lcd";
+ label = "lcd43";
pinctrl-names = "default";
pinctrl-0 = <<e430_pins>;
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 3/3] ARM: dts: Fix frequency scaling on Gumstix Pepper.
This works well for me--cpufreq seems much happier. Tested-by: Ash Charles On Thu, Jun 4, 2015 at 11:08 AM, Arun Bharadwaj wrote: > The device tree for Gumstix Pepper has DCDC2 and > DCDC3 correctly labelled but the upper limit values > are wrong. The confusion is due to the hardware > quirk where the DCDC2 and DCDC3 wires are flipped > in Pepper. > > Signed-off-by: Arun Bharadwaj > --- > arch/arm/boot/dts/am335x-pepper.dts | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/arm/boot/dts/am335x-pepper.dts > b/arch/arm/boot/dts/am335x-pepper.dts > index 99f855d..37b95f6 100644 > --- a/arch/arm/boot/dts/am335x-pepper.dts > +++ b/arch/arm/boot/dts/am335x-pepper.dts > @@ -448,7 +448,7 @@ > /* VDD_CORE voltage limits 0.95V - 1.26V with +/-4% > tolerance */ > regulator-name = "vdd_core"; > regulator-min-microvolt = <925000>; > - regulator-max-microvolt = <1325000>; > + regulator-max-microvolt = <115>; > regulator-boot-on; > regulator-always-on; > }; > @@ -457,7 +457,7 @@ > /* VDD_MPU voltage limits 0.95V - 1.1V with +/-4% > tolerance */ > regulator-name = "vdd_mpu"; > regulator-min-microvolt = <925000>; > - regulator-max-microvolt = <115>; > + regulator-max-microvolt = <1325000>; > regulator-boot-on; > regulator-always-on; > }; > -- > 2.1.4 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: High CPU usage when video streaming on EHCI, 3.17.8 kernel with DMA enabled
On Mon, May 18, 2015 at 7:59 AM, Tony Lindgren wrote: > [PATCH] dmaengine: omap-dma: Add support for memcpy Hi Tom, To follow up on your corresponding mail to the gumstix list [1], I tried on the 3.17.8 kernel on an Overo COM (DM37390) with the suggested dmaengine patch applied. Using "hdparm -t --DIRECT /dev/sda" with a USB hard drive attached via the USB EHCI port, I see a read speed of ~24MB/s (vs ~33MB/s on my laptop). I see the same behaviour on a recent kernel (from tony/omap-for-v4.2/cleanup, otherwise works nicely on an Overo FWIW) with and without the dmaengine patch. What would be the expected USB read speed for an OMAP3 platform? --Ash [1] http://gumstix.8.x6.nabble.com/Low-USB-speed-on-Overo-td4969907.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Supporting two SMSC9221 interfaces on GPMC in a dts
On Thu, Jan 29, 2015 at 8:20 AM, Tony Lindgren wrote: > Yeah I think this is how we did it for omap3-sbc-*.dts*. > >> This works but seems, well, verbose. Is there a way to setup multiple >> interfaces without having to duplicate the omap-gpmc-smsc9221.dtsi >> content? > > Hmm I wonder if the "[PATCH] dtc: parser: Add label while overriding > nodes" would help with this too? > > I agree it would be nice to be able to have device specific .dtsi > file that can be included multiple times for the most common devices. Thanks Tony. For now, I'll follow the lead of omap3-sbc-*.dts* for now in lieu of another technique suggestion. The "[PATCH] dtc: parser: Add label while overriding nodes" patch definitely looks promising so I'll watch for that landing in hopes of testing it for this case. --Ash -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Supporting two SMSC9221 interfaces on GPMC in a dts
Hi, The Gumstix Tobi-Duo board has two SMSC9221 NICs attached to the GPMC interface of an OMAP3. I'm trying to figure out how best to include both interfaces in the device tree file. With just one interface, I can #include "omap-gpmc-smsc9221.dtsi", add the extra board specific settings in to "ethernet@gpmc" in the board file as well as any settings needed for the gpmc. For two interfaces though, I can setup the gpmc details, configure one "ethernet@gpmc" node as before but then, need to manually create (i.e. copy the meat from the "omap-gpmc-smsc9221.dtsi") a second node. This works but seems, well, verbose. Is there a way to setup multiple interfaces without having to duplicate the omap-gpmc-smsc9221.dtsi content? Any hints much appreciated! Thanks, --Ash -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: DT support for OMAP3 ISP
For what it is worth, I was able to get a MT9V032 camera (caspa) working with an OMAP3 using the suggested linux-media branch with these two patches [1,2]. Thanks for the help :) --Ash [1] http://gumstix-misc.s3.amazonaws.com/patches/0001-First-cut-at-caspa-support-with-devicetree.patch [2] http://gumstix-misc.s3.amazonaws.com/patches/0002-Pulling-in.patch On Tue, Jan 6, 2015 at 6:41 PM, Ash Charles wrote: > Thanks for the hints. > > I tried the suggested branch adding omap3isp data to the Overo device > tree and device tree bindings for the mt9v032 device. I needed to > manually modprobe omap3-isp but the camera was registered and I was > able to use media-ctl to manipulate the v4l2 pipeline. I wasn't able > to stream as v4l2 was reporting "inappropriate ioctl"old driver > perhaps? > > I also tried changing the #define HIST_CONFIG_DMA 0 such that the > histogram block uses PIO instead of using the deprecated > omap_request_dma. I saw basically the same behaviour. What would be > the correct/modern way to use DMA here? > > --Ash > > On Tue, Jan 6, 2015 at 2:11 PM, Sakari Ailus wrote: >> (Fixed Laurent's e-mail.) >> >> Moikka, >> >> On Tue, Jan 06, 2015 at 01:42:18PM -0800, Tony Lindgren wrote: >>> * Ash Charles [150106 12:45]: >>> > Hi, >>> > >>> > I'm playing with the Caspa camera (mt9v032) and Overo on the 3.17 >>> > kernel. It looks like there has been some work on dt-bindings for the >>> > omap3isp (notably [1] and [2]) but I didn't see anything heading for >>> > mainline. >>> > >>> > What would be needed to support cameras using the omap3isp in a mainline >>> > kernel? >>> >>> No idea about the camera, but at least the legacy omap DMA calls need >>> to be replaced or removed as the legacy DMA API will go away soon. >> >> OMAP DMA is only used by the histogram block which can cope with PIO as well >> --- I think there at least was a #define for it. That's not a reason not to >> convert it however, it's just not as urgent it otherwise might be. I wonder >> if someone has patches for that already. >> >> Cc Laurent. >> >> -- >> Terveisin, >> >> Sakari Ailus >> e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: DT support for OMAP3 ISP
Thanks for the hints. I tried the suggested branch adding omap3isp data to the Overo device tree and device tree bindings for the mt9v032 device. I needed to manually modprobe omap3-isp but the camera was registered and I was able to use media-ctl to manipulate the v4l2 pipeline. I wasn't able to stream as v4l2 was reporting "inappropriate ioctl"old driver perhaps? I also tried changing the #define HIST_CONFIG_DMA 0 such that the histogram block uses PIO instead of using the deprecated omap_request_dma. I saw basically the same behaviour. What would be the correct/modern way to use DMA here? --Ash On Tue, Jan 6, 2015 at 2:11 PM, Sakari Ailus wrote: > (Fixed Laurent's e-mail.) > > Moikka, > > On Tue, Jan 06, 2015 at 01:42:18PM -0800, Tony Lindgren wrote: >> * Ash Charles [150106 12:45]: >> > Hi, >> > >> > I'm playing with the Caspa camera (mt9v032) and Overo on the 3.17 >> > kernel. It looks like there has been some work on dt-bindings for the >> > omap3isp (notably [1] and [2]) but I didn't see anything heading for >> > mainline. >> > >> > What would be needed to support cameras using the omap3isp in a mainline >> > kernel? >> >> No idea about the camera, but at least the legacy omap DMA calls need >> to be replaced or removed as the legacy DMA API will go away soon. > > OMAP DMA is only used by the histogram block which can cope with PIO as well > --- I think there at least was a #define for it. That's not a reason not to > convert it however, it's just not as urgent it otherwise might be. I wonder > if someone has patches for that already. > > Cc Laurent. > > -- > Terveisin, > > Sakari Ailus > e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
DT support for OMAP3 ISP
Hi, I'm playing with the Caspa camera (mt9v032) and Overo on the 3.17 kernel. It looks like there has been some work on dt-bindings for the omap3isp (notably [1] and [2]) but I didn't see anything heading for mainline. What would be needed to support cameras using the omap3isp in a mainline kernel? Thanks for any insight, --Ash [1] https://github.com/vaussard/linux/commits/overo-for-3.14/iommu/dt-v2 [2] http://git.linuxtv.org/cgit.cgi/sailus/media_tree.git/log/?h=rm696-043-dt -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP 3630 random crashes
Hi Casper,
What is the top-side marking on the memory chip on your Overo? There
were some random faults due to poor memory chips marked 'JW513' from
about 18 months ago.
--Ash
On Fri, Jun 20, 2014 at 7:00 AM, Casper Lyngesen Mogensen
wrote:
> Hi
>
> U-boot seems to set the speed to 165 Mhz
> "OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz"
>
> I have a LAN9221, but tried the other timings, still same result.
>
> Also tried running the entire system from an MMC card, same result, but my
> test had
> to run a little longer.
>
> Found a quicker test to reproduce the error, a little C-program:
>
> #include
> #include
> #include
>
> int main(void){
> long long var=0;
>
> int *ptr=NULL;
>
> int run=1;
> while(run){
> ptr=malloc(sizeof(int)*1000);
> if(ptr==NULL){
> run=0;
> }
> var+=1000;
> printf("mallocsize = %lld\n",var*sizeof(int));
> }
> }
>
>
> Booting from NFS, the system crashes at ~40mb allocated
> On MMC at ~60MB
>
> Med venlig hilsen/Best regards
>
> Casper Mogensen
>
>
> From: Tony Lindgren
> Sent: Friday, June 20, 2014 11:14
> To: Casper Lyngesen Mogensen
> Cc: linux-omap@vger.kernel.org
> Subject: Re: OMAP 3630 random crashes
>
> Hi,
>
> * Casper Lyngesen Mogensen [140620 01:52]:
>> Hi
>>
>> I have custom board with a Gumstix Overo, my board is similar to a
>> Tobi board. Right now i have it running with a 3.5.0 kernel. I'm
>> trying to upgrade the kernel, and have tried several versions (3.10 ->
>> 3.15) and i seem to be hitting the same problem with all versions, i
>> get random crashes. Found a way to trigger the crash within
>> minutes/seconds:
>>
>> # dd if=/dev/urandom of=/tmp/test.file bs=1024 count=10
>>
>> A count > 1 will at some point trigger the crash. The hang/crash
>> is repeatable everytime but the log is not, sometimes i do not get
>> any trace at all. I can provide more logs if necessary. Config and
>> crash log are below..
>>
>> Have tried disabling various peripherals, such as sound, usb,
>> ethernet, wifi, bluetooth, but with no luck. Also tried different Overo
>> boards.
>>
>> Hope someone can help me/point me in the right direction
>
> I was seeing similar issues with NFSroot until commit dcf21919
> (ARM: dts: Fix GPMC timings for LAN9220). Turns out LAN9220 has
> much slower timings compared to LAN9221. So you need to check that
> you're using right timings if you have LAN9220.
>
> Also, check what rate your bootloader is setting the L3 speed.
> If it's set to 200MHz, then LAN9220 timings seem to overflow the
> GPMC registers for the calculated values and bootloader timings
> are used instead.
>
>> Starting kernel ...
>>
>> [0.00] Booting Linux on physical CPU 0x0
>> [0.00] Linux version 3.15.0 (clmo@N66266) (gcc version 4.8.1
>> (crosstool-NG 1.19.0) ) #3 SMP Wed Jun 11 23:50:13 CEST 2014
>> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
>> cr=10c5387d
>> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
>> instruction cache
>> [0.00] Machine model: OMAP36xx/AM37xx/DM37xx Gumstix Overo on Tobi
>> [0.00] cma: CMA: reserved 16 MiB at 8d80
>> [0.00] Memory policy: Data cache writeback
>> [0.00] CPU: All CPU(s) started in SVC mode.
>> [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk )
>> [0.00] PERCPU: Embedded 9 pages/cpu @cecc6000 s14080 r8192 d14592
>> u36864
>> [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total
>> pages: 60704
>> [0.00] Kernel command line: console=ttyO2,115200n8 root=/dev/nfs
>> nfsroot=192.168.100.1:/export/bbroot,nolock rw
>> ip=192.168.100.7::192.168.100.1:::eth0:off mem=240M
>
> Maybe also check if your test works with NFSroot idsabled.
>
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Patch v2] omap: Add devicetree for Gumstix Pepper board
This adds the Gumstix Pepper[1] single-board computer based on the
TI AM335x processor. Schematics are available [2].
[1] https://store.gumstix.com/index.php/products/344/
[2] https://pubs.gumstix.com/boards/PEPPER/
Signed-off-by: Ash Charles
---
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/am335x-pepper.dts | 653
2 files changed, 655 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/am335x-pepper.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index a81a24c..9e0352f 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -277,7 +277,8 @@ dtb-$(CONFIG_SOC_AM33XX) += am335x-base0033.dtb \
am335x-boneblack.dtb \
am335x-evm.dtb \
am335x-evmsk.dtb \
- am335x-nano.dtb
+ am335x-nano.dtb \
+ am335x-pepper.dtb
dtb-$(CONFIG_ARCH_OMAP4) += omap4-duovero-parlor.dtb \
omap4-panda.dtb \
omap4-panda-a4.dtb \
diff --git a/arch/arm/boot/dts/am335x-pepper.dts
b/arch/arm/boot/dts/am335x-pepper.dts
new file mode 100644
index 000..0d35ab6
--- /dev/null
+++ b/arch/arm/boot/dts/am335x-pepper.dts
@@ -0,0 +1,653 @@
+/*
+ * Copyright (C) 2014 Gumstix, Inc. - https://www.gumstix.com/
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+/dts-v1/;
+
+#include
+#include "am33xx.dtsi"
+
+/ {
+ model = "Gumstix Pepper";
+ compatible = "gumstix,am335x-pepper", "ti,am33xx";
+
+ cpus {
+ cpu@0 {
+ cpu0-supply = <&dcdc3_reg>;
+ };
+ };
+
+ memory {
+ device_type = "memory";
+ reg = <0x8000 0x2000>; /* 512 MB */
+ };
+
+ buttons: user_buttons {
+ compatible = "gpio-keys";
+ };
+
+ leds: user_leds {
+ compatible = "gpio-leds";
+ };
+
+ panel: lcd_panel {
+ compatible = "ti,tilcdc,panel";
+ };
+
+ sound: sound_iface {
+ compatible = "ti,da830-evm-audio";
+ };
+
+ vbat: fixedregulator@0 {
+ compatible = "regulator-fixed";
+ };
+
+ v3v3c_reg: fixedregulator@1 {
+ compatible = "regulator-fixed";
+ };
+
+ vdd5_reg: fixedregulator@2 {
+ compatible = "regulator-fixed";
+ };
+};
+
+/* I2C Busses */
+&i2c0 {
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c0_pins>;
+
+ clock-frequency = <40>;
+
+ tps: tps@24 {
+ reg = <0x24>;
+ };
+
+ eeprom: eeprom@50 {
+ compatible = "at,24c256";
+ reg = <0x50>;
+ };
+
+ audio_codec: tlv320aic3106@1b {
+ compatible = "ti,tlv320aic3106";
+ reg = <0x1b>;
+ };
+
+ accel: lis331dlh@1d {
+ compatible = "st,lis3lv02d";
+ reg = <0x1d>;
+ };
+};
+
+&i2c1 {
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c1_pins>;
+ clock-frequency = <40>;
+};
+
+&am33xx_pinmux {
+ i2c0_pins: pinmux_i2c0 {
+ pinctrl-single,pins = <
+ 0x188 (PIN_INPUT_PULLUP | MUX_MODE0)/*
i2c0_sda.i2c0_sda */
+ 0x18c (PIN_INPUT_PULLUP | MUX_MODE0)/*
i2c0_scl.i2c0_scl */
+ >;
+ };
+ i2c1_pins: pinmux_i2c1 {
+ pinctrl-single,pins = <
+ 0x10C (PIN_INPUT_PULLUP | MUX_MODE3)/*
mii1_crs,i2c1_sda */
+ 0x110 (PIN_INPUT_PULLUP | MUX_MODE3)/*
mii1_rxerr,i2c1_scl */
+ >;
+ };
+};
+
+/* Accelerometer */
+&accel {
+ pinctrl-names = "default";
+ pinctrl-0 = <&accel_pins>;
+
+ Vdd-supply = <&ldo3_reg>;
+ Vdd_IO-supply = <&ldo3_reg>;
+ st,irq1-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 = <92>;
+ st,max-limit-x = <14>;
+ st,min-limit-y = <14>;
+ st,max-limit-y = <92>;
+ st,min-limit-z = <92>;
+ st,max-limit-z = <14>;
+};
+
+&am33xx_pinmux {
+ accel_pins: pinmux_accel {
+ pinctrl-single,pins = <
+ 0x98 (PIN_INPUT | MUX_MODE7) /* gpmc_wen.gpio2_4 */
+ >;
+ };
+};
+
+/* Audio */
+&audio_codec {
+ st
Re: [PATCH] omap: Add devicetree for Gumstix Pepper board
On Tue, Jun 10, 2014 at 8:59 AM, Florian Vaussard
wrote:
> It is not very common to add oneself as the maintainer of a single .dts
> file. I could only found the am335x-nano.dts with such a way of doing.
> Usually get_maintainer.pl will also take into account the commit author
> and properly handle this case.
Okay--I'll remove this. Ironically, I was looking at the nano to make
sure I'd done everything I needed to ;-).
...
> For all the boards that I have seen, all the properties of a new node
> are declared at the same place, where you put some of them at the end. I
> have not a strong opinion on this, but I find it a bit more difficult to
> read.
...
> Splitting the pinmux is also unusual, but in this case I found it more
> readable.
My goal both by moving the properties and the pinmux was to separate
out chunks of functionality into discrete sections. It makes it easy
to resolve an issue with a specific board feature (e.g. LEDs) or adapt
for a new board version as the pinmux and any node properties are
grouped together.
I recognize this is something of a personal bias though so I can
certainly re-organize if this is stylistically bad.
...
>> +&am33xx_pinmux {
>> + accel_pins: pinmux_accel {
>> + pinctrl-single,pins = <
>> + 0x98 (PIN_INPUT_PULLUP | MUX_MODE7) /*
>> gpmc_wen.gpio2_4 */
>
> The INT pin of the LIS33 chip seems to be push-pull, thus enabling the
> pullup on the SoC side will increase the current consumption when held down.
Good catch.
...
>> +&am33xx_pinmux {
>> + audio_pins: pinmux_audio {
>> + pinctrl-single,pins = <
>> + 0x1AC (PIN_INPUT_PULLDOWN | MUX_MODE0) /*
>> mcasp0_ahcklx.mcasp0_ahclkx */
>> + 0x194 (PIN_INPUT_PULLDOWN | MUX_MODE0) /*
>> mcasp0_fsx.mcasp0_fsx */
>> + 0x190 (PIN_INPUT_PULLDOWN | MUX_MODE0) /*
>> mcasp0_aclkx.mcasp0_aclkx */
>> + 0x198 (PIN_INPUT_PULLDOWN | MUX_MODE0) /*
>> mcasp0_axr0.mcasp0_axr0 */
>> + 0x1A8 (PIN_INPUT_PULLDOWN | MUX_MODE0) /*
>> mcasp0_axr1.mcasp0_axr1 */
>> + 0x40 (PIN_OUTPUT_PULLUP | MUX_MODE7)/*
>> gpmc_a0.gpio1_16 */
>
> You already have an external pullup in your design, so this one seems
> superfluous.
You're correct. Changed.
...
>> +/* Power */
>> +&vbat {
>> + regulator-name = "vbat";
>> + regulator-min-microvolt = <500>;
>> + regulator-max-microvolt = <500>;
>> + regulator-always-on;
removed regulator-always-on
>> +};
>> +
>> +&v3v3c_reg {
>> + regulator-name = "v3v3c_reg";
>> + regulator-min-microvolt = <330>;
>> + regulator-max-microvolt = <330>;
>> + vin-supply = <&vbat>;
>> + regulator-always-on;
removed regulator-always-on
>> +};
>> +
>> +&vdd5_reg {
>> + regulator-name = "vdd5_reg";
>> + regulator-min-microvolt = <500>;
>> + regulator-max-microvolt = <500>;
>> + regulator-always-on;
removed regulator-always-on
>> + vin-supply = <&vbat>;
>> +};
>> +
>> +/include/ "tps65217.dtsi"
>> +
>> +&tps {
>> + backlight {
>> + isel = <1>; /* ISET1 */
>> + fdim = <200>; /* TPS65217_BL_FDIM_200HZ */
>> + default-brightness = <80>;
>> + };
>> +
>> + regulators {
>> + dcdc1_reg: regulator@0 {
>> + /* VDD_1V8 system supply */
>> + regulator-always-on;
removed regulator-always-on
>> + };
>> +
>> + dcdc2_reg: regulator@1 {
>> + /* VDD_CORE voltage limits 0.95V - 1.26V with +/-4%
>> tolerance */
>> + regulator-name = "vdd_core";
>> + regulator-min-microvolt = <925000>;
>> + regulator-max-microvolt = <1325000>;
>> + regulator-boot-on;
>> + regulator-always-on;
removed regulator-always-on
>> + };
>> +
>> + dcdc3_reg: regulator@2 {
>> + /* VDD_MPU voltage limits 0.95V - 1.1V with +/-4%
>> tolerance */
>> + regulator-name = "vdd_mpu";
>> + regulator-min-microvolt = <925000>;
>> + regulator-max-microvolt = <115>;
>> + regulator-boot-on;
>> + regulator-always-on;
removed regulator-always-on
>> + };
>> +
>> + ldo1_reg: regulator@3 {
>> + /* VRTC 1.8V always-on supply */
>> + regulator-always-on;
This is the backup supply shouldn't be switched off.
>> + };
>> +
>> + ldo2_reg: regulator@4 {
>> + /* 3.3V rail */
>> + regulator-always-on;
removed regulator-always-on
>> + };
>> +
>> + ldo3_reg: regulator@5 {
>> + /* VDD_3V3A 3.3V rail */
>> + regulator-always-on;
removed regulator-always-on
>> + re
[PATCH] omap: Add devicetree for Gumstix Pepper board
This adds the Gumstix Pepper[1] single-board computer based on the
TI AM335x processor. Schematics are available [2].
[1] https://store.gumstix.com/index.php/products/344/
[2] https://pubs.gumstix.com/boards/PEPPER/
Signed-off-by: Ash Charles
---
MAINTAINERS | 6 +
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/am335x-pepper.dts | 661
3 files changed, 669 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/am335x-pepper.dts
diff --git a/MAINTAINERS b/MAINTAINERS
index 51ebb77..d44e2e3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6427,6 +6427,12 @@ L: linux-omap@vger.kernel.org
S: Maintained
F: arch/arm/boot/dts/am335x-nano.dts
+OMAP/GUMSTIX PEPPER MACHINE SUPPORT
+M: Ash Charles
+L: linux-omap@vger.kernel.org
+S: Maintained
+F: arch/arm/boot/dts/am335x-pepper.dts
+
OMFS FILESYSTEM
M: Bob Copeland
L: linux-karma-de...@lists.sourceforge.net
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index a81a24c..9e0352f 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -277,7 +277,8 @@ dtb-$(CONFIG_SOC_AM33XX) += am335x-base0033.dtb \
am335x-boneblack.dtb \
am335x-evm.dtb \
am335x-evmsk.dtb \
- am335x-nano.dtb
+ am335x-nano.dtb \
+ am335x-pepper.dtb
dtb-$(CONFIG_ARCH_OMAP4) += omap4-duovero-parlor.dtb \
omap4-panda.dtb \
omap4-panda-a4.dtb \
diff --git a/arch/arm/boot/dts/am335x-pepper.dts
b/arch/arm/boot/dts/am335x-pepper.dts
new file mode 100644
index 000..27d9b75
--- /dev/null
+++ b/arch/arm/boot/dts/am335x-pepper.dts
@@ -0,0 +1,661 @@
+/*
+ * Copyright (C) 2014 Gumstix, Inc. - https://www.gumstix.com/
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+/dts-v1/;
+
+#include "am33xx.dtsi"
+
+/ {
+ model = "Gumstix Pepper";
+ compatible = "gumstix,am335x-pepper", "ti,am33xx";
+
+ cpus {
+ cpu@0 {
+ cpu0-supply = <&dcdc3_reg>;
+ };
+ };
+
+ memory {
+ device_type = "memory";
+ reg = <0x8000 0x2000>; /* 512 MB */
+ };
+
+ buttons: user_buttons {
+ compatible = "gpio-keys";
+ };
+
+ leds: user_leds {
+ compatible = "gpio-leds";
+ };
+
+ panel: lcd_panel {
+ compatible = "ti,tilcdc,panel";
+ };
+
+ sound: sound_iface {
+ compatible = "ti,da830-evm-audio";
+ };
+
+ vbat: fixedregulator@0 {
+ compatible = "regulator-fixed";
+ };
+
+ v3v3c_reg: fixedregulator@1 {
+ compatible = "regulator-fixed";
+ };
+
+ vdd5_reg: fixedregulator@2 {
+ compatible = "regulator-fixed";
+ };
+};
+
+/* I2C Busses */
+&i2c0 {
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c0_pins>;
+
+ clock-frequency = <40>;
+
+ tps: tps@24 {
+ reg = <0x24>;
+ };
+
+ eeprom: eeprom@50 {
+ compatible = "at,24c256";
+ reg = <0x50>;
+ };
+
+ audio_codec: tlv320aic3106@1b {
+ compatible = "ti,tlv320aic3106";
+ reg = <0x1b>;
+ };
+
+ accel: lis331dlh@1d {
+ compatible = "st,lis3lv02d";
+ reg = <0x1d>;
+ };
+};
+
+&i2c1 {
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c1_pins>;
+ clock-frequency = <40>;
+};
+
+&am33xx_pinmux {
+ i2c0_pins: pinmux_i2c0 {
+ pinctrl-single,pins = <
+ 0x188 (PIN_INPUT_PULLUP | MUX_MODE0)/*
i2c0_sda.i2c0_sda */
+ 0x18c (PIN_INPUT_PULLUP | MUX_MODE0)/*
i2c0_scl.i2c0_scl */
+ >;
+ };
+ i2c1_pins: pinmux_i2c1 {
+ pinctrl-single,pins = <
+ 0x10C (PIN_INPUT_PULLUP | MUX_MODE3)/*
mii1_crs,i2c1_sda */
+ 0x110 (PIN_INPUT_PULLUP | MUX_MODE3)/*
mii1_rxerr,i2c1_scl */
+ >;
+ };
+};
+
+/* Accelerometer */
+&accel {
+ pinctrl-names = "default";
+ pinctrl-0 = <&accel_pins>;
+
+ Vdd-supply = <&ldo3_reg>;
+ Vdd_IO-supply = <&ldo3_reg>;
+ st,irq1-click;
+ st,wakeup-x-lo;
+ st,wakeup-x-hi;
+ st,wakeup-y-lo;
+ st,wakeup-y-hi;
+ st,wakeup-z-lo;
+
Re: [PATCH 00/18] ARM: dts: Better support for Gumstix Overo
Hi Florian, On Thu, Jan 9, 2014 at 9:06 AM, Benoit Cousson wrote: >> The patches 13 to 17 are based on the hardware schematics and >> compile-tested, as I >> do not have the necessary hardware (anyone willing to send me some boards >> ? :-) Firstly: thanks! Secondly: Could you email (a...@gumstix.com) me a wish list of boards/hardware? I'll see what I can wrangle. --Ash -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
