From: Johannes Berg <johannes@sipsolutions.net> To: Brian Norris <briannorris@chromium.org> Cc: Kalle Valo <kvalo@codeaurora.org>, Jouni Malinen <j@w1.fi>, Pkshih <pkshih@realtek.com>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org> Subject: Re: [PATCH 1/2] nl80211: vendor-cmd: qca: add dynamic SAR power limits Date: Thu, 30 Jul 2020 15:17:57 +0200 [thread overview] Message-ID: <b17c0e5ad80050df4da85653d413a71cfcc37629.camel@sipsolutions.net> (raw) In-Reply-To: <CA+ASDXMf7iXuE9hQ-XitPPfvXP0EK5FchJLCu2+5Ag=ZC=0H0w@mail.gmail.com> (sfid-20200602_033247_740183_F75D1728) On Mon, 2020-06-01 at 18:32 -0700, Brian Norris wrote: > I haven't quite reached the 3 month lag on the prior replies here :) But I did, almost ;-) > I do want to see this question resolved somehow, or else we'll be > dragging along out-of-tree patches for...(counts on fingers)...4 > different nl80211 APIs for the same feature, and a driver-detecting > user space for it. Right. > I think I was half-hoping that we'd get to chat at > netdev about this, but that's not happening any time soon. (Topic for > another day: does a "wireless workshop" still happen at a virtual-only > conference?) Yes, but only a short 1.5hr video call I guess. I'm not even sure what to do there yet. [snip] Thanks for the overview! > Also, Kalle had some concerns about stable ABI questions: shouldn't we > bake in some kind of "check for support" feature to these kinds of > APIs [3]? That would help ease transition, if we do start with a > vendor API and move to a common one in the future. Given the nature of > this feature, I wouldn't expect there will be a large variety of users > making use of the APIs -- and I, for one, would be happy to migrate my > user space over some period of time, as needed. We do that? We list out the available vendor APIs, and in most cases (perhaps not the one you've noticed there) we also list out the availability of real nl80211 APIs in some way. johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net> To: Brian Norris <briannorris@chromium.org> Cc: Jouni Malinen <j@w1.fi>, Pkshih <pkshih@realtek.com>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>, Kalle Valo <kvalo@codeaurora.org> Subject: Re: [PATCH 1/2] nl80211: vendor-cmd: qca: add dynamic SAR power limits Date: Thu, 30 Jul 2020 15:17:57 +0200 [thread overview] Message-ID: <b17c0e5ad80050df4da85653d413a71cfcc37629.camel@sipsolutions.net> (raw) In-Reply-To: <CA+ASDXMf7iXuE9hQ-XitPPfvXP0EK5FchJLCu2+5Ag=ZC=0H0w@mail.gmail.com> (sfid-20200602_033247_740183_F75D1728) On Mon, 2020-06-01 at 18:32 -0700, Brian Norris wrote: > I haven't quite reached the 3 month lag on the prior replies here :) But I did, almost ;-) > I do want to see this question resolved somehow, or else we'll be > dragging along out-of-tree patches for...(counts on fingers)...4 > different nl80211 APIs for the same feature, and a driver-detecting > user space for it. Right. > I think I was half-hoping that we'd get to chat at > netdev about this, but that's not happening any time soon. (Topic for > another day: does a "wireless workshop" still happen at a virtual-only > conference?) Yes, but only a short 1.5hr video call I guess. I'm not even sure what to do there yet. [snip] Thanks for the overview! > Also, Kalle had some concerns about stable ABI questions: shouldn't we > bake in some kind of "check for support" feature to these kinds of > APIs [3]? That would help ease transition, if we do start with a > vendor API and move to a common one in the future. Given the nature of > this feature, I wouldn't expect there will be a large variety of users > making use of the APIs -- and I, for one, would be happy to migrate my > user space over some period of time, as needed. We do that? We list out the available vendor APIs, and in most cases (perhaps not the one you've noticed there) we also list out the availability of real nl80211 APIs in some way. johannes _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-07-30 13:18 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-18 15:48 [PATCH 0/2] ath10k: SAR power limit vendor command Kalle Valo 2019-12-18 15:48 ` Kalle Valo 2019-12-18 15:48 ` [PATCH 1/2] nl80211: vendor-cmd: qca: add dynamic SAR power limits Kalle Valo 2019-12-18 15:48 ` Kalle Valo 2019-12-19 9:44 ` Pkshih 2019-12-19 9:44 ` Pkshih 2019-12-19 15:48 ` Jouni Malinen 2019-12-19 15:48 ` Jouni Malinen 2019-12-19 18:32 ` Brian Norris 2019-12-19 18:32 ` Brian Norris 2019-12-19 18:55 ` Jouni Malinen 2019-12-19 18:55 ` Jouni Malinen 2019-12-19 23:40 ` Brian Norris 2019-12-19 23:40 ` Brian Norris 2020-03-17 16:54 ` Kalle Valo 2020-03-17 16:54 ` Kalle Valo 2020-03-20 12:55 ` Johannes Berg 2020-03-20 12:55 ` Johannes Berg 2020-06-02 1:32 ` Brian Norris 2020-06-02 1:32 ` Brian Norris 2020-07-16 9:35 ` Kalle Valo 2020-07-16 9:35 ` Kalle Valo 2020-07-16 18:56 ` Brian Norris 2020-07-16 18:56 ` Brian Norris 2020-07-24 9:26 ` Kalle Valo 2020-07-24 9:26 ` Kalle Valo 2020-07-30 13:24 ` Johannes Berg 2020-07-30 13:24 ` Johannes Berg 2020-08-01 1:31 ` Brian Norris 2020-08-01 1:31 ` Brian Norris 2020-09-08 5:55 ` Kalle Valo 2020-09-08 5:55 ` Kalle Valo 2020-07-30 13:17 ` Johannes Berg [this message] 2020-07-30 13:17 ` Johannes Berg 2019-12-18 15:48 ` [PATCH 2/2] ath10k: allow dynamic SAR power limits to be configured Kalle Valo 2019-12-18 15:48 ` Kalle Valo 2019-12-19 9:45 ` Pkshih 2019-12-19 9:45 ` Pkshih 2020-04-16 7:38 ` Kalle Valo 2020-04-16 7:38 ` Kalle Valo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=b17c0e5ad80050df4da85653d413a71cfcc37629.camel@sipsolutions.net \ --to=johannes@sipsolutions.net \ --cc=ath10k@lists.infradead.org \ --cc=briannorris@chromium.org \ --cc=j@w1.fi \ --cc=kvalo@codeaurora.org \ --cc=linux-wireless@vger.kernel.org \ --cc=pkshih@realtek.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.