From: Benoit Cousson <bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Andrey Konovalov
<andrey.konovalov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: rnayak-l0cyMroinI0@public.gmane.org,
luca-XPOmlcxoEMv1KXRcyAk9cg@public.gmane.org,
p.pisati-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] ARM: dts: move wl12xx pins to the proper pinmux for pandaboard
Date: Wed, 23 Oct 2013 10:33:51 +0200 [thread overview]
Message-ID: <526789EF.7000507@baylibre.com> (raw)
In-Reply-To: <525852A4.6090500-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Hi Andrey,
On 11/10/2013 21:33, Andrey Konovalov wrote:
> Commit 851320e (ARM: dts: Fix muxing and regulator for wl12xx on the
> SDIO bus for pandaboard) put the wl12xx pins into omap4_pmx_wkup. This
> is not correct, and results in the following messages at the boot time:
>
> pinctrl-single 4a31e040.pinmux: mux offset out of range: 0x38 (0x38)
> pinctrl-single 4a31e040.pinmux: could not add functions for
> pinmux_wl12xx_pins 56x
>
> Actually these pins belong to omap4_pmx_core.
>
> Signed-off-by: Andrey Konovalov <andrey.konovalov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
That patch does not apply on any on my branches. Could you rebase it
on top of my for_3.13/dts branch.
Thanks,
Benoit
--
Benoît Cousson
BayLibre
Embedded Linux Technology Lab
www.baylibre.com
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-10-23 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 19:33 [PATCH] ARM: dts: move wl12xx pins to the proper pinmux for pandaboard Andrey Konovalov
[not found] ` <525852A4.6090500-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-10-12 2:48 ` Tony Lindgren
2013-10-23 8:33 ` Benoit Cousson [this message]
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=526789EF.7000507@baylibre.com \
--to=bcousson-rdvid1duhrbwk0htik3j/w@public.gmane.org \
--cc=andrey.konovalov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luca-XPOmlcxoEMv1KXRcyAk9cg@public.gmane.org \
--cc=p.pisati-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rnayak-l0cyMroinI0@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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).