No description
93f8a37113
Consider a scenario when a device which supports auto suspend is connected to DUT and auto suspend happened. Now, as the device is disconnected to DUT. Resume_work is called due to extcon notification of disconnect and then again suspend is expected to schedule. As a part of disconnect, pwr event irq and DP_HS_PHY_IRQ also got triggered and now since usb is in lpm, resume work got scheduled twice. This resume work flushed sm_work which is stuck because disable_irq call is waiting for pwr_irq call which called resume_work to complete. This is clearly a circular dependency because resume work will flush sm_work which is waiting for pwr_irq_thread to be complete because disable_irq in msm_suspend waits for pwr_irq_handler to complete. Solve this by replacing disable_irq api with disable_irq_nosync so that it doesn't block control suspend. Below are the sequence of events. usb is auto suspended with device connected to DUT. Now device is disconnected from DUT and hence resume hanppens first and then suspend. dwc3_resume_work is called due to extcon as a part of disconnect then suspend will be scheduled. When dwc3 is still in lpm, i.e dwc3_resume_work did not take effect yet. Now power event irq is fired because of which resume work runs. This resume work flushes sm work. Which is currently executing msm_suspend where disable_irq is waiting for power_irq call to finish which is waiting for sm_work to finish. Change-Id: Ibf6e73663d4acaf997291e7eff6577adeaad6e8a Signed-off-by: Rohith Kollalsi <quic_rkollals@quicinc.com> |
||
|---|---|---|
| arch | ||
| block | ||
| certs | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| firmware | ||
| fs | ||
| include | ||
| init | ||
| ipc | ||
| kernel | ||
| lib | ||
| LICENSES | ||
| mm | ||
| net | ||
| samples | ||
| scripts | ||
| security | ||
| sound | ||
| techpack | ||
| tools | ||
| usr | ||
| virt | ||
| .clang-format | ||
| .cocciconfig | ||
| .get_maintainer.ignore | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| abi_gki_aarch64.xml | ||
| abi_gki_aarch64_cuttlefish_whitelist | ||
| abi_gki_aarch64_qcom_whitelist | ||
| abi_gki_aarch64_whitelist | ||
| Android.bp | ||
| AndroidKernel.mk | ||
| build.config.aarch64 | ||
| build.config.allmodconfig | ||
| build.config.allmodconfig.aarch64 | ||
| build.config.allmodconfig.x86_64 | ||
| build.config.common | ||
| build.config.cuttlefish.aarch64 | ||
| build.config.cuttlefish.x86_64 | ||
| build.config.gki | ||
| build.config.gki.aarch64 | ||
| build.config.gki.x86_64 | ||
| build.config.goldfish.arm | ||
| build.config.goldfish.arm64 | ||
| build.config.goldfish.mips | ||
| build.config.goldfish.mips64 | ||
| build.config.goldfish.x86 | ||
| build.config.goldfish.x86_64 | ||
| build.config.x86_64 | ||
| COPYING | ||
| CREDITS | ||
| cuttlefish.fragment | ||
| gen_headers_arm.bp | ||
| gen_headers_arm64.bp | ||
| Kbuild | ||
| Kconfig | ||
| kernel_headers.py | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| verity_dev_keys.x509 | ||
Linux kernel
============
There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.
In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``. The formatted documentation can also be read online at:
https://www.kernel.org/doc/html/latest/
There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.
See Documentation/00-INDEX for a list of what is contained in each file.
Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.