From: Rob Herring <robh@kernel.org>
To: Heiko Schocher <hs@denx.de>
Cc: linux-mtd@lists.infradead.org, Fabio Estevam <festevam@denx.de>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] mtd: devices: add devicetree documentation for microchip 48l640
Date: Wed, 2 Jun 2021 14:29:50 -0500 [thread overview]
Message-ID: <20210602192950.GA3827845@robh.at.kernel.org> (raw)
In-Reply-To: <20210601043546.1345704-2-hs@denx.de>
On Tue, Jun 01, 2021 at 06:35:45AM +0200, Heiko Schocher wrote:
> The Microchip 48l640 is a 8KByte EERAM connected via SPI.
> Add devicetree bindings documentation.
>
> Signed-off-by: Heiko Schocher <hs@denx.de>
> ---
>
> Changes in v3:
> Add Fabio to cc
>
> Changes in v2:
> as Rob helped, fix warnings from running command
> 'make DT_CHECKER_FLAGS=-m dt_binding_check'
>
> .../bindings/mtd/microchip,mchp48l640.yaml | 45 +++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/microchip,mchp48l640.yaml
>
> diff --git a/Documentation/devicetree/bindings/mtd/microchip,mchp48l640.yaml b/Documentation/devicetree/bindings/mtd/microchip,mchp48l640.yaml
> new file mode 100644
> index 0000000000000..08089f2db0761
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/microchip,mchp48l640.yaml
> @@ -0,0 +1,45 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/mtd/microchip,mchp48l640.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: MTD SPI driver for Microchip 48l640 (and similar) serial EERAM
This is not the driver.
> +
> +maintainers:
> + - Heiko Schocher <hs@denx.de>
> +
> +description: |
> + The Microchip 48l640 is a 8KByte EERAM connected via SPI.
> +
> + datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/20006055B.pdf
> +
> +properties:
> + compatible:
> + items:
> + - const: microchip,48l640
> +
> + reg:
> + maxItems: 1
> +
> + spi-max-frequency: true
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + spi-eeram@0 {
eeram@0
Otherwise,
Reviewed-by: Rob Herring <robh@kernel.org>
> + compatible = "microchip,48l640";
> + reg = <0>;
> + spi-max-frequency = <20000000>;
> + };
> + };
> +...
> --
> 2.31.1
next prev parent reply other threads:[~2021-06-02 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 4:35 [PATCH v3 0/2] mtd: devices: add support for microchip 48l640 EERAM Heiko Schocher
2021-06-01 4:35 ` [PATCH v3 1/2] mtd: devices: add devicetree documentation for microchip 48l640 Heiko Schocher
2021-06-02 19:29 ` Rob Herring [this message]
2021-06-03 3:51 ` Heiko Schocher
2021-06-01 4:35 ` [PATCH v3 2/2] mtd: devices: add support for microchip 48l640 EERAM Heiko Schocher
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=20210602192950.GA3827845@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=hs@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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).