From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config
Date: Sun, 29 Jan 2017 10:05:56 +0800 [thread overview]
Message-ID: <20170129020554.GG5662@dragon> (raw)
In-Reply-To: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com>
On Wed, Jan 25, 2017 at 06:25:48AM +0100, linux-kernel-dev at beckhoff.com wrote:
> From: Patrick Bruenn <p.bruenn@beckhoff.com>
>
> The pinmux configuration in device tree was different from manual
> muxing in <u-boot>/board/freescale/mx53loco/mx53loco.c
> All pins were configured as NO_PAD_CTL(1 << 31), which was fine as the
> bootloader already did the correct pinmuxing for us.
> But recently u-boot is migrating to reuse device tree files from the
> kernel tree, so it seems to be better to have the correct pinmuxing in
> our files, too.
>
> Signed-off-by: Patrick Bruenn <p.bruenn@beckhoff.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: linux-kernel-dev@beckhoff.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Patrick Bruenn <p.bruenn@beckhoff.com>,
trini@konsulko.com, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org, robh+dt@kernel.org, sbabic@denx.de,
kernel@pengutronix.de, fabio.estevam@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config
Date: Sun, 29 Jan 2017 10:05:56 +0800 [thread overview]
Message-ID: <20170129020554.GG5662@dragon> (raw)
In-Reply-To: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com>
On Wed, Jan 25, 2017 at 06:25:48AM +0100, linux-kernel-dev@beckhoff.com wrote:
> From: Patrick Bruenn <p.bruenn@beckhoff.com>
>
> The pinmux configuration in device tree was different from manual
> muxing in <u-boot>/board/freescale/mx53loco/mx53loco.c
> All pins were configured as NO_PAD_CTL(1 << 31), which was fine as the
> bootloader already did the correct pinmuxing for us.
> But recently u-boot is migrating to reuse device tree files from the
> kernel tree, so it seems to be better to have the correct pinmuxing in
> our files, too.
>
> Signed-off-by: Patrick Bruenn <p.bruenn@beckhoff.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: linux-kernel-dev@beckhoff.com
Cc: kernel@pengutronix.de, fabio.estevam@nxp.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, trini@konsulko.com, sbabic@denx.de,
Patrick Bruenn <p.bruenn@beckhoff.com>
Subject: Re: [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config
Date: Sun, 29 Jan 2017 10:05:56 +0800 [thread overview]
Message-ID: <20170129020554.GG5662@dragon> (raw)
In-Reply-To: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com>
On Wed, Jan 25, 2017 at 06:25:48AM +0100, linux-kernel-dev@beckhoff.com wrote:
> From: Patrick Bruenn <p.bruenn@beckhoff.com>
>
> The pinmux configuration in device tree was different from manual
> muxing in <u-boot>/board/freescale/mx53loco/mx53loco.c
> All pins were configured as NO_PAD_CTL(1 << 31), which was fine as the
> bootloader already did the correct pinmuxing for us.
> But recently u-boot is migrating to reuse device tree files from the
> kernel tree, so it seems to be better to have the correct pinmuxing in
> our files, too.
>
> Signed-off-by: Patrick Bruenn <p.bruenn@beckhoff.com>
Applied, thanks.
next prev parent reply other threads:[~2017-01-29 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 5:25 [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config linux-kernel-dev at beckhoff.com
2017-01-25 5:25 ` linux-kernel-dev
2017-01-25 5:25 ` linux-kernel-dev-QonKdJ6Bx35Wk0Htik3J/w
2017-01-29 2:05 ` Shawn Guo [this message]
2017-01-29 2:05 ` Shawn Guo
2017-01-29 2:05 ` Shawn Guo
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=20170129020554.GG5662@dragon \
--to=shawnguo@kernel.org \
--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.