Re: [PATCH 6/6] tty: serial: Add 8250-core based omap driver
On Thu, Jul 10, 2014 at 11:03 AM, Carlos Hernandez c...@ti.com wrote: 1) Append no_console_suspend to bootargs Not needed. ideally with pinctrl wakeup capability, this should work. if you do no_console_suspend, the module is not powered down. -- 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 baseline test results for v3.14
On Wed, Apr 2, 2014 at 11:35 AM, Tony Lindgren t...@atomide.com wrote: * Paul Walmsley p...@pwsan.com [140402 09:36]: On Wed, 2 Apr 2014, Tony Lindgren wrote: * Paul Walmsley p...@pwsan.com [140402 09:07]: Here are some basic OMAP test results for Linux v3.14. Logs and other details at: http://www.pwsan.com/omap/testlogs/test_v3.14/20140402004448/ Boot to userspace: FAIL ( 1/12): 2430sdp Is this a new regression with MMC? Looks like your boot log for this ends with Waiting for root device /dev/mmcblk0p1 It's new since v3.14-rc1: http://www.spinics.net/lists/arm-kernel/msg306448.html http://www.spinics.net/lists/arm-kernel/msg306454.html http://www.spinics.net/lists/arm-kernel/msg306455.html OK looks like I never noticed that one before. Probably because of NFSroot. Paul uses MMC filesystem, I use NFS. As Felipe Pointed out as well, I did rootcause MMC filesystem mount issue here: http://marc.info/?l=linux-omapm=139637044425644w=2 NFS does work for me on 3.14 tag http://slexy.org/raw/s20plaLoaT (on SDP2430) 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
Re: need help to configure IRQ on gpio 139 pandaboard using device tree
On Wed, Dec 11, 2013 at 8:28 AM, Denis CIOCCA denis.cio...@st.com wrote: Hi everybody, I'm trying to configure an IRQ on pandaboard using device tree but I'm not able to understand how I can do it. I want to configure the the gpio_139 pin and without device tree my command was: OMAP4_MUX(MCSPI1_SIMO, OMAP_MUX_MODE3 | OMAP_PIN_INPUT_PULLUP), I need to associate it to a i2c device, declared in this way: here is how you'd figure it out in dt world ;) - it might be a little simpler or harder depending on which end of the development world one is from... (gmail might be screwing up my formatting a little.. so apologies before hand. http://pastebin.mozilla.org/3755622 is a copy if you need one.. anyways, step 1: from trm, you get to know that the pin is part of core SYSCTRL_PADCONF_CORE as it states for register instance in the trm. step 2: you compute the offset step 3: you define the pinctrl dt node step 4: you'd provide the device using it reference - rather trivial ;) diff --git a/arch/arm/boot/dts/omap4-panda-es.dts b/arch/arm/boot/dts/omap4-panda-es.dts index 56c4354..8f8d36c 100644 --- a/arch/arm/boot/dts/omap4-panda-es.dts +++ b/arch/arm/boot/dts/omap4-panda-es.dts @@ -41,6 +41,25 @@ 0xb6 (PIN_OUTPUT | MUX_MODE3) /* gpio_110 */ ; }; + + lsm303d_pins: lsm303d_pins { + pinctrl-single,pins = + /* + * Example for 4460 device: + * from arch/arm/boot/dts/omap4.dtsi: + * omap4_pmx_core: reg = 0x4a100040 + * the base address -- ^^ + * + * Now, the offset is computed as following: + * Download TRM: http://www.ti.com/lit/ug/swpu235aa/swpu235aa.pdf + * Searching in TRM for MCSPI1_SIMO (page 4145), you see: + * 32 bit register 0x4a100134, it is on the higher 16 bits + * 0x4a100134(SOMI) + 2 (SIMO) = 0x4a100136 + * offset hence is = 0x4a100136 - 0x4a100040 = 0xF6 + */ + 0xF6 (PIN_INPUT_PULLUP | MUX_MODE3) /* mcspi1_somi.gpio_139 */ + ; + }; }; led_wkgpio_pins { @@ -62,3 +81,16 @@ gpios = gpio1 8 GPIO_ACTIVE_HIGH; }; }; +i2c4 { + pinctrl-names = default; + pinctrl-0 = i2c4_pins; + + clock-frequency = 40; + + lsm303d@03 { + pinctrl-names = default; + pinctrl-0 = lsm303d_pins; + compatible = st,lsm303d; + reg = 0x03; + }; +}; -- 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 1/3] ARM: OMAP2+: Add support to parse 'main_clk' info from DT
Hi Rajendra, On Tue, Jul 23, 2013 at 1:24 AM, Rajendra Nayak rna...@ti.com wrote: [...] diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c index 5cc5123..12fa589 100644 --- a/arch/arm/mach-omap2/omap_hwmod.c +++ b/arch/arm/mach-omap2/omap_hwmod.c @@ -2381,12 +2386,10 @@ static void __init _init_mpu_rt_base(struct omap_hwmod *oh, void *data) oh-name); /* Extract the IO space from device tree blob */ - if (!of_have_populated_dt()) + if (!np) return; - np = of_dev_hwmod_lookup(of_find_node_by_name(NULL, ocp), oh); - if (np) - va_start = of_iomap(np, 0); + va_start = of_iomap(np, 0); This hunk needs a rebase with 3.11-rc5 due to commit 130142d91467e8a07f3a863db369225a89e84d75 (ARM: OMAP2+: hwmod: rt address space index for DT) } else { va_start = ioremap(mem-pa_start, mem-pa_end - mem-pa_start); } [...] -- 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