From: Alex Elder <hidden> Date: 2021-07-27 21:21:20
This series continues preparation for implementing runtime power
management for IPA. We need to ensure that the IPA core clock and
interconnects are operational whenever IPA hardware is accessed.
And in particular this means that any external entry point that can
lead to accessing IPA hardware must guarantee the hardware is "up"
when it is accessed.
The first four patches in this series take IPA clock references when
needed by such external entry points, dropping those references in
those same functions when they are no longer required.
The last patch is a bit different, though it too prepares for
enabling runtime power management. It avoids suspending/resuming
endpoints if setup is not complete.
-Alex
Alex Elder (5):
net: ipa: get clock in ipa_probe()
net: ipa: get another clock for ipa_setup()
net: ipa: add clock reference for remoteproc SSR
net: ipa: add a clock reference for netdev operations
net: ipa: don't suspend endpoints if setup not complete
drivers/net/ipa/ipa_main.c | 37 ++++++++++++++++++++++++++-----------
drivers/net/ipa/ipa_modem.c | 14 +++++++++++++-
drivers/net/ipa/ipa_smp2p.c | 5 +++++
3 files changed, 44 insertions(+), 12 deletions(-)
--
2.27.0
From: Alex Elder <hidden> Date: 2021-07-27 21:21:25
Any entry point that leads to IPA hardware access must ensure the
hardware is operational (clocked). Currently we ensure this by
taking an extra clock reference during setup that is not released
until we receive a system suspend request. But this extra reference
will soon go away.
When the platform driver ->probe function is called, we first need
hardware access in ipa_config(). Although ipa_config() takes an IPA
clock reference, it the special reference taken to prevent suspending
the hardware.
Have ipa_probe() take a reference before calling ipa_config(), so
that the "no-suspend" reference can eventually go away. Drop this
reference before ipa_probe() returns.
Similarly, the driver ->remove function can be called at any time.
Take an IPA clock reference at the beginning of that function, and
drop it again after the deconfig stage has completed (at which point
hardware access is no longer needed).
Signed-off-by: Alex Elder <redacted>
---
drivers/net/ipa/ipa_main.c | 18 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)
@@ -770,9 +770,12 @@ static int ipa_probe(struct platform_device *pdev)if(ret)gotoerr_table_exit;+/* The clock needs to be active for config and setup */+ipa_clock_get(ipa);+ret=ipa_config(ipa,data);if(ret)-gotoerr_modem_exit;+gotoerr_clock_put;/* Error */dev_info(dev,"IPA driver initialized");
@@ -781,7 +784,7 @@ static int ipa_probe(struct platform_device *pdev)*we'redonehere.*/if(modem_init)-return0;+gotoout_clock_put;/* Done; no error *//* Otherwise we need to load the firmware and have Trust Zone validate*andinstallit.Ifthatsucceedswecanproceedwithsetup.
@@ -794,11 +797,15 @@ static int ipa_probe(struct platform_device *pdev)if(ret)gotoerr_deconfig;+out_clock_put:+ipa_clock_put(ipa);+return0;err_deconfig:ipa_deconfig(ipa);-err_modem_exit:+err_clock_put:+ipa_clock_put(ipa);ipa_modem_exit(ipa);err_table_exit:ipa_table_exit(ipa);
@@ -824,6 +831,8 @@ static int ipa_remove(struct platform_device *pdev)structipa_clock*clock=ipa->clock;intret;+ipa_clock_get(ipa);+if(ipa->setup_complete){ret=ipa_modem_stop(ipa);/* If starting or stopping is in progress, try once more */
@@ -838,6 +847,9 @@ static int ipa_remove(struct platform_device *pdev)}ipa_deconfig(ipa);++ipa_clock_put(ipa);+ipa_modem_exit(ipa);ipa_table_exit(ipa);ipa_endpoint_exit(ipa);
From: Alex Elder <hidden> Date: 2021-07-27 21:21:28
The IPA network device can be opened at any time, and an opened
network device can be stopped any time. Both of these callback
functions require access to the hardware, and therefore they need
the IPA clock to be operational. Take an IPA clock reference in
both the ->open and ->stop callback functions, dropping the
reference when they are done accessing hardware.
The ->start_xmit callback requires a little different handling,
and that will be added separately.
Signed-off-by: Alex Elder <redacted>
---
drivers/net/ipa/ipa_modem.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
From: Alex Elder <hidden> Date: 2021-07-27 21:21:35
Two places call ipa_setup(). The first, ipa_probe(), holds an IPA
clock reference when calling ipa_setup() (if the AP is responsible
for IPA firmware loading). But if the modem is loading IPA
firmware, ipa_smp2p_modem_setup_ready_isr() calls ipa_setup() after
the modem has signaled the hardware is ready. This can happen at
any time, and there is no guarantee the hardware is active.
Have ipa_smp2p_modem_setup() take an IPA clock reference before it
calls ipa_setup(), and release it once setup is complete.
Signed-off-by: Alex Elder <redacted>
---
drivers/net/ipa/ipa_smp2p.c | 5 +++++
1 file changed, 5 insertions(+)
@@ -156,11 +156,16 @@ static irqreturn_t ipa_smp2p_modem_setup_ready_isr(int irq, void *dev_id)if(!smp2p->disabled){intret;+/* The clock needs to be active for setup */+ipa_clock_get(smp2p->ipa);+ret=ipa_setup(smp2p->ipa);if(ret)dev_err(&smp2p->ipa->pdev->dev,"error %d from ipa_setup()\n",ret);smp2p->disabled=true;++ipa_clock_put(smp2p->ipa);}mutex_unlock(&smp2p->mutex);
From: Alex Elder <hidden> Date: 2021-07-27 21:21:38
Until we complete the setup stage of initialization, GSI is not
initialized and therefore endpoints aren't usable. So avoid
suspending endpoints during system suspend unless setup is complete.
Clear the setup_complete flag at the top of ipa_teardown() to
reflect the fact that things are no longer in setup state.
Get rid of a misplaced (and superfluous) comment.
Signed-off-by: Alex Elder <redacted>
---
drivers/net/ipa/ipa_main.c | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
@@ -194,6 +194,9 @@ static void ipa_teardown(struct ipa *ipa)structipa_endpoint*exception_endpoint;structipa_endpoint*command_endpoint;+/* We're going to tear everything down, as if setup never completed */+ipa->setup_complete=false;+ipa_qmi_teardown(ipa);ipa_endpoint_default_route_clear(ipa);exception_endpoint=ipa->name_map[IPA_ENDPOINT_AP_LAN_RX];
@@ -885,13 +888,11 @@ static int ipa_suspend(struct device *dev){structipa*ipa=dev_get_drvdata(dev);-/* When a suspended RX endpoint has a packet ready to receive, we-*getanIPASUSPENDinterrupt.Wetriggerasystemresumein-*thatcase,butonlyonthefirstsuchinterruptsincesuspend.-*/-__clear_bit(IPA_FLAG_RESUMED,ipa->flags);--ipa_endpoint_suspend(ipa);+/* Endpoints aren't usable until setup is complete */+if(ipa->setup_complete){+__clear_bit(IPA_FLAG_RESUMED,ipa->flags);+ipa_endpoint_suspend(ipa);+}ipa_clock_put(ipa);
@@ -917,7 +918,9 @@ static int ipa_resume(struct device *dev)*/ipa_clock_get(ipa);-ipa_endpoint_resume(ipa);+/* Endpoints aren't usable until setup is complete */+if(ipa->setup_complete)+ipa_endpoint_resume(ipa);return0;}
From: Alex Elder <hidden> Date: 2021-07-27 21:21:41
The remoteproc SSR callback function for the modem requires hardware
access when handling a modem crash or shutdown. Take and later
release an IPA clock reference in ipa_modem_crashed(), to ensure the
hardware is operational.
Signed-off-by: Alex Elder <redacted>
---
drivers/net/ipa/ipa_modem.c | 5 +++++
1 file changed, 5 insertions(+)
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 27 Jul 2021 16:19:28 -0500 you wrote:
This series continues preparation for implementing runtime power
management for IPA. We need to ensure that the IPA core clock and
interconnects are operational whenever IPA hardware is accessed.
And in particular this means that any external entry point that can
lead to accessing IPA hardware must guarantee the hardware is "up"
when it is accessed.
[...]