From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: bjorn.helgaas@gmail.com
Cc: Jinjian.Song@fibocom.com, Reid.he@fibocom.com, bjorn@helgaas.com,
haijun.liu@mediatek.com, helgaas@kernel.org, kuba@kernel.org,
netdev@vger.kernel.org, rafael.wang@fibocom.com,
somashekhar.puttagangaiah@intel.com, jtornosm@redhat.com
Subject: Re: [v5,net-next]net: wwan: t7xx : V5 ptach upstream work
Date: Fri, 23 Jun 2023 17:01:42 +0200 [thread overview]
Message-ID: <20230623150142.292838-1-jtornosm@redhat.com> (raw)
In-Reply-To: <CABhMZUXyY6-cnxPcU5MFy2-RoVuCx65PUVwMKsM5gqhgtdNy2Q@mail.gmail.com>
I have a proposal because at this moment with the current status, t7xx is not
functional due to problems like this 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)
and after this the traffic is not working.
As yu know the situation was stalled and it seems that the final solution for
the complete series can take longer, so 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).
I think the first commit of the series is independent of the others and it can
be re-applied cleanly. Later on, the other commits related to fw flashing and
coredump collection new features could be added taking into account Bjorn's
comments (and of course updated doc if needed).
Thanks
Jose Ignacio
next prev parent reply other threads:[~2023-06-23 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TY2PR02MB3615EB80E1F26563CB1ED92D8C4DA@TY2PR02MB3615.apcprd02.prod.outlook.com>
2023-06-05 17:35 ` [v5,net-next]net: wwan: t7xx : V5 ptach upstream work Bjorn Helgaas
2023-06-23 15:01 ` Jose Ignacio Tornos Martinez [this message]
2023-06-23 15:28 ` Bjorn Helgaas
2023-06-26 2:05 ` 答复: " Jinjian Song(Jack)
2023-06-26 8:20 ` Jose Ignacio Tornos Martinez
2023-06-26 12:12 ` 答复: " Jinjian Song(Jack)
2023-06-26 12:41 ` Jose Ignacio Tornos Martinez
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=20230623150142.292838-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=Jinjian.Song@fibocom.com \
--cc=Reid.he@fibocom.com \
--cc=bjorn.helgaas@gmail.com \
--cc=bjorn@helgaas.com \
--cc=haijun.liu@mediatek.com \
--cc=helgaas@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafael.wang@fibocom.com \
--cc=somashekhar.puttagangaiah@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox