From mboxrd@z Thu Jan 1 00:00:00 1970 From: shawnguo@kernel.org (Shawn Guo) Date: Sun, 29 Jan 2017 10:05:56 +0800 Subject: [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config In-Reply-To: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com> References: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com> Message-ID: <20170129020554.GG5662@dragon> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Jan 25, 2017 at 06:25:48AM +0100, linux-kernel-dev at beckhoff.com wrote: > From: Patrick Bruenn > > The pinmux configuration in device tree was different from manual > muxing in /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 Applied, thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shawn Guo Subject: Re: [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config Date: Sun, 29 Jan 2017 10:05:56 +0800 Message-ID: <20170129020554.GG5662@dragon> References: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: linux-kernel-dev@beckhoff.com Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, Patrick Bruenn , 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 List-Id: devicetree@vger.kernel.org On Wed, Jan 25, 2017 at 06:25:48AM +0100, linux-kernel-dev@beckhoff.com wrote: > From: Patrick Bruenn > > The pinmux configuration in device tree was different from manual > muxing in /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 Applied, thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753093AbdA2CJB (ORCPT ); Sat, 28 Jan 2017 21:09:01 -0500 Received: from mail.kernel.org ([198.145.29.136]:57778 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752812AbdA2CI4 (ORCPT ); Sat, 28 Jan 2017 21:08:56 -0500 Date: Sun, 29 Jan 2017 10:05:56 +0800 From: Shawn Guo 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 Subject: Re: [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config Message-ID: <20170129020554.GG5662@dragon> References: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170125052548.27402-1-linux-kernel-dev@beckhoff.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 25, 2017 at 06:25:48AM +0100, linux-kernel-dev@beckhoff.com wrote: > From: Patrick Bruenn > > The pinmux configuration in device tree was different from manual > muxing in /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 Applied, thanks.