From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: omap4-panda-common: Fix pin muxing for wl12xx
Date: Tue, 26 Nov 2013 13:55:37 -0800 [thread overview]
Message-ID: <20131126215537.GO26766@atomide.com> (raw)
In-Reply-To: <528E4295.2040109@ti.com>
* Dan Murphy <dmurphy@ti.com> [131121 09:28]:
> 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?
Heh the patch just looks that way, looking at the curly brackets
thing do get moved properly.
> >> 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?
Also commit f446043f1aa7 (regulator: fixed: fix regulator_list_voltage() for
regression) is needed that recently got merged. But with v3.13-rc1 +
f446043f1aa7 + this patch no luck whatsoever bringing up the wl12xx so there
must be also some regression somewhere from v3.12 on that?
Regards,
Tony
next prev parent reply other threads:[~2013-11-26 21:55 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 [this message]
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
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=20131126215537.GO26766@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).