From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: linux-mtd@lists.infradead.org, andrew@lunn.ch,
computersforpeace@gmail.com, dwmw2@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] mtd: mchp23k256: device tree and mchp23lcv1024
Date: Tue, 23 May 2017 09:39:57 +0200 [thread overview]
Message-ID: <20170523093957.24110476@bbrezillon> (raw)
In-Reply-To: <20170523004317.16908-1-chris.packham@alliedtelesis.co.nz>
On Tue, 23 May 2017 12:43:12 +1200
Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
> This series adds device tree support to the mchp23k256 driver and
> support for the mchp23lcv1024 chip. I suspect there are more compatible
> variants that we could now enumerate if desired.
>
> Chris Packham (5):
> mtd: mchp23k256: Add OF device ID table
> mtd: mchp23k256: switch to mtd_device_register()
> mtd: handle partitioning on devices with 0 erasesize
> mtd: mchp23k256: add partitioning support
> mtd: mchp23k256: Add support for mchp23lcv1024
Shouldn't we add a spi_device_id table to allow non-DT users to probe
mchp23lcv1024 chips?
>
> .../bindings/mtd/microchip,mchp23k256.txt | 18 ++++++
> drivers/mtd/devices/mchp23k256.c | 65 ++++++++++++++++++----
> drivers/mtd/mtdpart.c | 25 ++++++---
> 3 files changed, 87 insertions(+), 21 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mtd/microchip,mchp23k256.txt
>
next prev parent reply other threads:[~2017-05-23 7:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 0:43 [PATCH v3 0/5] mtd: mchp23k256: device tree and mchp23lcv1024 Chris Packham
2017-05-23 0:43 ` [PATCH v3 1/5] mtd: mchp23k256: Add OF device ID table Chris Packham
2017-05-23 0:43 ` [PATCH v3 2/5] mtd: mchp23k256: switch to mtd_device_register() Chris Packham
2017-05-23 0:43 ` [PATCH v3 3/5] mtd: handle partitioning on devices with 0 erasesize Chris Packham
2017-05-23 0:43 ` [PATCH v3 4/5] mtd: mchp23k256: add partitioning support Chris Packham
2017-05-23 0:43 ` [PATCH v3 5/5] mtd: mchp23k256: Add support for mchp23lcv1024 Chris Packham
2017-05-23 0:58 ` Andrew Lunn
2017-05-23 1:38 ` Chris Packham
2017-05-23 1:57 ` Andrew Lunn
2017-05-23 7:14 ` Boris Brezillon
2017-05-23 20:29 ` Chris Packham
2017-05-23 7:39 ` Boris Brezillon [this message]
2017-05-23 11:52 ` [PATCH v3 0/5] mtd: mchp23k256: device tree and mchp23lcv1024 Andrew Lunn
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=20170523093957.24110476@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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).