[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161205163106.GJ1459@lahna.fi.intel.com>
Date: Mon, 5 Dec 2016 18:31:06 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Marek Vasut <marek.vasut@...il.com>
Cc: Lee Jones <lee.jones@...aro.org>,
Cyrille Pitchen <cyrille.pitchen@...el.com>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
Richard Weinberger <richard@....at>,
Brian Norris <computersforpeace@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
Peter Tyser <ptyser@...-inc.com>, key.seong.lim@...el.com,
linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org
Subject: Re: [PATCH v6 0/3] spi-nor: Add support for Intel SPI serial flash
controller
On Mon, Dec 05, 2016 at 02:33:12PM +0100, Marek Vasut wrote:
> On 12/05/2016 12:27 PM, Mika Westerberg wrote:
> > On Mon, Nov 28, 2016 at 03:06:23PM +0300, Mika Westerberg wrote:
> >> This is 6th iteration of the series. You can find the previous versions
> >> archived on:
> >>
> >> v5: https://lwn.net/Articles/706363/
> >> v4: https://lwn.net/Articles/703773/
> >> v3: https://lwn.net/Articles/697231/
> >> v2: http://lists.infradead.org/pipermail/linux-mtd/2016-June/068277.html
> >> v1: https://lkml.org/lkml/2016/6/14/269
> >>
> >> This patch series adds support for the Intel SPI serial flash controller
> >> found on many recent Intel CPUs including Baytrail and Braswell. This
> >> driver makes it possible to access the BIOS and other platform data which
> >> is stored on the SPI serial flash. It is also possible to upgrade the BIOS
> >> using this driver if it has not been protected by special hardware bits.
> >>
> >> The patch [1/3] includes documentation how to upgrade BIOS on MinnowBoard
> >> MAX.
> >>
> >> Since poking the SPI serial flash can brick the machine, this driver can
> >> only be enabled when CONFIG_EXPERT=y and even then it will remain read-only
> >> unless instructed othwerwise by module parameter.
> >
> > Hi Lee,
> >
> > I think we have enough acks from the MTD maintainers. I wonder if you
> > could merge this series via your MFD tree?
> >
> Ideally you'd merge 1/3 via MTD and 2,3/3 via MFD, but I'm not sure if
> that is possible and if that is a sensible thing to do.
There is a dependency between patches 1 and 2 (and 3) so they should be
merged together to avoid build errors. I'm fine if they go via either
tree as long as someone picks them up ;-)
Powered by blists - more mailing lists