Received: by 2002:ac2:5a04:0:0:0:0:0 with SMTP id q4csp956059lfn; Fri, 18 Feb 2022 01:34:16 -0800 (PST) X-Google-Smtp-Source: ABdhPJwtlY4tm+oAwFEk7z9EtPGYwlueU205g0sxH9k2Pu94Z0iT6v1Dvurmnbj4EWHWwun+6GOQ X-Received: by 2002:a17:906:bc8d:b0:6cf:6b41:e48e with SMTP id lv13-20020a170906bc8d00b006cf6b41e48emr5749481ejb.372.1645176856698; Fri, 18 Feb 2022 01:34:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645176856; cv=none; d=google.com; s=arc-20160816; b=Q085pv/7pe9tA0krxKs5UjzdxmQSyfpDYCgNw2Ck3wZ191atYrmmjUJ8vUVviPc58A 2Lqk1tmLYOlzXS2jp8CbEzaWHRfkHEBflOQWjBoKBGe4YlB7BETUIK4Y1G6jLKc5/BWL gEcMZvOjyTgUnjafVokOgDHIk8QJ1pjf0PfOtZnNRUo6J882g4sjd1+qo6u7EUA4fgkX 131nXUBWt4NrwzVp88jG6SbN0idBMR0tEaBatAGrKK1huCX5JDE+fmwX05WPMOgT4TZ9 e/YJkAHaSsX7xe9n8Ynw02wz4hFII+iV2iTl1FJiNwNgVYtrJonaK5XwbZZkJJ1LGhsy qLtw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=9X3uHuSgIlzYfA7/YTiVCBE2/LuZuqCQKAPLcWi5R8I=; b=W/gZ1lTyKJw2GZ/Trk+SNMprDEb36YyECeycH0WNIQ7WONO/YRvfok0LrJKh139sS+ Z+mh/kCZepUNR3bgzoxg2Jk6HczbDc6XCC67XCcRb9rGhiP2spMjOArerTa0gj0Ftq5s neDnNQdDxP6hwec294hYdEyD+KbGOGZpWUKQ5tkXn1VzaBcSU8/AmlyaZGLSy4hwAd5O aVLv4WtvfyyVxaDxU1KKew3WugoY1sOUEBeY0w9M97RA9xUoa4/+p4G/HfrhVWmeOW1p xcMqe69p4UUP5TnPxJi3XGGtoFEPL3XrNpafmmRjpxtwzyhwBtRq39YKnuSa/ZQ0CU4W 7S4w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m14si6154306edd.534.2022.02.18.01.33.52; Fri, 18 Feb 2022 01:34:16 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233478AbiBRJXc (ORCPT + 99 others); Fri, 18 Feb 2022 04:23:32 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:33672 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233301AbiBRJXb (ORCPT ); Fri, 18 Feb 2022 04:23:31 -0500 Received: from viti.kaiser.cx (viti.kaiser.cx [IPv6:2a01:238:43fe:e600:cd0c:bd4a:7a3:8e9f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9DA7A2C12E for ; Fri, 18 Feb 2022 01:23:14 -0800 (PST) Received: from dslb-178-004-174-047.178.004.pools.vodafone-ip.de ([178.4.174.47] helo=martin-debian-2.paytec.ch) by viti.kaiser.cx with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1nKzTo-0005Qj-Nr; Fri, 18 Feb 2022 10:23:08 +0100 From: Martin Kaiser To: Greg Kroah-Hartman Cc: Larry Finger , Phillip Potter , Michael Straube , linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org, Martin Kaiser Subject: [PATCH RFC] staging: r8188eu: comment about the chip's packet format Date: Fri, 18 Feb 2022 10:22:53 +0100 Message-Id: <20220218092252.853807-1-martin@kaiser.cx> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The structs phy_rx_agc_info and phy_status_rpt define parts of the header data that the r8188eu chipset sends to this driver via usb. Add a comment to clarify that we cannot modify the content of these structures and remove seemingly unused fields. Signed-off-by: Martin Kaiser --- Dear all, I experimented with "cleaning up" these structures and related code before discovering that their content comes from usb packets we receive from the r8188eu chipset. Would it make sense to add a word of warning to prevent others from repeating this exercise? Thanks, Martin drivers/staging/r8188eu/include/odm_HWConfig.h | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/drivers/staging/r8188eu/include/odm_HWConfig.h b/drivers/staging/r8188eu/include/odm_HWConfig.h index b37962edb2ed..35a562372a1a 100644 --- a/drivers/staging/r8188eu/include/odm_HWConfig.h +++ b/drivers/staging/r8188eu/include/odm_HWConfig.h @@ -14,6 +14,13 @@ /* structure and define */ +/* + * Attention: struct phy_status_rpt and struct phy_rx_agc_info describe + * data structures that this driver receives from the r8188eu chip via usb. + * Do not change the content of these structures, do not remove seemingly + * unused entries. + */ + struct phy_rx_agc_info { #ifdef __LITTLE_ENDIAN u8 gain:7, trsw:1; -- 2.30.2