From: balajitk@ti•com (Balaji T K)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: dts: omap4-panda-common: Fix pin muxing for wl12xx
Date: Wed, 27 Nov 2013 21:34:31 +0530 [thread overview]
Message-ID: <5296180F.7040104@ti.com> (raw)
In-Reply-To: <528E4295.2040109@ti.com>
On Thursday 21 November 2013 10:57 PM, Dan Murphy wrote:
> On 11/21/2013 10:58 AM, Tony Lindgren wrote:
>> * Balaji T K <balajitk@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 4a31e040.pinmux: could not add functions for pinmux_wl12xx_pins 56x
>
> Why is the led pins moved then?
Hi Dan,
I just moved 27 lines (wl12xx_pins, wl12xx_gpio) up, git diff generated smaller
diff stat by moving 10 line of code (led_wkgpio_pins) further down :-)
>
>>> SDIO card is not detected after moving pin mux to omap4_pmx_core since
>>> sdmmc5_clk pull is disabled. Enable Pull up on sdmmc5_clk to detect SDIO card.
>> Cool, does this fix the issue with the WLAN not coming up after a warm reset
>> on panda?
>>
>> Regards,
>>
>> Tony
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo at vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2013-11-27 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 13:50 [PATCH 0/2] ARM: dts: omap4: Fix pin muxing for wl12xx Balaji T K
2013-11-21 13:50 ` [PATCH 1/2] ARM: dts: omap4-panda-common: " Balaji T K
2013-11-21 16:58 ` Tony Lindgren
2013-11-21 17:27 ` Dan Murphy
2013-11-26 21:55 ` Tony Lindgren
2013-11-27 16:29 ` Balaji T K
2013-11-27 16:48 ` Tony Lindgren
2013-11-27 23:47 ` Tony Lindgren
2013-11-27 16:04 ` Balaji T K [this message]
2013-11-21 13:50 ` [PATCH 2/2] ARM: dts: omap4-sdp: " Balaji T K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5296180F.7040104@ti.com \
--to=balajitk@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox