Discussion:
[PATCH v7] mfd: syscon: Decouple syscon interface from platform devices
Pankaj Dubey
2014-09-30 08:35:27 UTC
Permalink
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface provider.

For example, certain SoCs (e.g. Exynos) contain system controller
blocks which perform various functions such as power domain control,
CPU power management, low power mode control, but in addition contain
certain IP integration glue, such as various signal masks,
coprocessor power control, etc. In such case, there is a need to have
a dedicated driver for such system controller but also share registers
with other drivers. The latter is where the syscon interface is helpful.

In case of DT based platforms, this patch decouples syscon object from
syscon platform driver, and allows to create syscon objects first time
when it is required by calling of syscon_regmap_lookup_by APIs and keep
a list of such syscon objects along with syscon provider device_nodes
and regmap handles.

For non-DT based platforms, this patch keeps syscon platform driver
structure so that syscon can be probed and such non-DT based drivers
can use syscon_regmap_lookup_by_pdev API and access regmap handles.
Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT based,
we can completely remove platform driver of syscon, and keep only helper
functions to get regmap handles.

Suggested-by: Arnd Bergmann <***@arndb.de>
Suggested-by: Tomasz Figa <***@gmail.com>
Tested-by: Vivek Gautam <***@samsung.com>
Tested-by: Javier Martinez Canillas <***@collabora.co.uk>
Signed-off-by: Pankaj Dubey <***@samsung.com>
Reviewed-by: Arnd Bergmann <***@arndb.de>
Tested-by: Heiko Stuebner <***@sntech.de>
Reviewed-by: Heiko Stuebner <***@sntech.de>
---
Patch v6 and related discussions can be found here [1].

Change since v5:
- Addressed review comments from "Heiko Stuebner".
- Updated commit description.
- Including Arnd's and Heiko's Reviewed-by.

Change since v5:
- Dropping creation of dummy platform device in of_syscon_register.
- As we are changing syscon to decouple from platform_device, creation of
dummy platform_device does not look good option, and as suggested by Arnd,
I made another attempt so that regmap_mmio_init API should work with NULL
dev pointer itself. Since regmap needs to know about Syscon device node
properties so let's parse device node of syscon in syscon itself for any
such properties and using regmap_config parameter pass all such information
to regmap. Other concern of crashes due to NULL dev pointer in regmap already
addressed in separate patches of regmap. Please see [2] and [3].

Changes since v4:
- Addressed Tomasz Figa's comments for v4.
- Added error handing in of_syscon_register function.
- Using devm_regmap_init_mmio instead of regmap_init_mmio.

Changes since v3:
- Addressed Arnd's comment for v2.
- Updated of_syscon_register for adding dev pointer in regmap_init_mmio.
- For early users created dummy platform device.

Changes since v2:
- Added back platform device support from syscon, with one change that
syscon will not be probed for DT based platform.
- Added back syscon_regmap_lookup_by_pdevname API so that non-DT base
users of syscon will not be broken.
- Removed unwanted change in syscon.h.
- Modified Signed-off-by list, added Suggested-by of Tomasz Figa and
Arnd Bergmann.
- Added Tested-by of Vivek Gautam for testing on Exynos platform.

Changes since v1:
- Removed of_syscon_unregister function.
- Modified of_syscon_register function and it will be used by syscon.c
to create syscon objects whenever required.
- Removed platform device support from syscon.
- Removed syscon_regmap_lookup_by_pdevname API support.
- As there are significant changes w.r.t patchset v1, I am taking over
author for this patchset from Tomasz Figa.

[1]: https://lkml.org/lkml/2014/9/29/99
[2]: https://lkml.org/lkml/2014/9/18/130
[3]: https://lkml.org/lkml/2014/9/27/2
drivers/mfd/syscon.c | 96 ++++++++++++++++++++++++++++++++++++++------------
1 file changed, 74 insertions(+), 22 deletions(-)

diff --git a/drivers/mfd/syscon.c b/drivers/mfd/syscon.c
index ca15878..72373b1 100644
--- a/drivers/mfd/syscon.c
+++ b/drivers/mfd/syscon.c
@@ -15,6 +15,7 @@
#include <linux/err.h>
#include <linux/io.h>
#include <linux/module.h>
+#include <linux/list.h>
#include <linux/of.h>
#include <linux/of_address.h>
#include <linux/of_platform.h>
@@ -22,31 +23,94 @@
#include <linux/platform_device.h>
#include <linux/regmap.h>
#include <linux/mfd/syscon.h>
+#include <linux/slab.h>

