Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 64AC670 for ; Thu, 20 May 2021 09:29:53 +0000 (UTC) Received: by mail-wm1-f41.google.com with SMTP id z85-20020a1c7e580000b029017a76f3afbaso2254965wmc.2 for ; Thu, 20 May 2021 02:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :user-agent; bh=0cGf1aBFrVZ9AWx/JMeJaEcovPhb2SGzpzNb2QM+Nk0=; b=uHOB9zSLOzNOqCaCdv3tAd2rduYeX+Y6HLl91ACEXI0mAiipvTrz62XOO2SaIgoVty Pf+RMtbo6f9V42RwSERPXTfjWo95E9cFtuWO9WKA3FnlyXzYA2sixDVebOmpsiGxbbrs 9H75RMmiqXRnaSuCiHDHAfG1oZEYV+e0kFKI3et7gI5qVSablXEgzMq74sy11W+OVSBg fv7UHDUKttjvUQS8McyFbz5R9rRxXKz5CWcwkYd/YNSYTQwhvZ8bx4KdaLHqPOOdvH9T sB+YUNNslLh91vbqAYFcpIySpJbri7dhqbJjx3hah4/GEvkwzv8dQ2huIVBDg0fLwNfN LmAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:user-agent; bh=0cGf1aBFrVZ9AWx/JMeJaEcovPhb2SGzpzNb2QM+Nk0=; b=eNrxm8BpsydSPJn//R69EcGjYyXaft9QGz9yYlANPC5Gw2sZ7kkBOPSbHjkOiodA4k qhF5lXrYjW1R/deSf8oGy0nNfLckpKSwHaHi7OYf8+O0ocBoBaQaFLCCUwddC5BRuKOU t+XkaHSoyw0QE5QG+cCc/lFtmHMBgrMZuHRcLGNIjU9rv6A396YaLV1YoxV/TigJrbZ3 NTVMD48F6fWEUlmARWoMcsKyCB+fusThU9p/VPAuB7w09Mpdr0urGe/gx75K5SrPrSpG wdxn2YClyv+UMMeleODukLLkeL568f6IfdgvqgXnu0dftYzFbB7u1W7nRhtEY6godg6Q CHQQ== X-Gm-Message-State: AOAM533CGus5C3lnv/lcKFhz/GdocpmViFw5CZU0Pt/sMpdHttRUhs7b nq5jQAz3YscREUXcIGwnCXc= X-Google-Smtp-Source: ABdhPJyzQVEd0/LMaL/vCBhQFOWm/v6djjo0ZDbNWBjNqUGvVSd07eOXBWJMelsuPcjU1JJMY/FRXA== X-Received: by 2002:a7b:ce0f:: with SMTP id m15mr3040219wmc.55.1621502991917; Thu, 20 May 2021 02:29:51 -0700 (PDT) Received: from agape.jhs ([5.171.80.207]) by smtp.gmail.com with ESMTPSA id x2sm2018708wmj.3.2021.05.20.02.29.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 20 May 2021 02:29:51 -0700 (PDT) Date: Thu, 20 May 2021 11:29:49 +0200 From: Fabio Aiuto To: hdegoede@redhat.com, Larry.Finger@lwfinger.net Cc: gregkh@linuxfoundation.org, johannes@sipsolutions.net, linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org Subject: staging: rtl8723bs: removal of 5G code Message-ID: <20210520092946.GA1404@agape.jhs> X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) Hi all, I'm stick with removal of 5Ghz code from rtl8723bs wireless card driver (in staging subsystem). I think that this task comprehend deletion of all code managing 80Mhz bandwidth and upper bandwidth (160 and 80+80). For the latter it's simple, there's quite no code (unused enums and obsolete comments). The former seems to be trickier, there are handlers like this: /* 3 Set Reg483 */ SubChnlNum = phy_GetSecondaryChnl_8723B(Adapter); rtw_write8(Adapter, REG_DATA_SC_8723B, SubChnlNum); phy_GetSecondaryChnl_8723B() contains code like: } else if (pHalData->CurrentChannelBW == CHANNEL_WIDTH_40) { if (pHalData->nCur40MhzPrimeSC == HAL_PRIME_CHNL_OFFSET_UPPER) SCSettingOf20 = VHT_DATA_SC_20_UPPER_OF_80MHZ; else if (pHalData->nCur40MhzPrimeSC == HAL_PRIME_CHNL_OFFSET_LOWER) SCSettingOf20 = VHT_DATA_SC_20_LOWER_OF_80MHZ; } so if we are on a 40M channel some settings involving 80M are made and the whole is then written on card registers. May I get rid of the whole? Are there some implications I should be aware of? Is secondary channel needed if we are on 40M bandwidth? Thank you in advance, fabio