[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230626131344.2364f834@kernel.org>
Date: Mon, 26 Jun 2023 13:13:44 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jose Ignacio Tornos Martinez <jtornosm@...hat.com>
Cc: loic.poulain@...aro.org, ryazanov.s.a@...il.com,
johannes@...solutions.net, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, jinjian.song@...ocom.com
Subject: Re: [PATCH] net: wwan: t7xx: Add AP CLDMA
On Mon, 26 Jun 2023 10:20:37 +0200 Jose Ignacio Tornos Martinez wrote:
> At this moment with the current status, t7xx is not functional due to
> problems like this after connection, if there is no activity:
> [ 57.370534] mtk_t7xx 0000:72:00.0: [PM] SAP suspend error: -110
> [ 57.370581] mtk_t7xx 0000:72:00.0: can't suspend
> (t7xx_pci_pm_runtime_suspend [mtk_t7xx] returned -110)
> because after this, the traffic no longer works.
>
> The complete series 'net: wwan: t7xx: fw flashing & coredump support'
> was reverted because of issues with the pci implementation.
> In order to have at least the modem working, it would be enough if just
> the first commit of the series is re-applied:
> d20ef656f994 net: wwan: t7xx: Add AP CLDMA).
> With that, the Application Processor would be controlled, correctly
> suspended and the commented problems would be fixed (I am testing here
> like this with no related issue).
>
> This commit is independent of the others in the series and not related to
> the commented pci implementation for the new features: fw flashing and
> coredump collection.
>
> Original text from the commit that would be re-applied:
>
> d20ef656f994 net: wwan: t7xx: Add AP CLDMA
> Author: Haijun Liu <haijun.liu@...iatek.com>
> Date: Tue Aug 16 09:53:28 2022 +0530
>
> The t7xx device contains two Cross Layer DMA (CLDMA) interfaces to
> communicate with AP and Modem processors respectively. So far only
> MD-CLDMA was being used, this patch enables AP-CLDMA.
>
> Rename small Application Processor (sAP) to AP.
A bit of a bad timing, the merge window for 6.5 has just opened
and we're busy settling the bugs in linux-next right now. So you
will need to repost this change in 2 weeks...
## Form letter - net-next-closed
The merge window for v6.5 has begun and therefore net-next is closed
for new drivers, features, code refactoring and optimizations.
We are currently accepting bug fixes only.
Please repost when net-next reopens after July 10th.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
Powered by blists - more mailing lists