Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1156928pxb; Wed, 10 Feb 2021 01:13:55 -0800 (PST) X-Google-Smtp-Source: ABdhPJyrBSXvVZVLTKTReKhw+3L1BSzPjhs0eG64cE5vRjOjUuW8qXD4jFkFVslcBBLNou5gnn9D X-Received: by 2002:a17:906:80d9:: with SMTP id a25mr1902080ejx.405.1612948434799; Wed, 10 Feb 2021 01:13:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612948434; cv=none; d=google.com; s=arc-20160816; b=IHWWKMGRQJf2gh+nM9OftSu+n8JdBJhHZTc2RMv/w4VLhRLvN4uz4FcE0nEJj4gflw 15nz+DViqyDl+V/ByKV4VmtyLSA5Zw6vWv53SRiqGp/GCR8qqhxBBoGBdZjBpG3dWU+M 4trmUcq2MkTktWi2cuiEM/2WucCG9GUG9r/KLzm9E5jpzHWbuNEa1skqhxhxgFyjpQ/g wDOaycpS/pk01U18uC3Z3xjaKBQtbXVAyPgg/OGx9/JxVRmuWF2IGzflcELRP4wZ4XQw loRqJ/TbdBN5+wCzVp1cQeWdDkhie6/+6rESM1cQvXgAP0tWJe9laf55uOQKJso0NVz4 rotA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=+g9Y8cyC/XpZejdxK4prgqdb7eO7ulFp3q9d8kXhFus=; b=g9nYBDm8LicqNPqFtaynLysZ3ywksfxGqypIEQBjNDjMIlnoQ95quFfabTIgtrqGtm sWOjNAAI1a9lacyOpH5Ir9Q7hfZzxWW052rlxPX5FEF9X9Am3RcWsFVevA4Ys3HQnhQ1 5uGwmsXh/VGXmUoviqDIQVUkKaIDA1djGYbDPCcGdm+gCcbd8BWFli6DC9H64oh48wgX Y58sM6M3RG1yI396pE871Fzzvv6EXSWj3BEQJGGOPEnuPCQ5Tq1Emfr5zq6xeklFhBqj 9+H5sCb3dL2iVbkDJHXPg/+lIEmVXz0q3JTJlfc7K1lpw7IojOhWVTtdfJS6bQL24M9p tWEw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p13si928754ejo.460.2021.02.10.01.13.31; Wed, 10 Feb 2021 01:13:54 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230419AbhBJJFv (ORCPT + 99 others); Wed, 10 Feb 2021 04:05:51 -0500 Received: from mail-ej1-f44.google.com ([209.85.218.44]:44938 "EHLO mail-ej1-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229952AbhBJI7e (ORCPT ); Wed, 10 Feb 2021 03:59:34 -0500 Received: by mail-ej1-f44.google.com with SMTP id w1so2642192ejf.11 for ; Wed, 10 Feb 2021 00:59:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+g9Y8cyC/XpZejdxK4prgqdb7eO7ulFp3q9d8kXhFus=; b=fvvrc1enAdCn3uYDvVVJb2g6QtYuDnaA2YwvbT7kYjNqVaJSfLFLEqXecckqGZJWS/ 0YPSoyj1aHlOu7MH/i/upCUBr0sV7JnViEluqu9tsLl80XLsATDDNsWabOqACPShuhdN 4cpG1dslFISxVB8Dm3gV44rvvbmTAo/UJuh9Uq6SPGZPaclHfzdmXjFUi42ExGW22IOY XwpHU0RetC2U0qP78mEm/sDCjayoTu2QtU2KGo4a7OpBhd0z+GjqeXQI8d9Q279f8bcv DeGzvmpoJj5quzsCm9Rc9Wyl44T/8bsrDJmNwyJF5SBmUJnSfVuorLDZ8+Q3z7hJLdeJ YgnQ== X-Gm-Message-State: AOAM533KKm9VG1mgRz2BqETzFE19xg+Mt+qVTf7DTc6r567KHKhlUggQ pvWPLrkV4iOdx4MPyN2RFltgaijbyXGDbg== X-Received: by 2002:a17:906:408b:: with SMTP id u11mr1875869ejj.299.1612947523498; Wed, 10 Feb 2021 00:58:43 -0800 (PST) Received: from mail-ed1-f47.google.com (mail-ed1-f47.google.com. [209.85.208.47]) by smtp.gmail.com with ESMTPSA id i6sm663857ejd.110.2021.02.10.00.58.42 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 10 Feb 2021 00:58:43 -0800 (PST) Received: by mail-ed1-f47.google.com with SMTP id t5so1924535eds.12 for ; Wed, 10 Feb 2021 00:58:42 -0800 (PST) X-Received: by 2002:a50:9d4d:: with SMTP id j13mr2146450edk.83.1612947522632; Wed, 10 Feb 2021 00:58:42 -0800 (PST) MIME-Version: 1.0 References: <20210210080636.GT2696@kadam> In-Reply-To: <20210210080636.GT2696@kadam> From: karthek Date: Wed, 10 Feb 2021 14:28:31 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] staging: rtl8723bs: fix function comments to follow kernel-doc To: Dan Carpenter Cc: Greg Kroah-Hartman , Stephen Rothwell , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 10, 2021 at 1:37 PM Dan Carpenter wrote: > > On Wed, Feb 10, 2021 at 02:42:30AM +0530, karthik alapati wrote: > > fix checkpatch.pl warning for "block comments should align the > > * on each line" and make function comments follow kernel-doc > > > > Signed-off-by: karthik alapati > > --- > > .../staging/rtl8723bs/hal/rtl8723b_phycfg.c | 209 ++++++++---------- > > 1 file changed, 91 insertions(+), 118 deletions(-) > > > > diff --git a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c > > index cf23414d7..b7fca881c 100644 > > --- a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c > > +++ b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c > > @@ -20,16 +20,11 @@ > > #define MAX_DOZE_WAITING_TIMES_9x 64 > > > > /** > > -* Function: phy_CalculateBitShift > > -* > > -* OverView: Get shifted position of the BitMask > > -* > > -* Input: > > -* u32 BitMask, > > -* > > -* Output: none > > -* Return: u32 Return the shift bit bit position of the mask > > -*/ > > + * phy_CalculateBitShift - Get shifted position of the BitMask. > > + * @BitMask: Bitmask. > > + * > > + * Return: Return the shift bit position of the mask > > + */ > > static u32 phy_CalculateBitShift(u32 BitMask) > > { > > u32 i; > > @@ -43,19 +38,17 @@ static u32 phy_CalculateBitShift(u32 BitMask) > > > > > > /** > > -* Function: PHY_QueryBBReg > > -* > > -* OverView: Read "specific bits" from BB register > > -* > > -* Input: > > -* struct adapter * Adapter, > > -* u32 RegAddr, The target address to be readback > > -* u32 BitMask The target bit position in the target address > > -* to be readback > > -* Output: None > > -* Return: u32 Data The readback register value > > -* Note: This function is equal to "GetRegSetting" in PHY programming guide > > -*/ > > + * PHY_QueryBBReg - Read "specific bits" from BB register. > > + * @Adapter: > > + * @RegAddr: The target address to be readback > > + * @BitMask: The target bit position in the target address > > + * to be readback > > + * > > + * Return: The readback register value > > + * > > + * .. Note:: This function is equal to "GetRegSetting" in PHY programming > > + * guide > > + */ > > u32 PHY_QueryBBReg_8723B(struct adapter *Adapter, u32 RegAddr, u32 BitMask) > > { > > u32 OriginalValue, BitShift; > > @@ -64,7 +57,10 @@ u32 PHY_QueryBBReg_8723B(struct adapter *Adapter, u32 RegAddr, u32 BitMask) > > return 0; > > #endif > > > > - /* RT_TRACE(COMP_RF, DBG_TRACE, ("--->PHY_QueryBBReg(): RegAddr(%#lx), BitMask(%#lx)\n", RegAddr, BitMask)); */ > > + /** > > + * RT_TRACE(COMP_RF, DBG_TRACE, ("--->PHY_QueryBBReg(): > > + * RegAddr(%#lx), BitMask(%#lx)\n", RegAddr, BitMask)); > > + */ > > Just delete this (in a separate patch). > > > > > OriginalValue = rtw_read32(Adapter, RegAddr); > > BitShift = phy_CalculateBitShift(BitMask); > > @@ -75,22 +71,17 @@ u32 PHY_QueryBBReg_8723B(struct adapter *Adapter, u32 RegAddr, u32 BitMask) > > > > > > /** > > -* Function: PHY_SetBBReg > > -* > > -* OverView: Write "Specific bits" to BB register (page 8~) > > -* > > -* Input: > > -* struct adapter * Adapter, > > -* u32 RegAddr, The target address to be modified > > -* u32 BitMask The target bit position in the target address > > -* to be modified > > -* u32 Data The new register value in the target bit position > > -* of the target address > > -* > > -* Output: None > > -* Return: None > > -* Note: This function is equal to "PutRegSetting" in PHY programming guide > > -*/ > > + * PHY_SetBBReg - Write "Specific bits" to BB register (page 8~). > > + * @Adapter: > > + * @RegAddr: The target address to be modified > > + * @BitMask: The target bit position in the target address > > + * to be modified > > + * @Data: The new register value in the target bit position > > + * of the target address > > + * > > + * .. Note:: This function is equal to "PutRegSetting" in PHY programming > > + * guide > > + */ > > > > void PHY_SetBBReg_8723B( > > struct adapter *Adapter, > > @@ -106,7 +97,10 @@ void PHY_SetBBReg_8723B( > > return; > > #endif > > > > - /* RT_TRACE(COMP_RF, DBG_TRACE, ("--->PHY_SetBBReg(): RegAddr(%#lx), BitMask(%#lx), Data(%#lx)\n", RegAddr, BitMask, Data)); */ > > + /** > > + * RT_TRACE(COMP_RF, DBG_TRACE, ("--->PHY_SetBBReg(): > > + * RegAddr(%#lx), BitMask(%#lx), Data(%#lx)\n", RegAddr, BitMask, Data)); > > + */ > > Delete. > > > > > if (BitMask != bMaskDWord) { /* if not "double word" write */ > > OriginalValue = rtw_read32(Adapter, RegAddr); > > @@ -184,27 +178,21 @@ static u32 phy_RFSerialRead_8723B( > > } > > > > /** > > -* Function: phy_RFSerialWrite_8723B > > -* > > -* OverView: Write data to RF register (page 8~) > > -* > > -* Input: > > -* struct adapter * Adapter, > > -* RF_PATH eRFPath, Radio path of A/B/C/D > > -* u32 Offset, The target address to be read > > -* u32 Data The new register Data in the target bit position > > -* of the target to be read > > -* > > -* Output: None > > -* Return: None > > -* Note: Threre are three types of serial operations: > > -* 1. Software serial write > > -* 2. Hardware LSSI-Low Speed Serial Interface > > -* 3. Hardware HSSI-High speed > > -* serial write. Driver need to implement (1) and (2). > > -* This function is equal to the combination of RF_ReadReg() and RFLSSIRead() > > + * phy_RFSerialWrite_8723B - Write data to RF register (page 8~). > > + * @Adapter: > > + * @eRFPath: Radio path of A/B/C/D > > + * @Offset: The target address to be read > > + * @Data: The new register Data in the target bit position > > + * of the target to be read > > + * > > + * .. Note:: Threre are three types of serial operations: > > + * 1. Software serial write > > + * 2. Hardware LSSI-Low Speed Serial Interface > > + * 3. Hardware HSSI-High speed > > + * serial write. Driver need to implement (1) and (2). > > + * This function is equal to the combination of RF_ReadReg() and RFLSSIRead() > > * > > - * Note: For RF8256 only > > + * .. Note:: For RF8256 only > > * The total count of RTL8256(Zebra4) register is around 36 bit it only employs > > * 4-bit RF address. RTL8256 uses "register mode control bit" (Reg00[12], Reg00[10]) > > * to access register address bigger than 0xf. See "Appendix-4 in PHY Configuration > > @@ -225,7 +213,7 @@ static u32 phy_RFSerialRead_8723B( > > * > > * > > * > > -*/ > > + */ > > static void phy_RFSerialWrite_8723B( > > struct adapter *Adapter, > > enum RF_PATH eRFPath, > > @@ -249,33 +237,33 @@ static void phy_RFSerialWrite_8723B( > > /* Put write addr in [5:0] and write data in [31:16] */ > > /* */ > > /* DataAndAddr = (Data<<16) | (NewOffset&0x3f); */ > > - DataAndAddr = ((NewOffset<<20) | (Data&0x000fffff)) & 0x0fffffff; /* T65 RF */ > > + DataAndAddr = ((NewOffset<<20) | (Data&0x000fffff)) & 0x0fffffff; > > + /*T65 RF */ > > This doesn't make sense at all now. > > > > > /* */ > > /* Write Operation */ > > /* */ > > PHY_SetBBReg(Adapter, pPhyReg->rf3wireOffset, bMaskDWord, DataAndAddr); > > - /* RTPRINT(FPHY, PHY_RFW, ("RFW-%d Addr[0x%lx]= 0x%lx\n", eRFPath, pPhyReg->rf3wireOffset, DataAndAddr)); */ > > + /** > > + *RTPRINT(FPHY, PHY_RFW, ("RFW-%d Addr[0x%lx]= 0x%lx\n", eRFPath, > > + *pPhyReg->rf3wireOffset, DataAndAddr)); > > + */ > > Delete. > > > > > } > > > > > > /** > > -* Function: PHY_QueryRFReg > > -* > > -* OverView: Query "Specific bits" to RF register (page 8~) > > -* > > -* Input: > > -* struct adapter * Adapter, > > -* RF_PATH eRFPath, Radio path of A/B/C/D > > -* u32 RegAddr, The target address to be read > > -* u32 BitMask The target bit position in the target address > > -* to be read > > -* > > -* Output: None > > -* Return: u32 Readback value > > -* Note: This function is equal to "GetRFRegSetting" in PHY programming guide > > -*/ > > + * PHY_QueryRFReg - Query "Specific bits" to RF register (page 8~). > > + * @Adapter: > > + * @eRFPath: Radio path of A/B/C/D > > + * @RegAdd: The target address to be read > > + * @BitMask: The target bit position in the target address > > + * to be read > > + * > > + * Return: Readback value > > + * > > + * .. Note:: This function is equal to "GetRFRegSetting" in PHY programming guide > > + */ > > u32 PHY_QueryRFReg_8723B( > > struct adapter *Adapter, > > u8 eRFPath, > > @@ -296,23 +284,17 @@ u32 PHY_QueryRFReg_8723B( > > } > > > > /** > > -* Function: PHY_SetRFReg > > -* > > -* OverView: Write "Specific bits" to RF register (page 8~) > > -* > > -* Input: > > -* struct adapter * Adapter, > > -* RF_PATH eRFPath, Radio path of A/B/C/D > > -* u32 RegAddr, The target address to be modified > > -* u32 BitMask The target bit position in the target address > > -* to be modified > > -* u32 Data The new register Data in the target bit position > > -* of the target address > > -* > > -* Output: None > > -* Return: None > > -* Note: This function is equal to "PutRFRegSetting" in PHY programming guide > > -*/ > > + * PHY_SetRFReg - Write "Specific bits" to RF register (page 8~). > > + * @Adapter: > > + * @eRFPath: Radio path of A/B/C/D > > + * @RegAddr: The target address to be modified > > + * @BitMask: The target bit position in the target address > > + * to be modified > > + * @Data: The new register Data in the target bit position > > + * of the target address > > + * > > + * .. Note:: This function is equal to "PutRFRegSetting" in PHY programming guide > > > Don't put a huge white space after the ::. > > regards, > dan carpenter > > > + */ > > void PHY_SetRFReg_8723B( > > struct adapter *Adapter, > > u8 eRFPath, > > @@ -344,15 +326,7 @@ void PHY_SetRFReg_8723B( > > > > > > /*----------------------------------------------------------------------------- > > - * Function: PHY_MACConfig8192C > > - * > > - * Overview: Condig MAC by header file or parameter file. > > - * > > - * Input: NONE > > - * > > - * Output: NONE > > - * > > - * Return: NONE > > + * PHY_MACConfig8192C - Condig MAC by header file or parameter file. > > * > > * Revised History: > > * When Who Remark > > @@ -369,17 +343,12 @@ s32 PHY_MACConfig8723B(struct adapter *Adapter) > > } > > > > /** > > -* Function: phy_InitBBRFRegisterDefinition > > -* > > -* OverView: Initialize Register definition offset for Radio Path A/B/C/D > > -* > > -* Input: > > -* struct adapter * Adapter, > > -* > > -* Output: None > > -* Return: None > > -* Note: The initialization value is constant and it should never be changes > > -*/ > > + * phy_InitBBRFRegisterDefinition - Initialize Register definition offset for > > + * Radio Path A/B/C/D > > + * @Adapter: > > + * > > + * .. Note:: The initialization value is constant and it should never be changes > > + */ > > static void phy_InitBBRFRegisterDefinition(struct adapter *Adapter) > > { > > struct hal_com_data *pHalData = GET_HAL_DATA(Adapter); > > @@ -675,6 +644,7 @@ static void phy_SetRegBW_8723B( > > ) > > { > > u16 RegRfMod_BW, u2tmp = 0; > > + > > > This is not related to comments. Do it in a separate patch. > > > RegRfMod_BW = rtw_read16(Adapter, REG_TRXPTCL_CTL_8723B); > > > > switch (CurrentBW) { > > @@ -789,7 +759,7 @@ static void phy_PostSetBwMode8723B(struct adapter *Adapter) > > > > PHY_SetBBReg(Adapter, rFPGA1_RFMOD, bRFMOD, 0x0); > > > > -/* PHY_SetBBReg(Adapter, rFPGA0_AnalogParameter2, BIT10, 1); */ > > + /*PHY_SetBBReg(Adapter, rFPGA0_AnalogParameter2, BIT10, 1); */ > > This format is wrong. Anyway, just delete the commented out code. > > regards, > dan carpenter > how can i delete that, i have no idea what this driver does i'm just fixing coding style issues for eudyptula challenge. i dont think its a good idea to delete the code without knowing its purpose even though its commented out