From: Peter Hunt <peter.hunt@opengear.com>
To: peter.hunt@opengear.com, Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: ryazanov.s.a@gmail.com, johannes@sipsolutions.net,
mani@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v8 2/2] net: wwan: mhi_wwan_ctrl: drive DTR/RTS via the IP_CTRL channel
Date: Thu, 8 Oct 2026 18:17:41 -0600 [thread overview]
Message-ID: <20261009001741.1081798-1-peter.hunt@opengear.com> (raw)
In-Reply-To: <CAFEp6-1gb5KgK5rtz4U80AGvs_g2ZPELUge9Q=bhy4+=coJ-GQ@mail.gmail.com>
Hi Loic,
On Thu, Oct 8, 2026 at 5:30 PM Loic Poulain wrote:
> This function ensures that the work is either cancelled or has
> completed, but it does not prevent it from being requeued
> concurrently. That can happen when rx_refill is rescheduled from
> mhi_wwan_dtr_queue_rx(). Using disable_delayed_work_sync() here would
> be preferable.
Agreed, thanks. The automated review of v7 also pointed out that a
retry already inside mhi_queue_buf() could race with
mhi_unprepare_from_transfer(). In v9 the DL sink buffer is only ever
requeued from the refill work (the DL callback just schedules it), and
remove() calls disable_delayed_work_sync() before
mhi_unprepare_from_transfer(), the same order mhi_wwan_ctrl_stop()
already uses for the data ports.
Thanks,
Peter
prev parent reply other threads:[~2026-10-09 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 18:22 [PATCH net-next v8 0/2] net: wwan: support DTR/RTS on AT ports via MHI IP_CTRL Peter Hunt
2026-10-07 18:22 ` [PATCH net-next v8 1/2] net: wwan: core: propagate modem control signals to port drivers Peter Hunt
2026-10-08 15:19 ` Loic Poulain
2026-10-09 0:17 ` Peter Hunt
2026-10-07 18:22 ` [PATCH net-next v8 2/2] net: wwan: mhi_wwan_ctrl: drive DTR/RTS via the IP_CTRL channel Peter Hunt
2026-10-08 15:30 ` Loic Poulain
2026-10-09 0:17 ` Peter Hunt [this message]
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=20261009001741.1081798-1-peter.hunt@opengear.com \
--to=peter.hunt@opengear.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox