On Mon, Jun 24, 2019 at 6:21 PM Alex Elder <elder@xxxxxxxxxx> wrote:
> On 6/18/19 2:03 PM, Johannes Berg wrote:
>
> > Really there are two possible ways (and they intersect to some extent).
> >
> > One is the whole multi-function device, where a single WWAN device is
> > composed of channels offered by actually different drivers, e.g. for a
> > typical USB device you might have something like cdc_ether and the
> > usb_wwan TTY driver. In this way, we need to "compose" the WWAN device
> > similarly, e.g. by using the underlying USB device "struct device"
> > pointer to tie it together.
>
> I *think* this model makes the most sense. But at this point
> it would take very little to convince me otherwise... (And then
> I saw Arnd's message advocating the other one, unfortunately...)
>
> > The other is something like IPA or the Intel modem driver, where the
> > device is actually a single (e.g. PCIe) device and just has a single
> > driver, but that single driver offers different channels.
>
> What I don't like about this is that it's more monolithic. It
> seems better to have the low-level IPA or Intel modem driver (or
> any other driver that can support communication between the AP
> and WWAN device) present communication paths that other function-
> specific drivers can attach to and use.
I did not understand Johannes description as two competing models
for the same code, but rather two kinds of existing hardware that
a new driver system would have to deal with.
I was trying to simplify it to just having the second model, by adding
a hack to support the first, but my view was rather unpopular so
far, so if everyone agrees on one way to do it, don't worry about me ;-)
> > Now, it's not clear to me where IPA actually falls, because so far we've
> > been talking about the IPA driver only as providing *netdevs*, not any
> > control channels, so I'm not actually sure where the control channel is.
>
> There is user space code that handles all of this, and as far as I
> can tell, parts of it will always remain proprietary.
Two replies on this:
- to answer Johannes question, my understanding is that the interface
between kernel and firmware/hardware for IPA has a single 'struct
device' that is used for both the data and the control channels,
rather than having a data channel and an independent control device,
so this falls into the same category as the Intel one (please correct
me on that)
- The user space being proprietary is exactly what we need to avoid
with the wwan subsystem. We need to be able to use the same
method for setting up Intel, Qualcomm, Samsung, Unisoc or
Hisilicon modems or anything else that hooks into the subsystem,
and support that in network manager as well as the Android
equivalent.
If Qualcomm wants to provide their own proprietary user space
solution, we can't stop them, but then that should also work on
all the others unless they intentionally break it. ;-)
> > and simply require that the channel is attached to the wwan device with
> > the representation-specific call (wwan_attach_netdev, wwan_attach_tty,
> > ...).
>
> Or maybe have the WWAN device present interfaces with attributes,
> and have drivers that are appropriate for each interface attach
> to only the ones they recognize they support.
I think you both mean the same thing here, a structure with callback
pointers that may or may not be filled by the driver depending on its
capabilities.
What we should try to avoid though is a way to add driver private
interfaces that risk having multiple drivers create similar functionality
in incompatible ways.
Arnd
