Re: OMAP4430 power management support

[Adam Ford]

I dont' know if it helps, but I struggeled with this too.

With my DM3730 (OMAP 3630), I had to enable Device Drivers->Adaptive
Voltage Scaling Class Support which enables CONFIG_POWER_AVS, a
requirement for POWER_AVS_OMAP.

Once I did that, I was able to get AVS Class 3 working on my DM3730
using th3 4.2+ kernel.  I haven't tried it with 3.14, but I would
expect it to be something similar.

adam

On Wed, Jan 6, 2016 at 9:08 AM, Nishanth Menon  wrote:
> On 01/06/2016 09:05 AM, Frank Jenner wrote:
>> On Wed, Jan 6, 2016 at 9:26 AM, Nishanth Menon  wrote:
>>> On 01/06/2016 08:22 AM, Frank Jenner wrote:
 Hello,

 I am working on trying to enable power management features on a
 product that was based on the OMAP4430 SoC and the mainline 3.14
 kernel. In particular, I am interested in enabling Smart Reflex/AVS
 and frequency scaling (via cpufreq) functionality.
>>>
>>>
>>> AVS class1.5 is supposed to be the official AVS class to be supported on
>>> OMAP3630, OMAP4, OMAP5 SoCs. unfortunately, we dont have that supported
>>> in upstream yet - let alone with cpufreq.
>>>
>>> --
>>> Regards,
>>> Nishanth Menon
>>
>> Sorry my original post might have been TL;DR, but is there a public
>> fork/branch that does have the support?
>
>
> There should be TI vendor kernels on 3.0 or 3.4 kernel that should have
> full entitlement of the SoC if you need that.. but I doubt there has
> been work on OMAP4 on more recent kernels to my knowledge. All work on
> OMAP4/3 is mostly community driven and in upstream.
>
> https://plus.google.com/+NishanthMenon/posts/gvyZQcNieoq
> kind of gives an overview of where we need to go. all contributions are
> welcome.
>
> --
> Regards,
> Nishanth Menon
> --
> 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

OMAP3630-ISP and MT9P031 Device Tree Help

[Adam Ford]

I am trying to setup the device tree to enable a parallel camera
interface as found on the LPD Dev Kit.

The instructions I am using for the basis are:
https://alaganraj.wordpress.com/2015/08/08/beagleboard-xm-camera-li-5m03-mt9p031-support-with-device-tree/

It I get the same results when I compile it into the kernel or as a
module, but the errors are the same.

When I modprobe it, I get:

# modprobe omap3-isp
 omap3isp 480bc000.isp: parsing endpoint
/ocp/isp@480bc000/ports/port@0/endpoint, interface 0
 omap3isp 480bc000.isp: Revision 15.0 found
iommu: Adding device 480bc000.isp to group 0
 omap-iommu 480bd400.mmu: 480bd400.mmu: version 1.1
omap3isp 480bc000.isp: hist: using DMA channel dma0chan6
 omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP
CCP2 was not initialized!
omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP
CSI2a was not initialized!
omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP
CCDC was not initialized!
omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP
preview was not initialized!
 omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP
resizer was not initialized!
omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP
AEWB was not initialized!
omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP
AF was not initialized!
omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP
histogram was not initialized!
#

 I then modprobe the mt9p031 driver, and it won't initialize, but it
is detected.

# modprobe mt9p031
[  127.390808] 1-0048 supply vdd not found, using dummy regulator
[  127.398101] 1-0048 supply vaa not found, using dummy regulator
[  127.404907] omap3isp 480bc000.isp: isp_xclk_set_rate: cam_xclka set
to 2160 Hz (div 8)
[  127.432861] mt9p031 1-0048: MT9P031 detected at address 0x48
[  127.438873] omap3isp 480bc000.isp: Entity type for entity mt9p031
1-0048 was not initialized!
#

I can post my device tree if necessary, but it's basically like what's
in the link above.  Does anyone have any ideas on what I am doing
wrong?

adam
--
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: OMAP4430 power management support

[Adam Ford]

Any chance you can define what you mean by 'issues' and 'old'?

Logic PD (my daytime employer) uses AVS 3 in their custom Linux
distribution.  If that's going to be a problem, I would like to notify
some people there.

adam

On Wed, Jan 6, 2016 at 1:12 PM, Nishanth Menon <menon.nisha...@gmail.com> wrote:
> On 01/06/2016 10:02 AM, Adam Ford wrote:
>> I dont' know if it helps, but I struggeled with this too.
>>
>> With my DM3730 (OMAP 3630), I had to enable Device Drivers->Adaptive
>> Voltage Scaling Class Support which enables CONFIG_POWER_AVS, a
>> requirement for POWER_AVS_OMAP.
>>
>> Once I did that, I was able to get AVS Class 3 working on my DM3730
>> using th3 4.2+ kernel.  I haven't tried it with 3.14, but I would
>
>
> Arggh... using AVS class3 with DM3730 will create all kinds of issues
> later on as the device gets old. Wish we had managed to get AVS 1.5
> basic functionality upstream :(.
>
>
> --
> Regards,
> Nishanth Menon
--
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] ARM: OMAP2+: LogicPD Torpedo: Revert Duplicative Entries

[Adam Ford]

Revert commit 7cd6ca770d1b ("ARM: dts: Change I2C2 and I2C3 to 400KHz
for LogicPD Torpedo DM3730 devkit")  It was already done and it is
just a duplicate.

Signed-off-by: Adam Ford <aford...@gmail.com>
---
 arch/arm/boot/dts/logicpd-torpedo-som.dtsi | 8 
 1 file changed, 8 deletions(-)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi 
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index 7fed0bd..78c5243 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -112,14 +112,6 @@
clock-frequency = <40>;
 };
 
- {
-   clock-frequency = <40>;
-};
-
- {
-   clock-frequency = <40>;
-};
-
 /*
  * Only found on the wireless SOM. For the SOM without wireless, the pins for
  * MMC3 can be routed with jumpers to the second MMC slot on the devkit and
-- 
1.9.1

--
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

PWM Driver for OMAP (and backlight)

[Adam Ford]

Happy Holidays everyone.

I have a DM3730 that am trying to setup timer 10 to drive a PWM that
controls the LCD backlight.

Using the linux-next git branch, I am trying to use the
pwm-omap-dmtimer function and  I have configured the Device Tree as
follows:

bl: backlight {
compatible = "pwm-backlight";
pinctrl-names = "default";
pinctrl-0 = <_pins _pwm_pins>;

pwms = < 0 500>;

brightness-levels = <0 10 20 30 40 50 60 70 80 90 100>;
default-brightness-level = <7>;

enable-gpios = < 26 GPIO_ACTIVE_HIGH>; /* gpio_154 */
default-on;
};

