Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp4702881rwe; Mon, 17 Apr 2023 17:38:19 -0700 (PDT) X-Google-Smtp-Source: AKy350Y6VXLzzCeecNInk3EDPGaTFaHX/Z8R6SGnAxgfjiUsNy/ZwEgF6FWkfxT+hE/6wpw/r0Wy X-Received: by 2002:a05:6a00:21c6:b0:624:7aac:ab7 with SMTP id t6-20020a056a0021c600b006247aac0ab7mr19630615pfj.18.1681778298787; Mon, 17 Apr 2023 17:38:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681778298; cv=none; d=google.com; s=arc-20160816; b=s66nNXoWzfj01SCho7UCarGGzG795rfGayoMhgu+ecRsIpII4TD+XP9QszRFIQKAz9 Y78Pd0QisrWbJ28avooaiLFsk7vazmeSR8hAzQQxs19cDTebehQJcRevbQtiH9rF5vfC dQq4yU6WKnwitHLclHeCFH+tcUiBNS7r8haLy/+A2x7PKCaaY77kPs/q4hjgSJ1xHocH GN78nBxPqqGOhbkiAXQHRhoz7JhrC24WvHK1nx34VaI88XLmva0W2YcPE9tNeAqdRElU 85o0cnyCPRFW6aEdzZKk6aGcgVfbUn11yIuorzXLbcPFG13Y7QXqXsslF5DQ6VxL34B8 SEdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:content-transfer-encoding :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:thread-topic:subject:cc:to:from:authenticated-by; bh=bdB6IydkFi6RhwE890KXK/Cuclcl6Fuogr3KR/5Zq+w=; b=ixN9XMAUpbhFZfzPXuIqUFkfronSMhirwwT21qoY9SlyAi4XHSQcDTaz7LOOMkkevF QQf0YzT4bYVTIhkfM27cHc0PmhRCegE/RaMasn05uPNTuDoXKWf4wOomsSt5FwlV8GxS c9tJ87Wdwm/48/R6XL1/aM5AKsvxpjZsZ6BlHmQVMHhugkbK/bmX9TOGOiNpuEHaDRQj 4dGeeXcl/QwK8Jn9DYCWZNbDGgPmi1Rmis0eJod7tc5/Qh+Py/LPSHKd9wfLjSoXJxQa iZ0T1WlDJMTYIiFLqyWXP0uos8THNcTQyipjfhEWsvbZqmaNIMgy6p2mTVirCRvEMqv4 4dGg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-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 4-20020a630704000000b0051aaccf1e13si289524pgh.724.2023.04.17.17.38.09; Mon, 17 Apr 2023 17:38:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-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-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229546AbjDRAhA convert rfc822-to-8bit (ORCPT + 63 others); Mon, 17 Apr 2023 20:37:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54160 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229477AbjDRAg6 (ORCPT ); Mon, 17 Apr 2023 20:36:58 -0400 Received: from rtits2.realtek.com.tw (rtits2.realtek.com [211.75.126.72]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7BF78422C for ; Mon, 17 Apr 2023 17:36:57 -0700 (PDT) Authenticated-By: X-SpamFilter-By: ArmorX SpamTrap 5.77 with qID 33I0aW1U1008548, This message is accepted by code: ctloc85258 Received: from mail.realtek.com (rtexh36505.realtek.com.tw[172.21.6.25]) by rtits2.realtek.com.tw (8.15.2/2.81/5.90) with ESMTPS id 33I0aW1U1008548 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK); Tue, 18 Apr 2023 08:36:32 +0800 Received: from RTEXMBS04.realtek.com.tw (172.21.6.97) by RTEXH36505.realtek.com.tw (172.21.6.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.32; Tue, 18 Apr 2023 08:36:32 +0800 Received: from RTEXMBS04.realtek.com.tw (172.21.6.97) by RTEXMBS04.realtek.com.tw (172.21.6.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.7; Tue, 18 Apr 2023 08:36:32 +0800 Received: from RTEXMBS04.realtek.com.tw ([fe80::e138:e7f1:4709:ff4d]) by RTEXMBS04.realtek.com.tw ([fe80::e138:e7f1:4709:ff4d%5]) with mapi id 15.01.2375.007; Tue, 18 Apr 2023 08:36:31 +0800 From: Ping-Ke Shih To: Sascha Hauer , linux-wireless CC: Hans Ulli Kroll , Larry Finger , Tim K , "Alex G ." , Nick Morrow , Viktor Petrenko , Andreas Henriksson , ValdikSS , "kernel@pengutronix.de" Subject: RE: [PATCH v3 3/4] wifi: rtw88: set pkg_type correctly for specific rtw8821c variants Thread-Topic: [PATCH v3 3/4] wifi: rtw88: set pkg_type correctly for specific rtw8821c variants Thread-Index: AQHZcTWhs9mTMlEeIUm9+FRiD4ucxa8wOCrg Date: Tue, 18 Apr 2023 00:36:31 +0000 Message-ID: References: <20230417140358.2240429-1-s.hauer@pengutronix.de> <20230417140358.2240429-4-s.hauer@pengutronix.de> In-Reply-To: <20230417140358.2240429-4-s.hauer@pengutronix.de> Accept-Language: en-US, zh-TW Content-Language: zh-TW X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.21.69.188] x-kse-serverinfo: RTEXMBS04.realtek.com.tw, 9 x-kse-antispam-interceptor-info: fallback x-kse-antivirus-interceptor-info: fallback Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-KSE-AntiSpam-Interceptor-Info: fallback X-KSE-ServerInfo: RTEXH36505.realtek.com.tw, 9 X-KSE-AntiSpam-Interceptor-Info: fallback X-KSE-Antivirus-Interceptor-Info: fallback X-KSE-AntiSpam-Interceptor-Info: fallback X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,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-wireless@vger.kernel.org > -----Original Message----- > From: Sascha Hauer > Sent: Monday, April 17, 2023 10:04 PM > To: linux-wireless > Cc: Hans Ulli Kroll ; Larry Finger ; Ping-Ke Shih > ; Tim K ; Alex G . ; Nick Morrow > ; Viktor Petrenko ; Andreas Henriksson ; > ValdikSS ; kernel@pengutronix.de; Sascha Hauer > Subject: [PATCH v3 3/4] wifi: rtw88: set pkg_type correctly for specific rtw8821c variants > > According to the vendor driver the pkg_type has to be set to '1' > for some rtw8821c variants. As the pkg_type has been hardcoded to > '0', add a field for it in struct rtw_hal and set this correctly > in the rtw8821c part. > With this parsing of a rtw_table is influenced and check_positive() > in phy.c returns true for some cases here. The same is done in the > vendor driver. However, this has no visible effect on the driver > here. I agree this patch, but still want to know more about the meaning of "...no visible effect...". Do you mean your USB device works well with/without this patch? or, IO is absolutely the same when loading parameters with check_positive()? > > Signed-off-by: Sascha Hauer Reviewed-by: Ping-Ke Shih [..]