From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 054FDC433E0 for ; Sat, 1 Aug 2020 01:31:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D293B20838 for ; Sat, 1 Aug 2020 01:31:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="oC77DcWB" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727093AbgHABbq (ORCPT ); Fri, 31 Jul 2020 21:31:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39442 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726883AbgHABbp (ORCPT ); Fri, 31 Jul 2020 21:31:45 -0400 Received: from mail-qt1-x841.google.com (mail-qt1-x841.google.com [IPv6:2607:f8b0:4864:20::841]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3C79CC06174A for ; Fri, 31 Jul 2020 18:31:45 -0700 (PDT) Received: by mail-qt1-x841.google.com with SMTP id 6so24486965qtt.0 for ; Fri, 31 Jul 2020 18:31:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=u5hs4CNSdR7fBcs1oGUPKpLdocqk8/qQSUjfBk/TvWE=; b=oC77DcWBFdF3fXleFDJWdR5GXpak41S3u3jRxZbLbSetON6j+xbSdnyUkyMlB+kXYl 39ijl2NY/bCAfc6MSrmC2JkY3Biwl5ep9gwqKCxObpIIT6SFLSxsH/ds3rMdEVx3KqBu VbHz8f1Emz320uLthuzNcP1Wyb/v5C88ts0RE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=u5hs4CNSdR7fBcs1oGUPKpLdocqk8/qQSUjfBk/TvWE=; b=dewyXosrXr60Fwe58CwQ4nRZCN8eFRSLUU1i0WT+pyKPvCtxadlFz4m/bsaehygI1l l9hbPperdUkpQr/vOXIm3X2yqcGBHOUZ723HEsdsyWrLyJDRVHbHs9ha+xG+gkZ4S6nH 03s11AQUvvAnoLensZ6X25RPuB6GWINjnySAnGerqaBGZnCdW4MXnk5pBIUtelZfbwZL FR169i6Q8aUcI/Wo+rtmPsXAU3faq56DCVuB7Xu17RklJaCcG/UkGJ5xBC/RH8RcpAxU 22aEIGIDJLBqBfeHxPORAkrNIqCRgrC3KI305X4UYAyrdP/nYCXGvLY2sVxkMORyhrxR 649w== X-Gm-Message-State: AOAM530rx//ezgeexPtDueXhWwDG9gbhhWAOZgwy2I/vFdRfOCPbHd7w LB3uULq1BluI6LS1321QrTd8egaa+Ak= X-Google-Smtp-Source: ABdhPJxZfi0PwwPWoasgFn8k3Ksi+KoARfMJICakhUWcXwAwEow6jz1a2Z5eGS1Rq7q1U/IqXOUVRw== X-Received: by 2002:ac8:e89:: with SMTP id v9mr6579251qti.100.1596245503242; Fri, 31 Jul 2020 18:31:43 -0700 (PDT) Received: from mail-qv1-f51.google.com (mail-qv1-f51.google.com. [209.85.219.51]) by smtp.gmail.com with ESMTPSA id q126sm9442856qke.34.2020.07.31.18.31.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 31 Jul 2020 18:31:41 -0700 (PDT) Received: by mail-qv1-f51.google.com with SMTP id l13so8651784qvt.10 for ; Fri, 31 Jul 2020 18:31:40 -0700 (PDT) X-Received: by 2002:a05:6214:1143:: with SMTP id b3mr6968406qvt.84.1596245499947; Fri, 31 Jul 2020 18:31:39 -0700 (PDT) MIME-Version: 1.0 References: <1576684108-30177-1-git-send-email-kvalo@codeaurora.org> <1576684108-30177-2-git-send-email-kvalo@codeaurora.org> <1576748692.7758.17.camel@realtek.com> <20191219154828.GA12287@w1.fi> <20191219185522.GA16010@w1.fi> <871rpqly6a.fsf@kamboji.qca.qualcomm.com> <87lfjjx0o7.fsf@codeaurora.org> <87y2n9clhj.fsf@codeaurora.org> In-Reply-To: From: Brian Norris Date: Fri, 31 Jul 2020 18:31:27 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 1/2] nl80211: vendor-cmd: qca: add dynamic SAR power limits To: Johannes Berg Cc: Kalle Valo , Jouni Malinen , "linux-wireless@vger.kernel.org" , Pkshih , "ath10k@lists.infradead.org" , Wen Gong Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Thu, Jul 30, 2020 at 6:24 AM Johannes Berg wrote: > > Good, I was just checking that we all are on the same page. > > But are we? ;-) I think you were deferring to, "how would user space use it?" And, "would a common API really help anyone?" (And then you implied "anyone" = "Chrome OS.") I expressed a moderate benefit from a common API, but I'd settle for a non-common (but upstream) one instead. I also doubt many non-hardware-customized Linux distributions will make use of this any time soon. I don't think that implied you were truly on a different page. But your response below may say otherwise: > I don't really see anything in the new proposal [1] that really explains > why the common API that we've sort of vaguely outlined in this thread > couldn't work? It just speaks of technical difficulties ("need a > reporting API too"), but should we let that stop us? > > [1] https://patchwork.kernel.org/patch/11686317/ Indeed, I don't see any reason beyond technical difficulties. I'd love to have a few extra hours in my day to spend on writing such an API, if that would really unblock months of deadlock. Unfortunately, those hours tend to get eaten by all sorts of other things these days, so an honest assessment would probably say I won't get around to it soon. SAR regulatory concerns aren't really sexy enough to convince me to spend my weekends on it... (...oh wait, it's Friday evening already. Hmm.) Regards, Brian From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-qk1-x744.google.com ([2607:f8b0:4864:20::744]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k1gNH-0007JF-Le for ath10k@lists.infradead.org; Sat, 01 Aug 2020 01:31:48 +0000 Received: by mail-qk1-x744.google.com with SMTP id l23so30648450qkk.0 for ; Fri, 31 Jul 2020 18:31:45 -0700 (PDT) Received: from mail-qv1-f50.google.com (mail-qv1-f50.google.com. [209.85.219.50]) by smtp.gmail.com with ESMTPSA id i30sm1373457qte.30.2020.07.31.18.31.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 31 Jul 2020 18:31:41 -0700 (PDT) Received: by mail-qv1-f50.google.com with SMTP id j10so8322006qvo.13 for ; Fri, 31 Jul 2020 18:31:40 -0700 (PDT) MIME-Version: 1.0 References: <1576684108-30177-1-git-send-email-kvalo@codeaurora.org> <1576684108-30177-2-git-send-email-kvalo@codeaurora.org> <1576748692.7758.17.camel@realtek.com> <20191219154828.GA12287@w1.fi> <20191219185522.GA16010@w1.fi> <871rpqly6a.fsf@kamboji.qca.qualcomm.com> <87lfjjx0o7.fsf@codeaurora.org> <87y2n9clhj.fsf@codeaurora.org> In-Reply-To: From: Brian Norris Date: Fri, 31 Jul 2020 18:31:27 -0700 Message-ID: Subject: Re: [PATCH 1/2] nl80211: vendor-cmd: qca: add dynamic SAR power limits List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Johannes Berg Cc: Pkshih , Jouni Malinen , "linux-wireless@vger.kernel.org" , "ath10k@lists.infradead.org" , Wen Gong , Kalle Valo On Thu, Jul 30, 2020 at 6:24 AM Johannes Berg wrote: > > Good, I was just checking that we all are on the same page. > > But are we? ;-) I think you were deferring to, "how would user space use it?" And, "would a common API really help anyone?" (And then you implied "anyone" = "Chrome OS.") I expressed a moderate benefit from a common API, but I'd settle for a non-common (but upstream) one instead. I also doubt many non-hardware-customized Linux distributions will make use of this any time soon. I don't think that implied you were truly on a different page. But your response below may say otherwise: > I don't really see anything in the new proposal [1] that really explains > why the common API that we've sort of vaguely outlined in this thread > couldn't work? It just speaks of technical difficulties ("need a > reporting API too"), but should we let that stop us? > > [1] https://patchwork.kernel.org/patch/11686317/ Indeed, I don't see any reason beyond technical difficulties. I'd love to have a few extra hours in my day to spend on writing such an API, if that would really unblock months of deadlock. Unfortunately, those hours tend to get eaten by all sorts of other things these days, so an honest assessment would probably say I won't get around to it soon. SAR regulatory concerns aren't really sexy enough to convince me to spend my weekends on it... (...oh wait, it's Friday evening already. Hmm.) Regards, Brian _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k