pwm10: dmtimer-pwm@10 {
status = "okay";
compatible = "ti,omap-dmtimer-pwm";
ti,timers = <>;
#pwm-cells = <3>;
};

The Pinmuxing is configured as follows:
backlight_pwm_pins: pinmux_backlight_pwm_pins {
pinctrl-single,pins = <
OMAP3_CORE1_IOPAD(0x20B8, PIN_OUTPUT | MUX_MODE2)   /* gpmc_ncs5.gpio_56 */
>;
};

backlight_pins: pinmux_backlight_pins {
pinctrl-single,pins = <
OMAP3_CORE1_IOPAD(0x2188, PIN_OUTPUT | MUX_MODE4)   /* mcbsp4_dx.gpio_154 */
>;
};


I can certainly combine the backlight pinmuxing, but I can't figure
out the following errors

I get the following error:
[0.387145] omap-dmtimer-pwm dmtimer-pwm@10: Missing dmtimer platform data
[0.387176] omap-dmtimer-pwm: probe of dmtimer-pwm@10 failed with error -22
[0.389495] pwm-backlight backlight: unable to request PWM
[0.389617] pwm-backlight: probe of backlight failed with error -22

I assume that the backlight fails because the pwm fails, and I was
hoping some of you guys with more experience with this new pwm driver
might have some insight.  I have the pwm driver built into the kernel.
I wasn't sure if I could directly reference timer10 from the backlight
since the examples showed it referencing a pwm.

adam
--
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] ARM: OMAP2+: LogicPD Torpedo: Add Touchscreen Support

[Adam Ford]

The development kit uses a TSC2004 chip attached to I2C3.

Signed-off-by: Adam Ford <aford...@gmail.com>
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 27 +++
 1 file changed, 27 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index 6854bda..fb13f18 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -204,6 +204,12 @@
>;
};
 
+   tsc2004_pins: pinmux_tsc2004_pins {
+   pinctrl-single,pins = <
+   OMAP3_CORE1_IOPAD(0x2186, PIN_INPUT | MUX_MODE4)
/* mcbsp4_dr.gpio_153 */
+   >;
+   };
+
backlight_pins: pinmux_backlight_pins {
pinctrl-single,pins = <
OMAP3_CORE1_IOPAD(0x20B8, PIN_OUTPUT | MUX_MODE4)   
/* gpmc_ncs5.gpio_56 */
@@ -262,6 +268,27 @@
};
 };
 
+ {
+   touchscreen: tsc2004@48 {
+   compatible = "ti,tsc2004";
+   reg = <0x48>;
+   vio-supply = <>;
+   pinctrl-names = "default";
+   pinctrl-0 = <_pins>;
+   interrupts-extended = < 25 IRQ_TYPE_EDGE_RISING>; /* gpio 
153 */
+
+   touchscreen-fuzz-x = <4>;
+   touchscreen-fuzz-y = <7>;
+   touchscreen-fuzz-pressure = <2>;
+   touchscreen-size-x = <4096>;
+   touchscreen-size-y = <4096>;
+   touchscreen-max-pressure = <2048>;
+
+   ti,x-plate-ohms = <280>;
+   ti,esd-recovery-timeout-ms = <8000>;
+   };
+};
+
  {
interrupts-extended = < 72 _pmx_core OMAP3_UART1_RX>;
 };
-- 
1.9.1

--
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 5/5] fbdev: omap2: panel-dpi: allow specification of a vcc regulator

[Adam Ford]

Tomi,

Do you have any thought on how to approach adding sleep/delay
functions?  I have a display that requires a small delay before and
after the enable gpio toggle.  I assume that some may require a delay
after the regulator starts for it to be be ready.  For now I have a
temp hack that just inserts a blanket 300mS wait, but I'd rather have
something mainstreamed in the device tree, but I don't want to walk
over someone else's work either.

I'd love to help if you have an idea of how you vision it.

adam

On Wed, Dec 16, 2015 at 11:38 AM, Tomi Valkeinen  wrote:
>
>
> On 10/12/15 15:11, Uwe Kleine-König wrote:
>> From: Uwe Kleine-König 
>>
>> To allow supporting displays that need some logic to enable power to the
>> display add support for a vcc-supply property to drive a regulator.
>>
>> Signed-off-by: Uwe Kleine-König 
>> ---
>>  Documentation/devicetree/bindings/video/panel-dpi.txt |  1 +
>>  drivers/video/fbdev/omap2/displays-new/panel-dpi.c| 13 +
>>  2 files changed, 14 insertions(+)
>
> Same comments here about the bindings.
>
>> diff --git a/Documentation/devicetree/bindings/video/panel-dpi.txt 
>> b/Documentation/devicetree/bindings/video/panel-dpi.txt
>> index 1a1d8f6f884f..eaa39d1b1279 100644
>> --- a/Documentation/devicetree/bindings/video/panel-dpi.txt
>> +++ b/Documentation/devicetree/bindings/video/panel-dpi.txt
>> @@ -8,6 +8,7 @@ Optional properties:
>>  - label: a symbolic name for the panel
>>  - enable-gpios: panel enable gpio
>>  - reset-gpios: GPIO to control the RESET pin
>> +- vcc-supply: phandle of regulator that will be used to enable power to the 
>> display
>>
>>  Required nodes:
>>  - "panel-timing" containing video timings
>> diff --git a/drivers/video/fbdev/omap2/displays-new/panel-dpi.c 
>> b/drivers/video/fbdev/omap2/displays-new/panel-dpi.c
>> index 7e2f9e0813dc..65c6d9e6862b 100644
>> --- a/drivers/video/fbdev/omap2/displays-new/panel-dpi.c
>> +++ b/drivers/video/fbdev/omap2/displays-new/panel-dpi.c
>> @@ -15,6 +15,7 @@
>>  #include 
>>  #include 
>>  #include 
>> +#include 
>>
>>  #include 
>>  #include 
>> @@ -33,6 +34,7 @@ struct panel_drv_data {
>>
>>   struct gpio_desc *enable_gpio;
>>   struct gpio_desc *reset_gpio;
>> + struct regulator *vcc_supply;
>>  };
>>
>>  #define to_panel_data(p) container_of(p, struct panel_drv_data, dssdev)
>> @@ -84,6 +86,12 @@ static int panel_dpi_enable(struct omap_dss_device 
>> *dssdev)
>>   if (r)
>>   return r;
>>
>> + r = regulator_enable(ddata->vcc_supply);
>> + if (r) {
>> + in->ops.dpi->disable(in);
>> + return r;
>> + }
>> +
>>   gpiod_set_value_cansleep(ddata->reset_gpio, 0);
>>   gpiod_set_value_cansleep(ddata->enable_gpio, 1);
>>
>> @@ -107,6 +115,7 @@ static void panel_dpi_disable(struct omap_dss_device 
>> *dssdev)
>>   gpio_set_value_cansleep(ddata->backlight_gpio, 0);
>>
>>   gpiod_set_value_cansleep(ddata->enable_gpio, 0);
>> + regulator_disable(ddata->vcc_supply);
>>
>>   in->ops.dpi->disable(in);
>>
>> @@ -218,6 +227,10 @@ static int panel_dpi_probe_of(struct platform_device 
>> *pdev)
>>   if (IS_ERR(ddata->reset_gpio))
>>   return PTR_ERR(ddata->reset_gpio);
>>
>> + ddata->vcc_supply = devm_regulator_get(>dev, "vcc");
>> + if (IS_ERR(ddata->vcc_supply))
>> + return PTR_ERR(ddata->vcc_supply);
>> +
>>   ddata->backlight_gpio = -ENOENT;
>>
>>   r = of_get_display_timing(node, "panel-timing", );
>
> Some panels might need to sleep before/after the regulator, but the same
> goes for enable gpio. And we don't have a sane way to handle that at the
> moment, so I think this is fine.
>
>  Tomi
>
--
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 display kconfig options changing

