From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Mark Rutland <mark.rutland@arm.com>,
andrew@lunn.ch, devicetree@vger.kernel.org,
Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org, Marek Vasut <marek.vasut@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-mtd@lists.infradead.org,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
computersforpeace@gmail.com, dwmw2@infradead.org
Subject: Re: [PATCH v4 1/5] mtd: mchp23k256: Add OF device ID table
Date: Mon, 29 May 2017 11:13:19 +0200 [thread overview]
Message-ID: <20170529111319.1c261582@bbrezillon> (raw)
In-Reply-To: <20170524234916.16181-2-chris.packham@alliedtelesis.co.nz>
On Thu, 25 May 2017 11:49:12 +1200
Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
> This allows registering of this device via a Device Tree.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> Tested-by: Andrew Lunn <andrew@lunn.ch>
Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> Changes in v2:
> - collect review/test from Andrew
> Changes in v3:
> - None
> Changes in v4:
> - None
>
> .../devicetree/bindings/mtd/microchip,mchp23k256.txt | 18 ++++++++++++++++++
> drivers/mtd/devices/mchp23k256.c | 8 ++++++++
> 2 files changed, 26 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/microchip,mchp23k256.txt
>
> diff --git a/Documentation/devicetree/bindings/mtd/microchip,mchp23k256.txt b/Documentation/devicetree/bindings/mtd/microchip,mchp23k256.txt
> new file mode 100644
> index 000000000000..25e5ad38b0f0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/microchip,mchp23k256.txt
> @@ -0,0 +1,18 @@
> +* MTD SPI driver for Microchip 23K256 (and similar) serial SRAM
> +
> +Required properties:
> +- #address-cells, #size-cells : Must be present if the device has sub-nodes
> + representing partitions.
> +- compatible : Must be "microchip,mchp23k256"
> +- reg : Chip-Select number
> +- spi-max-frequency : Maximum frequency of the SPI bus the chip can operate at
> +
> +Example:
> +
> + spi-sram@0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "microchip,mchp23k256";
> + reg = <0>;
> + spi-max-frequency = <20000000>;
> + };
> diff --git a/drivers/mtd/devices/mchp23k256.c b/drivers/mtd/devices/mchp23k256.c
> index e237db9f1bdb..9d8306a15833 100644
> --- a/drivers/mtd/devices/mchp23k256.c
> +++ b/drivers/mtd/devices/mchp23k256.c
> @@ -19,6 +19,7 @@
> #include <linux/sizes.h>
> #include <linux/spi/flash.h>
> #include <linux/spi/spi.h>
> +#include <linux/of_device.h>
>
> struct mchp23k256_flash {
> struct spi_device *spi;
> @@ -166,9 +167,16 @@ static int mchp23k256_remove(struct spi_device *spi)
> return mtd_device_unregister(&flash->mtd);
> }
>
> +static const struct of_device_id mchp23k256_of_table[] = {
> + { .compatible = "microchip,mchp23k256" },
> + {}
> +};
> +MODULE_DEVICE_TABLE(of, mchp23k256_of_table);
> +
> static struct spi_driver mchp23k256_driver = {
> .driver = {
> .name = "mchp23k256",
> + .of_match_table = of_match_ptr(mchp23k256_of_table),
> },
> .probe = mchp23k256_probe,
> .remove = mchp23k256_remove,
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2017-05-29 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170524234916.16181-1-chris.packham@alliedtelesis.co.nz>
[not found] ` <20170524234916.16181-1-chris.packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2017-05-24 23:49 ` [PATCH v4 1/5] mtd: mchp23k256: Add OF device ID table Chris Packham
2017-05-29 9:13 ` Boris Brezillon [this message]
2017-05-31 17:50 ` Rob Herring
2017-05-24 23:49 ` [PATCH v4 5/5] mtd: mchp23k256: Add support for mchp23lcv1024 Chris Packham
2017-05-29 9:15 ` Boris Brezillon
2017-05-31 17:52 ` Rob Herring
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=20170529111319.1c261582@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.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).