From: Stephen Warren <hidden> Date: 2011-09-22 17:51:46
From: Dilan Lee <redacted>
Various drivers need to use the I2C bus during suspend. Generally, this
is already supported, since devices are suspended based on (the inverse of)
probe order, and an I2C-based device can't probe until the I2C bus upon
which it sits has been probed first.
However, some subsystems, notably ASoC, do not enjoy such simple bus/child
probing relationships. In particular, an ASoC machine driver (and hence a
sound card) may probe very early on before all its required resources are
available. After all required resources become available, the overall
machine driver initialization is performed. Suspend of a sound card occurs
based on the machine driver's probe timing, which may mean suspend occurs
after an I2C bus has been suspended. In turn, components within the sound
card suspend when the overall card suspends. If one of those components
is an I2C device, this may mean the device attempts to suspend after the
I2C bus it sits upon. Conversely, resume may occur before the I2C bus is
available. Consequently, I2C accesses during suspend/resume will fail.
This causes the following issue:
We found the register settings of wm8903(an audio codec) can't be modified
in snd_soc_suspend since I2C bus has been suspended before snd_soc_suspend.
Pop noise will occur when system resume from LP0 if the register settings
of wm8903 haven't be modified correctly in snd_soc_suspend.
To solve this, the I2C bus driver is modified to use suspend_noirq and
resume_noirq instead of suspend and resume. This delays the I2C bus suspend
until after the ASoC card-level suspend, and everything works.
It is acknowledged that this is not an ideal solution. However, this solution
is the best currently available within the kernel.
Suggested alternatives are:
* Implement an explicit dependency management system within the kernel for
device suspend/resume, such that I2C bus would not be suspended before
the sound card that requires it. It is reported that Linus rejected this
proposal since he wanted suspend ordering to be based on probe ordering.
* Enhance device probing such that the ASoC sound card device could defer
its probing until all required resources were available. This would
then cause the overall sound card suspend to occur at an appropriate early
time. Grant Likely was reported to have been working towards this goal.
[swarren: Rewrote patch description to reflect upstream discussion]
Signed-off-by: Dilan Lee <redacted>
Signed-off-by: Stephen Warren <redacted>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Mark Brown <redacted>
---
v2: Summarized the email thread in patch description.
Added Arnd/Mark's ack/review tags
drivers/i2c/busses/i2c-tegra.c | 19 +++++++++++++------
1 files changed, 13 insertions(+), 6 deletions(-)
From: Grant Likely <hidden> Date: 2011-09-22 18:03:42
On Thu, Sep 22, 2011 at 11:51:32AM -0600, Stephen Warren wrote:
From: Dilan Lee <redacted>
Various drivers need to use the I2C bus during suspend. Generally, this
is already supported, since devices are suspended based on (the inverse of)
probe order, and an I2C-based device can't probe until the I2C bus upon
which it sits has been probed first.
However, some subsystems, notably ASoC, do not enjoy such simple bus/child
probing relationships. In particular, an ASoC machine driver (and hence a
sound card) may probe very early on before all its required resources are
available. After all required resources become available, the overall
machine driver initialization is performed. Suspend of a sound card occurs
based on the machine driver's probe timing, which may mean suspend occurs
after an I2C bus has been suspended. In turn, components within the sound
card suspend when the overall card suspends. If one of those components
is an I2C device, this may mean the device attempts to suspend after the
I2C bus it sits upon. Conversely, resume may occur before the I2C bus is
available. Consequently, I2C accesses during suspend/resume will fail.
This causes the following issue:
We found the register settings of wm8903(an audio codec) can't be modified
in snd_soc_suspend since I2C bus has been suspended before snd_soc_suspend.
Pop noise will occur when system resume from LP0 if the register settings
of wm8903 haven't be modified correctly in snd_soc_suspend.
To solve this, the I2C bus driver is modified to use suspend_noirq and
resume_noirq instead of suspend and resume. This delays the I2C bus suspend
until after the ASoC card-level suspend, and everything works.
It is acknowledged that this is not an ideal solution. However, this solution
is the best currently available within the kernel.
Suggested alternatives are:
* Implement an explicit dependency management system within the kernel for
device suspend/resume, such that I2C bus would not be suspended before
the sound card that requires it. It is reported that Linus rejected this
proposal since he wanted suspend ordering to be based on probe ordering.
This really should be revisted. That was in the context of full
system suspend, but we're now in a world of runtime suspend which
absolutely does need dependency tracking or reference counting to get
the ordering right.
* Enhance device probing such that the ASoC sound card device could defer
its probing until all required resources were available. This would
then cause the overall sound card suspend to occur at an appropriate early
time. Grant Likely was reported to have been working towards this goal.
Yes, I'll send you my current patch for you to look at. One of the
engineers from Linaro is going to be pushing that patch set forward.
However, I don't know if it helps with this problem because I believe
that the suspend order is based on the implicit probe order of
devices, but my patch allows drivers to cause the probe order to get
rearranged at runtime. I don't believe there is a global list showing
the order that devices successfully got probed, but I may be wrong
here.
g.
quoted hunk
[swarren: Rewrote patch description to reflect upstream discussion]
Signed-off-by: Dilan Lee <redacted>
Signed-off-by: Stephen Warren <redacted>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Mark Brown <redacted>
---
v2: Summarized the email thread in patch description.
Added Arnd/Mark's ack/review tags
drivers/i2c/busses/i2c-tegra.c | 19 +++++++++++++------
1 files changed, 13 insertions(+), 6 deletions(-)
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Mark Brown <hidden> Date: 2011-09-22 18:13:17
On Thu, Sep 22, 2011 at 12:03:35PM -0600, Grant Likely wrote:
On Thu, Sep 22, 2011 at 11:51:32AM -0600, Stephen Warren wrote:
quoted
* Implement an explicit dependency management system within the kernel for
device suspend/resume, such that I2C bus would not be suspended before
the sound card that requires it. It is reported that Linus rejected this
proposal since he wanted suspend ordering to be based on probe ordering.
This really should be revisted. That was in the context of full
system suspend, but we're now in a world of runtime suspend which
absolutely does need dependency tracking or reference counting to get
the ordering right.
FWIW this was one of the bigger issues in the PM miniconference in Santa
Rosa, though a lot of the discission involved explaining the issues to
some of the x86 guys and there wasn't mssive progress on solutions.
quoted
* Enhance device probing such that the ASoC sound card device could defer
its probing until all required resources were available. This would
then cause the overall sound card suspend to occur at an appropriate early
time. Grant Likely was reported to have been working towards this goal.
Yes, I'll send you my current patch for you to look at. One of the
engineers from Linaro is going to be pushing that patch set forward.
However, I don't know if it helps with this problem because I believe
that the suspend order is based on the implicit probe order of
devices, but my patch allows drivers to cause the probe order to get
rearranged at runtime. I don't believe there is a global list showing
the order that devices successfully got probed, but I may be wrong
here.
Yes, I'm not convinced it'll change anything here. Though I guess it
should be a simple matter of programming to move devices around the list
depending on when they probe.