[Adam Ford]

Tomi,

I'd like to also test the LogicPD Torpedo which has been using the FB
drivers until this point. I just pushed some LCD info for inclusion in
4.5, but if I need to make changes, I'd like to do that sooner than
later.  Any insturctions would be helpful.  Will this impact people
who use the SGX drivers?


Thanks

adam

On Fri, Dec 18, 2015 at 7:53 AM, Tony Lindgren  wrote:
> Hi,
>
> * Tomi Valkeinen  [151218 00:55]:
>> Hi Tony,
>>
>> I've just pushed a patch series to fbdev for-next branch which makes the
>> OMAP DRM and FB drivers independent of each other. This requires
>> changing the related Kconfig options.
>
> OK
>
>> What should I do with omap2plus_defconfig?
>>
>> At the moment omap2plus_defconfig enables the omapfb driver and panels
>> as modules. Should I change it to do the same with the new code? Or
>> should I change it to use omapdrm, which is the better maintained and
>> developed driver (although no one has probably tried omapdrm on omap2)?
>
> I'm all for changing omap2plus_defconfnig to use omapdrm.
>
> Do you have a link to a page we can point people to for instructions
> for what needs to be changed to get things working with omapdrm?
>
> For omap2, I can try to peek into my rack for n800.
>
> 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] ARM: OMAP2+: LogicPD Torpedo: Revert Duplicative Entries

[Adam Ford]

Revert 6f0f6c40b66 ("ARM: dts: Set VAUX1 and VAUX4 on Logic PD Torpedo")
because it It was already done and it's just a duplicate.  See:
2d11961f3e55 ("ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V respectively")

Signed-off-by: Adam Ford <aford...@gmail.com>
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 10 --
 1 file changed, 10 deletions(-)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index b017871..b07d1d9 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -83,16 +83,6 @@
regulator-max-microvolt = <180>;
 };
 
- {
-   regulator-min-microvolt = <300>;
-   regulator-max-microvolt = <300>;
-};
-
- {
-   regulator-min-microvolt = <180>;
-   regulator-max-microvolt = <180>;
-};
-
  {
status = "okay";
 };
-- 
1.9.1

--
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] ARM: OMAP2+: LogicPD Torpedo + Wireless: Add Bluetooth

[Adam Ford]

Bindings for the WL1283 Bluetooth was removed from the shared transport
driver in commit c0bd1b9e5895 ("Revert ti-st: add device tree support")
Until we havea better binding, we need to use the platform data to
initialize Bluetooth.

Signed-off-by: Adam Ford <aford...@gmail.com>
---
 arch/arm/mach-omap2/pdata-quirks.c | 24 +++-
 1 file changed, 23 insertions(+), 1 deletion(-)

diff --git a/arch/arm/mach-omap2/pdata-quirks.c 
b/arch/arm/mach-omap2/pdata-quirks.c
index e097055..e781e4f 100644
--- a/arch/arm/mach-omap2/pdata-quirks.c
+++ b/arch/arm/mach-omap2/pdata-quirks.c
@@ -150,6 +150,21 @@ static struct platform_device wl18xx_device = {
}
 };
 
+static struct ti_st_plat_data wilink7_pdata = {
+   .nshutdown_gpio = 162,
+   .dev_name = "/dev/ttyO1",
+   .flow_cntrl = 1,
+   .baud_rate = 30,
+};
+
+static struct platform_device wl128x_device = {
+   .name   = "kim",
+   .id = -1,
+   .dev= {
+   .platform_data = _pdata,
+   }
+};
+
 static struct platform_device btwilink_device = {
.name   = "btwilink",
.id = -1,
@@ -276,6 +291,13 @@ static void __init omap3_tao3530_legacy_init(void)
hsmmc2_internal_input_clk();
 }
 
+static void __init omap3_logicpd_torpedo_init(void)
+{
+   omap3_gpio126_127_129();
+   platform_device_register(_device);
+   platform_device_register(_device);
+}
+
 /* omap3pandora legacy devices */
 #define PANDORA_WIFI_IRQ_GPIO  21
 #define PANDORA_WIFI_NRESET_GPIO   23
