Skip to contentSkip to conversation

PM: wakeup: Add routine to help fetch wakeup source object.

PATCH Superseded Ran Wang 3 participants 8 messages Jul 24, 2019 – Aug 19, 2019

Subsystems (6)

v5 of 10 Superseded Latest is v10 →

lore
Share & tools
lore

Ran Wang

author
#0 lore raw

PATCH v5 1/3 PM: wakeup: Add routine to help fetch wakeup source object.

Some user might want to go through all registered wakeup sources and doing things accordingly. For example, SoC PM driver might need to do HW programming to prevent powering down specific IP which wakeup source depending on. So add this API to help walk through all registered wakeup source objects on that list and return them one by one.

---
Change in v5:
- Update commit message, add decription of walk through all wakeup source objects.
- Add SCU protection in function wakeup_source_get_next().
- Rename wakeup_source member 'attached_dev' to 'dev' and move it up (before wakeirq).

Change in v4:
- None.

Change in v3:
- Adjust indentation of *attached_dev;.

Change in v2:
- None.

 drivers/base/power/wakeup.c | 24 ++++++++++++++++++++++++
 include/linux/pm_wakeup.h   |  3 +++
 2 files changed, 27 insertions(+)
drivers/base/power/wakeup.c +24 -0
index ee31d4f..2fba891 100644
@@ -14,6 +14,7 @@
 #include <linux/suspend.h>
 #include <linux/seq_file.h>
 #include <linux/debugfs.h>
+#include <linux/of_device.h>
 #include <linux/pm_wakeirq.h>
 #include <trace/events/power.h>
 
@@ -226,6 +227,28 @@ void wakeup_source_unregister(struct wakeup_source *ws)
 	}
 }
 EXPORT_SYMBOL_GPL(wakeup_source_unregister);
