Hi Arend, On Sun, 2022-01-09 at 13:00 +0100, Arend van Spriel wrote: > On January 8, 2022 12:31:19 AM James Prestwood <prestwoj@xxxxxxxxx> > wrote: > > > On Thu, 2022-01-06 at 23:01 +0100, Johannes Berg wrote: > > > Hi Preston, > > > > > > Ugh, sorry. I'm way behind on a whole bunch of emails (about 4 > > > dozen > > > to > > > be honest) ... trying to catch up, but only so many hours a day. > > > > No worries, thanks for getting to it :) > > > > > > > [...] > > > > > > > > > At which point it's probably not really worth it? Emulating it in > > > the > > > driver by repeatedly issuing time events also seems like a bad > > > idea, > > > worse even than doing it in the application, since the > > > application > > > could > > > at least try to synchronise it a bit with whatever it needs to be > > > doing, > > > whereas the driver can't do that at all. > > > > If this is the case then sure, its just offloading the same nasty > > procedure into the driver/FW. You know more than me about this > > topic > > but I'm still trying to understand how this would differ much from > > AP > > mode? > > > > In my own mind I see SET_CHANNEL doing the same thing as START_AP, > > just > > without sending out beacons/probes and the iftype being station. > > Maybe > > this is an oversimplifation but it seems like the FW/driver *can* > > sit > > on channel without some time constraint if it supports AP mode. > > Even if it only supports STA mode it can. The constraint being that > it is > not associated (or busy trying to associate) to an AP. When it is > associated it has to sit on the channel of the AP, as announced in > it's > beacon and/or probe response, at regular intervals. You referred to > DPP to > provision the STA so I assume it is not associated, right? Could you > write > out the whole scenario as you think it should/could be done? Correct, I'm only talking about doing this while not associated. As for my intentended scenario I simply want to call CMD_SET_CHANNEL then run the entire DPP auth/config protocol while on this channel. Then, once finished, call (a new API) CMD_SET_CHANNEL_CANCEL. Currently I'm stuck doing CMD_REMAIN_ON_CHANNEL over and over. Which leaves moments of time where the device is idle, potentially missing DPP frames. This is especially bad for drivers which choose short ROC timeouts. Also, since the ROC duration isn't honored userspace has to manage its own separate timer and re-issue ROC if the driver decided to use a different timeout. It just ends up being a mess and extremely overcomplicated for something as simple as going offchannel. I feel there has got to be a cleaner way to handle this. P2P has a similar use case discovering peers AFAIK. Thanks, James > > Regards, > Arend > >
