Received: by 2002:a05:7412:e794:b0:fa:551:50a7 with SMTP id o20csp2483013rdd; Fri, 12 Jan 2024 10:42:41 -0800 (PST) X-Google-Smtp-Source: AGHT+IHtqz83rSBetpTWJ9f7/0UM+EFv0zrU7LsCJ/JEv6q3EX8DlDaP0temphZS+snKyr4EhcHC X-Received: by 2002:a2e:938b:0:b0:2cd:122e:4424 with SMTP id g11-20020a2e938b000000b002cd122e4424mr950993ljh.17.1705084961683; Fri, 12 Jan 2024 10:42:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1705084961; cv=none; d=google.com; s=arc-20160816; b=o7VVpzK7Stz6x6skFc4PGLToJVGiq7OtufDOGLkk74yJ/tOGezXTOUAeRcTILHTwgH YjeXcD9L6qtKi0C0+YDBhbW/zrJwWVXzKSAIbezfQQgRRJXtkJ3oziwSjJ4Ju1APFjz+ MyLZ/r0+YZGcNI5gzmT1MyKgCuQjgIx9WssHvZdkRvkTWVop6XAjQc1e29yNA6RpecX4 HKNZ99PpWVT0PfzT7dKs9MlgGNn0GneHOboKt8KBW4lgk860Yg8z/9A74Y72LLZZcV0x 3MY4muN5WqTflXt9q6mNbbin36twDFU6WJjduzC9X6WhcmcKm+fLxOqiEDBirpn5oCxn goQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:list-unsubscribe:list-subscribe:list-id:precedence :user-agent:content-transfer-encoding:references:in-reply-to:date:cc :to:from:subject:message-id:dkim-signature; bh=pFgsS3VYj//YTTIIwXJHY+CeFpCzprMxXACWgrWpTNc=; fh=7L4JMqhmb0sZiMbVWFUCCjSLnN+oUs0AEWA/AIa/kdU=; b=f/7PPsChNfxqEfp54iOEzBVsGC237VbM7GeW1eg2vUkRGB1kb9nP9QHai47nRtsCiu uSa3yrmpNSC2d1Q6c39FSLcoErpQON+WqYvskIwLlrlU6A00qU/WBJYAc2Ii8c/Bhpli eWvOK2yCmaUkQVii9WGzp38w36twbeIWh3tE3ZdCQfgAgquWFWe64A7EhY0GJ6oHc9LY hLyuJ6i78Go6xjI/7Fzm4QBC6LnV9AxaBDVgB00O7BFl/q69EfLaZafQisiIZrHNZZUO X7XD7Hw7C8fBCTDPlHPagHI4YYwAFyLmcmhqhaiiDz587NO/mgctFNEUQ312//TtD6+d 22rA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=vkzg4qjJ; spf=pass (google.com: domain of linux-wireless+bounces-1843-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-wireless+bounces-1843-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [147.75.80.249]) by mx.google.com with ESMTPS id ch12-20020a0564021bcc00b00558bc743737si971250edb.47.2024.01.12.10.42.41 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 12 Jan 2024 10:42:41 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless+bounces-1843-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=vkzg4qjJ; spf=pass (google.com: domain of linux-wireless+bounces-1843-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-wireless+bounces-1843-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id 41C3D1F24757 for ; Fri, 12 Jan 2024 18:42:41 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 4F53C1548E; Fri, 12 Jan 2024 18:42:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="vkzg4qjJ" X-Original-To: linux-wireless@vger.kernel.org Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B08BE156CD for ; Fri, 12 Jan 2024 18:42:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=pFgsS3VYj//YTTIIwXJHY+CeFpCzprMxXACWgrWpTNc=; t=1705084952; x=1706294552; b=vkzg4qjJrw3w7KAS/5YEC9JJXytzk3qii3Pj6XWLrLQoqGB uMLmZiK9ZQBP7H0YH90wuyYxRVsdniaX9Zfdin3T6ui27HUIxQd2bmeL9eawl8whV9yuVj13jNWV0 O9CiNn/KM5erOlYU6N2AcjA/sJIRae5jsPEa87xWYDQ6KQYKQfSJj1/i8iskQrF/5KHdxxhb/TzcV R47WAeS4r8D4ad8zXpmGmZYS21fODDOeUevkok4f0WUVm7p/Uv5bi3FDzpbCZrzeU5jEYHj/yaZf8 q4OpX/lZz0AISs5HRncSowV1zg9/H5ti2Ppi1vvVpR9RTbvdqe3A9U6lxJ461YeA==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.97) (envelope-from ) id 1rOMU9-0000000GvqW-03OU; Fri, 12 Jan 2024 19:42:29 +0100 Message-ID: Subject: Re: [PATCH 5/8] wifi: mac80211: disallow drivers with HT wider than HE From: Johannes Berg To: Kalle Valo , Miri Korenblit Cc: linux-wireless@vger.kernel.org, Gregory Greenman Date: Fri, 12 Jan 2024 19:42:27 +0100 In-Reply-To: <87wmsehf3d.fsf@kernel.org> References: <20240111161746.3978601-1-miriam.rachel.korenblit@intel.com> <20240111181514.da15fe3214d2.I4df51ad2f4c844615c168bf9bdb498925b3c77d4@changeid> <87wmsehf3d.fsf@kernel.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.50.2 (3.50.2-1.fc39) Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Fri, 2024-01-12 at 15:10 +0200, Kalle Valo wrote: > Miri Korenblit writes: >=20 > > + /* currently no support for HE client where HT has 40 MHz but not H= T */ > > + if (iftd->he_cap.has_he && > > + iftd->types_mask & (BIT(NL80211_IFTYPE_STATION) | > > + BIT(NL80211_IFTYPE_P2P_CLIENT)) && > > + sband->ht_cap.ht_supported && > > + sband->ht_cap.cap & IEEE80211_HT_CAP_SUP_WIDTH_20_40 && > > + !(iftd->he_cap.he_cap_elem.phy_cap_info[0] & he_40_mhz_cap)) > > + return -EINVAL; >=20 > Should there be a warning message so that this is noticed if it ever > happens? I don't know. Yeah I don't really know either. I've done that a lot in the past, but these days I'm kind of thinking that people who develop their drivers should have some debug story and be able to figure it out? You know better perhaps ... Though it'd kind of suck to indent this further with WARN_ON ;-) johannes