+/**
+ * wakeup_source_get_next - Get next wakeup source from the list
+ * @ws: Previous wakeup source object, null means caller want first one.
+ */
+struct wakeup_source *wakeup_source_get_next(struct wakeup_source *ws)
+{
+	struct list_head *ws_head = &wakeup_sources;
+	struct wakeup_source *next_ws = NULL;
+	int idx;
+
+	idx = srcu_read_lock(&wakeup_srcu);
+	if (ws)
+		next_ws = list_next_or_null_rcu(ws_head, &ws->entry,
+				struct wakeup_source, entry);
+	else
+		next_ws = list_entry_rcu(ws_head->next,
+				struct wakeup_source, entry);
+	srcu_read_unlock(&wakeup_srcu, idx);
+
+	return next_ws;
+}
+EXPORT_SYMBOL_GPL(wakeup_source_get_next);
 
 /**
  * device_wakeup_attach - Attach a wakeup source object to a device object.
@@ -242,6 +265,7 @@ static int device_wakeup_attach(struct device *dev, struct wakeup_source *ws)
 		return -EEXIST;
 	}
 	dev->power.wakeup = ws;
+	ws->dev = dev;
 	if (dev->power.wakeirq)
 		device_wakeup_attach_irq(dev, dev->power.wakeirq);
 	spin_unlock_irq(&dev->power.lock);
include/linux/pm_wakeup.h +3 -0
index 9102760..fc23c1a 100644
@@ -23,6 +23,7 @@ struct wake_irq;
  * @name: Name of the wakeup source
  * @entry: Wakeup source list entry
  * @lock: Wakeup source lock
+ * @dev: The device it attached to
  * @wakeirq: Optional device specific wakeirq
  * @timer: Wakeup timer list
  * @timer_expires: Wakeup timer expiration
@@ -42,6 +43,7 @@ struct wakeup_source {
 	const char 		*name;
 	struct list_head	entry;
 	spinlock_t		lock;
+	struct device		*dev;
 	struct wake_irq		*wakeirq;
 	struct timer_list	timer;
 	unsigned long		timer_expires;
@@ -88,6 +90,7 @@ extern void wakeup_source_add(struct wakeup_source *ws);
 extern void wakeup_source_remove(struct wakeup_source *ws);
 extern struct wakeup_source *wakeup_source_register(const char *name);
 extern void wakeup_source_unregister(struct wakeup_source *ws);
+extern struct wakeup_source *wakeup_source_get_next(struct wakeup_source *ws);
 extern int device_wakeup_enable(struct device *dev);
 extern int device_wakeup_disable(struct device *dev);
 extern void device_set_wakeup_capable(struct device *dev, bool capable);
Signature · 1 line
2.7.4
author
#1 lore raw

PATCH v5 2/3 Documentation: dt: binding: fsl: Add 'little-endian' and update Chassis define

By default, QorIQ SoC's RCPM register block is Big Endian. But there are some exceptions, such as LS1088A and LS2088A, are Little Endian. So add this optional property to help identify them.

Actually LS2021A and other Layerscapes won't totally follow Chassis 2.1, so separate them from powerpc SoC.

---
Change in v5:
- Add 'Reviewed-by: Rob Herring <[email protected]>' to commit message.
- Rename property 'fsl,#rcpm-wakeup-cells' to '#fsl,rcpm-wakeup-cells'. please see https://lore.kernel.org/patchwork/patch/1101022/

Change in v4:
- Adjust indectation of 'ls1021a, ls1012a, ls1043a, ls1046a'.

Change in v3:
- None.

Change in v2:
- None.

 Documentation/devicetree/bindings/soc/fsl/rcpm.txt | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)
Documentation/devicetree/bindings/soc/fsl/rcpm.txt +10 -4
index e284e4e..5a33619 100644
@@ -5,7 +5,7 @@ and power management.
 
 Required properites:
   - reg : Offset and length of the register set of the RCPM block.
-  - fsl,#rcpm-wakeup-cells : The number of IPPDEXPCR register cells in the
+  - #fsl,rcpm-wakeup-cells : The number of IPPDEXPCR register cells in the
 	fsl,rcpm-wakeup property.
   - compatible : Must contain a chip-specific RCPM block compatible string
 	and (if applicable) may contain a chassis-version RCPM compatible
@@ -20,6 +20,7 @@ Required properites:
 	* "fsl,qoriq-rcpm-1.0": for chassis 1.0 rcpm
 	* "fsl,qoriq-rcpm-2.0": for chassis 2.0 rcpm
 	* "fsl,qoriq-rcpm-2.1": for chassis 2.1 rcpm
+	* "fsl,qoriq-rcpm-2.1+": for chassis 2.1+ rcpm
 
 All references to "1.0" and "2.0" refer to the QorIQ chassis version to
 which the chip complies.
@@ -27,14 +28,19 @@ Chassis Version		Example Chips
 ---------------		-------------------------------
 1.0				p4080, p5020, p5040, p2041, p3041
 2.0				t4240, b4860, b4420
-2.1				t1040, ls1021
+2.1				t1040,
+2.1+				ls1021a, ls1012a, ls1043a, ls1046a
+
+Optional properties:
+ - little-endian : RCPM register block is Little Endian. Without it RCPM
+   will be Big Endian (default case).
 
 Example:
 The RCPM node for T4240:
 	rcpm: global-utilities@e2000 {
 		compatible = "fsl,t4240-rcpm", "fsl,qoriq-rcpm-2.0";
 		reg = <0xe2000 0x1000>;
-		fsl,#rcpm-wakeup-cells = <2>;
+		#fsl,rcpm-wakeup-cells = <2>;
 	};
 
 * Freescale RCPM Wakeup Source Device Tree Bindings
@@ -44,7 +50,7 @@ can be used as a wakeup source.
 
   - fsl,rcpm-wakeup: Consists of a phandle to the rcpm node and the IPPDEXPCR
 	register cells. The number of IPPDEXPCR register cells is defined in
-	"fsl,#rcpm-wakeup-cells" in the rcpm node. The first register cell is
+	"#fsl,rcpm-wakeup-cells" in the rcpm node. The first register cell is
 	the bit mask that should be set in IPPDEXPCR0, and the second register
 	cell is for IPPDEXPCR1, and so on.
 
Signature · 1 line
2.7.4
author
#2 lore raw

PATCH v5 3/3 soc: fsl: add RCPM driver

In reply to Ran Wang

The NXP's 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.

This driver depends on PM wakeup source framework which help to collect wake information.

---
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   | 126 +++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 135 insertions(+)
 create mode 100644 drivers/soc/fsl/rcpm.c
drivers/soc/fsl/Kconfig +8 -0
index f9ad8ad..4918856 100644
@@ -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
drivers/soc/fsl/Makefile +1 -0
index 71dee8d..906f1cd 100644
@@ -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
drivers/soc/fsl/rcpm.c new file +126 -0

126 lines not on this page · raw message

Signature · 1 line
2.7.4
#3 lore raw
In reply to Ran Wang
Quoted 53 lines · CEST Ran Wang

Some user might want to go through all registered wakeup sources and doing things accordingly. For example, SoC PM driver might need to do HW programming to prevent powering down specific IP which wakeup source depending on. So add this API to help walk through all registered wakeup source objects on that list and return them one by one.

---
Change in v5:
- Update commit message, add decription of walk through all wakeup source objects.
- Add SCU protection in function wakeup_source_get_next().
- Rename wakeup_source member 'attached_dev' to 'dev' and move it up (before wakeirq).

Change in v4:
- None.

Change in v3:
- Adjust indentation of *attached_dev;.

Change in v2:
- None.

 drivers/base/power/wakeup.c | 24 ++++++++++++++++++++++++
 include/linux/pm_wakeup.h   |  3 +++
 2 files changed, 27 insertions(+)
drivers/base/power/wakeup.c +10 -0
index ee31d4f..2fba891 100644
@@ -14,6 +14,7 @@
 #include <linux/suspend.h>
 #include <linux/seq_file.h>
 #include <linux/debugfs.h>
+#include <linux/of_device.h>
 #include <linux/pm_wakeirq.h>
 #include <trace/events/power.h>
 
@@ -226,6 +227,28 @@ void wakeup_source_unregister(struct wakeup_source *ws)
 	}
 }
 EXPORT_SYMBOL_GPL(wakeup_source_unregister);
+/**
+ * wakeup_source_get_next - Get next wakeup source from the list
+ * @ws: Previous wakeup source object, null means caller want first one.
+ */
+struct wakeup_source *wakeup_source_get_next(struct wakeup_source *ws)
+{
+	struct list_head *ws_head = &wakeup_sources;
+	struct wakeup_source *next_ws = NULL;
+	int idx;

drivers/base/power/wakeup.c void wakeup_source_unregister(struct wakeup_source *ws) · line 248

Quoted 10 lines
drivers/base/power/wakeup.c +10 -0
+
+	idx = srcu_read_lock(&wakeup_srcu);
+	if (ws)
+		next_ws = list_next_or_null_rcu(ws_head, &ws->entry,
+				struct wakeup_source, entry);
+	else
+		next_ws = list_entry_rcu(ws_head->next,
+				struct wakeup_source, entry);
+	srcu_read_unlock(&wakeup_srcu, idx);
+

This is incorrect.

The SRCU cannot be unlocked until the caller of this is done with the object returned by it, or that object can be freed while it is still being accessed.

Besides, this patch conflicts with some general wakeup sources changes in the works, so it needs to be deferred and rebased on top of those changes.

Quoted 43 lines
drivers/base/power/wakeup.c +4 -0
+	return next_ws;
+}
+EXPORT_SYMBOL_GPL(wakeup_source_get_next);
 
 /**
  * device_wakeup_attach - Attach a wakeup source object to a device object.
@@ -242,6 +265,7 @@ static int device_wakeup_attach(struct device *dev, struct wakeup_source *ws)
 		return -EEXIST;
 	}
 	dev->power.wakeup = ws;
+	ws->dev = dev;
 	if (dev->power.wakeirq)
 		device_wakeup_attach_irq(dev, dev->power.wakeirq);
 	spin_unlock_irq(&dev->power.lock);
include/linux/pm_wakeup.h +3 -0
index 9102760..fc23c1a 100644
@@ -23,6 +23,7 @@ struct wake_irq;
  * @name: Name of the wakeup source
  * @entry: Wakeup source list entry
  * @lock: Wakeup source lock
+ * @dev: The device it attached to
  * @wakeirq: Optional device specific wakeirq
  * @timer: Wakeup timer list
  * @timer_expires: Wakeup timer expiration
@@ -42,6 +43,7 @@ struct wakeup_source {
 	const char 		*name;
 	struct list_head	entry;
 	spinlock_t		lock;
+	struct device		*dev;
 	struct wake_irq		*wakeirq;
 	struct timer_list	timer;
 	unsigned long		timer_expires;
@@ -88,6 +90,7 @@ extern void wakeup_source_add(struct wakeup_source *ws);
 extern void wakeup_source_remove(struct wakeup_source *ws);
 extern struct wakeup_source *wakeup_source_register(const char *name);
 extern void wakeup_source_unregister(struct wakeup_source *ws);
+extern struct wakeup_source *wakeup_source_get_next(struct wakeup_source *ws);
 extern int device_wakeup_enable(struct device *dev);
 extern int device_wakeup_disable(struct device *dev);
 extern void device_set_wakeup_capable(struct device *dev, bool capable);
author
#4 lore raw

Hi Rafael,

Quoted 70 lines · Rafael J. Wysocki
Quoted 6 lines · CEST Ran Wang

Some user might want to go through all registered wakeup sources and doing things accordingly. For example, SoC PM driver might need to do HW programming to prevent powering down specific IP which wakeup source depending on. So add this API to help walk through all registered wakeup source objects on that list and return them one by one.

Quoted 7 lines

---
Change in v5:
- Update commit message, add decription of walk through all wakeup source objects.
- Add SCU protection in function wakeup_source_get_next().
- Rename wakeup_source member 'attached_dev' to 'dev' and move it

up

drivers/base/power/wakeup.c void wakeup_source_unregister(struct

Quoted 28 lines

(before wakeirq).

Change in v4:
- None.

Change in v3:
- Adjust indentation of *attached_dev;.

Change in v2:
- None.

 drivers/base/power/wakeup.c | 24 ++++++++++++++++++++++++
 include/linux/pm_wakeup.h   |  3 +++
 2 files changed, 27 insertions(+)
drivers/base/power/wakeup.c +1 -0
index ee31d4f..2fba891 100644
@@ -14,6 +14,7 @@
 #include <linux/suspend.h>
 #include <linux/seq_file.h>
 #include <linux/debugfs.h>
+#include <linux/of_device.h>
 #include <linux/pm_wakeirq.h>
 #include <trace/events/power.h>
 
@@ -226,6 +227,28 @@ void wakeup_source_unregister(struct

wakeup_source *ws)

Quoted 12 lines
drivers/base/power/wakeup.c +9 -0
 	}
 }
 EXPORT_SYMBOL_GPL(wakeup_source_unregister);
+/**
+ * wakeup_source_get_next - Get next wakeup source from the list
+ * @ws: Previous wakeup source object, null means caller want first one.
+ */
+struct wakeup_source *wakeup_source_get_next(struct wakeup_source
+*ws) {
+	struct list_head *ws_head = &wakeup_sources;
+	struct wakeup_source *next_ws = NULL;
+	int idx;

drivers/base/power/wakeup.c void wakeup_source_unregister(struct wakeup_source *ws) · line 248

Quoted 10 lines
drivers/base/power/wakeup.c +10 -0
+
+	idx = srcu_read_lock(&wakeup_srcu);
+	if (ws)
+		next_ws = list_next_or_null_rcu(ws_head, &ws->entry,
+				struct wakeup_source, entry);
+	else
+		next_ws = list_entry_rcu(ws_head->next,
+				struct wakeup_source, entry);
+	srcu_read_unlock(&wakeup_srcu, idx);
+

This is incorrect.

Quoted 2 lines

The SRCU cannot be unlocked until the caller of this is done with the object returned by it, or that object can be freed while it is still being accessed.

Thanks for the comment. Looks like I was not fully understanding your point on
v4 discussion. So I will implement 3 APIs by referring wakeup_sources_stats_seq_start/next/stop()

Quoted 2 lines

Besides, this patch conflicts with some general wakeup sources changes in the works, so it needs to be deferred and rebased on top of those changes.

Could you please tell me which is the right code base I should developing on?
I just tried applying v5 patch on latest git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git branch master (d1abaeb Linux 5.3-rc5) and no conflict encountered.

Thanks & Regards,
Ran

#5 lore raw
Quoted 80 lines · Ran Wang

Hi Rafael,

Quoted 70 lines · Rafael J. Wysocki
Quoted 6 lines · CEST Ran Wang

Some user might want to go through all registered wakeup sources and doing things accordingly. For example, SoC PM driver might need to do HW programming to prevent powering down specific IP which wakeup source depending on. So add this API to help walk through all registered wakeup source objects on that list and return them one by one.

Quoted 7 lines

---
Change in v5:
- Update commit message, add decription of walk through all wakeup source objects.
- Add SCU protection in function wakeup_source_get_next().
- Rename wakeup_source member 'attached_dev' to 'dev' and move it

up

drivers/base/power/wakeup.c void wakeup_source_unregister(struct

Quoted 28 lines

(before wakeirq).

Change in v4:
- None.

Change in v3:
- Adjust indentation of *attached_dev;.

Change in v2:
- None.

 drivers/base/power/wakeup.c | 24 ++++++++++++++++++++++++
 include/linux/pm_wakeup.h   |  3 +++
 2 files changed, 27 insertions(+)
drivers/base/power/wakeup.c +1 -0
index ee31d4f..2fba891 100644
@@ -14,6 +14,7 @@
 #include <linux/suspend.h>
 #include <linux/seq_file.h>
 #include <linux/debugfs.h>
+#include <linux/of_device.h>
 #include <linux/pm_wakeirq.h>
 #include <trace/events/power.h>
 
@@ -226,6 +227,28 @@ void wakeup_source_unregister(struct

wakeup_source *ws)

Quoted 12 lines
drivers/base/power/wakeup.c +9 -0
    }
 }
 EXPORT_SYMBOL_GPL(wakeup_source_unregister);
