From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Alex Elder <elder@linaro.org>,
m.chetan.kumar@intel.com, Dan Williams <dcbw@redhat.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [RFC] wwan: add a new WWAN subsystem
Date: Tue, 25 Feb 2020 16:39:00 +0100 [thread overview]
Message-ID: <983917b5637ce1d9948c94f638d857d37a2ab808.camel@sipsolutions.net> (raw)
In-Reply-To: <20200225151521.GA7663@lunn.ch>
On Tue, 2020-02-25 at 16:15 +0100, Andrew Lunn wrote:
> Looking at it bottom up, is the WWAN device itself made up of multiple
> devices? Are the TTYs separate drivers to the packet moving engines?
Possibly, yes, it depends a bit.
> They have there own USB end points, and could just be standard CDC
> ACM?
Yeah, for a lot of USB devices that's indeed the case.
> driver/base/component.c could be useful for bringing together these
> individual devices to form the whole WWAN device.
Huh, I was unaware of this, I'll take a look!
A very brief look suggests that it wants to have a driver for the whole
thing in the end, which isn't really true here, but perhaps we could
"make one up" and have that implement the userspace API. I need to take
a closer look, thanks for the pointer.
> Plus you need to avoid confusion by not adding another "component
> framework" which means something totally different to the existing
> component framework.
:)
johannes
next prev parent reply other threads:[~2020-02-25 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 10:00 [RFC] wwan subsystem Johannes Berg
2020-02-25 10:00 ` [RFC] wwan: add a new WWAN subsystem Johannes Berg
2020-02-25 15:15 ` Andrew Lunn
2020-02-25 15:39 ` Johannes Berg [this message]
2020-02-26 22:15 ` Dan Williams
2020-03-02 13:06 ` Johannes Berg
2020-02-25 19:00 ` David Miller
2020-02-25 19:40 ` Johannes Berg
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=983917b5637ce1d9948c94f638d857d37a2ab808.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrew@lunn.ch \
--cc=bjorn.andersson@linaro.org \
--cc=dcbw@redhat.com \
--cc=elder@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.chetan.kumar@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).