From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-mtd@lists.infradead.org
Cc: Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Lee Jones <lee.jones@linaro.org>,
Peter Tyser <ptyser@xes-inc.com>,
key.seong.lim@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] spi-nor: Add support for Intel SPI serial flash controller
Date: Wed, 6 Jul 2016 14:46:00 +0300 [thread overview]
Message-ID: <20160706114600.GD23527@lahna.fi.intel.com> (raw)
In-Reply-To: <1466609565-113251-1-git-send-email-mika.westerberg@linux.intel.com>
On Wed, Jun 22, 2016 at 06:32:42PM +0300, Mika Westerberg wrote:
> Hi,
>
> This is second version of the series. The first version can be found here:
>
> https://lkml.org/lkml/2016/6/14/269
>
> This 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.
>
> Changes from v1:
>
> [1/3] spi-nor: Add support for Intel SPI serial flash controller
>
> * Older hardware does not support 64k erase command so added erase_64k
> flag which is set only for Broxton (BXT).
>
> * Fix protection range offset for Broxton. Now there is ispi->pregs
> pointing to the start of the protection registers.
>
> * Change naming of constants from BCR_BYT -> BYT_BCR and so on.
>
> [2/3] mfd: lpc_ich: Add support for SPI serial flash host controller
>
> * Drop lpc_ich_finalize_spi_cell() and initialize cell directly in
> lpc_ich_init_spi().
>
> * Use info->type in switch in lpc_ich_init_spi().
>
> * Add defines for magic numbers used in lpc_ich_init_spi().
>
> * Use PLATFORM_DEVID_NONE with mfd_add_devices().
>
> [3/3] mfd: lpc_ich: Add support for Intel Apollo Lake SoC
>
> * No changes
>
> Mika Westerberg (3):
> spi-nor: Add support for Intel SPI serial flash controller
> mfd: lpc_ich: Add support for SPI serial flash host controller
> mfd: lpc_ich: Add support for Intel Apollo Lake SoC
Ping. Any comments on this?
prev parent reply other threads:[~2016-07-06 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 15:32 [PATCH v2 0/3] spi-nor: Add support for Intel SPI serial flash controller Mika Westerberg
2016-06-22 15:32 ` [PATCH v2 1/3] " Mika Westerberg
2016-08-09 11:37 ` Mika Westerberg
2016-08-09 19:32 ` Jagan Teki
2016-08-10 7:31 ` Mika Westerberg
2016-06-22 15:32 ` [PATCH v2 2/3] mfd: lpc_ich: Add support for SPI serial flash host controller Mika Westerberg
2016-06-22 15:32 ` [PATCH v2 3/3] mfd: lpc_ich: Add support for Intel Apollo Lake SoC Mika Westerberg
2016-07-06 11:46 ` Mika Westerberg [this message]
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=20160706114600.GD23527@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=key.seong.lim@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ptyser@xes-inc.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).