On Mon, 2019-06-24 at 18:40 +0200, Arnd Bergmann wrote: > 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. Right. > 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 ;-) :-) However, to also reply to Alex: I don't know exactly how IPA works, but for the Intel modem at least you can't fundamentally have two drivers for different parts of the functionality, since it's just a single piece of hardware and you need to allocate hardware resources from a common pool etc. So you cannot split the driver into "Intel modem control channel driver" and "Intel modem data channel driver". In fact, it's just a single "struct device" on the PCIe bus that you can bind to, and only one driver can bind at a time. So, IOW, I'm not sure I see how you'd split that up. I guess you could if you actually do something like the "rmnet" model, and I suppose you're free to do that for IPA if you like, but I tend to think that's actually a burden, not a win since you just get more complex code that needs to interact with more pieces. A single driver for a single hardware that knows about the few types of channels seems simpler to me. > - 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) That sounds about the same then, right. Are the control channels to IPA are actually also tunnelled over the rmnet protocol? And even if they are, perhaps they have a different hardware queue or so? That'd be the case for Intel - different hardware queue, same (or at least similar) protocol spoken for the DMA hardware itself, but different contents of the messages obviously. > - 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. ;-) :-) I tend to think there's always going to be some level of specific handling here, because e.g. the Intel modem can expose MBIM or AT command control channels, but not much else (that'd be useful for us anyway, since we don't know how to speak debug protocol etc.). Other modems will expose *only* AT commands, or *only* MBIM, and yet others may also offer QMI and then that might be preferable. > > > 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. Right. johannes
