All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Balaji T K <balajitk@ti.com>
Cc: bcousson@baylibre.com, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: omap4-panda-common: Fix pin muxing for wl12xx
Date: Thu, 21 Nov 2013 08:58:23 -0800	[thread overview]
Message-ID: <20131121165823.GM10317@atomide.com> (raw)
In-Reply-To: <1385041804-19115-2-git-send-email-balajitk@ti.com>

* 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
> 
> 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

WARNING: multiple messages have this Message-ID (diff)
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: Thu, 21 Nov 2013 08:58:23 -0800	[thread overview]
Message-ID: <20131121165823.GM10317@atomide.com> (raw)
In-Reply-To: <1385041804-19115-2-git-send-email-balajitk@ti.com>

* 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
> 
> 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

  reply	other threads:[~2013-11-21 16:58 UTC|newest]

Thread overview: 20+ 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 ` Balaji T K
2013-11-21 13:50 ` [PATCH 1/2] ARM: dts: omap4-panda-common: " Balaji T K
2013-11-21 13:50   ` Balaji T K
2013-11-21 16:58   ` Tony Lindgren [this message]
2013-11-21 16:58     ` Tony Lindgren
2013-11-21 17:27     ` Dan Murphy
2013-11-21 17:27       ` Dan Murphy
2013-11-26 21:55       ` Tony Lindgren
2013-11-26 21:55         ` Tony Lindgren
2013-11-27 16:29         ` Balaji T K
2013-11-27 16:29           ` Balaji T K
2013-11-27 16:48           ` Tony Lindgren
2013-11-27 16:48             ` Tony Lindgren
2013-11-27 23:47             ` Tony Lindgren
2013-11-27 23:47               ` Tony Lindgren
2013-11-27 16:04       ` Balaji T K
2013-11-27 16:04         ` Balaji T K
2013-11-21 13:50 ` [PATCH 2/2] ARM: dts: omap4-sdp: " Balaji T K
2013-11-21 13:50   ` 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=20131121165823.GM10317@atomide.com \
    --to=tony@atomide.com \
    --cc=balajitk@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.