From: Vamsi Samavedam <vskrishn@codeaurora.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [net-next] qmi_wwan: set FLAG_SEND_ZLP to avoid network initiated disconnect
Date: Thu, 14 Dec 2017 13:39:59 -0800 [thread overview]
Message-ID: <20171214213959.GC21058@vskrishn2-linux.qualcomm.com> (raw)
On Thu, Dec 14, 2017 at 07:55:50PM +0100, Bjørn Mork wrote:
> It has been reported that the dummy byte we add to avoid
> ZLPs can be forwarded by the modem to the PGW/GGSN, and that
> some operators will drop the connection if this happens.
>
> In theory, QMI devices are based on CDC ECM and should as such
> both support ZLPs and silently ignore the dummy byte. The latter
> assumption failed. Let's test out the first.
>
> Signed-off-by: Bjørn Mork <bjorn@mork.no>
> ---
> I am a bit worried about the effect of this change on all the
> devices I can't test myself. But trying it is the only way we
> can ever find out....
flag zlp is tested with pids: 9034,9048,904c,9075, 908E,9079,
908A,909F and 90A4. In general, qualcomm usb firmware can
handle zlps.
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Vamsi Samavedam <vskrishn@codeaurora.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH net-next] qmi_wwan: set FLAG_SEND_ZLP to avoid network initiated disconnect
Date: Thu, 14 Dec 2017 13:39:59 -0800 [thread overview]
Message-ID: <20171214213959.GC21058@vskrishn2-linux.qualcomm.com> (raw)
In-Reply-To: <20171214185550.15779-1-bjorn@mork.no>
On Thu, Dec 14, 2017 at 07:55:50PM +0100, Bjørn Mork wrote:
> It has been reported that the dummy byte we add to avoid
> ZLPs can be forwarded by the modem to the PGW/GGSN, and that
> some operators will drop the connection if this happens.
>
> In theory, QMI devices are based on CDC ECM and should as such
> both support ZLPs and silently ignore the dummy byte. The latter
> assumption failed. Let's test out the first.
>
> Signed-off-by: Bjørn Mork <bjorn@mork.no>
> ---
> I am a bit worried about the effect of this change on all the
> devices I can't test myself. But trying it is the only way we
> can ever find out....
flag zlp is tested with pids: 9034,9048,904c,9075, 908E,9079,
908A,909F and 90A4. In general, qualcomm usb firmware can
handle zlps.
next reply other threads:[~2017-12-14 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 21:39 Vamsi Samavedam [this message]
2017-12-14 21:39 ` [PATCH net-next] qmi_wwan: set FLAG_SEND_ZLP to avoid network initiated disconnect Vamsi Samavedam
-- strict thread matches above, loose matches on Subject: below --
2017-12-15 18:50 [net-next] " David Miller
2017-12-15 18:50 ` [PATCH net-next] " David Miller
2017-12-14 21:42 [net-next] " Bjørn Mork
2017-12-14 21:42 ` [PATCH net-next] " Bjørn Mork
2017-12-14 18:55 [net-next] " Bjørn Mork
2017-12-14 18:55 ` [PATCH net-next] " Bjørn Mork
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=20171214213959.GC21058@vskrishn2-linux.qualcomm.com \
--to=vskrishn@codeaurora.org \
--cc=bjorn@mork.no \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.