@@ -503,7 +525,7 @@ static struct pdata_init pdata_quirks[] __initdata = {
{ "nokia,omap3-n950", hsmmc2_internal_input_clk, },
{ "isee,omap3-igep0020-rev-f", omap3_igep0020_rev_f_legacy_init, },
{ "isee,omap3-igep0030-rev-g", omap3_igep0030_rev_g_legacy_init, },
-   { "logicpd,dm3730-torpedo-devkit", omap3_gpio126_127_129, },
+   { "logicpd,dm3730-torpedo-devkit", omap3_logicpd_torpedo_init, },
{ "ti,omap3-evm-37xx", omap3_evm_legacy_init, },
{ "ti,am3517-evm", am3517_evm_legacy_init, },
{ "technexion,omap3-tao3530", omap3_tao3530_legacy_init, },
-- 
1.9.1

--
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] ARM: OMAP2+: LogicPD Torpedo + Wireless: Revert duplicative DTS entries

[Adam Ford]

Revert commit 6f0f6c40b66 ("ARM: dts: Set VAUX1 and VAUX4 on Logic PD Torpedo")
because it It was already done and it's just a duplicate.  See:
commit 2d11961f3e55 ("ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V 
respectively")
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 10 --
 1 file changed, 10 deletions(-)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index b017871..b07d1d9 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -83,16 +83,6 @@
regulator-max-microvolt = <180>;
 };
 
- {
-   regulator-min-microvolt = <300>;
-   regulator-max-microvolt = <300>;
-};
-
- {
-   regulator-min-microvolt = <180>;
-   regulator-max-microvolt = <180>;
-};
-
  {
status = "okay";
 };
-- 
1.9.1

--
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] ARM: OMAP2+: LogicPD Torpedo: Add LCD Type 15 Support

[Adam Ford]

Add basic support for Logic PD type 15 display for older development kits.
This uses GPIO for the backlight.

Signed-off-by: Adam Ford <aford...@gmail.com>
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 110 --
 1 file changed, 100 insertions(+), 10 deletions(-)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index b017871..1b9e1cf 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -114,6 +104,70 @@
};
 };
 
+ {
+   regulator-always-on;
+};
+
+ {
+   status = "ok";
+   vdds_dsi-supply = <>;
+   pinctrl-names = "default";
+   pinctrl-0 = <_dpi_pins1>;
+   port {
+   dpi_out: endpoint {
+   remote-endpoint = <_in>;
+   data-lines = <16>;
+   };
+   };
+};
+
+/ {
+   aliases {
+   display0 = 
+   };
+
+   lcd0: display@0 {
+   compatible = "panel-dpi";
+   label = "15";
+   status = "okay";
+   /* default-on; */
+   pinctrl-names = "default";
+   enable-gpios = < 27 GPIO_ACTIVE_HIGH>;/* gpio155, lcd 
INI */
+
+   port {
+   lcd_in: endpoint {
+   remote-endpoint = <_out>;
+   };
+   };
+
+   panel-timing {
+   clock-frequency = <900>;
+   hactive = <480>;
+   vactive = <272>;
+   hfront-porch = <3>;
+   hback-porch = <2>;
+   hsync-len = <42>;
+   vback-porch = <3>;
+   vfront-porch = <4>;
+   vsync-len = <11>;
+   hsync-active = <0>;
+   vsync-active = <0>;
+   de-active = <1>;
+   pixelclk-active = <1>;
+   };
+   };
+
+   bl: backlight {
+   compatible = "gpio-backlight";
+   pinctrl-names = "default";
+   pinctrl-0 = <_pins>;
+
+   gpios = < 24 GPIO_ACTIVE_HIGH>, /* gpio_56 */
+   < 26 GPIO_ACTIVE_HIGH>; /* gpio_154 */
+   default-on;
+   };
+};
+
  {
interrupts-extended = < 83 _pmx_core 0x11a>;
pinctrl-names = "default";
@@ -149,6 +203,42 @@
OMAP3_CORE1_IOPAD(0x214e, PIN_INPUT | MUX_MODE0)
/* sdmmc1_dat3.sdmmc1_dat3 */
>;
};
+
+   backlight_pins: pinmux_backlight_pins {
+   pinctrl-single,pins = <
+   OMAP3_CORE1_IOPAD(0x20B8, PIN_OUTPUT | MUX_MODE4)   
/* gpmc_ncs5.gpio_56 */
+   OMAP3_CORE1_IOPAD(0x2188, PIN_OUTPUT | MUX_MODE4)   
/* mcbsp4_dx.gpio_154 */
+   >;
+   };
+
+   dss_dpi_pins1: pinmux_dss_dpi_pins1 {
+   pinctrl-single,pins = <
+   OMAP3_CORE1_IOPAD(0x20d4, PIN_OUTPUT | MUX_MODE0)   /* 
dss_pclk.dss_pclk */
+   OMAP3_CORE1_IOPAD(0x20d6, PIN_OUTPUT | MUX_MODE0)   /* 
dss_hsync.dss_hsync */
+   OMAP3_CORE1_IOPAD(0x20d8, PIN_OUTPUT | MUX_MODE0)   /* 
dss_vsync.dss_vsync */
+   OMAP3_CORE1_IOPAD(0x20da, PIN_OUTPUT | MUX_MODE0)   /* 
dss_acbias.dss_acbias */
+
+   OMAP3_CORE1_IOPAD(0x20e8, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data6.dss_data6 */
+   OMAP3_CORE1_IOPAD(0x20ea, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data7.dss_data7 */
+   OMAP3_CORE1_IOPAD(0x20ec, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data8.dss_data8 */
+   OMAP3_CORE1_IOPAD(0x20ee, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data9.dss_data9 */
+   OMAP3_CORE1_IOPAD(0x20f0, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data10.dss_data10 */
+   OMAP3_CORE1_IOPAD(0x20f2, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data11.dss_data11 */
+   OMAP3_CORE1_IOPAD(0x20f4, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data12.dss_data12 */
+   OMAP3_CORE1_IOPAD(0x20f6, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data13.dss_data13 */
+   OMAP3_CORE1_IOPAD(0x20f8, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data14.dss_data14 */
+   OMAP3_CORE1_IOPAD(0x20fa, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data15.dss_data15 */
+   OMAP3_CORE1_IOPAD(0x20fc, PIN_OUTPUT | MUX_MODE0)   /* 
dss_data16.dss_data16 */
+   OMAP3_CORE1_IOPAD(0x20fe, PIN_OUTPUT | MU

[PATCH] ARM: OMAP2+: LogicPD Torpedo + Wireless: add Bluetooth support Add WL1283 support through pdata-quirks since the driver lacks DT support

[Adam Ford]

Signed-off-by: Adam Ford <aford...@gmail.com>
---
 arch/arm/mach-omap2/pdata-quirks.c | 24 +++-
 1 file changed, 23 insertions(+), 1 deletion(-)

diff --git a/arch/arm/mach-omap2/pdata-quirks.c 
b/arch/arm/mach-omap2/pdata-quirks.c
index e097055..e781e4f 100644
--- a/arch/arm/mach-omap2/pdata-quirks.c
+++ b/arch/arm/mach-omap2/pdata-quirks.c
@@ -150,6 +150,21 @@ static struct platform_device wl18xx_device = {
}
 };
 
+static struct ti_st_plat_data wilink7_pdata = {
+   .nshutdown_gpio = 162,
+   .dev_name = "/dev/ttyO1",
+   .flow_cntrl = 1,
+   .baud_rate = 30,
+};
+
+static struct platform_device wl128x_device = {
+   .name   = "kim",
+   .id = -1,
+   .dev= {
+   .platform_data = _pdata,
+   }
+};
+
 static struct platform_device btwilink_device = {
.name   = "btwilink",
.id = -1,
@@ -276,6 +291,13 @@ static void __init omap3_tao3530_legacy_init(void)
hsmmc2_internal_input_clk();
 }
 
+static void __init omap3_logicpd_torpedo_init(void)
+{
+   omap3_gpio126_127_129();
+   platform_device_register(_device);
+   platform_device_register(_device);
+}
+
 /* omap3pandora legacy devices */
 #define PANDORA_WIFI_IRQ_GPIO  21
 #define PANDORA_WIFI_NRESET_GPIO   23
@@ -503,7 +525,7 @@ static struct pdata_init pdata_quirks[] __initdata = {
{ "nokia,omap3-n950", hsmmc2_internal_input_clk, },
{ "isee,omap3-igep0020-rev-f", omap3_igep0020_rev_f_legacy_init, },
{ "isee,omap3-igep0030-rev-g", omap3_igep0030_rev_g_legacy_init, },
-   { "logicpd,dm3730-torpedo-devkit", omap3_gpio126_127_129, },
+   { "logicpd,dm3730-torpedo-devkit", omap3_logicpd_torpedo_init, },
{ "ti,omap3-evm-37xx", omap3_evm_legacy_init, },
{ "ti,am3517-evm", am3517_evm_legacy_init, },
{ "technexion,omap3-tao3530", omap3_tao3530_legacy_init, },
-- 
1.9.1

--
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] ARM: dts: Enable Shared Transport and Bluetooth on LogicPD Torpedo + Wireless module

[Adam Ford]

Configure the shared transport which enables communication with GPS/Bluetooth 
module.
Setup UART2 for communication at 3MBps with flow control.
Setup GPIO_162 as Bluetooth Enable.

Signed-off-by: Adam Ford <adam.f...@logicpd.com>
---
 arch/arm/boot/dts/logicpd-torpedo-som.dtsi | 27 +++
 1 file changed, 27 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi 
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index c8091ff..b7460ea 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -32,6 +32,18 @@
enable-active-high;
vin-supply = <>;
};
+
+   kim {
+   compatible = "kim";
+   nshutdown_gpio = <162>; /* Bank3, pin21 */
+   dev_name = "/dev/ttyO1";
+   flow_cntrl = <1>;
+   baud_rate = <30>;
+   };
+
+   btwilink {
+   compatible = "btwilink";
+   };
 };
 
  {
@@ -157,6 +169,21 @@
OMAP3_CORE1_IOPAD(0x2142, PIN_OUTPUT | MUX_MODE0)   
/* mcbsp2_dx */
>;
};
+   uart2_pins: pinmux_uart2_pins {
+pinctrl-single,pins = <
+OMAP3_CORE1_IOPAD(0x2174, PIN_INPUT | MUX_MODE0)   
/* uart2_cts.uart2_cts */
+OMAP3_CORE1_IOPAD(0x2176, PIN_OUTPUT | MUX_MODE0)  
/* uart2_rts .uart2_rts*/
+OMAP3_CORE1_IOPAD(0x2178, PIN_OUTPUT | MUX_MODE0)  
/* uart2_tx.uart2_tx */
+OMAP3_CORE1_IOPAD(0x217a, PIN_INPUT | MUX_MODE0)   
/* uart2_rx.uart2_rx */
+   OMAP3_CORE1_IOPAD(0x2198, PIN_OUTPUT | MUX_MODE4)   
/* GPIO_162,BT_EN */
+>;
+};
+};
+
+ {
+   interrupts-extended = < 73 _pmx_core OMAP3_UART2_RX>;
+pinctrl-names = "default";
+pinctrl-0 = <_pins>;
 };
 
 _pmx_core2 {
-- 
1.9.1

--
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

Question about TI Shared Transport

[Adam Ford]

Gigi,

I am working on modifying the DTS and DTSI files for the LogicPD Torpedo which 
Tony added in Kernel 4.2

There was a flurry of activity earlier this year regarding device tree bindings 
for the shared transport and using the Bluetooth with it as seen here:  
https://patchwork.ozlabs.org/patch/464777/

I was able to get the Logic PD device to work with Bluetooth and the Shared 
Transport using the instructions found 
http://processors.wiki.ti.com/index.php/Shared_Transport_Driver#Device_Tree_kernel

When I attempted to submit patches for the btwilink, the check script noted 
that the documentation for btwlink and shared transport bindings were missing.  
It seems like there might be a new way to attach the BTWILINK to the UART, but 
I wasn't sure if there was a better solution available yet.

I also noticed that using the shared transport mechanism in 4.2.x worked, but 
trying the same method in 4.3 resulted in a segmentation fault.  Does anyone 
have any updated instructions for the proper way to use the BTWILINK?

Thank you,
adam

Adam Ford  //  Sr. Apps Engineer
Logic PD
411 Washington Ave N, Suite 400  
Minneapolis, MN 55401
M // 612.246.6391
T // 612.436.5117x7113
F // 612.672.6489
adam.f...@logicpd.com  
Logic PD // Twitter // LinkedIn

NOTICE: Important disclaimers and limitations apply to this email.
Please see this web page for our disclaimers and limitations:
http://logicpd.com/email-disclaimer/


--
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: Question about TI Shared Transport

[Adam Ford]

The revert appears in the 4.2.4 log as well, so it happened before 4.2 was 
released. From what I can see, that ti-st directory hasn't changed between 
4.2.4 and the 4.3.

-Original Message-
From: Grygorii Strashko [mailto:grygorii.stras...@ti.com] 
Sent: Monday, October 26, 2015 9:55 AM
To: Adam Ford <adam.f...@logicpd.com>; 'gigi.jos...@ti.com' 
<gigi.jos...@ti.com>; 'mar...@holtmann.org' <mar...@holtmann.org>; 
'devicet...@vger.kernel.org' <devicet...@vger.kernel.org>
Cc: 'Tony Lindgren' <t...@atomide.com>; 'linux-omap@vger.kernel.org' 
<linux-omap@vger.kernel.org>; Sekhar Nori <nsek...@ti.com>
Subject: Re: Question about TI Shared Transport

On 10/26/2015 03:58 PM, Adam Ford wrote:
> Gigi,
>
> I am working on modifying the DTS and DTSI files for the LogicPD Torpedo 
> which Tony added in Kernel 4.2
>
> There was a flurry of activity earlier this year regarding device tree 
> bindings for the shared transport and using the Bluetooth with it as seen 
> here:  https://patchwork.ozlabs.org/patch/464777/
>
> I was able to get the Logic PD device to work with Bluetooth and the Shared 
> Transport using the instructions found 
> http://processors.wiki.ti.com/index.php/Shared_Transport_Driver#Device_Tree_kernel
>
> When I attempted to submit patches for the btwilink, the check script noted 
> that the documentation for btwlink and shared transport bindings were 
> missing.  It seems like there might be a new way to attach the BTWILINK to 
> the UART, but I wasn't sure if there was a better solution available yet.
>
> I also noticed that using the shared transport mechanism in 4.2.x worked, but 
> trying the same method in 4.3 resulted in a segmentation fault.  Does anyone 
> have any updated instructions for the proper way to use the BTWILINK?
>

It is not worked because OF support was reverted:
c0bd1b9 Revert "ti-st: add device tree support"


-- 
regards,
-grygorii
--
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] ARM: dts: Change I2C2 and I2C3 to 400KHz for LogicPD Torpedo DM3730 devkit

[Adam Ford]

When used with the Logic PD development kit, this makes the I2C buses match
the BSP released by Logic PD.

Signed-off-by: Adam Ford <adam.f...@logicpd.com>
---
 arch/arm/boot/dts/logicpd-torpedo-som.dtsi | 8 
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi 
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index 36387b1..8b803ed 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -99,6 +99,14 @@
};
 };
 
+ {
+   clock-frequency = <40>;
+};
+
+ {
+   clock-frequency = <40>;
+};
+
 /*
  * Only found on the wireless SOM. For the SOM without wireless, the pins for
  * MMC3 can be routed with jumpers to the second MMC slot on the devkit and
-- 
1.9.1

--
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] ARM: dts: Enable Shared Transport and Bluetooth on LogicPD Torpedo + Wireless module

[Adam Ford]

Configure the shared transport which enables communication with GPS/Bluetooth 
module.
Setup UART2 for communication at 3MBps with flow control.
Setup GPIO_162 as Bluetooth Enable.

Signed-off-by: Adam Ford <adam.f...@logicpd.com>
---
 arch/arm/boot/dts/logicpd-torpedo-som.dtsi | 27 +++
 1 file changed, 27 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi 
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index c8091ff..0ce3bc0 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -32,6 +32,18 @@
enable-active-high;
vin-supply = <>;
};
+
+   kim {
+   compatible = "kim";
+   nshutdown_gpio = <162>; /* Bank3, pin21 */
+   dev_name = "/dev/ttyO1";
+   flow_cntrl = <1>;
+   baud_rate = <30>;
+   };
+
+   btwilink {
+   compatible = "btwilink";
+   };
 };
 
  {
@@ -157,6 +169,21 @@
OMAP3_CORE1_IOPAD(0x2142, PIN_OUTPUT | MUX_MODE0)   
/* mcbsp2_dx */
>;
};
+   uart2_pins: pinmux_uart2_pins {
+   pinctrl-single,pins = <
+   OMAP3_CORE1_IOPAD(0x2174, PIN_INPUT | MUX_MODE0)
/* uart2_cts.uart2_cts */
+   OMAP3_CORE1_IOPAD(0x2176, PIN_OUTPUT | MUX_MODE0)   
/* uart2_rts .uart2_rts*/
+   OMAP3_CORE1_IOPAD(0x2178, PIN_OUTPUT | MUX_MODE0)   
/* uart2_tx.uart2_tx */
+   OMAP3_CORE1_IOPAD(0x217a, PIN_INPUT | MUX_MODE0)
/* uart2_rx.uart2_rx */
+   OMAP3_CORE1_IOPAD(0x2198, PIN_OUTPUT | MUX_MODE4)   
/* GPIO_162,BT_EN */
+   >;
+   };
+};
+
+ {
+   interrupts-extended = < 73 _pmx_core OMAP3_UART2_RX>;
+   pinctrl-names = "default";
+   pinctrl-0 = <_pins>;
 };
 
 _pmx_core2 {
-- 
1.9.1

--
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] ARM: dts: Set VAUX1 and VAUX4 on Logic PD Torpedo

[Adam Ford]

The schematic expects VAUX1 to be 3.0V attached to the debug port.
The schematic expects VAUX4 to be 1.8V.
VAUX4 powers VDDS_CSI2 on processor.

Signed-off-by: Adam Ford <adam.f...@logicpd.com>
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index afc13e5..b07d1d9 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -73,6 +73,16 @@
};
 };
 
+ {
+   regulator-min-microvolt = <300>;
+   regulator-max-microvolt = <300>;
+};
+
+ {
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <180>;
+};
+
  {
status = "okay";
 };
-- 
1.9.1

--
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

ARM OMAP Shared Transport Driver Regression in 4.3

[Adam Ford]

After compiling the shared transport driver as a module, it works just
fine as-is in the 4.2.x kernels when enabled with modprobe.

However when compiled as module and enabled with modprobe with the
4.3-rc7, it generates a segmentation fault and the dependent drivers
(like BTWILINK) don't function.

This was done an Logic PD Torpedo Torpedo + Wireless which utilizes a
DM3730 processor.

# modprobe st_drv
\[   16.543182] Unable to handle kernel NULL pointer dereference at
virtual address 
[   16.551757] pgd = cb0a8000
[   16.554718] [] *pgd=8f70e831, *pte=, *ppte=
[   16.561370] Internal error: Oops: 17 [#1] SMP ARM
[   16.566345] Modules linked in: st_drv(+) arc4 wl12xx wlcore
mac80211 cfg80211 wlcore_sdio
[   16.575073] CPU: 0 PID: 137 Comm: modprobe Not tainted 4.3.0-rc7-dirty #2
[   16.582214] Hardware name: Generic OMAP36xx (Flattened Device Tree)
[   16.588836] task: cb06b180 ti: cb0a6000 task.ti: cb0a6000
[   16.594543] PC is at kim_probe+0x78/0x220 [st_drv]
[   16.599609] LR is at st_core_init+0x90/0x154 [st_drv]
[   16.604949] pc : []lr : []psr: 600d0013
[   16.604949] sp : cb0a7d68  ip : 0001  fp : bf1bf008
[   16.617065] r10: 308b3ea8  r9 : 0001  r8 : 
[   16.622558] r7 : fdfb  r6 : bf1beef0  r5 : cf1ea000  r4 : cb2b7f00
[   16.629455] r3 : cb2b7e00  r2 : dead4ead  r1 : bf1be65c  r0 : 
[   16.636322] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[   16.643859] Control: 10c5387d  Table: 8b0a8019  DAC: 0051
[   16.649902] Process modprobe (pid: 137, stack limit = 0xcb0a6218)
[   16.656341] Stack: (0xcb0a7d68 to 0xcb0a8000)
[   16.660949] 7d60:   cf1ea010 bf1beef0 cf1ea010
cf1ea010 bf1beef0 fdfb
[   16.669586] 7d80: 0005 c03dd7ec c03dd7a8 cf1ea010 c11c2058
bf1beef0  c03dbdac
[   16.678222] 7da0: cf1ea010 bf1beef0 cf1ea044 c0991f60 
c03dbf3c  bf1beef0
[   16.686828] 7dc0: c03dbea8 c03da224 cf0caaa4 cf1ece10 bf1beef0
cb2aeec0  c03db4d8
[   16.695465] 7de0: bf1be65c bf1beef0 c09163a0 bf1beef0 c09163a0
cf74c040 bf1c2000 c03dc890
[   16.704101] 7e00:  c09163a0 c09163a0 c0009804 cfd42ea4
c011fb68 cb0a6000 c09c3cb4
[   16.712738] 7e20: 000f cfbb1000 cfd42ea4  005b
c0091058 cccee540 00d0
[   16.721374] 7e40: 00d0 c01607a0 cb0a7f40 c0091058 c0911f9c
600d0013 a00d0013 bf1befc0
[   16.730010] 7e60: bf1befc0 c09c74e8 cccee540 0001 cf74c180
308b3ea8 bf1bf008 c0119304
[   16.738616] 7e80: c09c74e8 bf1befc0 cb0a7f40 c09c74e8 bf1befc0
c00cb1e0 bf1befcc 7fff
[   16.747253] 7ea0:  c00c8c08 cccee540 c119ffe4 c00c8428
bf1befcc bf1bf1dc d1ddd718
[   16.755889] 7ec0: bf1befcc  0010 cf6c6000 
c01560b0 ff00 
[   16.764526] 7ee0:  bf1bde78 0002  
  
[   16.773162] 7f00:     
 c00cb9ac 
[   16.781799] 7f20: a41b b6e06423  000b1750 d1df341b
cb0a6000 0051 c00cba1c
[   16.790435] 7f40: d1d99000 0005a41b d1ddcf48 d1ddcd41 d1df2b48
322c 3c7c 
[   16.799041] 7f60:   0032 0033 001a
001e 0016 
[   16.807678] 7f80:  0005a41b 000b1750 000b1710 0080
c000f8c4 cb0a6000 
[   16.816314] 7fa0:  c000f720 0005a41b 000b1750 b6dac008
0005a41b 000b1750 000b1a28
[   16.824951] 7fc0: 0005a41b 000b1750 000b1710 0080 000b1a28
 000b1710 
[   16.833587] 7fe0: bea7db38 bea7db28 0001be18 b6ed22d0 600d0010
b6dac008 8fdf6861 8fdf6c61
[   16.842254] [] (kim_probe [st_drv]) from []
(platform_drv_probe+0x44/0xa4)
[   16.851348] [] (platform_drv_probe) from []
(driver_probe_device+0x1f4/0x2f0)
[   16.860717] [] (driver_probe_device) from []
(__driver_attach+0x94/0x98)
[   16.869628] [] (__driver_attach) from []
(bus_for_each_dev+0x6c/0xa0)
[   16.878265] [] (bus_for_each_dev) from []
(bus_add_driver+0x18c/0x214)
[   16.886993] [] (bus_add_driver) from []
(driver_register+0x78/0xf8)
[   16.895446] [] (driver_register) from []
(do_one_initcall+0x80/0x1dc)
[   16.904083] [] (do_one_initcall) from []
(do_init_module+0x5c/0x1d0)
[   16.912628] [] (do_init_module) from []
(load_module+0x1880/0x1fe0)
[   16.921081] [] (load_module) from []
(SyS_init_module+0xdc/0x14c)
[   16.929351] [] (SyS_init_module) from []
(ret_fast_syscall+0x0/0x1c)
[   16.937896] Code: 1a50 e5943094 e59f1170 e58340ec (e598)
[   16.944458] ---[ end trace dda7ebdfcb435ea8 ]---
Segmentation fault
#
--
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] ARM: dts: Change I2C2 and I2C3 to 400KHz for LogicPD Torpedo DM3730 devkit

[Adam Ford]

When used with the Logic PD development kit, this makes the I2C buses match
the BSP released by Logic PD.
---
 arch/arm/boot/dts/logicpd-torpedo-som.dtsi | 8 
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi 
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index 9777ff4..c8091ff 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -104,6 +104,14 @@
};
 };
 
+ {
+   clock-frequency = <40>;
+};
+
+ {
+   clock-frequency = <40>;
+};
+
 /*
  * Only found on the wireless SOM. For the SOM without wireless, the pins for
  * MMC3 can be routed with jumpers to the second MMC slot on the devkit and
-- 
1.9.1

--
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] ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V respectively

[Adam Ford]

The development kit schematic expects VAUX1 to be 3.0V.  Most users use the 
development kit as a reference.
The development kit schematic expects VAUX4 to be 1.8V.  VAUX4 powers VDDS_CSI2 
on processor.  If the voltage is too high it could damage the processor.
If it's too low, it won't work.
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index afc13e5..b07d1d9 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -73,6 +73,16 @@
};
 };
 
+ {
+   regulator-min-microvolt = <300>;
+   regulator-max-microvolt = <300>;
+};
+
+ {
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <180>;
+};
+
  {
status = "okay";
 };
-- 
1.9.1

--
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] ARM: dts: Add audio support for LogicPD Torpedo DM3730 devkit

[Adam Ford]

Use the TWL4030 Codec with mcbsp2 on Torpedo.

Signed-off-by: Adam Ford <adam.f...@logicpd.com>
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 10 ++
 arch/arm/boot/dts/logicpd-torpedo-som.dtsi| 13 +
 2 files changed, 23 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index 5b04300..afc13e5 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -48,6 +48,12 @@
};
};
 
+   sound {
+   compatible = "ti,omap-twl4030";
+   ti,model = "omap3logic";
+   ti,mcbsp = <>;
+   };
+
leds {
compatible = "gpio-leds";
pinctrl-names = "default";
@@ -67,6 +73,10 @@
};
 };
 
+ {
+   status = "okay";
+};
+
  {
ti,bb-uvolt = <320>;
ti,bb-uamp = <150>;
diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi 
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index 36387b1..9777ff4 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -96,6 +96,11 @@
reg = <0x48>;
interrupts = <7>; /* SYS_NIRQ cascaded to intc */
interrupt-parent = <>;
+   twl_audio: audio {
+   compatible = "ti,twl4030-audio";
+   codec {
+   };
+   };
};
 };
 
