Brian Norris <briannorris@xxxxxxxxxxxx> writes: >> > > This was discussed during the 2019 wireless workshop. The conclusion >> > > from that discussion was that while there is clear need for SAR power >> > > limits for various devices and multiple vendors/drivers, it did not look >> > > clear that a single common interface could be defined cleanly taken into >> > > account the differences in the ways vendors have designed the mechanism >> > > in driver and firmware implementations. As such, vendor specific >> > > commands were identified as the approach. >> > >> > [citation needed] >> >> I'm not aware of any publicly available meeting minutes that covered the >> details for that discussion. My personal notes indicate that there were >> at least two vendors indicating existence of vendor specific commands >> for configuring SAR parameters, a discussion about the parameters used >> for this being different, and a conclusion that this would be an example >> kernel interface where a generic nl80211 interface may not be achievable >> and a vendor specific interface would be more likely. This discussion >> resulted in the discussion on how to use vendor specific nl80211 >> commands/attributes in upstream drivers and the eventual documentation >> of that in the location you noted. > > Hmm, I actually think I was only around for the pre-discussion, in > which y'all suggested you might later meet to decide what eventually > became [1]. So maybe I missed some specific examples that would > provide the [citation] I requested. > > That being said, I have personally fielded out-of-tree SAR > implementations from 4 different vendors: > > (a) Two of them (this ath10k proposal, roughly; and Realtek's) employ > exactly the same concept: N frequency ranges, each with associated > power limits. > (b) Two of them (Intel/variant-of-iwiwifi and Marvell/mwifiex) utilize > a platform-specific (BIOS or Device Tree) mechanism for enumerating > power tables, and the nl80211 API simply takes an index N (e.g., 0 or > 1), so user space can say "switch to mode N" > > Unfortunately, for (b), I think there are enough reasons to think they > won't share an API similar to (a) (for Marvell, their > platform-specific tables are large undocumented blobs -- I have a > feeling if we already had a common API for (a), they *could* have > implemented some translation in a nicer way in their driver, but they > haven't chosen to do that work and probably won't be convinced to do > so). > > But that still means there's some hope for (a). > > Anyway, I am happy that there's a documented policy for vendor APIs > [1], and I'm happy to see this proposal out here. I just want to see a > critical eye put to this particular proposal if possible, to see if we > can improve its flexibility (either now, or in a later version of a > QCA vendor command, or even in a common nl80211-proper command). > > So to put a little different spin on Pkshih's request: is there any > value in making this particular ath10k proposal a little more generic > (e.g., more granularity or flexibility in frequency bands, or more > precision in power limits), such that other vendors might implement > the same thing? Or would it be better to let each vendor implement > their similar-looking APIs (i.e., (a); or maybe even (b)) on their > own, and only later look at sharing? The downside of accepting SAR vendor commands to upstream is that (in theory) that should be supported a long time: 4. The newly proposed API shall be subject to stable API rules. https://wireless.wiki.kernel.org/en/developers/documentation/nl80211#vendor-specific_api So if sometime in the future we add a generic command the driver would need to support both vendor and generic commands. So, IF it makes sense to implement a generic command, I would rather have a generic command implemented from the beginning and drop the SAR vendor command patches altogether. For me either solutions are good enough, I'm not familiar enough with all the different SAR user space interfaces to make a good decision. -- https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
