Modify esoc driver to introduce new compatible and fops
for marmot external modem target.
Change-Id: I206a6ca7d964013cb1814e0fcf45997982ed45eb
Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
Modify esoc driver to introduce new compatible and fops
for sdxchitwan.
Change-Id: Ieb2c6c3ba6a05cf879c0b2c53cbf995540898774
Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
Wait for modem status to go low in crash shutdown. This helps
cover the race condition where there is a crash during graceful
shutdown and we end up in crash path and send crash notification
to clients even before the modem status has gone low. Also set
the crash flag in interrupt path to avoid double queueing of ssr
work.
Change-Id: I680b79c7a1de5e44cb9fcfa0f9d67517c0398f62
Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
In situations where graceful shutdown and errfatal occur parallely on
modem, the graceful shutdown thread can go into crash shutdown path
because the crash flag is set asynchronously in errfatal handler.
In this case clients are notified that modem has crashed even though
it hasn't crashed completely. Clients perform cleanup based on the
assumption that modem is completely crashed and this might lead use
after free scenarios. Therefore wait for modem status to go low to
set the crash flag.
Change-Id: Ibafc54b3a136816c33476a28492bd081b053eecc
Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
SSR shutdown and reboot notifier both invoke clients hooks. These hooks
might be invoked at the same time leading to a race. Synchronize the
two paths.
Change-Id: Ibd0f7248956d60d5831068ffcf88895adb1cd30d
Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
Add an error-fatal notifier hook to the list of other client hooks,
which would notify the clients about modem's unexpected reset or
error-fatal.
Change-Id: I185c4b05795b7ffb0768c240f25cc487f3d67b63
Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
Minimum toggle delay needed to ensure reset occurs correctly is
120ms. Change the minimum bound of usleep_range to 120ms.
Change-Id: I3a2a4301787ff5032698adc979cbf57153ecacfc
Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
Currently the external modem's boot fail configurations,
boot_fail_action and n_pon_tries, are set via module parameters.
Convert it to an IOCTL so that a registered user-space
application has control over the configurations.
Change-Id: Iaf412b873fa452b99811a50e7ae886cc49cfcf81
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Under some corner cases, the external modem could not be
configured to listen to warm-reset. For such a scenario,
even if esoc driver issued a warm reset, the modem would not
react to it, leading to a boot failure. Therefore, introduce a
new boot fail action to perform a stage-3 reset such that
the modem could start afresh.
Change-Id: I1cfc93da9cfe90cc6e3244330184d78a02f54c50
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Currently, the esoc driver calls the client's power-on and power-off
hooks with a boolean flag indicating if the external modem is in
error-fatal or not. However, this information itself isn't sufficient
for the clients. The clients also may rely on the actions such as, if
the driver would be shutting down the modem in the sequence or not.
Hence, convert the boolean flag to an integer based flag that carries
the bitmask of all such information.
Convert the esoc callbacks for the MHI driver as it's affected by this
API change.
Change-Id: I376e85ba499574a4c9e8cf3e845ab6311afe52d2
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Usually, the power_off hooks of the esoc clients are called
before the modem is powered down. Power down of the modem
is also triggered from the reboot notifier path. Hence, call
the power-off hooks from that path too.
Change-Id: Ie5a68fe15a86ec10dcd1f5499dd2d0415038ad7b
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Add basic operations to support sdxprairie in esoc driver that includes
compatibility, initializations and power control operations (reset,
shutdown, and so on). Most of the configurations are leveraged from
the existing sdx50 configurations.
Change-Id: Ide75e2f2efeac0767c1ecd760bda7e455ab527dc
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
A previous change (<8a1a862455ee0f> esoc: Check for modem status LOW
prior to error handling) introduced a bug wherein the driver polls
the gpio line for 3 seconds in an interrupt context, leading
to a watchdog bark. Hence, move the polling logic to a scheduled
work item in the same path.
Change-Id: I8ff17d354175920610f9ce69ed47e362f2de055d
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Update default action upon boot failure to trigger panic.
Change-Id: If976e35de282d2d9ab1fccf472732f21be20d67a
Signed-off-by: Adam Bickett <abickett@codeaurora.org>
With the check for the modem status to come LOW, the APQ
could be sure that the modem has not landed into any other
problems on its way to the debug path. Currently, we wait
for the modem status to come LOW only for the situation
where the APQ panics. However, this check is also needed
when the modem panics. The necessary action to handle the
crash is now placed after the check is done.
Change-Id: I16cf1e3a4fdacd1fc98c6f2ec6173de7ea22933a
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Add IPC logging support for detailed tracking of events that the
esoc driver would be handling.
Change-Id: Iadb63dc946efc355de2e68d6c4890aade1a04b0c
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
In order to control some parameters while debugging, such
as, change the number of PON attempts, change the action to
be taken in case the external modem doesn't boot, and so on,
add module parameters.
Change-Id: I508d795a8684533302d8c9668693b630029cecb4
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Increase the post power-on delay from 50 ms to 150 ms. This is
to give sufficient time for the external modem to complete the
PCIe link training.
Change-Id: I712177d1fc5d160848ccc838cadbb0f85b2fe1a7
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Power down external modem during primary reboot. This ensures the
external modem is in a consistent state on the subsequent powerup
after the reboot.
Change-Id: I52da95e450a58f4180153d5e069bd2dae8d6132e
CRs-Fixed: 2244359
Signed-off-by: Adam Bickett <abickett@codeaurora.org>
Due to recent hardware limitations, the requirement is to do
the warm reset of the modem twice. Once for collecting the
dumps and the other for transferring the firmware images.
If during the process, the driver receives a failed notification,
then power-off the modem. Hence, add code to support these
functionalities.
Change-Id: I4923b6e89474a44bdde477ccbd0c4e73b9648aae
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Update toggle time for sdx50m warm reset, shutdown, and cold reset
to follow the updated configuration.
Change-Id: I7b256fd7596f40403c745e92e6e60c9712a1f313
Signed-off-by: Adam Bickett <abickett@codeaurora.org>
The correct order for graceful shutdown should be: send sysmon-shutdown,
call the poweroff clinet hooks and finally pull the reset line to low
to trigger a poweroff of the modem.
Change-Id: Ife1aa1db3bcb5aaf2dd643885502ab0bdf005149
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
When the esoc driver sends the sysmon-shutdown command to the
modem, it starts it's shutdown process. Then the APQ waits for
the modem status to come low. When it comes low, the modem sees
that the reset line is still held high by the APQ and starts a
powerup sequence again, which is incorrect.
By ignoring the path where the modem's status line is checked,
this situation is avoided. As soon as the esoc driver receives
the sysmon response from the modem, it would now pull the reset line
low, thus turning-off the modem completely.
Change-Id: I98454a49e858eccfbc9a39bfd642f2de691e7834
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
There is no way for the mdm-helper to know that the
modem has crashed to take necessary action.
Hence, added the support that sends a notification to the
user-space, through IOCTL, as and when the modem sends an
error fatal interrupt to the driver.
Change-Id: I0a596763b310641d4c9e93d03690ba96162515ff
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Some subsystems/drivers require notifications from the esoc
driver as soon as the it powers on/off the modem.
For this, the clients cannot directly depend on the
SSR notifications.
Hence, adding support such that the clients who are
interested in listening to such events can register
themselves. Moreover, the order in which these notifications
are sent to the clients can be prioritized statically.
Also, a flexibilty is added such that the user-space
can get information, such as link-id, from the interested
client.
Change-Id: I8274f0fd5210b7d0186dddf63afd69fc98d2e110
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
In the event of a modem error-fatal, and if the related SSR is set,
the esoc driver takes the path of doing a warm reboot of the
device. However, modern design requires that the communication
link to the modem is not lost and the fact that the reboot is
done by SDI.
As a result, a flexibility is added such that the modem doesn't
have to go through the warm reboot sequence, thus preserving
the link.
Change-Id: Id78b877b33cdd501972c9b3274284a6b4c73f291
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Add basic operations to support sdx50 in esoc driver that includes
compatibility, initializations and power control operations (reset,
shutdown, and so on).
Change-Id: Ia53a128b0259d0fc7680bc9452ceaead7b286ca8
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
This is a snapshot of the esoc driver as of msm-4.4 commit <9d5748a>
(Merge "ARM: dts: msm: disable wdog wakeup on msm8996 vplatform").
The change also removes the support for older modems which are no
longer used.
Change-Id: I879768a3c56c986e66371700c062f3fa41448af7
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
