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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F340DC352A1 for ; Tue, 6 Dec 2022 17:59:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229480AbiLFR7g (ORCPT ); Tue, 6 Dec 2022 12:59:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49246 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229449AbiLFR7e (ORCPT ); Tue, 6 Dec 2022 12:59:34 -0500 Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.48]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DB5A82873F for ; Tue, 6 Dec 2022 09:59:33 -0800 (PST) X-Virus-Scanned: Proofpoint Essentials engine Received: from mx1-us1.ppe-hosted.com (unknown [10.7.67.124]) by mx1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTPS id D45691A0083; Tue, 6 Dec 2022 17:59:26 +0000 (UTC) Received: from mail3.candelatech.com (mail2.candelatech.com [208.74.158.173]) by mx1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTP id A6BE3940084; Tue, 6 Dec 2022 17:59:26 +0000 (UTC) Received: from [10.0.0.50] (cpe-98-151-114-119.hawaii.res.rr.com [98.151.114.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail3.candelatech.com (Postfix) with ESMTPSA id EF54B13C2B0; Tue, 6 Dec 2022 09:59:25 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 mail3.candelatech.com EF54B13C2B0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=candelatech.com; s=default; t=1670349566; bh=8HOIkMGH1VwRGYr3vsQkOV2Swe7y0a7QrZwb2O72FSo=; h=Date:Subject:To:References:From:In-Reply-To:From; b=nt30aMaLSCkvr84T4yume3CVImzokcLSjp3QMPnxSytasc7iDQ1A6vCU5bIdo3y1L JWNvX+R1KmoqWlIgBIyRKLCz4Kf4rzzQuxzbXQ9HYWatwOU0LJmXEKeDDLLxlrhjPl 4e28NJfGbF3Ev7w+vkdXFUrxHWxDc0xc1URr0OxM= Message-ID: <413cbc75-14e8-f80d-e536-e1d72c5d1605@candelatech.com> Date: Tue, 6 Dec 2022 09:59:25 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: ax210: Ability to report noise floor? Content-Language: en-MW To: "Greenman, Gregory" , "linux-wireless@vger.kernel.org" References: <00a4d194f70c4f4c7b7df38b79c0df40ba87f0aa.camel@intel.com> From: Ben Greear Organization: Candela Technologies In-Reply-To: <00a4d194f70c4f4c7b7df38b79c0df40ba87f0aa.camel@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-MDID: 1670349567-inZfQFBNVo0Y X-MDID-O: us5-ut7-1670349567-inZfQFBNVo0Y Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 12/6/22 06:10, Greenman, Gregory wrote: > Hi Ben, > > On Mon, 2022-12-05 at 07:49 -0800, Ben Greear wrote: >> Hello, >> >> Is there any way to get Intel ax210 to report the noise floor? >> >> Thanks, >> Ben >> > > No, unfortunately we don't have this information in the driver. > > Regards, > Gregory > Someone told me the Windows driver had support for noise floor...so maybe just need some new API to be implemented to the firmware? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com