mirror of
https://github.com/rd-stuffs/msm-4.14.git
synced 2025-02-20 11:45:48 +08:00
ef222e3b72
The RPM may give back no ACK when sending a command: this means that it is locking up for some reason, or the command itself didn't get sent to it. When we get in this situation, an infinite wait for completion will lock up the device for an infinite amount of time, until the user manually reboots it with a power cut or KPDPWR+RESIN combination. For this reason, add a timeout to the completion wait (as of now, very large I'd say) to avoid indefinitely waiting and, if the timeout is reached with no ACK reply, just return a -ETIMEDOUT error, so that we will either end up recoverying from this error state or rebooting the device by panicking the kernel if subsequent retries won't work. This issue is largely seen on SMD communication and rarely on SoCs using GLINK to communicate to the RPM. Change-Id: Ifb701e767edab792d92d71fdc05a3e0edd91d766 Signed-off-by: Richard Raya <rdxzv.dev@gmail.com>
Linux kernel ============ This file was moved to Documentation/admin-guide/README.rst Please notice that there are several guides for kernel developers and users. These guides can be rendered in a number of formats, like HTML and PDF. In order to build the documentation, use ``make htmldocs`` or ``make pdfdocs``. 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.