static struct platform_driver syscon_driver;

+static DEFINE_SPINLOCK(syscon_list_slock);
+static LIST_HEAD(syscon_list);
+
struct syscon {
+ struct device_node *np;
struct regmap *regmap;
+ struct list_head list;
+};
+
+static struct regmap_config syscon_regmap_config = {
+ .reg_bits = 32,
+ .val_bits = 32,
+ .reg_stride = 4,
};

-static int syscon_match_node(struct device *dev, void *data)
+static struct syscon *of_syscon_register(struct device_node *np)
{
- struct device_node *dn = data;
+ struct syscon *syscon;
+ struct regmap *regmap;
+ void __iomem *base;
+ int ret;
+ struct regmap_config syscon_config = syscon_regmap_config;
+
+ if (!of_device_is_compatible(np, "syscon"))
+ return ERR_PTR(-EINVAL);
+
+ syscon = kzalloc(sizeof(*syscon), GFP_KERNEL);
+ if (!syscon)
+ return ERR_PTR(-ENOMEM);
+
+ base = of_iomap(np, 0);
+ if (!base) {
+ ret = -ENOMEM;
+ goto err_map;
+ }
+
+ /* Parse the device's DT node for an endianness specification */
+ if (of_property_read_bool(np, "big-endian"))
+ syscon_config.val_format_endian = REGMAP_ENDIAN_BIG;
+ else if (of_property_read_bool(np, "little-endian"))
+ syscon_config.val_format_endian = REGMAP_ENDIAN_LITTLE;
+
+ regmap = regmap_init_mmio(NULL, base, &syscon_config);
+ if (IS_ERR(regmap)) {
+ pr_err("regmap init failed\n");
+ ret = PTR_ERR(regmap);
+ goto err_regmap;
+ }
+
+ syscon->regmap = regmap;
+ syscon->np = np;
+
+ spin_lock(&syscon_list_slock);
+ list_add_tail(&syscon->list, &syscon_list);
+ spin_unlock(&syscon_list_slock);

- return (dev->of_node == dn) ? 1 : 0;
+ return syscon;
+
+err_regmap:
+ iounmap(base);
+err_map:
+ kfree(syscon);
+ return ERR_PTR(ret);
}

struct regmap *syscon_node_to_regmap(struct device_node *np)
{
- struct syscon *syscon;
- struct device *dev;
+ struct syscon *entry, *syscon = NULL;

- dev = driver_find_device(&syscon_driver.driver, NULL, np,
- syscon_match_node);
- if (!dev)
- return ERR_PTR(-EPROBE_DEFER);
+ spin_lock(&syscon_list_slock);

- syscon = dev_get_drvdata(dev);
+ list_for_each_entry(entry, &syscon_list, list)
+ if (entry->np == np) {
+ syscon = entry;
+ break;
+ }
+
+ spin_unlock(&syscon_list_slock);
+
+ if (!syscon)
+ syscon = of_syscon_register(np);
+
+ if (IS_ERR(syscon))
+ return ERR_CAST(syscon);

return syscon->regmap;
}
@@ -110,17 +174,6 @@ struct regmap *syscon_regmap_lookup_by_phandle(struct device_node *np,
}
EXPORT_SYMBOL_GPL(syscon_regmap_lookup_by_phandle);

