From: Jakub Kicinski <kuba@kernel.org>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: loic.poulain@linaro.org, ryazanov.s.a@gmail.com,
johannes@sipsolutions.net, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jinjian.song@fibocom.com
Subject: Re: [PATCH] net: wwan: t7xx: Add AP CLDMA
Date: Mon, 26 Jun 2023 13:13:44 -0700 [thread overview]
Message-ID: <20230626131344.2364f834@kernel.org> (raw)
In-Reply-To: <20230626082040.15671-1-jtornosm@redhat.com>
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@mediatek.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
next prev parent reply other threads:[~2023-06-26 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 8:20 [PATCH] net: wwan: t7xx: Add AP CLDMA Jose Ignacio Tornos Martinez
2023-06-26 20:13 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-11 6:28 Jose Ignacio Tornos Martinez
2023-07-12 19:51 ` Simon Horman
2023-07-12 19:51 ` Simon Horman
2023-07-13 0:40 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230626131344.2364f834@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jinjian.song@fibocom.com \
--cc=johannes@sipsolutions.net \
--cc=jtornosm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryazanov.s.a@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.