From: Roger Quadros <rogerq@kernel.org>
To: miquel.raynal@bootlin.com, robh+dt@kernel.org
Cc: krzk@kernel.org, richard@nod.at, vigneshr@ti.com, kishon@ti.com,
nm@ti.com, linux-mtd@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Roger Quadros <rogerq@kernel.org>
Subject: [PATCH v3 0/3] mtd: rawnand: omap_elm: convert DT binding to yaml
Date: Sat, 26 Mar 2022 10:07:23 +0200 [thread overview]
Message-ID: <20220326080726.30372-1-rogerq@kernel.org> (raw)
Hi,
This series converts omap_elm DT bindings to yaml and adds
support for ELM on AM64 SoC.
Changelog:
v3
- use 'enum' for compatible specifier. Get rid of 'items'.
v2
- explain hwmod usage deprecated in commit log
- fix example node name to 'ecc'
- remove 'items' for single compatible specifier
cheers,
-roger
Roger Quadros (3):
dt-bindings: mtd: ti,elm: Convert to yaml
dt-bindings: mtd: ti,elm: Add support for AM64 ELM
mtd: rawnand: omap_elm: Add compatible for AM64 ELM
Documentation/devicetree/bindings/mtd/elm.txt | 16 -----
.../devicetree/bindings/mtd/ti,elm.yaml | 72 +++++++++++++++++++
drivers/mtd/nand/raw/omap_elm.c | 1 +
3 files changed, 73 insertions(+), 16 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/mtd/elm.txt
create mode 100644 Documentation/devicetree/bindings/mtd/ti,elm.yaml
--
2.17.1
next reply other threads:[~2022-03-26 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 8:07 Roger Quadros [this message]
2022-03-26 8:07 ` [PATCH v3 1/3] dt-bindings: mtd: ti,elm: Convert to yaml Roger Quadros
2022-04-11 9:00 ` Miquel Raynal
2022-03-26 8:07 ` [PATCH v3 2/3] dt-bindings: mtd: ti,elm: Add support for AM64 ELM Roger Quadros
2022-03-26 8:14 ` Krzysztof Kozlowski
2022-04-11 9:00 ` Miquel Raynal
2022-03-26 8:07 ` [PATCH v3 3/3] mtd: rawnand: omap_elm: Add compatible " Roger Quadros
2022-04-11 9:00 ` Miquel Raynal
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=20220326080726.30372-1-rogerq@kernel.org \
--to=rogerq@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=nm@ti.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--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).