-static const struct of_device_id of_syscon_match[] = {
- { .compatible = "syscon", },
- { },
-};
-
-static struct regmap_config syscon_regmap_config = {
- .reg_bits = 32,
- .val_bits = 32,
- .reg_stride = 4,
-};
-
static int syscon_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
@@ -167,7 +220,6 @@ static struct platform_driver syscon_driver = {
.driver = {
.name = "syscon",
.owner = THIS_MODULE,
- .of_match_table = of_syscon_match,
},
.probe = syscon_probe,
.id_table = syscon_ids,
--
1.7.9.5
Doug Anderson
2014-09-30 16:09:22 UTC
Permalink
Pankaj,
Post by Pankaj Dubey
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface provider.
For example, certain SoCs (e.g. Exynos) contain system controller
blocks which perform various functions such as power domain control,
CPU power management, low power mode control, but in addition contain
certain IP integration glue, such as various signal masks,
coprocessor power control, etc. In such case, there is a need to have
a dedicated driver for such system controller but also share registers
with other drivers. The latter is where the syscon interface is helpful.
In case of DT based platforms, this patch decouples syscon object from
syscon platform driver, and allows to create syscon objects first time
when it is required by calling of syscon_regmap_lookup_by APIs and keep
a list of such syscon objects along with syscon provider device_nodes
and regmap handles.
For non-DT based platforms, this patch keeps syscon platform driver
structure so that syscon can be probed and such non-DT based drivers
can use syscon_regmap_lookup_by_pdev API and access regmap handles.
Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT based,
we can completely remove platform driver of syscon, and keep only helper
functions to get regmap handles.
---
Patch v6 and related discussions can be found here [1].
- Addressed review comments from "Heiko Stuebner".
- Updated commit description.
- Including Arnd's and Heiko's Reviewed-by.
- Dropping creation of dummy platform device in of_syscon_register.
- As we are changing syscon to decouple from platform_device, creation of
dummy platform_device does not look good option, and as suggested by Arnd,
I made another attempt so that regmap_mmio_init API should work with NULL
dev pointer itself. Since regmap needs to know about Syscon device node
properties so let's parse device node of syscon in syscon itself for any
such properties and using regmap_config parameter pass all such information
to regmap. Other concern of crashes due to NULL dev pointer in regmap already
addressed in separate patches of regmap. Please see [2] and [3].
- Addressed Tomasz Figa's comments for v4.
- Added error handing in of_syscon_register function.
- Using devm_regmap_init_mmio instead of regmap_init_mmio.
- Addressed Arnd's comment for v2.
- Updated of_syscon_register for adding dev pointer in regmap_init_mmio.
- For early users created dummy platform device.
- Added back platform device support from syscon, with one change that
syscon will not be probed for DT based platform.
- Added back syscon_regmap_lookup_by_pdevname API so that non-DT base
users of syscon will not be broken.
- Removed unwanted change in syscon.h.
- Modified Signed-off-by list, added Suggested-by of Tomasz Figa and
Arnd Bergmann.
- Added Tested-by of Vivek Gautam for testing on Exynos platform.
- Removed of_syscon_unregister function.
- Modified of_syscon_register function and it will be used by syscon.c
to create syscon objects whenever required.
- Removed platform device support from syscon.
- Removed syscon_regmap_lookup_by_pdevname API support.
- As there are significant changes w.r.t patchset v1, I am taking over
author for this patchset from Tomasz Figa.
[1]: https://lkml.org/lkml/2014/9/29/99
[2]: https://lkml.org/lkml/2014/9/18/130
[3]: https://lkml.org/lkml/2014/9/27/2
drivers/mfd/syscon.c | 96 ++++++++++++++++++++++++++++++++++++++------------
1 file changed, 74 insertions(+), 22 deletions(-)
You probably already have enough tags, but just in case. ;) On an
rk3288-based system (this patch backported to 3.14):

Tested-by: Doug Anderson <***@chromium.org>
Pankaj Dubey
2014-10-06 09:02:54 UTC
Permalink
Hi Lee,

