Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2139168pxb; Thu, 11 Feb 2021 05:31:22 -0800 (PST) X-Google-Smtp-Source: ABdhPJzF9fLVFOlYSywC6T/ReYiSK2we3WuDJgPClMUP3zxDJWF5O0k4dW4z/He/N4alGcz0cn50 X-Received: by 2002:a17:907:2897:: with SMTP id em23mr8597097ejc.550.1613050282191; Thu, 11 Feb 2021 05:31:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613050282; cv=none; d=google.com; s=arc-20160816; b=OkFsI5ig920ZrAOXI/d+sfwHWv0urpsse5fZgJafaEeH7wDn5+stX/9Kye+XHF1fTQ b4kiVhOXIffJfG5z5jBQblk7TsYUEzoA/K+8sVA9cZ8uMha7cfw2pXJpskYqr3El9ylc FbVATM1d+yXQwAmg2I7HedAvJTZF/mYB9Z1eBZ3m807auuUenGMFKV88EApT+201StNE /tlKmC9gGc174b8vMOBDdMCZhqW5NjUpRpYt45pJ+IQ0ALUxqaBmJU7y1mRVoI97Tvcg JUXjs9khhwkTe9BH+ipj1u1O5GADzpU1cQ8ApYyIHr8XQE0UMmuFEr+BTvBEPqivxGI8 7I5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=mHguUTQ+HpUwQwSGrjw+UqtJ71Oy5W4N5x1Fw8xX/pY=; b=tRCZ6xXgSDM4TSX31YsSef3iJryKUbhPvSU4ixPbIm6Yi67uG63y0bcoKTIyKS9z+k ykkUNT9uNXby6vhz9HsHj1zbWCh3x0MxDUfvFW8ztePjVJ4JGFQJ70MplxIx7VqwD3I6 9ti6eN6KTYj8RliF+YpApHfLu4l6lmibwttfVlA5L0RQIOsKFHTaBC3lbxCQm+LYUf30 lODqOap0HSSeGFrtiwYIPRu+QYLHK3lVtKDpjWLk9seWhkoqZX8oOJ6ywrkH4ic2ZPnQ x5O7Zgmc7g3oMHqDQqyGnGmhccP4/LaLmpBaiUVnO2ddZTBXmuXrFU8jXvSu+G+gadjk Rd3Q== 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 a1si3792243edj.524.2021.02.11.05.30.56; Thu, 11 Feb 2021 05:31:22 -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 S231909AbhBKN2i (ORCPT + 99 others); Thu, 11 Feb 2021 08:28:38 -0500 Received: from mail-pg1-f170.google.com ([209.85.215.170]:44998 "EHLO mail-pg1-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231769AbhBKNGd (ORCPT ); Thu, 11 Feb 2021 08:06:33 -0500 Received: by mail-pg1-f170.google.com with SMTP id j5so3806098pgb.11 for ; Thu, 11 Feb 2021 05:06:13 -0800 (PST) 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:references :mime-version:content-disposition:in-reply-to; bh=mHguUTQ+HpUwQwSGrjw+UqtJ71Oy5W4N5x1Fw8xX/pY=; b=YrwzQII4r9OgkwbnpikTbdlb0QGgH19sLpAp0AiqP19hN3a5LloPdfEgOotUCVvBV/ I/eRJ38AFXFaYE3zmyu4kucTcFW2f+8zm/zdJd+RwnoUGqlZVV+rt6GD4NJXZkcmEfDc yoRlCo5hlgbhFUXux3O983paL75yTyehA/h58jNWUAjbDdlFEhDinflVszPERzx+xWcf 53aUowk9G9NRBocoLSHgAU7w2JVk/qFcXEELo3zHqITujtcjMalbwuN6ksFkhqw4gcGi 357shvbmUzLS/TiNQIHIPSsGZBZeGJrsDBsMELABHh1L+a2b4wktVeDL4SlZKVTCL1pt LFIg== X-Gm-Message-State: AOAM5336j6JbYFEoPdZWxv09qXqgBuOEzCK0IsRx7J2OMrX4tAsKFiAx +AT/PQjypzOWXF1qBDfdICE= X-Received: by 2002:a05:6a00:1a03:b029:1d3:1fa3:4a5d with SMTP id g3-20020a056a001a03b02901d31fa34a5dmr7787278pfv.1.1613048747751; Thu, 11 Feb 2021 05:05:47 -0800 (PST) Received: from karthik-strix-linux.karthek.com ([192.140.155.38]) by smtp.gmail.com with ESMTPSA id y8sm6364808pfe.36.2021.02.11.05.05.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 Feb 2021 05:05:46 -0800 (PST) Date: Thu, 11 Feb 2021 18:35:42 +0530 From: karthik alapati To: Greg Kroah-Hartman , Stephen Rothwell Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: [PATCH v4 1/2] staging: rtl8723bs: fix function comments to follow kernel-doc Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org there are some good function comments not following kernel-doc. Make them follow kernel-doc style Signed-off-by: karthik alapati --- .../staging/rtl8723bs/hal/rtl8723b_phycfg.c | 185 +++++++----------- 1 file changed, 73 insertions(+), 112 deletions(-) diff --git a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c index cf23414d7..77132e4ee 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; @@ -75,22 +68,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, @@ -184,27 +172,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 +207,7 @@ static u32 phy_RFSerialRead_8723B( * * * -*/ + */ static void phy_RFSerialWrite_8723B( struct adapter *Adapter, enum RF_PATH eRFPath, @@ -261,21 +243,18 @@ static void phy_RFSerialWrite_8723B( /** -* 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 +275,18 @@ 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. + */ void PHY_SetRFReg_8723B( struct adapter *Adapter, u8 eRFPath, @@ -344,15 +318,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 +335,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); -- 2.30.0