From: Roger Quadros <rogerq@kernel.org>
To: miquel.raynal@bootlin.com, robh+dt@kernel.org
Cc: 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 3/3] mtd: rawnand: omap_elm: Add compatible for AM64 ELM
Date: Wed, 23 Mar 2022 13:18:51 +0200 [thread overview]
Message-ID: <20220323111851.4699-4-rogerq@kernel.org> (raw)
In-Reply-To: <20220323111851.4699-1-rogerq@kernel.org>
The AM64 SoC has the Error Locator Module. Add compatible id for it.
Signed-off-by: Roger Quadros <rogerq@kernel.org>
---
drivers/mtd/nand/raw/omap_elm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/nand/raw/omap_elm.c b/drivers/mtd/nand/raw/omap_elm.c
index db105d9b560c..aa7f49c3f372 100644
--- a/drivers/mtd/nand/raw/omap_elm.c
+++ b/drivers/mtd/nand/raw/omap_elm.c
@@ -550,6 +550,7 @@ static SIMPLE_DEV_PM_OPS(elm_pm_ops, elm_suspend, elm_resume);
#ifdef CONFIG_OF
static const struct of_device_id elm_of_match[] = {
{ .compatible = "ti,am3352-elm" },
+ { .compatible = "ti,am64-elm" },
{},
};
MODULE_DEVICE_TABLE(of, elm_of_match);
--
2.17.1
prev parent reply other threads:[~2022-03-23 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 11:18 [PATCH 0/3] mtd: rawnand: omap_elm: convert DT binding to yaml Roger Quadros
2022-03-23 11:18 ` [PATCH 1/3] dt-bindings: mtd: ti,elm: Convert " Roger Quadros
2022-03-24 18:24 ` Krzysztof Kozlowski
2022-03-25 12:03 ` Roger Quadros
2022-03-23 11:18 ` [PATCH 2/3] dt-bindings: mtd: ti,elm: Add support for AM64 ELM Roger Quadros
2022-03-24 18:26 ` Krzysztof Kozlowski
2022-03-25 12:05 ` Roger Quadros
2022-03-25 12:08 ` Krzysztof Kozlowski
2022-03-25 12:13 ` Roger Quadros
2022-03-25 12:27 ` Krzysztof Kozlowski
2022-03-23 11:18 ` Roger Quadros [this message]
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=20220323111851.4699-4-rogerq@kernel.org \
--to=rogerq@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--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).