i2c: Use generic subsystem-level power management callbacks
Subsystems (3)
PATCH 1/1 i2c: Use generic subsystem-level power management callbacks
From: Rafael J. Wysocki <[email protected]>
There are three issues with the i2c's power management callbacks at the moment. First, they don't include any hibernate callbacks, although they should at least include the .restore() callback (there's no guarantee that the driver will be in memory before loading the image kernel and we must restore the pre-hibernation state of the device). Second, the "legacy" callbacks are not going to be invoked by the PM core since the bus type's pm object is not NULL. Finally, the system power transition (ie. suspend/resume) callbacks don't check if the device hasn't been already suspended at run time, in which case they should skip suspending it and handle it in a special way during resume. Also, it looks like the i2c bus type itself doesn't need any power management handling beyond that provided by the generic subsystem-level PM callbacks.
For these reasons, remove the power management callbacks defined by the i2c bus type and make it use the generic subsystem-level power management callbacks.
---
Jean,
I know I said I wanted to implement the generic callbacks later, but they were implemented in the meantime anyway, so I think we can use them now.
Please note that the "legacy" callbacks removed by this patch are already effectively dead, because they are not going to be called by the PM core anyway. I'm not sure if this is what we want, though, so please let me know in case it's not.
Thanks,
Rafael
--- drivers/i2c/i2c-core.c | 113 ------------------------------------------------- 1 file changed, 1 insertion(+), 112 deletions(-)
drivers/i2c/i2c-core.c +1 -112
@@ -156,107 +156,6 @@ static void i2c_device_shutdown(struct d driver->shutdown (client); } -#ifdef CONFIG_SUSPEND -static int i2c_device_pm_suspend (struct device *dev) -{ -const struct dev_pm_ops *pm; - -if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->suspend) -return 0 ; -return pm->suspend (dev); -} - -static int i2c_device_pm_resume (struct device *dev) -{ -const struct dev_pm_ops *pm; - -if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->resume) -return 0 ; -return pm->resume (dev); -} -#else -#define i2c_device_pm_suspend NULL -#define i2c_device_pm_resume NULL -#endif - -#ifdef CONFIG_PM_RUNTIME -static int i2c_device_runtime_suspend (struct device *dev) -{ -const struct dev_pm_ops *pm; - -if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->runtime_suspend) -return 0 ; -return pm->runtime_suspend (dev); -} - -static int i2c_device_runtime_resume (struct device *dev) -{ -const struct dev_pm_ops *pm; - -if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->runtime_resume) -return 0 ; -return pm->runtime_resume (dev); -} - -static int i2c_device_runtime_idle (struct device *dev) -{ -const struct dev_pm_ops *pm =NULL ; -int ret; - -if (dev->driver) - pm = dev->driver->pm; -if (pm && pm->runtime_idle) { - ret = pm->runtime_idle (dev); -if (ret) -return ret; - } - -return pm_runtime_suspend (dev); -} -#else -#define i2c_device_runtime_suspend NULL -#define i2c_device_runtime_resume NULL -#define i2c_device_runtime_idle NULL -#endif - -static int i2c_device_suspend (struct device *dev,pm_message_t mesg) -{ -struct i2c_client *client =i2c_verify_client (dev); -struct i2c_driver *driver; - -if (!client || !dev->driver) -return 0 ; - driver =to_i2c_driver (dev->driver); -if (!driver->suspend) -return 0 ; -return driver->suspend (client, mesg); -} - -static int i2c_device_resume (struct device *dev) -{ -struct i2c_client *client =i2c_verify_client (dev); -struct i2c_driver *driver; - -if (!client || !dev->driver) -return 0 ; - driver =to_i2c_driver (dev->driver); -if (!driver->resume) -return 0 ; -return driver->resume (client); -} -static void i2c_client_dev_release (struct device *dev) {kfree (to_i2c_client (dev));
@@ -295,23 +194,13 @@ static const struct attribute_group *i2c NULL }; -static const struct dev_pm_ops i2c_device_pm_ops = { - .suspend = i2c_device_pm_suspend, - .resume = i2c_device_pm_resume, - .runtime_suspend = i2c_device_runtime_suspend, - .runtime_resume = i2c_device_runtime_resume, - .runtime_idle = i2c_device_runtime_idle, -}; -struct bus_type i2c_bus_type = { .name ="i2c" , .match = i2c_device_match, .probe = i2c_device_probe, .remove = i2c_device_remove, .shutdown = i2c_device_shutdown, - .suspend = i2c_device_suspend, - .resume = i2c_device_resume, - .pm = &i2c_device_pm_ops, + .pm =GENERIC_SUBSYS_PM_OPS , };EXPORT_SYMBOL_GPL (i2c_bus_type);
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Rafael J. Wysocki
Please note that the "legacy" callbacks removed by this patch are already effectively dead, because they are not going to be called by the PM core anyway. I'm not sure if this is what we want, though, so please let me know in case it's not.
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the pm_ops structure would be empty.
The changes to the PM core necessary to do this are quite small. Does it seem like a reasonable thing to do?
Alan Stern
A message that is not in the archive (sent off-list or not yet received): Pine.LNX.4.44L0.1003131627270.19476-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org
Quoted 11 lines · Alan Stern
Quoted 4 lines · Rafael J. Wysocki
Please note that the "legacy" callbacks removed by this patch are already effectively dead, because they are not going to be called by the PM core anyway. I'm not sure if this is what we want, though, so please let me know in case it's not.
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
Quoted 5 lines
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.
Quoted 1 line
Does it seem like a reasonable thing to do?
Well, if someone spends time on implementing new callbacks for a bus type, writing them in such a way that they will call the "legacy" callbacks from drivers if necessary is not really a big deal IMO.
The problem in this particular case is that I don't know whether or not we _want_ the drivers' "legacy" callbacks to be invoked at all. The $subject patch assumes we don't, but if we do in fact, I'll rework it to do so.
I need that piece of information, though. :-)
Rafael
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · Rafael J. Wysocki
Quoted 8 lines
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.
Quoted 5 lines
Quoted 1 line
The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in
pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.
All you have to do is change the "else if" lines in device_[suspend|resume]() to "if".
Quoted 5 lines
Quoted 1 line
Does it seem like a reasonable thing to do?
Well, if someone spends time on implementing new callbacks for a bus type, writing them in such a way that they will call the "legacy" callbacks from drivers if necessary is not really a big deal IMO.
Sure. But suppose you _don't_ want to spend the time implementing new callbacks to replace the existing legacy suspend and resume methods, whereas you _do_ want to implement runtime PM. Runtime PM forces the bus type to have a pm_ops member, which as you point out, will prevent the legacy methods from being called.
Alan Stern
A message that is not in the archive (sent off-list or not yet received): Pine.LNX.4.44L0.1003141620540.1752-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org
Quoted 10 lines · Alan Stern
Quoted 8 lines · Rafael J. Wysocki
Quoted 8 lines
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in
pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.All you have to do is change the "else if" lines in device_[suspend|resume]() to "if".
Then, if a bus type implements both "new" and "old" callbacks, we'll end up calling both. Not nice.
Quoted 10 lines
Quoted 5 lines
Quoted 1 line
Does it seem like a reasonable thing to do?
Well, if someone spends time on implementing new callbacks for a bus type, writing them in such a way that they will call the "legacy" callbacks from drivers if necessary is not really a big deal IMO.
Sure. But suppose you _don't_ want to spend the time implementing new callbacks to replace the existing legacy suspend and resume methods, whereas you _do_ want to implement runtime PM. Runtime PM forces the bus type to have a
pm_opsmember,
Which is very much on purpose, because the legacy suspend and resume have no idea about the runtime stuff.
Quoted 1 line
which as you point out, will prevent the legacy methods from being called.
Yes, that's intentional.
That said, I think we might modify the generic callbacks in generic_ops.c to call the drivers' legacy callbacks if the "new" ones are not defined.
Rafael
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 17 lines · Rafael J. Wysocki
Quoted 16 lines · Alan Stern
Quoted 13 lines · Rafael J. Wysocki
Quoted 9 lines
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in
pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.
Quoted 5 lines
Quoted 2 lines
All you have to do is change the "else if" lines in device_[suspend|resume]() to "if".
Then, if a bus type implements both "new" and "old" callbacks, we'll end up calling both. Not nice.
Why would a bus type implement both? Or looked at another way, if it did implement both then wouldn't it want both sets of callbacks to be invoked?
If a bus type does define both types of callback by mistake and only wants one of them to be used, that's a bug -- pure and simple. It's not the PM core's fault if something goes wrong under those circumstances.
Quoted 8 lines
Quoted 4 lines
Sure. But suppose you _don't_ want to spend the time implementing new callbacks to replace the existing legacy suspend and resume methods, whereas you _do_ want to implement runtime PM. Runtime PM forces the bus type to have a
pm_opsmember,Which is very much on purpose, because the legacy suspend and resume have no idea about the runtime stuff.
Quoted 6 lines
Quoted 1 line
which as you point out, will prevent the legacy methods from being called.
Yes, that's intentional.
That said, I think we might modify the generic callbacks in
generic_ops.cto call the drivers' legacy callbacks if the "new" ones are not defined.
That's no good -- the routines in generic_ops.c invoke the _driver's_ callbacks, not the _bus type's_ callbacks.
I suppose you could write a new set of generic "legacy" callbacks that would work just as though the new ops weren't defined. Removing those "else"s would be a lot simpler, though.
Alan Stern
A message that is not in the archive (sent off-list or not yet received): Pine.LNX.4.44L0.1003142117200.7108-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org
Quoted 25 lines · Alan Stern
Quoted 17 lines · Rafael J. Wysocki
Quoted 16 lines · Alan Stern
Quoted 13 lines · Rafael J. Wysocki
Quoted 9 lines
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in
pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.Quoted 5 lines
Quoted 2 lines
All you have to do is change the "else if" lines in device_[suspend|resume]() to "if".
Then, if a bus type implements both "new" and "old" callbacks, we'll end up calling both. Not nice.
Quoted 8 lines
Why would a bus type implement both? Or looked at another way, if it did implement both then wouldn't it want both sets of callbacks to be invoked?
If a bus type does define both types of callback by mistake and only wants one of them to be used, that's a bug -- pure and simple. It's not the PM core's fault if something goes wrong under those circumstances.
In fact, I'd like the "legacy" callbacks to go, at least at the subsystem level, so I'd prefer not to make it easier to keep them around.
How many bus types are there and how many of them actually implement power management callbacks? I don't really think the issue is so big.
Rafael
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Rafael J. Wysocki
In fact, I'd like the "legacy" callbacks to go, at least at the subsystem level, so I'd prefer not to make it easier to keep them around.
How many bus types are there and how many of them actually implement power management callbacks? I don't really think the issue is so big.
I have no idea. But I'm in the middle of implementing runtime PM for SCSI. SCSI already has bus-level legacy callbacks, so to add the runtime methods without changing the existing system sleep behavior requires something like this.
The alternative is to write a bunch of tiny "shim" functions, sort of like what I ended up doing in the USB stack (see usb_dev_prepare() and the following routines in drivers/usb/core/usb.c).
Alan Stern
A message that is not in the archive (sent off-list or not yet received): Pine.LNX.4.44L0.1003151630370.1332-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org
Quoted 8 lines · Alan Stern
Quoted 5 lines · Rafael J. Wysocki
In fact, I'd like the "legacy" callbacks to go, at least at the subsystem level, so I'd prefer not to make it easier to keep them around.
How many bus types are there and how many of them actually implement power management callbacks? I don't really think the issue is so big.
Quoted 8 lines
I have no idea. But I'm in the middle of implementing runtime PM for SCSI. SCSI already has bus-level legacy callbacks, so to add the runtime methods without changing the existing system sleep behavior requires something like this.
The alternative is to write a bunch of tiny "shim" functions, sort of like what I ended up doing in the USB stack (see
usb_dev_prepare()and the following routines indrivers/usb/core/usb.c).
I prefer this approach to changing the core. If we changed the core, it would defeat the whole purpose of introducing the new framework.
Rafael
Quoted 8 lines · Alan Stern
Quoted 5 lines · Rafael J. Wysocki
In fact, I'd like the "legacy" callbacks to go, at least at the subsystem level, so I'd prefer not to make it easier to keep them around.
How many bus types are there and how many of them actually implement power management callbacks? I don't really think the issue is so big.
Quoted 8 lines
I have no idea. But I'm in the middle of implementing runtime PM for SCSI. SCSI already has bus-level legacy callbacks, so to add the runtime methods without changing the existing system sleep behavior requires something like this.
The alternative is to write a bunch of tiny "shim" functions, sort of like what I ended up doing in the USB stack (see
usb_dev_prepare()and the following routines indrivers/usb/core/usb.c).
I prefer this approach to changing the core. If we changed the core, it would defeat the whole purpose of introducing the new framework.
Rafael
Quoted 5 lines · Rafael J. Wysocki
In fact, I'd like the "legacy" callbacks to go, at least at the subsystem level, so I'd prefer not to make it easier to keep them around.
How many bus types are there and how many of them actually implement power management callbacks? I don't really think the issue is so big.
I have no idea. But I'm in the middle of implementing runtime PM for SCSI. SCSI already has bus-level legacy callbacks, so to add the runtime methods without changing the existing system sleep behavior requires something like this.
The alternative is to write a bunch of tiny "shim" functions, sort of like what I ended up doing in the USB stack (see usb_dev_prepare() and the following routines in drivers/usb/core/usb.c).
Alan Stern
Quoted 25 lines · Alan Stern
Quoted 17 lines · Rafael J. Wysocki
Quoted 16 lines · Alan Stern
Quoted 13 lines · Rafael J. Wysocki
Quoted 9 lines
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in
pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.Quoted 5 lines
Quoted 2 lines
All you have to do is change the "else if" lines in device_[suspend|resume]() to "if".
Then, if a bus type implements both "new" and "old" callbacks, we'll end up calling both. Not nice.
Quoted 8 lines
Why would a bus type implement both? Or looked at another way, if it did implement both then wouldn't it want both sets of callbacks to be invoked?
If a bus type does define both types of callback by mistake and only wants one of them to be used, that's a bug -- pure and simple. It's not the PM core's fault if something goes wrong under those circumstances.
In fact, I'd like the "legacy" callbacks to go, at least at the subsystem level, so I'd prefer not to make it easier to keep them around.
How many bus types are there and how many of them actually implement power management callbacks? I don't really think the issue is so big.
Rafael
Quoted 17 lines · Rafael J. Wysocki
Quoted 16 lines · Alan Stern
Quoted 13 lines · Rafael J. Wysocki
Quoted 9 lines
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in
pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.
Quoted 5 lines
Quoted 2 lines
All you have to do is change the "else if" lines in device_[suspend|resume]() to "if".
Then, if a bus type implements both "new" and "old" callbacks, we'll end up calling both. Not nice.
Why would a bus type implement both? Or looked at another way, if it did implement both then wouldn't it want both sets of callbacks to be invoked?
If a bus type does define both types of callback by mistake and only wants one of them to be used, that's a bug -- pure and simple. It's not the PM core's fault if something goes wrong under those circumstances.
Quoted 8 lines
Quoted 4 lines
Sure. But suppose you _don't_ want to spend the time implementing new callbacks to replace the existing legacy suspend and resume methods, whereas you _do_ want to implement runtime PM. Runtime PM forces the bus type to have a
pm_opsmember,Which is very much on purpose, because the legacy suspend and resume have no idea about the runtime stuff.
Quoted 6 lines
Quoted 1 line
which as you point out, will prevent the legacy methods from being called.
Yes, that's intentional.
That said, I think we might modify the generic callbacks in
generic_ops.cto call the drivers' legacy callbacks if the "new" ones are not defined.
That's no good -- the routines in generic_ops.c invoke the _driver's_ callbacks, not the _bus type's_ callbacks.
I suppose you could write a new set of generic "legacy" callbacks that would work just as though the new ops weren't defined. Removing those "else"s would be a lot simpler, though.
Alan Stern
Quoted 10 lines · Alan Stern
Quoted 8 lines · Rafael J. Wysocki
Quoted 8 lines
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in
pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.All you have to do is change the "else if" lines in device_[suspend|resume]() to "if".
Then, if a bus type implements both "new" and "old" callbacks, we'll end up calling both. Not nice.
Quoted 10 lines
Quoted 5 lines
Quoted 1 line
Does it seem like a reasonable thing to do?
Well, if someone spends time on implementing new callbacks for a bus type, writing them in such a way that they will call the "legacy" callbacks from drivers if necessary is not really a big deal IMO.
Sure. But suppose you _don't_ want to spend the time implementing new callbacks to replace the existing legacy suspend and resume methods, whereas you _do_ want to implement runtime PM. Runtime PM forces the bus type to have a
pm_opsmember,
Which is very much on purpose, because the legacy suspend and resume have no idea about the runtime stuff.
Quoted 1 line
which as you point out, will prevent the legacy methods from being called.
Yes, that's intentional.
That said, I think we might modify the generic callbacks in generic_ops.c to call the drivers' legacy callbacks if the "new" ones are not defined.
Rafael
Quoted 8 lines · Rafael J. Wysocki
Quoted 8 lines
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.
Quoted 5 lines
Quoted 1 line
The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in
pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.
All you have to do is change the "else if" lines in device_[suspend|resume]() to "if".
Quoted 5 lines
Quoted 1 line
Does it seem like a reasonable thing to do?
Well, if someone spends time on implementing new callbacks for a bus type, writing them in such a way that they will call the "legacy" callbacks from drivers if necessary is not really a big deal IMO.
Sure. But suppose you _don't_ want to spend the time implementing new callbacks to replace the existing legacy suspend and resume methods, whereas you _do_ want to implement runtime PM. Runtime PM forces the bus type to have a pm_ops member, which as you point out, will prevent the legacy methods from being called.
Alan Stern
Quoted 11 lines · Alan Stern
Quoted 4 lines · Rafael J. Wysocki
Please note that the "legacy" callbacks removed by this patch are already effectively dead, because they are not going to be called by the PM core anyway. I'm not sure if this is what we want, though, so please let me know in case it's not.
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
Quoted 5 lines
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the
pm_opsstructure would be empty.The changes to the PM core necessary to do this are quite small.
Not really. The detection that the particular callback is not present happens in pm_op(), while the decision which framework to use is made at the device_[suspend|resume]() level.
Quoted 1 line
Does it seem like a reasonable thing to do?
Well, if someone spends time on implementing new callbacks for a bus type, writing them in such a way that they will call the "legacy" callbacks from drivers if necessary is not really a big deal IMO.
The problem in this particular case is that I don't know whether or not we _want_ the drivers' "legacy" callbacks to be invoked at all. The $subject patch assumes we don't, but if we do in fact, I'll rework it to do so.
I need that piece of information, though. :-)
Rafael
Quoted 4 lines · Rafael J. Wysocki
Please note that the "legacy" callbacks removed by this patch are already effectively dead, because they are not going to be called by the PM core anyway. I'm not sure if this is what we want, though, so please let me know in case it's not.
You know, maybe we should allow bus types to use both the old and new interfaces. It would make life easier for other subsystems in addition to i2c.
This doesn't mean that the core would end up calling two sets of suspend routines. If the bus type uses legacy routines then all the non-runtime entries in the pm_ops structure would be empty.
The changes to the PM core necessary to do this are quite small. Does it seem like a reasonable thing to do?
Alan Stern
PATCH 1/1 i2c: Fix bus-level power management callbacks
In reply to Rafael J. WysockiQuoted 16 lines · Rafael J. Wysocki
From: Rafael J. Wysocki <[email protected]>
There are three issues with the i2c's power management callbacks at the moment. First, they don't include any hibernate callbacks, although they should at least include the .restore() callback (there's no guarantee that the driver will be in memory before loading the image kernel and we must restore the pre-hibernation state of the device). Second, the "legacy" callbacks are not going to be invoked by the PM core since the bus type's pm object is not NULL. Finally, the system power transition (ie. suspend/resume) callbacks don't check if the device hasn't been already suspended at run time, in which case they should skip suspending it and handle it in a special way during resume. Also, it looks like the i2c bus type itself doesn't need any power management handling beyond that provided by the generic subsystem-level PM callbacks.
Quoted 3 lines
For these reasons, remove the power management callbacks defined by the i2c bus type and make it use the generic subsystem-level power management callbacks.
I assume the lack of responses except for the Alan's one means the patch wasn't correct, so below is one that I think is better. It fixes all of the issues described above without breaking backwards compatibility.
Thanks,
Rafael
---
From: Rafael J. Wysocki <[email protected]>
Subject: i2c: Fix bus-level power management callbacks
There are three issues with the i2c bus type's power management callbacks at the moment. First, they don't include any hibernate callbacks, although they should at least include the .restore() callback (there's no guarantee that the driver will be present in memory before loading the image kernel and we must restore the pre-hibernation state of the device). Second, the "legacy" callbacks are not going to be invoked by the PM core since the bus type's pm object is not NULL. Finally, the system sleep PM (ie. suspend/resume) callbacks don't check if the device has been already suspended at run time, in which case they should skip suspending it. Also, it looks like the i2c bus type can use the generic subsystem-level runtime PM callbacks.
For these reasons, rework the system sleep PM callbacks provided by the i2c bus type to handle hibernation correctly and to invoke the "legacy" callbacks for drivers that provide them. In addition to that make the i2c bus type use the generic subsystem-level runtime PM callbacks.
--- drivers/i2c/i2c-core.c | 168 ++++++++++++++++++++++++++------------------- include/linux/pm_runtime.h | 7 + 2 files changed, 105 insertions(+), 70 deletions(-)
drivers/i2c/i2c-core.c +98 -70
@@ -156,107 +156,131 @@ static void i2c_device_shutdown(struct d driver->shutdown (client); } -#ifdef CONFIG_SUSPEND -static int i2c_device_pm_suspend (struct device *dev) +static int i2c_legacy_suspend (struct device *dev,pm_message_t mesg) { -const struct dev_pm_ops *pm; +struct i2c_client *client =i2c_verify_client (dev); +struct i2c_driver *driver; -if (!dev->driver) +if (!client || !dev->driver)return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->suspend) + driver =to_i2c_driver (dev->driver); +if (!driver->suspend)return 0 ; -return pm->suspend (dev); +return driver->suspend (client, mesg); } -static int i2c_device_pm_resume (struct device *dev) +static int i2c_legacy_resume (struct device *dev) { -const struct dev_pm_ops *pm; +struct i2c_client *client =i2c_verify_client (dev); +struct i2c_driver *driver; -if (!dev->driver) +if (!client || !dev->driver)return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->resume) + driver =to_i2c_driver (dev->driver); +if (!driver->resume)return 0 ; -return pm->resume (dev); +return driver->resume (client); } -#else -#define i2c_device_pm_suspend NULL -#define i2c_device_pm_resume NULL -#endif -#ifdef CONFIG_PM_RUNTIME -static int i2c_device_runtime_suspend (struct device *dev) +#ifdef CONFIG_PM_SLEEP +static int i2c_device_pm_suspend (struct device *dev) { -const struct dev_pm_ops *pm; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; -if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->runtime_suspend) +if (pm_runtime_suspended (dev))return 0 ; -return pm->runtime_suspend (dev); -} -static int i2c_device_runtime_resume (struct device *dev) -{ -const struct dev_pm_ops *pm; +if (pm) +return pm->suspend ? pm->suspend (dev) :0 ; -if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->runtime_resume) -return 0 ; -return pm->runtime_resume (dev); +return i2c_legacy_suspend (dev,PMSG_SUSPEND ); } -static int i2c_device_runtime_idle (struct device *dev) +static int i2c_device_pm_resume (struct device *dev) { -const struct dev_pm_ops *pm =NULL ; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ;int ret; -if (dev->driver) - pm = dev->driver->pm; -if (pm && pm->runtime_idle) { - ret = pm->runtime_idle (dev); -if (ret) -return ret; +if (pm) + ret = pm->resume ? pm->resume (dev) :0 ; +else + ret =i2c_legacy_resume (dev); + +if (!ret) { +pm_runtime_disable (dev); +pm_runtime_set_active (dev); +pm_runtime_enable (dev); } -return pm_runtime_suspend (dev); -} -#else -#define i2c_device_runtime_suspend NULL -#define i2c_device_runtime_resume NULL -#define i2c_device_runtime_idle NULL -#endif +return ret; +} -static int i2c_device_suspend (struct device *dev,pm_message_t mesg) +static int i2c_device_pm_freeze (struct device *dev) { -struct i2c_client *client =i2c_verify_client (dev); -struct i2c_driver *driver; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; -if (!client || !dev->driver) +if (pm_runtime_suspended (dev))return 0 ; - driver =to_i2c_driver (dev->driver); -if (!driver->suspend) -return 0 ; -return driver->suspend (client, mesg); + +if (pm) +return pm->freeze ? pm->freeze (dev) :0 ; + +return i2c_legacy_suspend (dev,PMSG_FREEZE ); } -static int i2c_device_resume (struct device *dev) +static int i2c_device_pm_thaw (struct device *dev) { -struct i2c_client *client =i2c_verify_client (dev); -struct i2c_driver *driver; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; -if (!client || !dev->driver) +if (pm_runtime_suspended (dev))return 0 ; - driver =to_i2c_driver (dev->driver); -if (!driver->resume) + +if (pm) +return pm->thaw ? pm->thaw (dev) :0 ; + +return i2c_legacy_resume (dev); +} + +static int i2c_device_pm_poweroff (struct device *dev) +{ +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; + +if (pm_runtime_suspended (dev))return 0 ; -return driver->resume (client); + +if (pm) +return pm->poweroff ? pm->poweroff (dev) :0 ; + +return i2c_legacy_suspend (dev,PMSG_HIBERNATE ); } +static int i2c_device_pm_restore (struct device *dev) +{ +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; +int ret; + +if (pm) + ret = pm->restore ? pm->restore (dev) :0 ; +else + ret =i2c_legacy_resume (dev); + +if (!ret) { +pm_runtime_disable (dev); +pm_runtime_set_active (dev); +pm_runtime_enable (dev); + } + +return ret; +} +#else /* !CONFIG_PM_SLEEP */ +#define i2c_device_pm_suspend NULL +#define i2c_device_pm_resume NULL +#define i2c_device_pm_freeze NULL +#define i2c_device_pm_thaw NULL +#define i2c_device_pm_poweroff NULL +#define i2c_device_pm_restore NULL +#endif /* !CONFIG_PM_SLEEP */ +static void i2c_client_dev_release (struct device *dev) {kfree (to_i2c_client (dev));
@@ -298,9 +322,15 @@ static const struct attribute_group *i2cstatic const struct dev_pm_ops i2c_device_pm_ops = { .suspend = i2c_device_pm_suspend, .resume = i2c_device_pm_resume, - .runtime_suspend = i2c_device_runtime_suspend, - .runtime_resume = i2c_device_runtime_resume, - .runtime_idle = i2c_device_runtime_idle, + .freeze = i2c_device_pm_freeze, + .thaw = i2c_device_pm_thaw, + .poweroff = i2c_device_pm_poweroff, + .restore = i2c_device_pm_restore, +SET_RUNTIME_PM_OPS ( + pm_generic_runtime_suspend, + pm_generic_runtime_resume, + pm_generic_runtime_idle + ) };struct bus_type i2c_bus_type = {
@@ -309,8 +339,6 @@ struct bus_type i2c_bus_type = { .probe = i2c_device_probe, .remove = i2c_device_remove, .shutdown = i2c_device_shutdown, - .suspend = i2c_device_suspend, - .resume = i2c_device_resume, .pm = &i2c_device_pm_ops, };EXPORT_SYMBOL_GPL (i2c_bus_type);
include/linux/pm_runtime.h +7 -0
@@ -30,6 +30,9 @@ extern void pm_runtime_enable(struct devextern void __pm_runtime_disable (struct device *dev,bool check_resume);extern void pm_runtime_allow (struct device *dev);extern void pm_runtime_forbid (struct device *dev); +extern int pm_generic_runtime_idle (struct device *dev); +extern int pm_generic_runtime_suspend (struct device *dev); +extern int pm_generic_runtime_resume (struct device *dev);static inline bool pm_children_suspended (struct device *dev) {
@@ -96,6 +99,10 @@ static inline bool device_run_wake(strucstatic inline void device_set_run_wake (struct device *dev,bool enable) {}static inline bool pm_runtime_suspended (struct device *dev) {return false; } +static inline int pm_generic_runtime_idle (struct device *dev) {return 0 ; } +static inline int pm_generic_runtime_suspend (struct device *dev) {return 0 ; } +static inline int pm_generic_runtime_resume (struct device *dev) {return 0 ; } +#endif /* !CONFIG_PM_RUNTIME */ static inline int pm_runtime_get (struct device *dev)
Re: [PATCH] i2c: Fix bus-level power management callbacks
Hi Rafael,
Quoted 24 lines · Rafael J. Wysocki
I assume the lack of responses except for the Alan's one means the patch wasn't correct, so below is one that I think is better. It fixes all of the issues described above without breaking backwards compatibility.
Thanks,
Rafael---
From: Rafael J. Wysocki <[email protected]>
Subject: i2c: Fix bus-level power management callbacksThere are three issues with the i2c bus type's power management callbacks at the moment. First, they don't include any hibernate callbacks, although they should at least include the .restore() callback (there's no guarantee that the driver will be present in memory before loading the image kernel and we must restore the pre-hibernation state of the device). Second, the "legacy" callbacks are not going to be invoked by the PM core since the bus type's pm object is not NULL. Finally, the system sleep PM (ie. suspend/resume) callbacks don't check if the device has been already suspended at run time, in which case they should skip suspending it. Also, it looks like the i2c bus type can use the generic subsystem-level runtime PM callbacks.
Quoted 7 lines
For these reasons, rework the system sleep PM callbacks provided by the i2c bus type to handle hibernation correctly and to invoke the "legacy" callbacks for drivers that provide them. In addition to that make the i2c bus type use the generic subsystem-level runtime PM callbacks.
Signed-off-by Rafael J. Wysocki <[email protected]>
Mark, you contributed the initial runtime PM support for the i2c subsystem, I thought you would have comments on Rafael's reimplementation?
Quoted 3 lines
--- drivers/i2c/i2c-core.c | 168 ++++++++++++++++++++++++++------------------- include/linux/pm_runtime.h | 7 +
I am a little surprised to see changes to a generic header file here, how is the i2c subsystem so special that we have needs other subsystems did not?
Quoted 42 lines
2 files changed, 105 insertions(+), 70 deletions(-)Index:
linux-2.6/drivers/i2c/i2c-core.c
===================================================================drivers/i2c/i2c-core.c +11
-12@@ -156,107 +156,131 @@ static void i2c_device_shutdown(struct d driver->shutdown (client); } -#ifdef CONFIG_SUSPEND -static int i2c_device_pm_suspend (struct device *dev) +static int i2c_legacy_suspend (struct device *dev,pm_message_t mesg) { -const struct dev_pm_ops *pm; +struct i2c_client *client =i2c_verify_client (dev); +struct i2c_driver *driver; -if (!dev->driver) +if (!client || !dev->driver)return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->suspend) + driver =to_i2c_driver (dev->driver); +if (!driver->suspend)return 0 ; -return pm->suspend (dev); +return driver->suspend (client, mesg); } -static int i2c_device_pm_resume (struct device *dev) +static int i2c_legacy_resume (struct device *dev) { -const struct dev_pm_ops *pm; +struct i2c_client *client =i2c_verify_client (dev); +struct i2c_driver *driver; -if (!dev->driver) +if (!client || !dev->driver)return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->resume)
drivers/i2c/i2c-core.c static void i2c_device_shutdown(struct d · line 186
Quoted 10 lines
drivers/i2c/i2c-core.c +3
-5+ driver =to_i2c_driver (dev->driver); +if (!driver->resume)return 0 ; - return pm->resume(dev); +return driver->resume (client); } -#else -#define i2c_device_pm_suspend NULL -#define i2c_device_pm_resume NULL -#endif
I fail to see why the functions above are outside of the #ifdef CONFIG_PM_SLEEP scope. They are only called by functions which are inside the #ifdef CONFIG_PM_SLEEP scope, so you'll get a build-time warning if CONFIG_PM_SLEEP isn't set.
Is there a plan to get rid of the above legacy functions at some point in time?
Quoted 8 lines
drivers/i2c/i2c-core.c +3
-3-#ifdef CONFIG_PM_RUNTIME -static int i2c_device_runtime_suspend (struct device *dev) +#ifdef CONFIG_PM_SLEEP +static int i2c_device_pm_suspend (struct device *dev) { -const struct dev_pm_ops *pm; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ;
drivers/i2c/i2c-core.c static void i2c_device_shutdown(struct d · line 199
Quoted 10 lines
drivers/i2c/i2c-core.c +1
-6-if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->runtime_suspend) +if (pm_runtime_suspended (dev))return 0 ; -return pm->runtime_suspend (dev); -}
Apart from the above, the code looks sane to me, but then again I don't know a thing about power management. I'll keep this patch in my i2c tree, scheduled for merge in 2.6.35. If there are any updates, please send them over, either as a new patch or as incremental changes which I will merge myself.
Signature · 1 line
Jean Delvare
Mark Brown
Acked-byRe: [PATCH] i2c: Fix bus-level power management callbacks
Quoted 3 lines · Jean Delvare
Mark, you contributed the initial runtime PM support for the i2c subsystem, I thought you would have comments on Rafael's reimplementation?
Yeah, see below...
Quoted 6 lines
Quoted 2 lines
drivers/i2c/i2c-core.c | 168 ++++++++++++++++++++++++++------------------- include/linux/pm_runtime.h | 7 +I am a little surprised to see changes to a generic header file here, how is the i2c subsystem so special that we have needs other subsystems did not?
Very few subsystems actually support runtime PM thus far - I think it's more the case that I2C is an early user than anything else.
Quoted 5 lines
Apart from the above, the code looks sane to me, but then again I don't know a thing about power management. I'll keep this patch in my i2c tree, scheduled for merge in 2.6.35. If there are any updates, please send them over, either as a new patch or as incremental changes which I will merge myself.
I'm in a similar position - the code looks fine except I'm not 100% sure I follow all the possible ifdefs and I've never actually used hibernate (s2disk isn't supported on ARM) but for what it's worth:
Re: [PATCH] i2c: Fix bus-level power management callbacks
Quoted 11 lines · Mark Brown
Quoted 3 lines · Jean Delvare
Mark, you contributed the initial runtime PM support for the i2c subsystem, I thought you would have comments on Rafael's reimplementation?
Yeah, see below...
Quoted 2 lines
Quoted 2 lines
drivers/i2c/i2c-core.c | 168 ++++++++++++++++++++++++++------------------- include/linux/pm_runtime.h | 7 +
Quoted 6 lines
Quoted 3 lines
I am a little surprised to see changes to a generic header file here, how is the i2c subsystem so special that we have needs other subsystems did not?
Very few subsystems actually support runtime PM thus far - I think it's more the case that I2C is an early user than anything else.
That's the case indeed.
Quoted 11 lines
Quoted 5 lines
Apart from the above, the code looks sane to me, but then again I don't know a thing about power management. I'll keep this patch in my i2c tree, scheduled for merge in 2.6.35. If there are any updates, please send them over, either as a new patch or as incremental changes which I will merge myself.
I'm in a similar position - the code looks fine except I'm not 100% sure I follow all the possible ifdefs and I've never actually used hibernate (s2disk isn't supported on ARM) but for what it's worth:
Acked-by Mark Brown <[email protected]>
Thanks!
Rafael
Re: [PATCH] i2c: Fix bus-level power management callbacks
In reply to Mark BrownQuoted 11 lines · Mark Brown
Quoted 3 lines · Jean Delvare
Mark, you contributed the initial runtime PM support for the i2c subsystem, I thought you would have comments on Rafael's reimplementation?
Yeah, see below...
Quoted 2 lines
Quoted 2 lines
drivers/i2c/i2c-core.c | 168 ++++++++++++++++++++++++++------------------- include/linux/pm_runtime.h | 7 +
Quoted 6 lines
Quoted 3 lines
I am a little surprised to see changes to a generic header file here, how is the i2c subsystem so special that we have needs other subsystems did not?
Very few subsystems actually support runtime PM thus far - I think it's more the case that I2C is an early user than anything else.
That's the case indeed.
Quoted 11 lines
Quoted 5 lines
Apart from the above, the code looks sane to me, but then again I don't know a thing about power management. I'll keep this patch in my i2c tree, scheduled for merge in 2.6.35. If there are any updates, please send them over, either as a new patch or as incremental changes which I will merge myself.
I'm in a similar position - the code looks fine except I'm not 100% sure I follow all the possible ifdefs and I've never actually used hibernate (s2disk isn't supported on ARM) but for what it's worth:
Acked-by Mark Brown <[email protected]>
Thanks!
Rafael
Mark Brown
Acked-byRe: [PATCH] i2c: Fix bus-level power management callbacks
In reply to Jean DelvareQuoted 3 lines · Jean Delvare
Mark, you contributed the initial runtime PM support for the i2c subsystem, I thought you would have comments on Rafael's reimplementation?
Yeah, see below...
Quoted 6 lines
Quoted 2 lines
drivers/i2c/i2c-core.c | 168 ++++++++++++++++++++++++++------------------- include/linux/pm_runtime.h | 7 +I am a little surprised to see changes to a generic header file here, how is the i2c subsystem so special that we have needs other subsystems did not?
Very few subsystems actually support runtime PM thus far - I think it's more the case that I2C is an early user than anything else.
Quoted 5 lines
Apart from the above, the code looks sane to me, but then again I don't know a thing about power management. I'll keep this patch in my i2c tree, scheduled for merge in 2.6.35. If there are any updates, please send them over, either as a new patch or as incremental changes which I will merge myself.
I'm in a similar position - the code looks fine except I'm not 100% sure I follow all the possible ifdefs and I've never actually used hibernate (s2disk isn't supported on ARM) but for what it's worth:
Re: [PATCH] i2c: Fix bus-level power management callbacks
In reply to Rafael J. WysockiHi Rafael,
Quoted 24 lines · Rafael J. Wysocki
I assume the lack of responses except for the Alan's one means the patch wasn't correct, so below is one that I think is better. It fixes all of the issues described above without breaking backwards compatibility.
Thanks,
Rafael---
From: Rafael J. Wysocki <[email protected]>
Subject: i2c: Fix bus-level power management callbacksThere are three issues with the i2c bus type's power management callbacks at the moment. First, they don't include any hibernate callbacks, although they should at least include the .restore() callback (there's no guarantee that the driver will be present in memory before loading the image kernel and we must restore the pre-hibernation state of the device). Second, the "legacy" callbacks are not going to be invoked by the PM core since the bus type's pm object is not NULL. Finally, the system sleep PM (ie. suspend/resume) callbacks don't check if the device has been already suspended at run time, in which case they should skip suspending it. Also, it looks like the i2c bus type can use the generic subsystem-level runtime PM callbacks.
Quoted 7 lines
For these reasons, rework the system sleep PM callbacks provided by the i2c bus type to handle hibernation correctly and to invoke the "legacy" callbacks for drivers that provide them. In addition to that make the i2c bus type use the generic subsystem-level runtime PM callbacks.
Signed-off-by Rafael J. Wysocki <[email protected]>
Mark, you contributed the initial runtime PM support for the i2c subsystem, I thought you would have comments on Rafael's reimplementation?
Quoted 3 lines
--- drivers/i2c/i2c-core.c | 168 ++++++++++++++++++++++++++------------------- include/linux/pm_runtime.h | 7 +
I am a little surprised to see changes to a generic header file here, how is the i2c subsystem so special that we have needs other subsystems did not?
Quoted 42 lines
2 files changed, 105 insertions(+), 70 deletions(-)Index:
linux-2.6/drivers/i2c/i2c-core.c
===================================================================drivers/i2c/i2c-core.c +11
-12@@ -156,107 +156,131 @@ static void i2c_device_shutdown(struct d driver->shutdown (client); } -#ifdef CONFIG_SUSPEND -static int i2c_device_pm_suspend (struct device *dev) +static int i2c_legacy_suspend (struct device *dev,pm_message_t mesg) { -const struct dev_pm_ops *pm; +struct i2c_client *client =i2c_verify_client (dev); +struct i2c_driver *driver; -if (!dev->driver) +if (!client || !dev->driver)return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->suspend) + driver =to_i2c_driver (dev->driver); +if (!driver->suspend)return 0 ; -return pm->suspend (dev); +return driver->suspend (client, mesg); } -static int i2c_device_pm_resume (struct device *dev) +static int i2c_legacy_resume (struct device *dev) { -const struct dev_pm_ops *pm; +struct i2c_client *client =i2c_verify_client (dev); +struct i2c_driver *driver; -if (!dev->driver) +if (!client || !dev->driver)return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->resume)
drivers/i2c/i2c-core.c static void i2c_device_shutdown(struct d · line 186
Quoted 10 lines
drivers/i2c/i2c-core.c +3
-5+ driver =to_i2c_driver (dev->driver); +if (!driver->resume)return 0 ; - return pm->resume(dev); +return driver->resume (client); } -#else -#define i2c_device_pm_suspend NULL -#define i2c_device_pm_resume NULL -#endif
I fail to see why the functions above are outside of the #ifdef CONFIG_PM_SLEEP scope. They are only called by functions which are inside the #ifdef CONFIG_PM_SLEEP scope, so you'll get a build-time warning if CONFIG_PM_SLEEP isn't set.
Is there a plan to get rid of the above legacy functions at some point in time?
Quoted 8 lines
drivers/i2c/i2c-core.c +3
-3-#ifdef CONFIG_PM_RUNTIME -static int i2c_device_runtime_suspend (struct device *dev) +#ifdef CONFIG_PM_SLEEP +static int i2c_device_pm_suspend (struct device *dev) { -const struct dev_pm_ops *pm; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ;
drivers/i2c/i2c-core.c static void i2c_device_shutdown(struct d · line 199
Quoted 10 lines
drivers/i2c/i2c-core.c +1
-6-if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->runtime_suspend) +if (pm_runtime_suspended (dev))return 0 ; -return pm->runtime_suspend (dev); -}
Apart from the above, the code looks sane to me, but then again I don't know a thing about power management. I'll keep this patch in my i2c tree, scheduled for merge in 2.6.35. If there are any updates, please send them over, either as a new patch or as incremental changes which I will merge myself.
Signature · 1 line
Jean Delvare
PATCH 1/1 i2c: Fix bus-level power management callbacks
In reply to Rafael J. WysockiQuoted 16 lines · Rafael J. Wysocki
From: Rafael J. Wysocki <[email protected]>
There are three issues with the i2c's power management callbacks at the moment. First, they don't include any hibernate callbacks, although they should at least include the .restore() callback (there's no guarantee that the driver will be in memory before loading the image kernel and we must restore the pre-hibernation state of the device). Second, the "legacy" callbacks are not going to be invoked by the PM core since the bus type's pm object is not NULL. Finally, the system power transition (ie. suspend/resume) callbacks don't check if the device hasn't been already suspended at run time, in which case they should skip suspending it and handle it in a special way during resume. Also, it looks like the i2c bus type itself doesn't need any power management handling beyond that provided by the generic subsystem-level PM callbacks.
Quoted 3 lines
For these reasons, remove the power management callbacks defined by the i2c bus type and make it use the generic subsystem-level power management callbacks.
I assume the lack of responses except for the Alan's one means the patch wasn't correct, so below is one that I think is better. It fixes all of the issues described above without breaking backwards compatibility.
Thanks,
Rafael
---
From: Rafael J. Wysocki <[email protected]>
Subject: i2c: Fix bus-level power management callbacks
There are three issues with the i2c bus type's power management callbacks at the moment. First, they don't include any hibernate callbacks, although they should at least include the .restore() callback (there's no guarantee that the driver will be present in memory before loading the image kernel and we must restore the pre-hibernation state of the device). Second, the "legacy" callbacks are not going to be invoked by the PM core since the bus type's pm object is not NULL. Finally, the system sleep PM (ie. suspend/resume) callbacks don't check if the device has been already suspended at run time, in which case they should skip suspending it. Also, it looks like the i2c bus type can use the generic subsystem-level runtime PM callbacks.
For these reasons, rework the system sleep PM callbacks provided by the i2c bus type to handle hibernation correctly and to invoke the "legacy" callbacks for drivers that provide them. In addition to that make the i2c bus type use the generic subsystem-level runtime PM callbacks.
--- drivers/i2c/i2c-core.c | 168 ++++++++++++++++++++++++++------------------- include/linux/pm_runtime.h | 7 + 2 files changed, 105 insertions(+), 70 deletions(-)
drivers/i2c/i2c-core.c +98 -70
@@ -156,107 +156,131 @@ static void i2c_device_shutdown(struct d driver->shutdown (client); } -#ifdef CONFIG_SUSPEND -static int i2c_device_pm_suspend (struct device *dev) +static int i2c_legacy_suspend (struct device *dev,pm_message_t mesg) { -const struct dev_pm_ops *pm; +struct i2c_client *client =i2c_verify_client (dev); +struct i2c_driver *driver; -if (!dev->driver) +if (!client || !dev->driver)return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->suspend) + driver =to_i2c_driver (dev->driver); +if (!driver->suspend)return 0 ; -return pm->suspend (dev); +return driver->suspend (client, mesg); } -static int i2c_device_pm_resume (struct device *dev) +static int i2c_legacy_resume (struct device *dev) { -const struct dev_pm_ops *pm; +struct i2c_client *client =i2c_verify_client (dev); +struct i2c_driver *driver; -if (!dev->driver) +if (!client || !dev->driver)return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->resume) + driver =to_i2c_driver (dev->driver); +if (!driver->resume)return 0 ; -return pm->resume (dev); +return driver->resume (client); } -#else -#define i2c_device_pm_suspend NULL -#define i2c_device_pm_resume NULL -#endif -#ifdef CONFIG_PM_RUNTIME -static int i2c_device_runtime_suspend (struct device *dev) +#ifdef CONFIG_PM_SLEEP +static int i2c_device_pm_suspend (struct device *dev) { -const struct dev_pm_ops *pm; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; -if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->runtime_suspend) +if (pm_runtime_suspended (dev))return 0 ; -return pm->runtime_suspend (dev); -} -static int i2c_device_runtime_resume (struct device *dev) -{ -const struct dev_pm_ops *pm; +if (pm) +return pm->suspend ? pm->suspend (dev) :0 ; -if (!dev->driver) -return 0 ; - pm = dev->driver->pm; -if (!pm || !pm->runtime_resume) -return 0 ; -return pm->runtime_resume (dev); +return i2c_legacy_suspend (dev,PMSG_SUSPEND ); } -static int i2c_device_runtime_idle (struct device *dev) +static int i2c_device_pm_resume (struct device *dev) { -const struct dev_pm_ops *pm =NULL ; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ;int ret; -if (dev->driver) - pm = dev->driver->pm; -if (pm && pm->runtime_idle) { - ret = pm->runtime_idle (dev); -if (ret) -return ret; +if (pm) + ret = pm->resume ? pm->resume (dev) :0 ; +else + ret =i2c_legacy_resume (dev); + +if (!ret) { +pm_runtime_disable (dev); +pm_runtime_set_active (dev); +pm_runtime_enable (dev); } -return pm_runtime_suspend (dev); -} -#else -#define i2c_device_runtime_suspend NULL -#define i2c_device_runtime_resume NULL -#define i2c_device_runtime_idle NULL -#endif +return ret; +} -static int i2c_device_suspend (struct device *dev,pm_message_t mesg) +static int i2c_device_pm_freeze (struct device *dev) { -struct i2c_client *client =i2c_verify_client (dev); -struct i2c_driver *driver; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; -if (!client || !dev->driver) +if (pm_runtime_suspended (dev))return 0 ; - driver =to_i2c_driver (dev->driver); -if (!driver->suspend) -return 0 ; -return driver->suspend (client, mesg); + +if (pm) +return pm->freeze ? pm->freeze (dev) :0 ; + +return i2c_legacy_suspend (dev,PMSG_FREEZE ); } -static int i2c_device_resume (struct device *dev) +static int i2c_device_pm_thaw (struct device *dev) { -struct i2c_client *client =i2c_verify_client (dev); -struct i2c_driver *driver; +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; -if (!client || !dev->driver) +if (pm_runtime_suspended (dev))return 0 ; - driver =to_i2c_driver (dev->driver); -if (!driver->resume) + +if (pm) +return pm->thaw ? pm->thaw (dev) :0 ; + +return i2c_legacy_resume (dev); +} + +static int i2c_device_pm_poweroff (struct device *dev) +{ +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; + +if (pm_runtime_suspended (dev))return 0 ; -return driver->resume (client); + +if (pm) +return pm->poweroff ? pm->poweroff (dev) :0 ; + +return i2c_legacy_suspend (dev,PMSG_HIBERNATE ); } +static int i2c_device_pm_restore (struct device *dev) +{ +const struct dev_pm_ops *pm = dev->driver ? dev->driver->pm :NULL ; +int ret; + +if (pm) + ret = pm->restore ? pm->restore (dev) :0 ; +else + ret =i2c_legacy_resume (dev); + +if (!ret) { +pm_runtime_disable (dev); +pm_runtime_set_active (dev); +pm_runtime_enable (dev); + } + +return ret; +} +#else /* !CONFIG_PM_SLEEP */ +#define i2c_device_pm_suspend NULL +#define i2c_device_pm_resume NULL +#define i2c_device_pm_freeze NULL +#define i2c_device_pm_thaw NULL +#define i2c_device_pm_poweroff NULL +#define i2c_device_pm_restore NULL +#endif /* !CONFIG_PM_SLEEP */ +static void i2c_client_dev_release (struct device *dev) {kfree (to_i2c_client (dev));
@@ -298,9 +322,15 @@ static const struct attribute_group *i2cstatic const struct dev_pm_ops i2c_device_pm_ops = { .suspend = i2c_device_pm_suspend, .resume = i2c_device_pm_resume, - .runtime_suspend = i2c_device_runtime_suspend, - .runtime_resume = i2c_device_runtime_resume, - .runtime_idle = i2c_device_runtime_idle, + .freeze = i2c_device_pm_freeze, + .thaw = i2c_device_pm_thaw, + .poweroff = i2c_device_pm_poweroff, + .restore = i2c_device_pm_restore, +SET_RUNTIME_PM_OPS ( + pm_generic_runtime_suspend, + pm_generic_runtime_resume, + pm_generic_runtime_idle + ) };struct bus_type i2c_bus_type = {
@@ -309,8 +339,6 @@ struct bus_type i2c_bus_type = { .probe = i2c_device_probe, .remove = i2c_device_remove, .shutdown = i2c_device_shutdown, - .suspend = i2c_device_suspend, - .resume = i2c_device_resume, .pm = &i2c_device_pm_ops, };EXPORT_SYMBOL_GPL (i2c_bus_type);
include/linux/pm_runtime.h +7 -0
@@ -30,6 +30,9 @@ extern void pm_runtime_enable(struct devextern void __pm_runtime_disable (struct device *dev,bool check_resume);extern void pm_runtime_allow (struct device *dev);extern void pm_runtime_forbid (struct device *dev); +extern int pm_generic_runtime_idle (struct device *dev); +extern int pm_generic_runtime_suspend (struct device *dev); +extern int pm_generic_runtime_resume (struct device *dev);static inline bool pm_children_suspended (struct device *dev) {
@@ -96,6 +99,10 @@ static inline bool device_run_wake(strucstatic inline void device_set_run_wake (struct device *dev,bool enable) {}static inline bool pm_runtime_suspended (struct device *dev) {return false; } +static inline int pm_generic_runtime_idle (struct device *dev) {return 0 ; } +static inline int pm_generic_runtime_suspend (struct device *dev) {return 0 ; } +static inline int pm_generic_runtime_resume (struct device *dev) {return 0 ; } +#endif /* !CONFIG_PM_RUNTIME */ static inline int pm_runtime_get (struct device *dev)