Hi, On Wed, 5 Jan 2022 at 03:48, Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote: > > Hi Alexander, > > alex.aring@xxxxxxxxx wrote on Thu, 30 Dec 2021 14:48:41 -0500: > > > Hi, > > > > On Thu, 30 Dec 2021 at 12:00, David Girault <David.Girault@xxxxxxxxx> wrote: > > > > > > Hi Alexander, > > > > > > At Qorvo, we have developped a SoftMAC driver for our DW3000 chip that will benefit such API. > > > > > Do you want to bring this driver upstream as well? Currently those > > callbacks will be introduced but no user is there. > > I think so far the upstream fate of the DW3000 driver has not been ruled > out so let's assume it won't be upstreamed (at least not fully), that's > also why we decided to begin with the hwsim driver. > ok. > However, when designing this series, it appeared quite clear that any > hardMAC driver would need this type of interface. The content of the > interface, I agree, could be further discussed and even edited, but the > main idea of giving the information to the phy driver about what is > happening regarding eg. scan operations or beacon frames, might make > sense regardless of the current users, no? > A HardMAC driver does not use this driver interface... but there exists a SoftMAC driver for a HardMAC transceiver. This driver currently works because we use dataframes only... It will not support scanning currently and somehow we should make iit not available for drivers like that and for drivers which don't set symbol duration. They need to be fixed. > This being said, if other people decide to upstream a hardMAC driver > and need these hooks to behave a little bit differently, it's their > right to tweak them and that would also be part of the game. > > Although we might not need these hooks in a near future at all if we > move to the filtering modes, because the promiscuous call with the > specific level might indicate to the device how it should configure > itself already. > My concern is that somebody else might want to remove those callbacks because they are not used. - Alex
