From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: imx5: fix SD2_DATA1 pad AUDMUX_AUD4 configuration
Date: Wed, 3 Apr 2013 02:21:18 +0200 [thread overview]
Message-ID: <201304030221.18506.marex@denx.de> (raw)
In-Reply-To: <20130402114323.GE24039@S2101-09.ap.freescale.net>
Dear Shawn Guo,
> Marek,
>
> On Tue, Apr 02, 2013 at 08:04:02AM +0200, Marek Vasut wrote:
> > The IOMUXC_AUDMUX_P4_INPUT_TXCLK_AMX_SELECT_INPUT must be configured as 1
> > instead of 0 to have AUD4 muxed on SD2 pins working.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Linus Walleij <linus.walleij@linaro.org>
> > Cc: Philipp Zabel <p.zabel@pengutronix.de>
> > Cc: Shawn Guo <shawn.guo@linaro.org>
> > ---
> >
> > drivers/pinctrl/pinctrl-imx53.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > NOTE: Shawn, we might want this in -stable too ?
>
> I have queued patch b466af3 (pinctrl: imx: move hard-coding data into
> device tree) on my imx/dt branch to remove these tables from pinctrl
> drivers.
>
> Since there is no in-tree users for MX53_PAD_SD2_DATA1__AUDMUX_AUD4_TXFS,
> and we're moving away from it, can we just patch
> arch/arm/boot/dts/imx53-pinfunc.h instead?
>
> Shawn
One serving of such patch, coming right up ;-)
btw. do you want to apply this one for -stable or do we just leave it as is ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-04-03 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 6:04 [PATCH] pinctrl: imx5: fix SD2_DATA1 pad AUDMUX_AUD4 configuration Marek Vasut
2013-04-02 11:43 ` Shawn Guo
2013-04-03 0:21 ` Marek Vasut [this message]
2013-04-03 5:24 ` Shawn Guo
2013-04-03 6:52 ` Marek Vasut
2013-04-03 8:38 ` Shawn Guo
2013-04-03 16:58 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2013-04-03 0:20 Marek Vasut
2013-04-03 5:27 ` Shawn Guo
2013-04-03 6:34 ` Marek Vasut
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=201304030221.18506.marex@denx.de \
--to=marex@denx.de \
--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 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.