+/**
+ * wakeup_source_get_next - Get next wakeup source from the list
+ * @ws: Previous wakeup source object, null means caller want first one.
+ */
+struct wakeup_source *wakeup_source_get_next(struct wakeup_source
+*ws) {
+   struct list_head *ws_head = &wakeup_sources;
+   struct wakeup_source *next_ws = NULL;
+   int idx;

drivers/base/power/wakeup.c void wakeup_source_unregister(struct wakeup_source *ws) · line 248

Quoted 10 lines
drivers/base/power/wakeup.c +10 -0
+
+   idx = srcu_read_lock(&wakeup_srcu);
+   if (ws)
+           next_ws = list_next_or_null_rcu(ws_head, &ws->entry,
+                           struct wakeup_source, entry);
+   else
+           next_ws = list_entry_rcu(ws_head->next,
+                           struct wakeup_source, entry);
+   srcu_read_unlock(&wakeup_srcu, idx);
+

This is incorrect.

Quoted 2 lines

The SRCU cannot be unlocked until the caller of this is done with the object returned by it, or that object can be freed while it is still being accessed.

Thanks for the comment. Looks like I was not fully understanding your point on
v4 discussion. So I will implement 3 APIs by referring wakeup_sources_stats_seq_start/next/stop()

Quoted 6 lines
Quoted 2 lines

Besides, this patch conflicts with some general wakeup sources changes in the works, so it needs to be deferred and rebased on top of those changes.

Could you please tell me which is the right code base I should developing on?
I just tried applying v5 patch on latest git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git branch master (d1abaeb Linux 5.3-rc5) and no conflict encountered.

It is better to use the most recent -rc from Linus (5.3-rc5 as of today) as the base unless your patches depend on some changes that are not in there.

author
#6 lore raw

Hi Rafael,

Quoted 91 lines · Rafael J. Wysocki
Quoted 11 lines · Ran Wang

Hi Rafael,

Quoted 7 lines · Rafael J. Wysocki
Quoted 5 lines · CEST Ran Wang

Some user might want to go through all registered wakeup sources and doing things accordingly. For example, SoC PM driver might need to do HW programming to prevent powering down specific IP which wakeup source depending on. So add this API to help walk through all registered wakeup source objects on that list and return them

one by one.

Quoted 64 lines
Quoted 64 lines
Quoted 9 lines

---
Change in v5:
- Update commit message, add decription of walk through all wakeup source objects.
- Add SCU protection in function wakeup_source_get_next().
- Rename wakeup_source member 'attached_dev' to 'dev' and move
it

up

drivers/base/power/wakeup.c void wakeup_source_unregister(struct

Quoted 28 lines

(before wakeirq).

Change in v4:
- None.

Change in v3:
- Adjust indentation of *attached_dev;.

Change in v2:
- None.

 drivers/base/power/wakeup.c | 24 ++++++++++++++++++++++++
 include/linux/pm_wakeup.h   |  3 +++
 2 files changed, 27 insertions(+)
(quoted diff) +0 -0

b/drivers/base/power/wakeup.c index ee31d4f..2fba891 100644

drivers/base/power/wakeup.c +1 -0
@@ -14,6 +14,7 @@
 #include <linux/suspend.h>
 #include <linux/seq_file.h>
 #include <linux/debugfs.h>
+#include <linux/of_device.h>
 #include <linux/pm_wakeirq.h>
 #include <trace/events/power.h>
 
@@ -226,6 +227,28 @@ void wakeup_source_unregister(struct

wakeup_source *ws)

Quoted 12 lines
drivers/base/power/wakeup.c +9 -0
    }
 }
 EXPORT_SYMBOL_GPL(wakeup_source_unregister);
