From mboxrd@z Thu Jan 1 00:00:00 1970 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 6BA2937CD5B for ; Tue, 3 Mar 2026 11:44:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772538271; cv=none; b=jV58ORat3KiyJw2HzV0P2XrmiAkSS7Kelvvchu+wRmNqjEXVRlK1Ua8rlHdas+DwFEjwWV3WHJfVFq+WalxM1ZA2c3e+R6v6iitaUWpR7pDZAkIVtIsqhzM3DvZxN36U8abqk9uG4OtkQ1bMTPcKRKtzpqimda+uREHZdH5neWc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772538271; c=relaxed/simple; bh=SghpSl6WTTnFqJZo0uRVa+z3rkXHx8QaaoqRG9gLVXk=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=R0X8jB3x9YjpcktOhvfaU7rQRn2oHTK1d7tKnrrj26DgpvgBjjv2rYWvNnguH7vRwnSGQsRKhRz+aO6PL+A1r79pCmsTLTSG/0E0/MeIu2nq00oSmlZS8C4qMJRv4AsM7voG1+ogkGFWSKI/MSKt+f8xRHXJXtbH5HVe2Duj2NQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=PiH5YxaU; arc=none smtp.client-ip=168.119.38.16 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 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="PiH5YxaU" 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=sANG3WimobWLRM22SiDtmZU3m5NPrQ5WoDvzNGZnOUw=; t=1772538270; x=1773747870; b=PiH5YxaUEzksPRZANE4J7RwZuqridbbzb4ITuwmOnvsKXGJ DR9uSPQq+0oazXPLdfbz1IlQyA0mCaU4tRMX4GOQFqRl9lCAMGEc/fjf1MEbB/Ftk4gFjXojtMf4P dPMl5TNS7V2rck6mO4XPbGkRmYzs8AiQhNj06WcExoczosSOcU+Anfrc/ur0EQpGC7Z0424V/l+rc SAOgTnJJNAQ3jG1XhkoGHXbWONPUbLOeNPi90KYIOgBwFnACluJ+r4JQWHtKr1gChI+q+a38rHpyN kAfOGSwKhTN/G6BrK01h2o0SyLrr9fguSLcGxZQfIoUa/y2m3Vs/qpF7+SJncRqw==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98.2) (envelope-from ) id 1vxOAs-0000000755l-1W44; Tue, 03 Mar 2026 12:44:26 +0100 Message-ID: <042df19bd62ca0f8044c3da496319c8b5fb79bdf.camel@sipsolutions.net> Subject: Re: [PATCH wireless-next v4 2/2] wifi: mac80211_hwsim: Add UHR capabilities to the driver From: Johannes Berg To: Karthikeyan Kathirvel Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org Date: Tue, 03 Mar 2026 12:44:25 +0100 In-Reply-To: References: <20260217054731.3667600-1-karthikeyan.kathirvel@oss.qualcomm.com> <20260217054731.3667600-3-karthikeyan.kathirvel@oss.qualcomm.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 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 Tue, 2026-03-03 at 17:11 +0530, Karthikeyan Kathirvel wrote: > Got it. It looks like this requires a deeper feature-level understanding= =20 > or a review of the full spec document for each feature. >=20 Certainly some understanding, but I don't think you have to necessarily deeply understand each feature - it's specified in the table of capabilities which are reserved where (though one notable exception is missing in the table, the update timeout.) > Instead, I used=20 > AI to simplify this. Below, I=E2=80=99ve pasted the AI output, categorize= d by=20 > AP/non-AP STA and by bands. Is this approach fine? Shall I go ahead and= =20 > make the changes based on this? I can't really say anything on that unless I go cross-check this with 9.4.2.354 UHR Capabilities Element, which you can do just as well as I can? :) > ### UHR MAC capabilities >=20 > | Macro | Role tag | Band tag | > |---------------------------------|-----------------------|----------| > | IEEE80211_UHR_MAC_CAP0_DPS_SUPP | Both (AP + non=E2=80=91AP STA) | A= ll | > | IEEE80211_UHR_MAC_CAP0_DPS_ASSIST_SUPP | Both | All | Also the table is pretty unreadable anyway. johannes