From: "Bjørn Mork" <bjorn@mork.no>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Dan Williams <dcbw@redhat.com>, Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: option: set driver_info for SIM5218 and compatibles
Date: Tue, 19 Mar 2019 15:59:36 +0100 [thread overview]
Message-ID: <878sxa9ag7.fsf@miraculix.mork.no> (raw)
In-Reply-To: <yw1xr2b3ylsp.fsf@mansr.com> (=?utf-8?Q?=22M=C3=A5ns_Rullg?= =?utf-8?Q?=C3=A5rd=22's?= message of "Tue, 19 Mar 2019 14:35:18 +0000")
Måns Rullgård <mans@mansr.com> writes:
> Dan Williams <dcbw@redhat.com> writes:
>
>> TLDR; some firmware uses the DTR signal as an indicator to come out of
>> low-power mode. Without doing so you cannot talk to the modem over any
>> of it's ports, QMI, net, or serial.
>
> I must be missing something, but how does a network interface have a DTR
> signal?
It does not. But the network function is (ab)using the Comm class USB
control message "SetControlLineState" to signal "wake up" from the host
to the device. Which is perfectly fine since the USB function in
question is vendor specific. The vendor can define any USB control
message to mean anything they want. Reusing a Comm class message
probably made sense to the firmware engineer designing this. We can
only note and adapt.
It doesn't have anything to do with DTR.
Bjørn
next prev parent reply other threads:[~2019-03-19 15:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 17:07 Mans Rullgard
2019-02-27 8:33 ` Johan Hovold
2019-02-27 11:57 ` Måns Rullgård
2019-02-27 13:13 ` Johan Hovold
2019-02-27 14:32 ` Måns Rullgård
2019-03-18 14:32 ` Måns Rullgård
2019-03-19 10:28 ` Johan Hovold
2019-03-19 10:54 ` Måns Rullgård
2019-03-19 11:08 ` Johan Hovold
2019-03-19 12:25 ` Måns Rullgård
2019-03-19 12:27 ` Johan Hovold
2019-03-19 12:43 ` Johan Hovold
2019-03-19 14:30 ` Dan Williams
2019-03-19 14:35 ` Måns Rullgård
2019-03-19 14:59 ` Bjørn Mork [this message]
2019-03-19 16:26 ` Måns Rullgård
2019-03-19 17:15 ` 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=878sxa9ag7.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=dcbw@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mans@mansr.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
all inboxes | Powered by JetHome®