On Thursday 21 November 2013 10:57 PM, Dan Murphy wrote:
On 11/21/2013 10:58 AM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [131121 05:51]:
pin mux wl12xx_gpio and wl12xx_pins should be part of omap4_pmx_core
and not omap4_pmx_wkup. So, move wl12xx_* to omap4_pmx_core.
Fix the
On Wednesday 27 November 2013 03:25 AM, Tony Lindgren wrote:
* Dan Murphy dmur...@ti.com [131121 09:28]:
On 11/21/2013 10:58 AM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [131121 05:51]:
pin mux wl12xx_gpio and wl12xx_pins should be part of omap4_pmx_core
and not omap4_pmx_wkup. So,
* Balaji T K balaj...@ti.com [131127 08:30]:
On Wednesday 27 November 2013 03:25 AM, Tony Lindgren wrote:
* Dan Murphy dmur...@ti.com [131121 09:28]:
On 11/21/2013 10:58 AM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [131121 05:51]:
pin mux wl12xx_gpio and wl12xx_pins should be part of
* Tony Lindgren t...@atomide.com [131127 08:49]:
* Balaji T K balaj...@ti.com [131127 08:30]:
On Wednesday 27 November 2013 03:25 AM, Tony Lindgren wrote:
* Dan Murphy dmur...@ti.com [131121 09:28]:
On 11/21/2013 10:58 AM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [131121 05:51]:
* Dan Murphy dmur...@ti.com [131121 09:28]:
On 11/21/2013 10:58 AM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [131121 05:51]:
pin mux wl12xx_gpio and wl12xx_pins should be part of omap4_pmx_core
and not omap4_pmx_wkup. So, move wl12xx_* to omap4_pmx_core.
Fix the following error
Balaji T K (2):
ARM: dts: omap4-panda-common: Fix pin muxing for wl12xx
ARM: dts: omap4-sdp: Fix pin muxing for wl12xx
arch/arm/boot/dts/omap4-panda-common.dtsi | 20 ++--
arch/arm/boot/dts/omap4-sdp.dts | 12 ++--
2 files changed, 16 insertions(+), 16
* Balaji T K balaj...@ti.com [131121 05:51]:
pin mux wl12xx_gpio and wl12xx_pins should be part of omap4_pmx_core
and not omap4_pmx_wkup. So, move wl12xx_* to omap4_pmx_core.
Fix the following error message:
pinctrl-single 4a31e040.pinmux: mux offset out of range: 0x38 (0x38)
pinctrl-single
pin mux wl12xx_gpio and wl12xx_pins should be part of omap4_pmx_core
and not omap4_pmx_wkup. So, move wl12xx_* to omap4_pmx_core.
Fix the following error message:
pinctrl-single 4a31e040.pinmux: mux offset out of range: 0x38 (0x38)
pinctrl-single 4a31e040.pinmux: could not add functions for
Mux mode for wlan/sdmmc5 should be MODE0 in pinmux_wl12xx_pins and
Enable Pull up on sdmmc5_clk to detect SDIO card.
Signed-off-by: Balaji T K balaj...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git
On 11/21/2013 10:58 AM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [131121 05:51]:
pin mux wl12xx_gpio and wl12xx_pins should be part of omap4_pmx_core
and not omap4_pmx_wkup. So, move wl12xx_* to omap4_pmx_core.
Fix the following error message:
pinctrl-single 4a31e040.pinmux: mux
Hello,
I need to add a couple of mux entries and am refer to
arch/arm/mach-omap2/mux.c file.
I would like to what is the differences between BALLNUM_34XX_ and
BALLNUM_3430_ entries. I could not find any mux entries specific to
BALLNUM_35XX_.
How does one decide if a pin needs to be pulled up
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Branch in linux-omap: for-next-vol2
Initial commit ID (Likely to change): dd1a4ddb989eded52aac34a85cea2f2b122fbc84
PatchWorks
http://patchwork.kernel.org/patch/62078/
Git (Likely to change, and takes a while to get
This adds the initialization for the pin muxing required
for USB to function properly on omap7xx hardware.
Signed-off-by: Cory Maccarrone darkstar6...@gmail.com
---
arch/arm/plat-omap/usb.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/arch/arm/plat-omap/usb.c b
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [091021 10:11]:
Wednesday 21 October 2009 02:51:35 Tony Lindgren napisał(a):
Let's just remove the omap_cfg_reg() calls from mach-omap1/serial.c, and
add them to the board-*.c files like you suggest above. We should be able
to find which ports to
From: Janusz Krzysztofik jkrzy...@tis.icnet.pl
Commit 15ac408ee5a509053a765b816e9179515329369f removed enabled_uart
and OMAP_TAG_UART. This works for mach-omap2, but causes issues on
mach-omap1 for some boards as the mach-omap1 serial.c was muxing
pins based on the enabled_uart flag for 15xx.
Wednesday 21 October 2009 02:51:35 Tony Lindgren napisał(a):
Let's just remove the omap_cfg_reg() calls from mach-omap1/serial.c, and
add them to the board-*.c files like you suggest above. We should be able
to find which ports to mux by looking at the enabled_uarts mask in the
commit
Some drivers have a requirement not to do the default pin
muxing for MMC
Those drivers can pass on nomux=1 from twl4030_hsmmc_info
and perform the pin muxing in their board file before call
to funciton twl4030_mmc_init()
Signded-off-by: Vikram Pandita vikram.pand...@ti.com
---
arch/arm/mach
Signed-off-by: Jarkko Nikula [EMAIL PROTECTED]
---
arch/arm/plat-omap/i2c.c | 51 -
1 files changed, 32 insertions(+), 19 deletions(-)
diff --git a/arch/arm/plat-omap/i2c.c b/arch/arm/plat-omap/i2c.c
index 7990ab1..23c2920 100644
---
On Mon, 9 Jun 2008 17:46:41 +0300
Jarkko Nikula [EMAIL PROTECTED] wrote:
Signed-off-by: Jarkko Nikula [EMAIL PROTECTED]
---
arch/arm/plat-omap/i2c.c | 51 +++
+- 1 files changed, 32 insertions(+), 19 deletions(-)
-static void __init
19 matches
Mail list logo
