| Message ID | 20191023082423.12569-3-ran.wang_1@nxp.com (mailing list archive) |
|---|---|
| State | Deferred |
| Headers | show |
| Series | [v9,1/3] PM: wakeup: Add routine to help fetch wakeup source object. | expand |
On Wed, Oct 23, 2019 at 10:24 AM Ran Wang <ran.wang_1@nxp.com> wrote: > > The NXP's QorIQ Processors based on ARM Core have RCPM module > (Run Control and Power Management), which performs system level > tasks associated with power management such as wakeup source control. > > This driver depends on PM wakeup source framework which help to > collect wake information. > > Signed-off-by: Ran Wang <ran.wang_1@nxp.com> > --- > Change in v9: > - Add kerneldoc for rcpm_pm_prepare(). > - Use pr_debug() to replace dev_info(), to print message when decide > skip current wakeup object, this is mainly for debugging (in order > to detect potential improper implementation on device tree which > might cause this skip). > - Refactor looping implementation in rcpm_pm_prepare(), add more > comments to help clarify. > > Change in v8: > - Adjust related API usage to meet wakeup.c's update in patch 1/3. > - Add sanity checking for the case of ws->dev or ws->dev->parent > is null. > > Change in v7: > - Replace 'ws->dev' with 'ws->dev->parent' to get aligned with > c8377adfa781 ("PM / wakeup: Show wakeup sources stats in sysfs") > - Remove '+obj-y += ftm_alarm.o' since it is wrong. > - Cosmetic work. > > Change in v6: > - Adjust related API usage to meet wakeup.c's update in patch 1/3. > > Change in v5: > - Fix v4 regression of the return value of wakeup_source_get_next() > didn't pass to ws in while loop. > - Rename wakeup_source member 'attached_dev' to 'dev'. > - Rename property 'fsl,#rcpm-wakeup-cells' to '#fsl,rcpm-wakeup-cells'. > please see https://lore.kernel.org/patchwork/patch/1101022/ > > Change in v4: > - Remove extra ',' in author line of rcpm.c > - Update usage of wakeup_source_get_next() to be less confusing to the > reader, code logic remain the same. > > Change in v3: > - Some whitespace ajdustment. > > Change in v2: > - Rebase Kconfig and Makefile update to latest mainline. > > drivers/soc/fsl/Kconfig | 8 +++ > drivers/soc/fsl/Makefile | 1 + > drivers/soc/fsl/rcpm.c | 148 +++++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 157 insertions(+) > create mode 100644 drivers/soc/fsl/rcpm.c > > diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig > index f9ad8ad..4918856 100644 > --- a/drivers/soc/fsl/Kconfig > +++ b/drivers/soc/fsl/Kconfig > @@ -40,4 +40,12 @@ config DPAA2_CONSOLE > /dev/dpaa2_mc_console and /dev/dpaa2_aiop_console, > which can be used to dump the Management Complex and AIOP > firmware logs. > + > +config FSL_RCPM > + bool "Freescale RCPM support" > + depends on PM_SLEEP > + help > + The NXP QorIQ Processors based on ARM Core have RCPM module > + (Run Control and Power Management), which performs all device-level > + tasks associated with power management, such as wakeup source control. > endmenu > diff --git a/drivers/soc/fsl/Makefile b/drivers/soc/fsl/Makefile > index 71dee8d..906f1cd 100644 > --- a/drivers/soc/fsl/Makefile > +++ b/drivers/soc/fsl/Makefile > @@ -6,6 +6,7 @@ > obj-$(CONFIG_FSL_DPAA) += qbman/ > obj-$(CONFIG_QUICC_ENGINE) += qe/ > obj-$(CONFIG_CPM) += qe/ > +obj-$(CONFIG_FSL_RCPM) += rcpm.o > obj-$(CONFIG_FSL_GUTS) += guts.o > obj-$(CONFIG_FSL_MC_DPIO) += dpio/ > obj-$(CONFIG_DPAA2_CONSOLE) += dpaa2-console.o > diff --git a/drivers/soc/fsl/rcpm.c b/drivers/soc/fsl/rcpm.c > new file mode 100644 > index 0000000..9378073 > --- /dev/null > +++ b/drivers/soc/fsl/rcpm.c > @@ -0,0 +1,148 @@ > +// SPDX-License-Identifier: GPL-2.0 > +// > +// rcpm.c - Freescale QorIQ RCPM driver > +// > +// Copyright 2019 NXP > +// > +// Author: Ran Wang <ran.wang_1@nxp.com> > + > +#include <linux/init.h> > +#include <linux/module.h> > +#include <linux/platform_device.h> > +#include <linux/of_address.h> > +#include <linux/slab.h> > +#include <linux/suspend.h> > +#include <linux/kernel.h> > + > +#define RCPM_WAKEUP_CELL_MAX_SIZE 7 > + > +struct rcpm { > + unsigned int wakeup_cells; > + void __iomem *ippdexpcr_base; > + bool little_endian; > +}; > + > +/** > + * rcpm_pm_prepare - performs device-level tasks associated with power > + * management, such as programming related to the wakeup source control. > + * @dev: Device to handle. > + * > + */ > +static int rcpm_pm_prepare(struct device *dev) > +{ > + int i, ret, idx; > + void __iomem *base; > + struct wakeup_source *ws; > + struct rcpm *rcpm; > + struct device_node *np = dev->of_node; > + u32 value[RCPM_WAKEUP_CELL_MAX_SIZE + 1]; > + > + rcpm = dev_get_drvdata(dev); > + if (!rcpm) > + return -EINVAL; > + > + base = rcpm->ippdexpcr_base; > + idx = wakeup_sources_read_lock(); > + > + /* Begin with first registered wakeup source */ > + for_each_wakeup_source(ws) { > + > + /* skip object which is not attached to device */ > + if (!ws->dev || !ws->dev->parent) > + continue; > + > + ret = device_property_read_u32_array(ws->dev->parent, > + "fsl,rcpm-wakeup", value, > + rcpm->wakeup_cells + 1); > + > + /* Wakeup source should refer to current rcpm device */ > + if (ret || (np->phandle != value[0])) { > + pr_debug("%s doesn't refer to this rcpm\n", ws->name); I'm still quite unsure why it is useful to print this message instead of printing one when the wakeup source does match (there may be many wakeup source objects you don't care about in principle), but whatever. > + continue; > + } > + > + /* Property "#fsl,rcpm-wakeup-cells" of rcpm node defines the > + * number of IPPDEXPCR register cells, and "fsl,rcpm-wakeup" > + * of wakeup source IP contains an integer array: <phandle to > + * RCPM node, IPPDEXPCR0 setting, IPPDEXPCR1 setting, > + * IPPDEXPCR2 setting, etc>. > + * > + * So we will go thought them and do programming accordngly. > + */ > + for (i = 0; i < rcpm->wakeup_cells; i++) { > + u32 tmp = value[i + 1]; > + void __iomem *address = base + i * 4; > + > + if (!tmp) > + continue; > + > + /* We can only OR related bits */ > + if (rcpm->little_endian) { > + tmp |= ioread32(address); > + iowrite32(tmp, address); > + } else { > + tmp |= ioread32be(address); > + iowrite32be(tmp, address); > + } > + } > + } > + > + wakeup_sources_read_unlock(idx); > + > + return 0; > +} > + > +static const struct dev_pm_ops rcpm_pm_ops = { > + .prepare = rcpm_pm_prepare, > +}; For the above: Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Hi Rafael, On Wednesday, October 23, 2019 17:12, Rafael J. Wysocki wrote: > > On Wed, Oct 23, 2019 at 10:24 AM Ran Wang <ran.wang_1@nxp.com> wrote: > > > > The NXP's QorIQ Processors based on ARM Core have RCPM module (Run > > Control and Power Management), which performs system level tasks > > associated with power management such as wakeup source control. > > > > This driver depends on PM wakeup source framework which help to > > collect wake information. > > > > Signed-off-by: Ran Wang <ran.wang_1@nxp.com> > > --- > > Change in v9: > > - Add kerneldoc for rcpm_pm_prepare(). > > - Use pr_debug() to replace dev_info(), to print message when decide > > skip current wakeup object, this is mainly for debugging (in order > > to detect potential improper implementation on device tree which > > might cause this skip). > > - Refactor looping implementation in rcpm_pm_prepare(), add more > > comments to help clarify. > > > > Change in v8: > > - Adjust related API usage to meet wakeup.c's update in patch 1/3. > > - Add sanity checking for the case of ws->dev or ws->dev->parent > > is null. > > <snip> > > + > > + /* Wakeup source should refer to current rcpm device */ > > + if (ret || (np->phandle != value[0])) { > > + pr_debug("%s doesn't refer to this rcpm\n", > > + ws->name); > > I'm still quite unsure why it is useful to print this message instead of printing one > when the wakeup source does match (there may be many wakeup source > objects you don't care about in principle), but whatever. OK, my previous idea was that user might likely mis-understand related description in bindings when adding node and property "fsl,rcpm-wakeup". Add this print might help him/her to get alerted that RCPM driver doesn't successfully parsing info which they didn't expect. Currently on LS1088ARDB board, I can only see one wakeup source the RCPM driver doesn’t need to care. > > + continue; > > + } > > + > > + /* Property "#fsl,rcpm-wakeup-cells" of rcpm node defines the > > + * number of IPPDEXPCR register cells, and "fsl,rcpm-wakeup" > > + * of wakeup source IP contains an integer array: <phandle to > > + * RCPM node, IPPDEXPCR0 setting, IPPDEXPCR1 setting, > > + * IPPDEXPCR2 setting, etc>. > > + * > > + * So we will go thought them and do programming accordngly. > > + */ > > + for (i = 0; i < rcpm->wakeup_cells; i++) { > > + u32 tmp = value[i + 1]; > > + void __iomem *address = base + i * 4; > > + > > + if (!tmp) > > + continue; > > + > > + /* We can only OR related bits */ > > + if (rcpm->little_endian) { > > + tmp |= ioread32(address); > > + iowrite32(tmp, address); > > + } else { > > + tmp |= ioread32be(address); > > + iowrite32be(tmp, address); > > + } > > + } > > + } > > + > > + wakeup_sources_read_unlock(idx); > > + > > + return 0; > > +} > > + > > +static const struct dev_pm_ops rcpm_pm_ops = { > > + .prepare = rcpm_pm_prepare, > > +}; > > For the above: > > Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Thanks for your time. Regards, Ran
On Wed, Oct 23, 2019 at 3:24 AM Ran Wang <ran.wang_1@nxp.com> wrote: > > The NXP's QorIQ Processors based on ARM Core have RCPM module Actually not just ARM based QorIQ processors are having RCPM, PowerPC based QorIQ SoCs also have RCPM. Does this driver also work with the PowerPC SoCs? Please clarify in the commit message and Kconfig description. > (Run Control and Power Management), which performs system level > tasks associated with power management such as wakeup source control. > > This driver depends on PM wakeup source framework which help to > collect wake information. > > Signed-off-by: Ran Wang <ran.wang_1@nxp.com> > --- > Change in v9: > - Add kerneldoc for rcpm_pm_prepare(). > - Use pr_debug() to replace dev_info(), to print message when decide > skip current wakeup object, this is mainly for debugging (in order > to detect potential improper implementation on device tree which > might cause this skip). > - Refactor looping implementation in rcpm_pm_prepare(), add more > comments to help clarify. > > Change in v8: > - Adjust related API usage to meet wakeup.c's update in patch 1/3. > - Add sanity checking for the case of ws->dev or ws->dev->parent > is null. > > Change in v7: > - Replace 'ws->dev' with 'ws->dev->parent' to get aligned with > c8377adfa781 ("PM / wakeup: Show wakeup sources stats in sysfs") > - Remove '+obj-y += ftm_alarm.o' since it is wrong. > - Cosmetic work. > > Change in v6: > - Adjust related API usage to meet wakeup.c's update in patch 1/3. > > Change in v5: > - Fix v4 regression of the return value of wakeup_source_get_next() > didn't pass to ws in while loop. > - Rename wakeup_source member 'attached_dev' to 'dev'. > - Rename property 'fsl,#rcpm-wakeup-cells' to '#fsl,rcpm-wakeup-cells'. > please see https://lore.kernel.org/patchwork/patch/1101022/ > > Change in v4: > - Remove extra ',' in author line of rcpm.c > - Update usage of wakeup_source_get_next() to be less confusing to the > reader, code logic remain the same. > > Change in v3: > - Some whitespace ajdustment. > > Change in v2: > - Rebase Kconfig and Makefile update to latest mainline. > > drivers/soc/fsl/Kconfig | 8 +++ > drivers/soc/fsl/Makefile | 1 + > drivers/soc/fsl/rcpm.c | 148 +++++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 157 insertions(+) > create mode 100644 drivers/soc/fsl/rcpm.c > > diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig > index f9ad8ad..4918856 100644 > --- a/drivers/soc/fsl/Kconfig > +++ b/drivers/soc/fsl/Kconfig > @@ -40,4 +40,12 @@ config DPAA2_CONSOLE > /dev/dpaa2_mc_console and /dev/dpaa2_aiop_console, > which can be used to dump the Management Complex and AIOP > firmware logs. > + > +config FSL_RCPM > + bool "Freescale RCPM support" > + depends on PM_SLEEP If this is only for ARM, probably add more dependency here? > + help > + The NXP QorIQ Processors based on ARM Core have RCPM module > + (Run Control and Power Management), which performs all device-level > + tasks associated with power management, such as wakeup source control. > endmenu > diff --git a/drivers/soc/fsl/Makefile b/drivers/soc/fsl/Makefile > index 71dee8d..906f1cd 100644 > --- a/drivers/soc/fsl/Makefile > +++ b/drivers/soc/fsl/Makefile > @@ -6,6 +6,7 @@ > obj-$(CONFIG_FSL_DPAA) += qbman/ > obj-$(CONFIG_QUICC_ENGINE) += qe/ > obj-$(CONFIG_CPM) += qe/ > +obj-$(CONFIG_FSL_RCPM) += rcpm.o > obj-$(CONFIG_FSL_GUTS) += guts.o > obj-$(CONFIG_FSL_MC_DPIO) += dpio/ > obj-$(CONFIG_DPAA2_CONSOLE) += dpaa2-console.o > diff --git a/drivers/soc/fsl/rcpm.c b/drivers/soc/fsl/rcpm.c > new file mode 100644 > index 0000000..9378073 > --- /dev/null > +++ b/drivers/soc/fsl/rcpm.c > @@ -0,0 +1,148 @@ > +// SPDX-License-Identifier: GPL-2.0 > +// > +// rcpm.c - Freescale QorIQ RCPM driver > +// > +// Copyright 2019 NXP > +// > +// Author: Ran Wang <ran.wang_1@nxp.com> > + > +#include <linux/init.h> > +#include <linux/module.h> > +#include <linux/platform_device.h> > +#include <linux/of_address.h> > +#include <linux/slab.h> > +#include <linux/suspend.h> > +#include <linux/kernel.h> > + > +#define RCPM_WAKEUP_CELL_MAX_SIZE 7 > + > +struct rcpm { > + unsigned int wakeup_cells; > + void __iomem *ippdexpcr_base; > + bool little_endian; > +}; > + > +/** > + * rcpm_pm_prepare - performs device-level tasks associated with power > + * management, such as programming related to the wakeup source control. > + * @dev: Device to handle. > + * > + */ > +static int rcpm_pm_prepare(struct device *dev) > +{ > + int i, ret, idx; > + void __iomem *base; > + struct wakeup_source *ws; > + struct rcpm *rcpm; > + struct device_node *np = dev->of_node; > + u32 value[RCPM_WAKEUP_CELL_MAX_SIZE + 1]; > + > + rcpm = dev_get_drvdata(dev); > + if (!rcpm) > + return -EINVAL; > + > + base = rcpm->ippdexpcr_base; > + idx = wakeup_sources_read_lock(); > + > + /* Begin with first registered wakeup source */ > + for_each_wakeup_source(ws) { > + > + /* skip object which is not attached to device */ > + if (!ws->dev || !ws->dev->parent) > + continue; > + > + ret = device_property_read_u32_array(ws->dev->parent, > + "fsl,rcpm-wakeup", value, > + rcpm->wakeup_cells + 1); > + > + /* Wakeup source should refer to current rcpm device */ > + if (ret || (np->phandle != value[0])) { > + pr_debug("%s doesn't refer to this rcpm\n", ws->name); I agree with Rafael that this looks a little bit weird. > + continue; > + } > + > + /* Property "#fsl,rcpm-wakeup-cells" of rcpm node defines the > + * number of IPPDEXPCR register cells, and "fsl,rcpm-wakeup" > + * of wakeup source IP contains an integer array: <phandle to > + * RCPM node, IPPDEXPCR0 setting, IPPDEXPCR1 setting, > + * IPPDEXPCR2 setting, etc>. > + * > + * So we will go thought them and do programming accordngly. > + */ > + for (i = 0; i < rcpm->wakeup_cells; i++) { > + u32 tmp = value[i + 1]; > + void __iomem *address = base + i * 4; > + > + if (!tmp) > + continue; > + > + /* We can only OR related bits */ > + if (rcpm->little_endian) { > + tmp |= ioread32(address); > + iowrite32(tmp, address); > + } else { > + tmp |= ioread32be(address); > + iowrite32be(tmp, address); > + } Can we do read once at the beginning and write once at the end, instead of doing IO read/write for every wakeup source? > + } > + } > + > + wakeup_sources_read_unlock(idx); > + > + return 0; > +} > + > +static const struct dev_pm_ops rcpm_pm_ops = { > + .prepare = rcpm_pm_prepare, > +}; > + > +static int rcpm_probe(struct platform_device *pdev) > +{ > + struct device *dev = &pdev->dev; > + struct resource *r; > + struct rcpm *rcpm; > + int ret; > + > + rcpm = devm_kzalloc(dev, sizeof(*rcpm), GFP_KERNEL); > + if (!rcpm) > + return -ENOMEM; > + > + r = platform_get_resource(pdev, IORESOURCE_MEM, 0); > + if (!r) > + return -ENODEV; > + > + rcpm->ippdexpcr_base = devm_ioremap_resource(&pdev->dev, r); > + if (IS_ERR(rcpm->ippdexpcr_base)) { > + ret = PTR_ERR(rcpm->ippdexpcr_base); > + return ret; > + } > + > + rcpm->little_endian = device_property_read_bool( > + &pdev->dev, "little-endian"); > + > + ret = device_property_read_u32(&pdev->dev, > + "#fsl,rcpm-wakeup-cells", &rcpm->wakeup_cells); > + if (ret) > + return ret; > + > + dev_set_drvdata(&pdev->dev, rcpm); > + > + return 0; > +} > + > +static const struct of_device_id rcpm_of_match[] = { > + { .compatible = "fsl,qoriq-rcpm-2.1+", }, > + {} > +}; > +MODULE_DEVICE_TABLE(of, rcpm_of_match); > + > +static struct platform_driver rcpm_driver = { > + .driver = { > + .name = "rcpm", > + .of_match_table = rcpm_of_match, > + .pm = &rcpm_pm_ops, > + }, > + .probe = rcpm_probe, > +}; > + > +module_platform_driver(rcpm_driver); > -- > 2.7.4 >
Hi Leo, On Thursday, October 24, 2019 06:48, Li Yang wrote: > > On Wed, Oct 23, 2019 at 3:24 AM Ran Wang <ran.wang_1@nxp.com> wrote: > > > > The NXP's QorIQ Processors based on ARM Core have RCPM module > > Actually not just ARM based QorIQ processors are having RCPM, PowerPC based > QorIQ SoCs also have RCPM. Does this driver also work with the PowerPC SoCs? > Please clarify in the commit message and Kconfig description. > > > (Run Control and Power Management), which performs system level tasks > > associated with power management such as wakeup source control. > > > > This driver depends on PM wakeup source framework which help to > > collect wake information. > > > > Signed-off-by: Ran Wang <ran.wang_1@nxp.com> <snip> > > diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig index > > f9ad8ad..4918856 100644 > > --- a/drivers/soc/fsl/Kconfig > > +++ b/drivers/soc/fsl/Kconfig > > @@ -40,4 +40,12 @@ config DPAA2_CONSOLE > > /dev/dpaa2_mc_console and /dev/dpaa2_aiop_console, > > which can be used to dump the Management Complex and AIOP > > firmware logs. > > + > > +config FSL_RCPM > > + bool "Freescale RCPM support" > > + depends on PM_SLEEP > > If this is only for ARM, probably add more dependency here? OK. > > + help > > + The NXP QorIQ Processors based on ARM Core have RCPM module > > + (Run Control and Power Management), which performs all device-level > > + tasks associated with power management, such as wakeup source > control. > > endmenu <snip> > > + > > +/** > > + * rcpm_pm_prepare - performs device-level tasks associated with > > +power > > + * management, such as programming related to the wakeup source control. > > + * @dev: Device to handle. > > + * > > + */ > > +static int rcpm_pm_prepare(struct device *dev) { > > + int i, ret, idx; > > + void __iomem *base; > > + struct wakeup_source *ws; > > + struct rcpm *rcpm; > > + struct device_node *np = dev->of_node; > > + u32 value[RCPM_WAKEUP_CELL_MAX_SIZE + 1]; > > + > > + rcpm = dev_get_drvdata(dev); > > + if (!rcpm) > > + return -EINVAL; > > + > > + base = rcpm->ippdexpcr_base; > > + idx = wakeup_sources_read_lock(); > > + > > + /* Begin with first registered wakeup source */ > > + for_each_wakeup_source(ws) { > > + > > + /* skip object which is not attached to device */ > > + if (!ws->dev || !ws->dev->parent) > > + continue; > > + > > + ret = device_property_read_u32_array(ws->dev->parent, > > + "fsl,rcpm-wakeup", value, > > + rcpm->wakeup_cells + 1); > > + > > + /* Wakeup source should refer to current rcpm device */ > > + if (ret || (np->phandle != value[0])) { > > + pr_debug("%s doesn't refer to this rcpm\n", > > + ws->name); > > I agree with Rafael that this looks a little bit weird. OK, let me remove this print in next version. > > + continue; > > + } > > + > > + /* Property "#fsl,rcpm-wakeup-cells" of rcpm node defines the > > + * number of IPPDEXPCR register cells, and "fsl,rcpm-wakeup" > > + * of wakeup source IP contains an integer array: <phandle to > > + * RCPM node, IPPDEXPCR0 setting, IPPDEXPCR1 setting, > > + * IPPDEXPCR2 setting, etc>. > > + * > > + * So we will go thought them and do programming accordngly. > > + */ > > + for (i = 0; i < rcpm->wakeup_cells; i++) { > > + u32 tmp = value[i + 1]; > > + void __iomem *address = base + i * 4; > > + > > + if (!tmp) > > + continue; > > + > > + /* We can only OR related bits */ > > + if (rcpm->little_endian) { > > + tmp |= ioread32(address); > > + iowrite32(tmp, address); > > + } else { > > + tmp |= ioread32be(address); > > + iowrite32be(tmp, address); > > + } > > Can we do read once at the beginning and write once at the end, instead of > doing IO read/write for every wakeup source? Sure, but another loop might need to be added after the one of wakeup source walk through, to program all IPPDEXPCR registers. Is that OK? Regards, Ran > > + } > > + } > > + > > + wakeup_sources_read_unlock(idx); > > + > > + return 0; > > +} > > + > > +static const struct dev_pm_ops rcpm_pm_ops = { > > + .prepare = rcpm_pm_prepare, > > +}; > > +
diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig index f9ad8ad..4918856 100644 --- a/drivers/soc/fsl/Kconfig +++ b/drivers/soc/fsl/Kconfig @@ -40,4 +40,12 @@ config DPAA2_CONSOLE /dev/dpaa2_mc_console and /dev/dpaa2_aiop_console, which can be used to dump the Management Complex and AIOP firmware logs. + +config FSL_RCPM + bool "Freescale RCPM support" + depends on PM_SLEEP + help + The NXP QorIQ Processors based on ARM Core have RCPM module + (Run Control and Power Management), which performs all device-level + tasks associated with power management, such as wakeup source control. endmenu diff --git a/drivers/soc/fsl/Makefile b/drivers/soc/fsl/Makefile index 71dee8d..906f1cd 100644 --- a/drivers/soc/fsl/Makefile +++ b/drivers/soc/fsl/Makefile @@ -6,6 +6,7 @@ obj-$(CONFIG_FSL_DPAA) += qbman/ obj-$(CONFIG_QUICC_ENGINE) += qe/ obj-$(CONFIG_CPM) += qe/ +obj-$(CONFIG_FSL_RCPM) += rcpm.o obj-$(CONFIG_FSL_GUTS) += guts.o obj-$(CONFIG_FSL_MC_DPIO) += dpio/ obj-$(CONFIG_DPAA2_CONSOLE) += dpaa2-console.o diff --git a/drivers/soc/fsl/rcpm.c b/drivers/soc/fsl/rcpm.c new file mode 100644 index 0000000..9378073 --- /dev/null +++ b/drivers/soc/fsl/rcpm.c @@ -0,0 +1,148 @@ +// SPDX-License-Identifier: GPL-2.0 +// +// rcpm.c - Freescale QorIQ RCPM driver +// +// Copyright 2019 NXP +// +// Author: Ran Wang <ran.wang_1@nxp.com> + +#include <linux/init.h> +#include <linux/module.h> +#include <linux/platform_device.h> +#include <linux/of_address.h> +#include <linux/slab.h> +#include <linux/suspend.h> +#include <linux/kernel.h> + +#define RCPM_WAKEUP_CELL_MAX_SIZE 7 + +struct rcpm { + unsigned int wakeup_cells; + void __iomem *ippdexpcr_base; + bool little_endian; +}; + +/** + * rcpm_pm_prepare - performs device-level tasks associated with power + * management, such as programming related to the wakeup source control. + * @dev: Device to handle. + * + */ +static int rcpm_pm_prepare(struct device *dev) +{ + int i, ret, idx; + void __iomem *base; + struct wakeup_source *ws; + struct rcpm *rcpm; + struct device_node *np = dev->of_node; + u32 value[RCPM_WAKEUP_CELL_MAX_SIZE + 1]; + + rcpm = dev_get_drvdata(dev); + if (!rcpm) + return -EINVAL; + + base = rcpm->ippdexpcr_base; + idx = wakeup_sources_read_lock(); + + /* Begin with first registered wakeup source */ + for_each_wakeup_source(ws) { + + /* skip object which is not attached to device */ + if (!ws->dev || !ws->dev->parent) + continue; + + ret = device_property_read_u32_array(ws->dev->parent, + "fsl,rcpm-wakeup", value, + rcpm->wakeup_cells + 1); + + /* Wakeup source should refer to current rcpm device */ + if (ret || (np->phandle != value[0])) { + pr_debug("%s doesn't refer to this rcpm\n", ws->name); + continue; + } + + /* Property "#fsl,rcpm-wakeup-cells" of rcpm node defines the + * number of IPPDEXPCR register cells, and "fsl,rcpm-wakeup" + * of wakeup source IP contains an integer array: <phandle to + * RCPM node, IPPDEXPCR0 setting, IPPDEXPCR1 setting, + * IPPDEXPCR2 setting, etc>. + * + * So we will go thought them and do programming accordngly. + */ + for (i = 0; i < rcpm->wakeup_cells; i++) { + u32 tmp = value[i + 1]; + void __iomem *address = base + i * 4; + + if (!tmp) + continue; + + /* We can only OR related bits */ + if (rcpm->little_endian) { + tmp |= ioread32(address); + iowrite32(tmp, address); + } else { + tmp |= ioread32be(address); + iowrite32be(tmp, address); + } + } + } + + wakeup_sources_read_unlock(idx); + + return 0; +} + +static const struct dev_pm_ops rcpm_pm_ops = { + .prepare = rcpm_pm_prepare, +}; + +static int rcpm_probe(struct platform_device *pdev) +{ + struct device *dev = &pdev->dev; + struct resource *r; + struct rcpm *rcpm; + int ret; + + rcpm = devm_kzalloc(dev, sizeof(*rcpm), GFP_KERNEL); + if (!rcpm) + return -ENOMEM; + + r = platform_get_resource(pdev, IORESOURCE_MEM, 0); + if (!r) + return -ENODEV; + + rcpm->ippdexpcr_base = devm_ioremap_resource(&pdev->dev, r); + if (IS_ERR(rcpm->ippdexpcr_base)) { + ret = PTR_ERR(rcpm->ippdexpcr_base); + return ret; + } + + rcpm->little_endian = device_property_read_bool( + &pdev->dev, "little-endian"); + + ret = device_property_read_u32(&pdev->dev, + "#fsl,rcpm-wakeup-cells", &rcpm->wakeup_cells); + if (ret) + return ret; + + dev_set_drvdata(&pdev->dev, rcpm); + + return 0; +} + +static const struct of_device_id rcpm_of_match[] = { + { .compatible = "fsl,qoriq-rcpm-2.1+", }, + {} +}; +MODULE_DEVICE_TABLE(of, rcpm_of_match); + +static struct platform_driver rcpm_driver = { + .driver = { + .name = "rcpm", + .of_match_table = rcpm_of_match, + .pm = &rcpm_pm_ops, + }, + .probe = rcpm_probe, +}; + +module_platform_driver(rcpm_driver);
The NXP's QorIQ Processors based on ARM Core have RCPM module (Run Control and Power Management), which performs system level tasks associated with power management such as wakeup source control. This driver depends on PM wakeup source framework which help to collect wake information. Signed-off-by: Ran Wang <ran.wang_1@nxp.com> --- Change in v9: - Add kerneldoc for rcpm_pm_prepare(). - Use pr_debug() to replace dev_info(), to print message when decide skip current wakeup object, this is mainly for debugging (in order to detect potential improper implementation on device tree which might cause this skip). - Refactor looping implementation in rcpm_pm_prepare(), add more comments to help clarify. Change in v8: - Adjust related API usage to meet wakeup.c's update in patch 1/3. - Add sanity checking for the case of ws->dev or ws->dev->parent is null. Change in v7: - Replace 'ws->dev' with 'ws->dev->parent' to get aligned with c8377adfa781 ("PM / wakeup: Show wakeup sources stats in sysfs") - Remove '+obj-y += ftm_alarm.o' since it is wrong. - Cosmetic work. Change in v6: - Adjust related API usage to meet wakeup.c's update in patch 1/3. Change in v5: - Fix v4 regression of the return value of wakeup_source_get_next() didn't pass to ws in while loop. - Rename wakeup_source member 'attached_dev' to 'dev'. - Rename property 'fsl,#rcpm-wakeup-cells' to '#fsl,rcpm-wakeup-cells'. please see https://lore.kernel.org/patchwork/patch/1101022/ Change in v4: - Remove extra ',' in author line of rcpm.c - Update usage of wakeup_source_get_next() to be less confusing to the reader, code logic remain the same. Change in v3: - Some whitespace ajdustment. Change in v2: - Rebase Kconfig and Makefile update to latest mainline. drivers/soc/fsl/Kconfig | 8 +++ drivers/soc/fsl/Makefile | 1 + drivers/soc/fsl/rcpm.c | 148 +++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 157 insertions(+) create mode 100644 drivers/soc/fsl/rcpm.c