mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: i.MX6: fix usdhc3 pinmuxing on tqma6x
Date: Tue, 27 Jun 2017 08:34:14 +0200	[thread overview]
Message-ID: <20170627063414.p67v4r5mlfphu7rl@pengutronix.de> (raw)
In-Reply-To: <1498230590-7661-1-git-send-email-m.tretter@pengutronix.de>

On Fri, Jun 23, 2017 at 05:09:50PM +0200, Michael Tretter wrote:
> The usdhc3 pin group wrongly referred the SD4 pads instead of the SD3 pads.
> This leads to issues when muxing the SD4_CMD and SD4_CLK pads for uart3.
> 
> This regression was introduced by code refactoring in commit a5207a6 ("ARM:
> dts: i.MX6: drop usage of pin group defines").
> 
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> ---
>  arch/arm/dts/imx6qdl-tqma6x.dtsi | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)

Applied, thanks

Sascha

> 
> diff --git a/arch/arm/dts/imx6qdl-tqma6x.dtsi b/arch/arm/dts/imx6qdl-tqma6x.dtsi
> index f0b1a0db7..82f9ec368 100644
> --- a/arch/arm/dts/imx6qdl-tqma6x.dtsi
> +++ b/arch/arm/dts/imx6qdl-tqma6x.dtsi
> @@ -76,12 +76,12 @@
>  
>  		pinctrl_usdhc3: usdhc3grp {
>  			fsl,pins = <
> -				MX6QDL_PAD_SD4_CMD__SD4_CMD		0x17059
> -				MX6QDL_PAD_SD4_CLK__SD4_CLK		0x10059
> -				MX6QDL_PAD_SD4_DAT0__SD4_DATA0		0x17059
> -				MX6QDL_PAD_SD4_DAT1__SD4_DATA1		0x17059
> -				MX6QDL_PAD_SD4_DAT2__SD4_DATA2		0x17059
> -				MX6QDL_PAD_SD4_DAT3__SD4_DATA3		0x17059
> +				MX6QDL_PAD_SD3_CMD__SD3_CMD		0x17059
> +				MX6QDL_PAD_SD3_CLK__SD3_CLK		0x10059
> +				MX6QDL_PAD_SD3_DAT0__SD3_DATA0		0x17059
> +				MX6QDL_PAD_SD3_DAT1__SD3_DATA1		0x17059
> +				MX6QDL_PAD_SD3_DAT2__SD3_DATA2		0x17059
> +				MX6QDL_PAD_SD3_DAT3__SD3_DATA3		0x17059
>  				MX6QDL_PAD_SD3_DAT4__SD3_DATA4		0x17059
>  				MX6QDL_PAD_SD3_DAT5__SD3_DATA5		0x17059
>  				MX6QDL_PAD_SD3_DAT6__SD3_DATA6		0x17059
> -- 
> 2.11.0
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2017-06-27  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 15:09 Michael Tretter
2017-06-27  6:34 ` Sascha Hauer [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=20170627063414.p67v4r5mlfphu7rl@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=m.tretter@pengutronix.de \
    /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