From: Boris Brezillon <boris.brezillon@bootlin.com>
To: "Grandbois, Brett" <brett.grandbois@opengear.com>
Cc: Marek Vasut <marek.vasut@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Richard Weinberger <richard@nod.at>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mtd: spi-nor: Add support for SPI boot flash access for AMD Family 16h
Date: Sat, 27 Oct 2018 17:39:45 +0200 [thread overview]
Message-ID: <20181027173945.241e87b2@bbrezillon> (raw)
In-Reply-To: <20181016005726.26813-1-brett.grandbois@opengear.com>
Hi Brett,
On Tue, 16 Oct 2018 00:57:41 +0000
"Grandbois, Brett" <brett.grandbois@opengear.com> wrote:
> Add support to expose the SPI boot flash on AMD Family 16h CPUs as a
> standard mtd device to give userspace BIOS updaters greater feature
> support. The BIOS and Kernel Developer's Guide refers to this as the
> 'SPI ROM' controller and so the driver follows that naming convention
> for consistency.
>
We're currently trying to convert spi-nor controller drivers to the
spi-mem interface [1]. Can you look at this new interface and tell me if
you'd be able to implement it? If that's not possible, then I'd prefer
to have this driver implement the mtd_info interface directly.
Thanks,
Boris
[1]https://elixir.bootlin.com/linux/latest/source/include/linux/spi/spi-mem.h#L185
next prev parent reply other threads:[~2018-10-27 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 0:57 [PATCH v2] mtd: spi-nor: Add support for SPI boot flash access for AMD Family 16h Grandbois, Brett
2018-10-27 15:39 ` Boris Brezillon [this message]
2018-10-29 23:15 ` Grandbois, Brett
2018-10-30 8:26 ` Boris Brezillon
2018-10-31 3:18 ` Grandbois, Brett
2018-10-31 13:17 ` Boris Brezillon
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=20181027173945.241e87b2@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=brett.grandbois@opengear.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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).