@@ -136,6 +141,14 @@
OMAP3_CORE1_IOPAD(0x218e, PIN_OUTPUT | MUX_MODE4)   
/* mcbsp1_fsr.gpio_157 */
>;
};
+   mcbsp2_pins: pinmux_mcbsp2_pins {
+   pinctrl-single,pins = <
+   OMAP3_CORE1_IOPAD(0x213c, PIN_INPUT | MUX_MODE0)
/* mcbsp2_fsx */
+   OMAP3_CORE1_IOPAD(0x213e, PIN_INPUT | MUX_MODE0)
/* mcbsp2_clkx */
+   OMAP3_CORE1_IOPAD(0x2140, PIN_INPUT | MUX_MODE0)
/* mcbsp2_dr */
+   OMAP3_CORE1_IOPAD(0x2142, PIN_OUTPUT | MUX_MODE0)   
/* mcbsp2_dx */
+   >;
+   };
 };
 
 _pmx_core2 {
-- 
1.9.1

--
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] ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V respectively for LogicPD Torpedo DM3730 devkit

[Adam Ford]

Signed-off-by: Adam Ford <adam.f...@logicpd.com>
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index 892ff1d..2ac1488 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -73,6 +73,16 @@
};
 };
 
+ {
+   regulator-min-microvolt = <300>;
+   regulator-max-microvolt = <300>;
+};
+
+ {
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <180>;
+};
+
  {
status = "okay";
 };