On Tuesday, September 30, 2014 9:39 PM Doug Anderson wrote,
Subject: Re: [PATCH v7] mfd: syscon: Decouple syscon interface from platform
devices
Pankaj,
Post by Pankaj Dubey
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface provider.
For example, certain SoCs (e.g. Exynos) contain system controller
blocks which perform various functions such as power domain control,
CPU power management, low power mode control, but in addition contain
certain IP integration glue, such as various signal masks, coprocessor
power control, etc. In such case, there is a need to have a dedicated
driver for such system controller but also share registers with other
drivers. The latter is where the syscon interface is helpful.
In case of DT based platforms, this patch decouples syscon object from
syscon platform driver, and allows to create syscon objects first time
when it is required by calling of syscon_regmap_lookup_by APIs and
keep a list of such syscon objects along with syscon provider
device_nodes and regmap handles.
For non-DT based platforms, this patch keeps syscon platform driver
structure so that syscon can be probed and such non-DT based drivers
can use syscon_regmap_lookup_by_pdev API and access regmap handles.
Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT based,
we can completely remove platform driver of syscon, and keep only
helper functions to get regmap handles.
---
Patch v6 and related discussions can be found here [1].
- Addressed review comments from "Heiko Stuebner".
- Updated commit description.
- Including Arnd's and Heiko's Reviewed-by.
- Dropping creation of dummy platform device in of_syscon_register.
- As we are changing syscon to decouple from platform_device, creation of
dummy platform_device does not look good option, and as suggested by Arnd,
I made another attempt so that regmap_mmio_init API should work with NULL
dev pointer itself. Since regmap needs to know about Syscon device node
properties so let's parse device node of syscon in syscon itself for any
such properties and using regmap_config parameter pass all such information
to regmap. Other concern of crashes due to NULL dev pointer in regmap already
addressed in separate patches of regmap. Please see [2] and [3].
- Addressed Tomasz Figa's comments for v4.
- Added error handing in of_syscon_register function.
- Using devm_regmap_init_mmio instead of regmap_init_mmio.
- Addressed Arnd's comment for v2.
- Updated of_syscon_register for adding dev pointer in regmap_init_mmio.
- For early users created dummy platform device.
- Added back platform device support from syscon, with one change that
syscon will not be probed for DT based platform.
- Added back syscon_regmap_lookup_by_pdevname API so that non-DT base
users of syscon will not be broken.
- Removed unwanted change in syscon.h.
- Modified Signed-off-by list, added Suggested-by of Tomasz Figa and
Arnd Bergmann.
- Added Tested-by of Vivek Gautam for testing on Exynos platform.
- Removed of_syscon_unregister function.
- Modified of_syscon_register function and it will be used by syscon.c
to create syscon objects whenever required.
- Removed platform device support from syscon.
- Removed syscon_regmap_lookup_by_pdevname API support.
- As there are significant changes w.r.t patchset v1, I am taking over
author for this patchset from Tomasz Figa.
[1]: https://lkml.org/lkml/2014/9/29/99
[2]: https://lkml.org/lkml/2014/9/18/130
[3]: https://lkml.org/lkml/2014/9/27/2
drivers/mfd/syscon.c | 96
++++++++++++++++++++++++++++++++++++++------------
Post by Pankaj Dubey
1 file changed, 74 insertions(+), 22 deletions(-)
You probably already have enough tags, but just in case. ;) On an rk3288-based
I think now we can take have this patch in. So will you please take this patch.

Thanks,
Pankaj Dubey
Lee Jones
2014-10-06 16:27:32 UTC
Permalink
Post by Pankaj Dubey
Hi Lee,
=20
On Tuesday, September 30, 2014 9:39 PM Doug Anderson wrote,
Subject: Re: [PATCH v7] mfd: syscon: Decouple syscon interface from=
platform
Post by Pankaj Dubey
devices
=20
Pankaj,
=20
=2Ecom>
Post by Pankaj Dubey
Currently a syscon entity can be only registered directly through=
a
Post by Pankaj Dubey
platform device that binds to a dedicated syscon driver. However =
in
Post by Pankaj Dubey
certain use cases it is desirable to make a device used with anot=
her
Post by Pankaj Dubey
driver a syscon interface provider.
For example, certain SoCs (e.g. Exynos) contain system controller
blocks which perform various functions such as power domain contr=
ol,
Post by Pankaj Dubey
CPU power management, low power mode control, but in addition con=
tain
Post by Pankaj Dubey
certain IP integration glue, such as various signal masks, coproc=
essor
Post by Pankaj Dubey
power control, etc. In such case, there is a need to have a dedic=
ated
Post by Pankaj Dubey
driver for such system controller but also share registers with o=
ther
Post by Pankaj Dubey
drivers. The latter is where the syscon interface is helpful.
In case of DT based platforms, this patch decouples syscon object=
from
Post by Pankaj Dubey
syscon platform driver, and allows to create syscon objects first=
time
Post by Pankaj Dubey
when it is required by calling of syscon_regmap_lookup_by APIs an=
d
Post by Pankaj Dubey
keep a list of such syscon objects along with syscon provider
device_nodes and regmap handles.
For non-DT based platforms, this patch keeps syscon platform driv=
er
Post by Pankaj Dubey
structure so that syscon can be probed and such non-DT based driv=
ers
Post by Pankaj Dubey
can use syscon_regmap_lookup_by_pdev API and access regmap handle=
s.
Post by Pankaj Dubey
Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT b=
ased,
Post by Pankaj Dubey
we can completely remove platform driver of syscon, and keep only
helper functions to get regmap handles.
=2Euk>
Post by Pankaj Dubey
---
Patch v6 and related discussions can be found here [1].
- Addressed review comments from "Heiko Stuebner".
- Updated commit description.
- Including Arnd's and Heiko's Reviewed-by.
- Dropping creation of dummy platform device in of_syscon_regist=
er.
Post by Pankaj Dubey
- As we are changing syscon to decouple from platform_device, cr=
eation of
Post by Pankaj Dubey
dummy platform_device does not look good option, and as sugges=
ted by Arnd,
Post by Pankaj Dubey
I made another attempt so that regmap_mmio_init API should wor=
k with NULL
Post by Pankaj Dubey
dev pointer itself. Since regmap needs to know about Syscon de=
vice node
Post by Pankaj Dubey
properties so let's parse device node of syscon in syscon itse=
lf for any
Post by Pankaj Dubey
such properties and using regmap_config parameter pass all suc=
h information
Post by Pankaj Dubey
to regmap. Other concern of crashes due to NULL dev pointer in=
regmap already
Post by Pankaj Dubey
addressed in separate patches of regmap. Please see [2] and [3=
].
Post by Pankaj Dubey
- Addressed Tomasz Figa's comments for v4.
- Added error handing in of_syscon_register function.
- Using devm_regmap_init_mmio instead of regmap_init_mmio.
- Addressed Arnd's comment for v2.
- Updated of_syscon_register for adding dev pointer in regmap_in=
it_mmio.
Post by Pankaj Dubey
- For early users created dummy platform device.
- Added back platform device support from syscon, with one chang=
e that
Post by Pankaj Dubey
syscon will not be probed for DT based platform.
- Added back syscon_regmap_lookup_by_pdevname API so that non-DT=
base
Post by Pankaj Dubey
users of syscon will not be broken.
- Removed unwanted change in syscon.h.
- Modified Signed-off-by list, added Suggested-by of Tomasz Figa=
and
Post by Pankaj Dubey
Arnd Bergmann.
- Added Tested-by of Vivek Gautam for testing on Exynos platform=
=2E
Post by Pankaj Dubey
- Removed of_syscon_unregister function.
- Modified of_syscon_register function and it will be used by sy=
scon.c
Post by Pankaj Dubey
to create syscon objects whenever required.
- Removed platform device support from syscon.
- Removed syscon_regmap_lookup_by_pdevname API support.
- As there are significant changes w.r.t patchset v1, I am takin=
g over
Post by Pankaj Dubey
author for this patchset from Tomasz Figa.
[1]: https://lkml.org/lkml/2014/9/29/99
[2]: https://lkml.org/lkml/2014/9/18/130
[3]: https://lkml.org/lkml/2014/9/27/2
drivers/mfd/syscon.c | 96
++++++++++++++++++++++++++++++++++++++------------
1 file changed, 74 insertions(+), 22 deletions(-)
=20
You probably already have enough tags, but just in case. ;) On an=
rk3288-based
Post by Pankaj Dubey
=20
=20
I think now we can take have this patch in. So will you please take t=
his patch.

I plan to take this when the merge window has closed.

--=20
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org =E2=94=82 Open source software for ARM SoCs
=46ollow Linaro: Facebook | Twitter | Blog
Lee Jones
2014-10-07 09:09:23 UTC
Permalink
Post by Pankaj Dubey
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface provider.
=20
For example, certain SoCs (e.g. Exynos) contain system controller
blocks which perform various functions such as power domain control,
CPU power management, low power mode control, but in addition contain
certain IP integration glue, such as various signal masks,
coprocessor power control, etc. In such case, there is a need to have
a dedicated driver for such system controller but also share register=
s
Post by Pankaj Dubey
with other drivers. The latter is where the syscon interface is helpf=
ul.
Post by Pankaj Dubey
=20
In case of DT based platforms, this patch decouples syscon object fro=
m
Post by Pankaj Dubey
syscon platform driver, and allows to create syscon objects first tim=
e
Post by Pankaj Dubey
when it is required by calling of syscon_regmap_lookup_by APIs and ke=
ep
Post by Pankaj Dubey
a list of such syscon objects along with syscon provider device_nodes
and regmap handles.
=20
For non-DT based platforms, this patch keeps syscon platform driver
structure so that syscon can be probed and such non-DT based drivers
can use syscon_regmap_lookup_by_pdev API and access regmap handles.
Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT based=
,
Post by Pankaj Dubey
we can completely remove platform driver of syscon, and keep only hel=
per
Post by Pankaj Dubey
functions to get regmap handles.
=20
Applied for v3.19.
Post by Pankaj Dubey
---
Patch v6 and related discussions can be found here [1].
=20
- Addressed review comments from "Heiko Stuebner".
- Updated commit description.
- Including Arnd's and Heiko's Reviewed-by.
=20
- Dropping creation of dummy platform device in of_syscon_register.
- As we are changing syscon to decouple from platform_device, creati=
on of=20
Post by Pankaj Dubey
dummy platform_device does not look good option, and as suggested =
by Arnd,
Post by Pankaj Dubey
I made another attempt so that regmap_mmio_init API should work wi=
th NULL
Post by Pankaj Dubey
dev pointer itself. Since regmap needs to know about Syscon device=
node
Post by Pankaj Dubey
properties so let's parse device node of syscon in syscon itself f=
or any
Post by Pankaj Dubey
such properties and using regmap_config parameter pass all such in=
formation
Post by Pankaj Dubey
to regmap. Other concern of crashes due to NULL dev pointer in reg=
map already
Post by Pankaj Dubey
addressed in separate patches of regmap. Please see [2] and [3].
=20
- Addressed Tomasz Figa's comments for v4.
- Added error handing in of_syscon_register function.
- Using devm_regmap_init_mmio instead of regmap_init_mmio.
=20
- Addressed Arnd's comment for v2.
- Updated of_syscon_register for adding dev pointer in regmap_init_m=
mio.
Post by Pankaj Dubey
- For early users created dummy platform device.
=20
- Added back platform device support from syscon, with one change th=
at
Post by Pankaj Dubey
syscon will not be probed for DT based platform.
- Added back syscon_regmap_lookup_by_pdevname API so that non-DT bas=
e
Post by Pankaj Dubey
users of syscon will not be broken.
- Removed unwanted change in syscon.h.
- Modified Signed-off-by list, added Suggested-by of Tomasz Figa and
Arnd Bergmann.
- Added Tested-by of Vivek Gautam for testing on Exynos platform.
=20
- Removed of_syscon_unregister function.
- Modified of_syscon_register function and it will be used by syscon=
=2Ec
Post by Pankaj Dubey
to create syscon objects whenever required.
- Removed platform device support from syscon.
- Removed syscon_regmap_lookup_by_pdevname API support.
- As there are significant changes w.r.t patchset v1, I am taking ov=
er
Post by Pankaj Dubey
author for this patchset from Tomasz Figa.
=20
[1]: https://lkml.org/lkml/2014/9/29/99
[2]: https://lkml.org/lkml/2014/9/18/130
[3]: https://lkml.org/lkml/2014/9/27/2
drivers/mfd/syscon.c | 96 ++++++++++++++++++++++++++++++++++++++--=
----------
Post by Pankaj Dubey
1 file changed, 74 insertions(+), 22 deletions(-)
=20
diff --git a/drivers/mfd/syscon.c b/drivers/mfd/syscon.c
index ca15878..72373b1 100644
--- a/drivers/mfd/syscon.c
+++ b/drivers/mfd/syscon.c
@@ -15,6 +15,7 @@
#include <linux/err.h>
#include <linux/io.h>
#include <linux/module.h>
+#include <linux/list.h>
#include <linux/of.h>
#include <linux/of_address.h>
#include <linux/of_platform.h>
@@ -22,31 +23,94 @@
#include <linux/platform_device.h>
#include <linux/regmap.h>
#include <linux/mfd/syscon.h>
+#include <linux/slab.h>
=20
static struct platform_driver syscon_driver;
=20
+static DEFINE_SPINLOCK(syscon_list_slock);
+static LIST_HEAD(syscon_list);
+
struct syscon {
+ struct device_node *np;
struct regmap *regmap;
+ struct list_head list;
+};
+
+static struct regmap_config syscon_regmap_config =3D {
+ .reg_bits =3D 32,
+ .val_bits =3D 32,
+ .reg_stride =3D 4,
};
=20
-static int syscon_match_node(struct device *dev, void *data)
+static struct syscon *of_syscon_register(struct device_node *np)
{
- struct device_node *dn =3D data;
+ struct syscon *syscon;
+ struct regmap *regmap;
+ void __iomem *base;
+ int ret;
+ struct regmap_config syscon_config =3D syscon_regmap_config;
+
+ if (!of_device_is_compatible(np, "syscon"))
+ return ERR_PTR(-EINVAL);
+
+ syscon =3D kzalloc(sizeof(*syscon), GFP_KERNEL);
+ if (!syscon)
+ return ERR_PTR(-ENOMEM);
+
+ base =3D of_iomap(np, 0);
+ if (!base) {
+ ret =3D -ENOMEM;
+ goto err_map;
+ }
+
+ /* Parse the device's DT node for an endianness specification */
+ if (of_property_read_bool(np, "big-endian"))
+ syscon_config.val_format_endian =3D REGMAP_ENDIAN_BIG;
+ else if (of_property_read_bool(np, "little-endian"))
+ syscon_config.val_format_endian =3D REGMAP_ENDIAN_LITTLE;
+
+ regmap =3D regmap_init_mmio(NULL, base, &syscon_config);
+ if (IS_ERR(regmap)) {
+ pr_err("regmap init failed\n");
+ ret =3D PTR_ERR(regmap);
+ goto err_regmap;
+ }
+
+ syscon->regmap =3D regmap;
+ syscon->np =3D np;
+
+ spin_lock(&syscon_list_slock);
+ list_add_tail(&syscon->list, &syscon_list);
+ spin_unlock(&syscon_list_slock);
=20
- return (dev->of_node =3D=3D dn) ? 1 : 0;
+ return syscon;
+
+ iounmap(base);
+ kfree(syscon);
+ return ERR_PTR(ret);
}
=20
struct regmap *syscon_node_to_regmap(struct device_node *np)
{
- struct syscon *syscon;
- struct device *dev;
+ struct syscon *entry, *syscon =3D NULL;
=20
- dev =3D driver_find_device(&syscon_driver.driver, NULL, np,
- syscon_match_node);
- if (!dev)
- return ERR_PTR(-EPROBE_DEFER);
+ spin_lock(&syscon_list_slock);
=20
- syscon =3D dev_get_drvdata(dev);
+ list_for_each_entry(entry, &syscon_list, list)
+ if (entry->np =3D=3D np) {
+ syscon =3D entry;
+ break;
+ }
+
+ spin_unlock(&syscon_list_slock);
+
+ if (!syscon)
+ syscon =3D of_syscon_register(np);
+
+ if (IS_ERR(syscon))
+ return ERR_CAST(syscon);
=20
return syscon->regmap;
}
@@ -110,17 +174,6 @@ struct regmap *syscon_regmap_lookup_by_phandle(s=
truct device_node *np,
Post by Pankaj Dubey
}
EXPORT_SYMBOL_GPL(syscon_regmap_lookup_by_phandle);
=20
-static const struct of_device_id of_syscon_match[] =3D {
- { .compatible =3D "syscon", },
- { },
-};
-
-static struct regmap_config syscon_regmap_config =3D {
- .reg_bits =3D 32,
- .val_bits =3D 32,
- .reg_stride =3D 4,
-};
-
static int syscon_probe(struct platform_device *pdev)
{
struct device *dev =3D &pdev->dev;
@@ -167,7 +220,6 @@ static struct platform_driver syscon_driver =3D {
.driver =3D {
.name =3D "syscon",
.owner =3D THIS_MODULE,
- .of_match_table =3D of_syscon_match,
},
.probe =3D syscon_probe,
.id_table =3D syscon_ids,
--=20
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org =E2=94=82 Open source software for ARM SoCs
=46ollow Linaro: Facebook | Twitter | Blog
Pankaj Dubey
2014-10-22 11:06:28 UTC
Permalink
Hello Lee,

On Tuesday, October 07, 2014 2:39 PM, Lee Jones wrote,
Post by Lee Jones
=20
Post by Pankaj Dubey
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with anothe=
r
Post by Lee Jones
Post by Pankaj Dubey
driver a syscon interface provider.
For example, certain SoCs (e.g. Exynos) contain system controller
blocks which perform various functions such as power domain control=
,
Post by Lee Jones
Post by Pankaj Dubey
CPU power management, low power mode control, but in addition conta=
in
Post by Lee Jones
Post by Pankaj Dubey
certain IP integration glue, such as various signal masks, coproces=
sor
Post by Lee Jones
Post by Pankaj Dubey
power control, etc. In such case, there is a need to have a dedicat=
ed
Post by Lee Jones
Post by Pankaj Dubey
driver for such system controller but also share registers with oth=
er
Post by Lee Jones
Post by Pankaj Dubey
drivers. The latter is where the syscon interface is helpful.
In case of DT based platforms, this patch decouples syscon object f=
rom
Post by Lee Jones
Post by Pankaj Dubey
syscon platform driver, and allows to create syscon objects first t=
ime
Post by Lee Jones
Post by Pankaj Dubey
when it is required by calling of syscon_regmap_lookup_by APIs and
keep a list of such syscon objects along with syscon provider
device_nodes and regmap handles.
For non-DT based platforms, this patch keeps syscon platform driver
structure so that syscon can be probed and such non-DT based driver=
s
Post by Lee Jones
Post by Pankaj Dubey
can use syscon_regmap_lookup_by_pdev API and access regmap handles.
Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT bas=
ed,
Post by Lee Jones
Post by Pankaj Dubey
we can completely remove platform driver of syscon, and keep only
helper functions to get regmap handles.
k>
Post by Lee Jones
=20
Applied for v3.19.
I can't see this in 3.18-rc1, as this patch is one of dependency for ma=
ny of Exynos PMU related patches,
will you please queue this patch for 3.18-rc2, so that already ready to=
be in patches having this patch as
dependency can be taken in.

Thanks,
Pankaj Dubey
Post by Lee Jones
=20
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead Linaro.org =E2=94=82 Open=
source software
Post by Lee Jones
for ARM SoCs Follow Linaro: Facebook | Twitter | Blog
Lee Jones
2014-10-22 12:12:19 UTC
Permalink
Post by Pankaj Dubey
Hello Lee,
=20
On Tuesday, October 07, 2014 2:39 PM, Lee Jones wrote,
Post by Lee Jones
=20
Currently a syscon entity can be only registered directly through=
a
Post by Pankaj Dubey
Post by Lee Jones
platform device that binds to a dedicated syscon driver. However =
in
Post by Pankaj Dubey
Post by Lee Jones
certain use cases it is desirable to make a device used with anot=
her
Post by Pankaj Dubey
Post by Lee Jones
driver a syscon interface provider.
For example, certain SoCs (e.g. Exynos) contain system controller
blocks which perform various functions such as power domain contr=
ol,
Post by Pankaj Dubey
Post by Lee Jones
CPU power management, low power mode control, but in addition con=
tain
Post by Pankaj Dubey
Post by Lee Jones
certain IP integration glue, such as various signal masks, coproc=
essor
Post by Pankaj Dubey
Post by Lee Jones
power control, etc. In such case, there is a need to have a dedic=
ated
Post by Pankaj Dubey
Post by Lee Jones
driver for such system controller but also share registers with o=
ther
Post by Pankaj Dubey
Post by Lee Jones
drivers. The latter is where the syscon interface is helpful.
In case of DT based platforms, this patch decouples syscon object=
from
Post by Pankaj Dubey
Post by Lee Jones
syscon platform driver, and allows to create syscon objects first=
time
Post by Pankaj Dubey
Post by Lee Jones
when it is required by calling of syscon_regmap_lookup_by APIs an=
d
Post by Pankaj Dubey
Post by Lee Jones
keep a list of such syscon objects along with syscon provider
device_nodes and regmap handles.
For non-DT based platforms, this patch keeps syscon platform driv=
er
Post by Pankaj Dubey
Post by Lee Jones
structure so that syscon can be probed and such non-DT based driv=
ers
Post by Pankaj Dubey
Post by Lee Jones
can use syscon_regmap_lookup_by_pdev API and access regmap handle=
s.
Post by Pankaj Dubey
Post by Lee Jones
Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT b=
ased,
Post by Pankaj Dubey
Post by Lee Jones
we can completely remove platform driver of syscon, and keep only
helper functions to get regmap handles.
=2Euk>
Post by Pankaj Dubey
Post by Lee Jones
=20
Applied for v3.19.
=20
I can't see this in 3.18-rc1, as this patch is one of dependency for =
many of Exynos PMU related patches,
Post by Pankaj Dubey
will you please queue this patch for 3.18-rc2, so that already ready =
to be in patches having this patch as
Post by Pankaj Dubey
dependency can be taken in.
As my message implies, this isn't going to make it into v3.18 but it
is queued for v3.19. It was sent far too late in the cycle (rc7 of 7)
to make it into the v3.18 merge-window.

In the meantime, please give this patch through testing whilst it's in
-next, to help mitigate any issues when it's applied into v3.19.

--=20
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org =E2=94=82 Open source software for ARM SoCs
=46ollow Linaro: Facebook | Twitter | Blog

Loading...