+/**
+ * wakeup_source_get_next - Get next wakeup source from the list
+ * @ws: Previous wakeup source object, null means caller want first one.
+ */
+struct wakeup_source *wakeup_source_get_next(struct wakeup_source
+*ws) {
+   struct list_head *ws_head = &wakeup_sources;
+   struct wakeup_source *next_ws = NULL;
+   int idx;

drivers/base/power/wakeup.c void wakeup_source_unregister(struct wakeup_source *ws) · line 248

Quoted 10 lines
drivers/base/power/wakeup.c +10 -0
+
+   idx = srcu_read_lock(&wakeup_srcu);
+   if (ws)
+           next_ws = list_next_or_null_rcu(ws_head, &ws->entry,
+                           struct wakeup_source, entry);
+   else
+           next_ws = list_entry_rcu(ws_head->next,
+                           struct wakeup_source, entry);
+   srcu_read_unlock(&wakeup_srcu, idx);
+

This is incorrect.

Quoted 2 lines
Quoted 2 lines

The SRCU cannot be unlocked until the caller of this is done with the object returned by it, or that object can be freed while it is still being

accessed.

Quoted 8 lines

Thanks for the comment. Looks like I was not fully understanding your point on
v4 discussion. So I will implement 3 APIs by referring wakeup_sources_stats_seq_start/next/stop()

Quoted 2 lines

Besides, this patch conflicts with some general wakeup sources changes in the works, so it needs to be deferred and rebased on top of those

changes.

Quoted 1 line
Quoted 8 lines
Quoted 3 lines

Could you please tell me which is the right code base I should developing on? I just tried applying v5 patch on latest
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git branch master

(d1abaeb Linux 5.3-rc5) and no conflict encountered.

It is better to use the most recent -rc from Linus (5.3-rc5 as of today) as the base unless your patches depend on some changes that are not in there.

OK, So I need to implement on latest git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git branch master, am I right?

However, I just checked v5.3-rc5 code and found it has the same HEAD (d1abaeb Linux 5.3-rc5 on which I did not observe v5 patch apply conflict, did I miss something? Thanks.

Regards,
Ran

#7 lore raw
Quoted 99 lines · CEST Ran Wang

Hi Rafael,

Quoted 96 lines · Rafael J. Wysocki
Quoted 11 lines · Ran Wang

Hi Rafael,

Quoted 7 lines · Rafael J. Wysocki
Quoted 5 lines · CEST Ran Wang

Some user might want to go through all registered wakeup sources and doing things accordingly. For example, SoC PM driver might need to do HW programming to prevent powering down specific IP which wakeup source depending on. So add this API to help walk through all registered wakeup source objects on that list and return them

one by one.

Quoted 64 lines
Quoted 64 lines
Quoted 9 lines

---
Change in v5:
- Update commit message, add decription of walk through all wakeup source objects.
- Add SCU protection in function wakeup_source_get_next().
- Rename wakeup_source member 'attached_dev' to 'dev' and move
it

up

drivers/base/power/wakeup.c void wakeup_source_unregister(struct

Quoted 28 lines

(before wakeirq).

Change in v4:
- None.

Change in v3:
- Adjust indentation of *attached_dev;.

Change in v2:
- None.

 drivers/base/power/wakeup.c | 24 ++++++++++++++++++++++++
 include/linux/pm_wakeup.h   |  3 +++
 2 files changed, 27 insertions(+)
(quoted diff) +0 -0

b/drivers/base/power/wakeup.c index ee31d4f..2fba891 100644

drivers/base/power/wakeup.c +1 -0
@@ -14,6 +14,7 @@
 #include <linux/suspend.h>
 #include <linux/seq_file.h>
 #include <linux/debugfs.h>
+#include <linux/of_device.h>
 #include <linux/pm_wakeirq.h>
 #include <trace/events/power.h>
 
@@ -226,6 +227,28 @@ void wakeup_source_unregister(struct

wakeup_source *ws)

Quoted 12 lines
drivers/base/power/wakeup.c +9 -0
    }
 }
 EXPORT_SYMBOL_GPL(wakeup_source_unregister);
+/**
+ * wakeup_source_get_next - Get next wakeup source from the list
+ * @ws: Previous wakeup source object, null means caller want first one.
+ */
+struct wakeup_source *wakeup_source_get_next(struct wakeup_source
+*ws) {
+   struct list_head *ws_head = &wakeup_sources;
+   struct wakeup_source *next_ws = NULL;
+   int idx;

drivers/base/power/wakeup.c void wakeup_source_unregister(struct wakeup_source *ws) · line 248

Quoted 10 lines
drivers/base/power/wakeup.c +10 -0
+
+   idx = srcu_read_lock(&wakeup_srcu);
+   if (ws)
+           next_ws = list_next_or_null_rcu(ws_head, &ws->entry,
+                           struct wakeup_source, entry);
+   else
+           next_ws = list_entry_rcu(ws_head->next,
+                           struct wakeup_source, entry);
+   srcu_read_unlock(&wakeup_srcu, idx);
+

This is incorrect.

Quoted 2 lines
Quoted 2 lines

The SRCU cannot be unlocked until the caller of this is done with the object returned by it, or that object can be freed while it is still being

accessed.

Quoted 8 lines

Thanks for the comment. Looks like I was not fully understanding your point on
v4 discussion. So I will implement 3 APIs by referring wakeup_sources_stats_seq_start/next/stop()

Quoted 2 lines

Besides, this patch conflicts with some general wakeup sources changes in the works, so it needs to be deferred and rebased on top of those

changes.

Quoted 4 lines

Could you please tell me which is the right code base I should developing on? I just tried applying v5 patch on latest
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git branch master

(d1abaeb Linux 5.3-rc5) and no conflict encountered.

Quoted 8 lines
Quoted 3 lines

It is better to use the most recent -rc from Linus (5.3-rc5 as of today) as the base unless your patches depend on some changes that are not in there.

OK, So I need to implement on latest git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git branch master, am I right?

However, I just checked v5.3-rc5 code and found it has the same HEAD (d1abaeb Linux 5.3-rc5 on which I did not observe v5 patch apply conflict, did I miss something? Thanks.

The conflict I mentioned earlier was with another patch series in the works which is not in 5.3-rc5. However, there are problems with that series and it is not linux-next now even, so please just base your series on top of -rc5.