-- 
1.9.1

--
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] ARM: dts: Change I2C2 and I2C3 to 400KHz for LogicPD Torpedo DM3730 devkit

[Adam Ford]

Signed-off-by: Adam Ford <adam.f...@logicpd.com>
---
 arch/arm/boot/dts/logicpd-torpedo-som.dtsi | 8 
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi 
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index 9777ff4..c8091ff 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -104,6 +104,14 @@
};
 };
 
+ {
+   clock-frequency = <40>;
+};
+
+ {
+   clock-frequency = <40>;
+};
+
 /*
  * Only found on the wireless SOM. For the SOM without wireless, the pins for
  * MMC3 can be routed with jumpers to the second MMC slot on the devkit and
-- 
1.9.1

--
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] ARM: dts: Add audio support for LogicPD Torpedo DM3730 devkit

[Adam Ford]

Signed-off-by: Adam Ford <adam.f...@logicpd.com>
---
 arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 10 ++
 arch/arm/boot/dts/logicpd-torpedo-som.dtsi| 13 +
 2 files changed, 23 insertions(+)

diff --git a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 
b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
index 91146c3..892ff1d 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
+++ b/arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts
@@ -48,6 +48,12 @@
};
};
 
+   sound {
+   compatible = "ti,omap-twl4030";
+   ti,model = "omap3logic";
+   ti,mcbsp = <>;
+   };
+
leds {
compatible = "gpio-leds";
pinctrl-names = "default";
@@ -67,6 +73,10 @@
};
 };
 
+ {
+   status = "okay";
+};
+
  {
ti,bb-uvolt = <320>;
ti,bb-uamp = <150>;
diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi 
b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
index 36387b1..9777ff4 100644
--- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
+++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi
@@ -96,6 +96,11 @@
reg = <0x48>;
interrupts = <7>; /* SYS_NIRQ cascaded to intc */
interrupt-parent = <>;
+   twl_audio: audio {
+   compatible = "ti,twl4030-audio";
+   codec {
+   };
+   };
};
 };
 
@@ -136,6 +141,14 @@
OMAP3_CORE1_IOPAD(0x218e, PIN_OUTPUT | MUX_MODE4)   
/* mcbsp1_fsr.gpio_157 */
>;
};
+   mcbsp2_pins: pinmux_mcbsp2_pins {
+   pinctrl-single,pins = <
+   OMAP3_CORE1_IOPAD(0x213c, PIN_INPUT | MUX_MODE0)
/* mcbsp2_fsx */
+   OMAP3_CORE1_IOPAD(0x213e, PIN_INPUT | MUX_MODE0)
/* mcbsp2_clkx */
+   OMAP3_CORE1_IOPAD(0x2140, PIN_INPUT | MUX_MODE0)
/* mcbsp2_dr */
+   OMAP3_CORE1_IOPAD(0x2142, PIN_OUTPUT | MUX_MODE0)   
/* mcbsp2_dx */
+   >;
+   };
 };
 
 _pmx_core2 {
-- 
1.9.1

--
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