[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200212120753.GF4028@sirena.org.uk>
Date: Wed, 12 Feb 2020 12:07:53 +0000
From: Mark Brown <broonie@...nel.org>
To: Adam Ford <aford173@...il.com>
Cc: Fabio Estevam <festevam@...il.com>,
linux-spi <linux-spi@...r.kernel.org>, Han Xu <han.xu@....com>,
Yogesh Gaur <yogeshgaur.83@...il.com>,
Ashish Kumar <ashish.kumar@....com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH V2 2/5] spi: fspi: dynamically alloc AHB memory
On Mon, Feb 03, 2020 at 04:53:34AM -0600, Adam Ford wrote:
> My motivation is to get the flexspi on the i.MX8MM to work, and I did
> a list of the patches applied on the NXP branch to see what was
> applied on top of their 4.19 kernel and this patch series generated
> from that list. Most of the NXP commits are one-line commits, and I
> don't know the motivation for what's happening. NXP did it, and I
> know it works on the Flexspi driver.
Adding new compatibles and so on seems fine but the patches making
random changes without explanation like the one for octal mode I just
replied to are more worrying, do they work with older versions of the IP
or in all use cases for example? I'd suggest cutting the initial patch
series down to the bare minimum needed to get things working and then
building on top of that if that's not already been done.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists