[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3BB206AB2B1BD448954845CE6FF69A8E01CB52FB01@NT-Mail07.beckhoff.com>
Date: Thu, 16 Nov 2017 04:09:37 +0000
From: Patrick BrĂ¼nn <P.Bruenn@...khoff.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "stable@...r.kernel.org" <stable@...r.kernel.org>,
Shawn Guo <shawnguo@...nel.org>,
Sasha Levin <alexander.levin@...izon.com>
Subject: RE: [PATCH 4.9 06/87] ARM: dts: imx53-qsb-common: fix FEC pinmux
config
>From: Greg Kroah-Hartman [mailto:gregkh@...uxfoundation.org]
>Sent: Montag, 13. November 2017 13:55
>
>4.9-stable review patch. If anyone has any objections, please let me know.
>
>------------------
>
>From: Patrick Bruenn <p.bruenn@...khoff.com>
>
>
>[ Upstream commit 8b649e426336d7d4800ff9c82858328f4215ba01 ]
>
>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.
>
As discussed for 4.4 stable queue this patch might break existing machines, if they use a different pinmux configuration with their own bootloader.
Please drop it from 4.9, too.
Regards,
Patrick
Beckhoff Automation GmbH & Co. KG | Managing Director: Dipl. Phys. Hans Beckhoff
Registered office: Verl, Germany | Register court: Guetersloh HRA 7075
Powered by blists - more mailing lists