All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Peter Hunt <peter.hunt@opengear.com>
Cc: loic.poulain@oss.qualcomm.com, ryazanov.s.a@gmail.com,
	dnlplm@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 v10 0/2] net: wwan: support DTR/RTS on AT ports via MHI IP_CTRL
Date: Tue, 20 Oct 2026 19:00:19 +0000	[thread overview]
Message-ID: <179252281927.159319.5542146548061223834.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013183500.261229-1-peter.hunt@opengear.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 13 Oct 2026 12:34:58 -0600 you wrote:
> Qualcomm/Sierra SDX55/SDX65 modems (e.g. EM9291) withhold unsolicited AT
> result codes until the host asserts DTR. The in-tree mhi_wwan_ctrl driver
> exposes AT ports but never signals DTR, so URCs never reach userspace.
> 
> Patch 1 extends the wwan core with an optional ->dtr_rts(port, mdmbits)
> port op. The TIOCM bitmask state is tracked in the wwan core, which raises
> DTR/RTS on first open of an AT port whose driver implements ->dtr_rts,
> drops them on last close (if HUPCL is set, which is the default for AT
> ports) and on port removal, and passes the resolved bitmask to the
> driver on TIOCMSET/TIOCMBIC/TIOCMBIS.
> 
> [...]

Here is the summary with links:
  - [net-next,v10,1/2] net: wwan: core: propagate modem control signals to port drivers
    https://git.kernel.org/netdev/net-next/c/241c9ed785d0
  - [net-next,v10,2/2] net: wwan: mhi_wwan_ctrl: drive DTR/RTS via the IP_CTRL channel
    https://git.kernel.org/netdev/net-next/c/d509edf90bc6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-20 19:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 18:34 [PATCH net-next v10 0/2] net: wwan: support DTR/RTS on AT ports via MHI IP_CTRL Peter Hunt
2026-10-13 18:34 ` [PATCH net-next v10 1/2] net: wwan: core: propagate modem control signals to port drivers Peter Hunt
2026-10-16  9:37   ` netdev-bot+sashiko
2026-10-16 20:56     ` Peter Hunt
2026-10-16 19:46   ` Loic Poulain
2026-10-13 18:35 ` [PATCH net-next v10 2/2] net: wwan: mhi_wwan_ctrl: drive DTR/RTS via the IP_CTRL channel Peter Hunt
2026-10-16  9:37   ` netdev-bot+sashiko
2026-10-16 20:58     ` Peter Hunt
2026-10-20 18:44       ` Jakub Kicinski
2026-10-16 19:47   ` Loic Poulain
2026-10-20 19:00 ` patchwork-bot+netdevbpf [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=179252281927.159319.5542146548061223834.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dnlplm@gmail.com \
    --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=peter.hunt@opengear.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.