[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190123152310.11680-3-angus@akkea.ca>
Date: Wed, 23 Jan 2019 08:23:07 -0700
From: "Angus Ainslie (Purism)" <angus@...ea.ca>
To: angus@...ea.ca
Cc: angus.ainslie@...i.sm, Vinod Koul <vkoul@...nel.org>,
dmaengine@...r.kernel.org, NXP Linux Team <linux-imx@....com>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Lucas Stach <l.stach@...gutronix.de>,
Daniel Baluta <daniel.baluta@...il.com>
Subject: [PATCH v3 2/5] dma: imx-sdma: add imx8mq sdma compatible parts
This is identical to the imx7d data structures but we need to
be able to differentiate that the imx8mq has 2 sdma controllers.
Signed-off-by: Angus Ainslie (Purism) <angus@...ea.ca>
---
drivers/dma/imx-sdma.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index 531a9d8b032a..2e691b1cd0eb 100644
--- a/drivers/dma/imx-sdma.c
+++ b/drivers/dma/imx-sdma.c
@@ -556,6 +556,12 @@ static struct sdma_driver_data sdma_imx7d = {
.script_addrs = &sdma_script_imx7d,
};
+static struct sdma_driver_data sdma_imx8mq = {
+ .chnenbl0 = SDMA_CHNENBL0_IMX35,
+ .num_events = 48,
+ .script_addrs = &sdma_script_imx7d,
+};
+
static const struct platform_device_id sdma_devtypes[] = {
{
.name = "imx25-sdma",
@@ -578,6 +584,9 @@ static const struct platform_device_id sdma_devtypes[] = {
}, {
.name = "imx7d-sdma",
.driver_data = (unsigned long)&sdma_imx7d,
+ }, {
+ .name = "imx8mq-sdma",
+ .driver_data = (unsigned long)&sdma_imx8mq,
}, {
/* sentinel */
}
@@ -592,6 +601,7 @@ static const struct of_device_id sdma_dt_ids[] = {
{ .compatible = "fsl,imx31-sdma", .data = &sdma_imx31, },
{ .compatible = "fsl,imx25-sdma", .data = &sdma_imx25, },
{ .compatible = "fsl,imx7d-sdma", .data = &sdma_imx7d, },
+ { .compatible = "fsl,imx8mq-sdma", .data = &sdma_imx8mq, },
{ /* sentinel */ }
};
MODULE_DEVICE_TABLE(of, sdma_dt_ids);
--
2.17.1
Powered by blists - more mailing lists