2013-05-28 08:20:07 +02:00
|
|
|
/*
|
|
|
|
* EIM driver for Freescale's i.MX chips
|
|
|
|
*
|
|
|
|
* Copyright (C) 2013 Freescale Semiconductor, Inc.
|
|
|
|
*
|
|
|
|
* This file is licensed under the terms of the GNU General Public
|
|
|
|
* License version 2. This program is licensed "as is" without any
|
|
|
|
* warranty of any kind, whether express or implied.
|
|
|
|
*/
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/clk.h>
|
|
|
|
#include <linux/io.h>
|
|
|
|
#include <linux/of_device.h>
|
2014-02-11 02:52:09 +01:00
|
|
|
#include <linux/mfd/syscon.h>
|
|
|
|
#include <linux/mfd/syscon/imx6q-iomuxc-gpr.h>
|
|
|
|
#include <linux/regmap.h>
|
2013-05-28 08:20:07 +02:00
|
|
|
|
2013-06-29 06:27:54 +02:00
|
|
|
struct imx_weim_devtype {
|
|
|
|
unsigned int cs_count;
|
|
|
|
unsigned int cs_regs_count;
|
|
|
|
unsigned int cs_stride;
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct imx_weim_devtype imx1_weim_devtype = {
|
|
|
|
.cs_count = 6,
|
|
|
|
.cs_regs_count = 2,
|
|
|
|
.cs_stride = 0x08,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct imx_weim_devtype imx27_weim_devtype = {
|
|
|
|
.cs_count = 6,
|
|
|
|
.cs_regs_count = 3,
|
|
|
|
.cs_stride = 0x10,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct imx_weim_devtype imx50_weim_devtype = {
|
|
|
|
.cs_count = 4,
|
|
|
|
.cs_regs_count = 6,
|
|
|
|
.cs_stride = 0x18,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct imx_weim_devtype imx51_weim_devtype = {
|
|
|
|
.cs_count = 6,
|
|
|
|
.cs_regs_count = 6,
|
|
|
|
.cs_stride = 0x18,
|
|
|
|
};
|
|
|
|
|
2018-06-29 02:04:21 +02:00
|
|
|
#define MAX_CS_REGS_COUNT 6
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
#define MAX_CS_COUNT 6
|
2018-12-17 16:47:59 +01:00
|
|
|
#define OF_REG_SIZE 3
|
2018-06-29 02:04:21 +02:00
|
|
|
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
struct cs_timing {
|
|
|
|
bool is_applied;
|
|
|
|
u32 regs[MAX_CS_REGS_COUNT];
|
|
|
|
};
|
|
|
|
|
|
|
|
struct cs_timing_state {
|
|
|
|
struct cs_timing cs[MAX_CS_COUNT];
|
|
|
|
};
|
|
|
|
|
2013-05-28 08:20:07 +02:00
|
|
|
static const struct of_device_id weim_id_table[] = {
|
2013-06-29 06:27:54 +02:00
|
|
|
/* i.MX1/21 */
|
|
|
|
{ .compatible = "fsl,imx1-weim", .data = &imx1_weim_devtype, },
|
|
|
|
/* i.MX25/27/31/35 */
|
|
|
|
{ .compatible = "fsl,imx27-weim", .data = &imx27_weim_devtype, },
|
|
|
|
/* i.MX50/53/6Q */
|
|
|
|
{ .compatible = "fsl,imx50-weim", .data = &imx50_weim_devtype, },
|
|
|
|
{ .compatible = "fsl,imx6q-weim", .data = &imx50_weim_devtype, },
|
|
|
|
/* i.MX51 */
|
|
|
|
{ .compatible = "fsl,imx51-weim", .data = &imx51_weim_devtype, },
|
|
|
|
{ }
|
2013-05-28 08:20:07 +02:00
|
|
|
};
|
|
|
|
MODULE_DEVICE_TABLE(of, weim_id_table);
|
|
|
|
|
2014-02-11 02:52:09 +01:00
|
|
|
static int __init imx_weim_gpr_setup(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
struct device_node *np = pdev->dev.of_node;
|
|
|
|
struct property *prop;
|
|
|
|
const __be32 *p;
|
|
|
|
struct regmap *gpr;
|
|
|
|
u32 gprvals[4] = {
|
|
|
|
05, /* CS0(128M) CS1(0M) CS2(0M) CS3(0M) */
|
|
|
|
033, /* CS0(64M) CS1(64M) CS2(0M) CS3(0M) */
|
|
|
|
0113, /* CS0(64M) CS1(32M) CS2(32M) CS3(0M) */
|
|
|
|
01111, /* CS0(32M) CS1(32M) CS2(32M) CS3(32M) */
|
|
|
|
};
|
|
|
|
u32 gprval = 0;
|
|
|
|
u32 val;
|
|
|
|
int cs = 0;
|
|
|
|
int i = 0;
|
|
|
|
|
|
|
|
gpr = syscon_regmap_lookup_by_phandle(np, "fsl,weim-cs-gpr");
|
|
|
|
if (IS_ERR(gpr)) {
|
|
|
|
dev_dbg(&pdev->dev, "failed to find weim-cs-gpr\n");
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
of_property_for_each_u32(np, "ranges", prop, p, val) {
|
|
|
|
if (i % 4 == 0) {
|
|
|
|
cs = val;
|
|
|
|
} else if (i % 4 == 3 && val) {
|
|
|
|
val = (val / SZ_32M) | 1;
|
|
|
|
gprval |= val << cs * 3;
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (i == 0 || i % 4)
|
|
|
|
goto err;
|
|
|
|
|
|
|
|
for (i = 0; i < ARRAY_SIZE(gprvals); i++) {
|
|
|
|
if (gprval == gprvals[i]) {
|
|
|
|
/* Found it. Set up IOMUXC_GPR1[11:0] with it. */
|
|
|
|
regmap_update_bits(gpr, IOMUXC_GPR1, 0xfff, gprval);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
err:
|
|
|
|
dev_err(&pdev->dev, "Invalid 'ranges' configuration\n");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2013-05-28 08:20:07 +02:00
|
|
|
/* Parse and set the timing for this device. */
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
static int __init weim_timing_setup(struct device *dev,
|
|
|
|
struct device_node *np, void __iomem *base,
|
|
|
|
const struct imx_weim_devtype *devtype,
|
|
|
|
struct cs_timing_state *ts)
|
2013-05-28 08:20:07 +02:00
|
|
|
{
|
2018-06-29 02:04:21 +02:00
|
|
|
u32 cs_idx, value[MAX_CS_REGS_COUNT];
|
2013-06-29 06:27:54 +02:00
|
|
|
int i, ret;
|
2018-12-17 16:47:59 +01:00
|
|
|
int reg_idx, num_regs;
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
struct cs_timing *cst;
|
2013-05-28 08:20:07 +02:00
|
|
|
|
2018-06-29 02:04:21 +02:00
|
|
|
if (WARN_ON(devtype->cs_regs_count > MAX_CS_REGS_COUNT))
|
|
|
|
return -EINVAL;
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
if (WARN_ON(devtype->cs_count > MAX_CS_COUNT))
|
|
|
|
return -EINVAL;
|
2018-06-29 02:04:21 +02:00
|
|
|
|
2018-12-17 16:47:59 +01:00
|
|
|
ret = of_property_read_u32_array(np, "fsl,weim-cs-timing",
|
|
|
|
value, devtype->cs_regs_count);
|
2013-05-28 08:20:07 +02:00
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
2018-12-17 16:47:59 +01:00
|
|
|
/*
|
|
|
|
* the child node's "reg" property may contain multiple address ranges,
|
|
|
|
* extract the chip select for each.
|
|
|
|
*/
|
|
|
|
num_regs = of_property_count_elems_of_size(np, "reg", OF_REG_SIZE);
|
|
|
|
if (num_regs < 0)
|
|
|
|
return num_regs;
|
|
|
|
if (!num_regs)
|
2013-05-28 08:20:07 +02:00
|
|
|
return -EINVAL;
|
2018-12-17 16:47:59 +01:00
|
|
|
for (reg_idx = 0; reg_idx < num_regs; reg_idx++) {
|
|
|
|
/* get the CS index from this child node's "reg" property. */
|
|
|
|
ret = of_property_read_u32_index(np, "reg",
|
|
|
|
reg_idx * OF_REG_SIZE, &cs_idx);
|
|
|
|
if (ret)
|
|
|
|
break;
|
2013-05-28 08:20:07 +02:00
|
|
|
|
2018-12-17 16:47:59 +01:00
|
|
|
if (cs_idx >= devtype->cs_count)
|
|
|
|
return -EINVAL;
|
2013-05-28 08:20:07 +02:00
|
|
|
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
/* prevent re-configuring a CS that's already been configured */
|
|
|
|
cst = &ts->cs[cs_idx];
|
|
|
|
if (cst->is_applied && memcmp(value, cst->regs,
|
|
|
|
devtype->cs_regs_count * sizeof(u32))) {
|
|
|
|
dev_err(dev, "fsl,weim-cs-timing conflict on %pOF", np);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2018-12-17 16:47:59 +01:00
|
|
|
/* set the timing for WEIM */
|
|
|
|
for (i = 0; i < devtype->cs_regs_count; i++)
|
|
|
|
writel(value[i],
|
|
|
|
base + cs_idx * devtype->cs_stride + i * 4);
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
if (!cst->is_applied) {
|
|
|
|
cst->is_applied = true;
|
|
|
|
memcpy(cst->regs, value,
|
|
|
|
devtype->cs_regs_count * sizeof(u32));
|
|
|
|
}
|
2018-12-17 16:47:59 +01:00
|
|
|
}
|
2013-06-29 06:27:54 +02:00
|
|
|
|
2013-05-28 08:20:07 +02:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-06-29 06:27:52 +02:00
|
|
|
static int __init weim_parse_dt(struct platform_device *pdev,
|
|
|
|
void __iomem *base)
|
2013-05-28 08:20:07 +02:00
|
|
|
{
|
2013-06-29 06:27:54 +02:00
|
|
|
const struct of_device_id *of_id = of_match_device(weim_id_table,
|
|
|
|
&pdev->dev);
|
|
|
|
const struct imx_weim_devtype *devtype = of_id->data;
|
2013-05-28 08:20:07 +02:00
|
|
|
struct device_node *child;
|
2015-02-19 08:24:10 +01:00
|
|
|
int ret, have_child = 0;
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
struct cs_timing_state ts = {};
|
2013-05-28 08:20:07 +02:00
|
|
|
|
2014-02-11 02:52:09 +01:00
|
|
|
if (devtype == &imx50_weim_devtype) {
|
|
|
|
ret = imx_weim_gpr_setup(pdev);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2016-02-22 13:01:53 +01:00
|
|
|
for_each_available_child_of_node(pdev->dev.of_node, child) {
|
bus: imx-weim: guard against timing configuration conflicts
When specifying weim child devices, there is a risk that more than
one timing setting is specified for the same chip select.
The driver cannot support such a configuration.
In case of conflict, this patch will print a warning to the log,
and will ignore the child node in question.
In this example, node acme@1 will be ignored, as it tries to modify
timing settings for CS0:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something else>;
};
};
However in this example, the driver will be happy:
&weim {
acme@0 {
compatible = "acme,whatever";
reg = <0 0 0x100>;
fsl,weim-cs-timing = <something>;
};
acme@1 {
compatible = "acme,whatnot";
reg = <0 0x500 0x100>;
fsl,weim-cs-timing = <something>;
};
};
Signed-off-by: Sven Van Asbroeck <TheSven73@googlemail.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2018-12-17 16:48:00 +01:00
|
|
|
ret = weim_timing_setup(&pdev->dev, child, base, devtype, &ts);
|
2015-02-19 08:24:10 +01:00
|
|
|
if (ret)
|
2017-07-18 23:42:51 +02:00
|
|
|
dev_warn(&pdev->dev, "%pOF set timing failed.\n",
|
|
|
|
child);
|
2015-02-19 08:24:10 +01:00
|
|
|
else
|
|
|
|
have_child = 1;
|
2013-05-28 08:20:07 +02:00
|
|
|
}
|
|
|
|
|
2015-02-19 08:24:10 +01:00
|
|
|
if (have_child)
|
2016-06-01 08:53:07 +02:00
|
|
|
ret = of_platform_default_populate(pdev->dev.of_node,
|
|
|
|
NULL, &pdev->dev);
|
2013-05-28 08:20:07 +02:00
|
|
|
if (ret)
|
2017-07-18 23:42:51 +02:00
|
|
|
dev_err(&pdev->dev, "%pOF fail to create devices.\n",
|
|
|
|
pdev->dev.of_node);
|
2013-05-28 08:20:07 +02:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2013-06-29 06:27:52 +02:00
|
|
|
static int __init weim_probe(struct platform_device *pdev)
|
2013-05-28 08:20:07 +02:00
|
|
|
{
|
|
|
|
struct resource *res;
|
2013-06-29 06:27:50 +02:00
|
|
|
struct clk *clk;
|
|
|
|
void __iomem *base;
|
2013-06-29 06:27:51 +02:00
|
|
|
int ret;
|
2013-05-28 08:20:07 +02:00
|
|
|
|
|
|
|
/* get the resource */
|
|
|
|
res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
|
2013-06-29 06:27:50 +02:00
|
|
|
base = devm_ioremap_resource(&pdev->dev, res);
|
2013-06-29 06:27:51 +02:00
|
|
|
if (IS_ERR(base))
|
|
|
|
return PTR_ERR(base);
|
2013-05-28 08:20:07 +02:00
|
|
|
|
|
|
|
/* get the clock */
|
2013-06-29 06:27:50 +02:00
|
|
|
clk = devm_clk_get(&pdev->dev, NULL);
|
|
|
|
if (IS_ERR(clk))
|
2013-06-29 06:27:51 +02:00
|
|
|
return PTR_ERR(clk);
|
2013-05-28 08:20:07 +02:00
|
|
|
|
2013-06-29 06:27:50 +02:00
|
|
|
ret = clk_prepare_enable(clk);
|
2013-05-28 08:20:07 +02:00
|
|
|
if (ret)
|
2013-06-29 06:27:51 +02:00
|
|
|
return ret;
|
2013-05-28 08:20:07 +02:00
|
|
|
|
|
|
|
/* parse the device node */
|
2013-06-29 06:27:50 +02:00
|
|
|
ret = weim_parse_dt(pdev, base);
|
2013-06-29 06:27:51 +02:00
|
|
|
if (ret)
|
2013-06-29 06:27:50 +02:00
|
|
|
clk_disable_unprepare(clk);
|
2013-06-29 06:27:51 +02:00
|
|
|
else
|
|
|
|
dev_info(&pdev->dev, "Driver registered.\n");
|
2013-05-28 08:20:07 +02:00
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct platform_driver weim_driver = {
|
|
|
|
.driver = {
|
2013-06-29 06:27:53 +02:00
|
|
|
.name = "imx-weim",
|
|
|
|
.of_match_table = weim_id_table,
|
2013-05-28 08:20:07 +02:00
|
|
|
},
|
|
|
|
};
|
2013-06-29 06:27:52 +02:00
|
|
|
module_platform_driver_probe(weim_driver, weim_probe);
|
2013-05-28 08:20:07 +02:00
|
|
|
|
|
|
|
MODULE_AUTHOR("Freescale Semiconductor Inc.");
|
|
|
|
MODULE_DESCRIPTION("i.MX EIM Controller Driver");
|
|
|
|
MODULE_LICENSE("GPL");
|