* [PATCH 0/1] drivers/staging/rtl8192u: adjust block comments @ 2019-06-20 9:45 Christian Müller 2019-06-20 9:45 ` [PATCH 1/1] drivers/staging/rtl8129u: " Christian Müller 0 siblings, 1 reply; 12+ messages in thread From: Christian Müller @ 2019-06-20 9:45 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, felix.trommer, Christian Müller Since our last attempt of a few enormous commits, we ditched our changes and started over again, this time with a lot smaller changes per patch adressing one small thing at a time. Sorry for the inconvenience last time! Christian Müller (1): drivers/staging/rtl8129u: adjust block comments drivers/staging/rtl8192u/r819xU_phy.c | 39 ++++++++++++++++++--------- 1 file changed, 26 insertions(+), 13 deletions(-) -- 2.17.1 ^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH 1/1] drivers/staging/rtl8129u: adjust block comments 2019-06-20 9:45 [PATCH 0/1] drivers/staging/rtl8192u: adjust block comments Christian Müller @ 2019-06-20 9:45 ` Christian Müller 2019-06-20 11:33 ` Greg KH 0 siblings, 1 reply; 12+ messages in thread From: Christian Müller @ 2019-06-20 9:45 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, felix.trommer, Christian Müller As stated in coding-styles.rst multiline comments should be structured in a way, that the actual comment starts on the second line of the commented portion. E.g: /* * Multiline comments * should look like * this. */ The comments in this file were of a format, that looked like this: /* Multiline comments previous * to this patch * looked like this. */ There is an exception to files in /net and drivers/net, where multiline comments are preferred to look like the second example above, but since this file resides in a different directory, this patch changes the style to match the preferred style. Signed-off-by: Christian Müller <muellerch-privat@web.de> Signed-off-by: Felix Trommer <felix.trommer@hotmail.de> --- drivers/staging/rtl8192u/r819xU_phy.c | 39 ++++++++++++++++++--------- 1 file changed, 26 insertions(+), 13 deletions(-) diff --git a/drivers/staging/rtl8192u/r819xU_phy.c b/drivers/staging/rtl8192u/r819xU_phy.c index 5f04afe53d69..a51ed10be431 100644 --- a/drivers/staging/rtl8192u/r819xU_phy.c +++ b/drivers/staging/rtl8192u/r819xU_phy.c @@ -363,7 +363,8 @@ static u32 phy_FwRFSerialRead(struct net_device *dev, u8 time = 0; u32 tmp; - /* Firmware RF Write control. + /* + * Firmware RF Write control. * We can not execute the scheme in the initial step. * Otherwise, RF-R/W will waste much time. * This is only for site survey. @@ -379,7 +380,8 @@ static u32 phy_FwRFSerialRead(struct net_device *dev, /* 6. We can not execute read operation if bit 31 is 1. */ read_nic_dword(dev, QPNR, &tmp); while (tmp & 0x80000000) { - /* If FW can not finish RF-R/W for more than ?? times. + /* + * If FW can not finish RF-R/W for more than ?? times. * We must reset FW. */ if (time++ < 100) { @@ -394,7 +396,8 @@ static u32 phy_FwRFSerialRead(struct net_device *dev, /* 8. Check if firmware send back RF content. */ read_nic_dword(dev, QPNR, &tmp); while (tmp & 0x80000000) { - /* If FW can not finish RF-R/W for more than ?? times. + /* + * If FW can not finish RF-R/W for more than ?? times. * We must reset FW. */ if (time++ < 100) { @@ -426,7 +429,8 @@ static void phy_FwRFSerialWrite(struct net_device *dev, u8 time = 0; u32 tmp; - /* Firmware RF Write control. + /* + * Firmware RF Write control. * We can not execute the scheme in the initial step. * Otherwise, RF-R/W will waste much time. * This is only for site survey. @@ -445,7 +449,8 @@ static void phy_FwRFSerialWrite(struct net_device *dev, /* 6. Write operation. We can not write if bit 31 is 1. */ read_nic_dword(dev, QPNR, &tmp); while (tmp & 0x80000000) { - /* If FW can not finish RF-R/W for more than ?? times. + /* + * If FW can not finish RF-R/W for more than ?? times. * We must reset FW. */ if (time++ < 100) { @@ -455,11 +460,13 @@ static void phy_FwRFSerialWrite(struct net_device *dev, break; } } - /* 7. No matter check bit. We always force the write. + /* + * 7. No matter check bit. We always force the write. * Because FW will not accept the command. */ write_nic_dword(dev, QPNR, data); - /* According to test, we must delay 20us to wait firmware + /* + * According to test, we must delay 20us to wait firmware * to finish RF write operation. */ /* We support delay in firmware side now. */ @@ -828,7 +835,8 @@ static void rtl8192_BB_Config_ParaFile(struct net_device *dev) reg_u32); } - /* Check if the CCK HighPower is turned ON. + /* + * Check if the CCK HighPower is turned ON. * This is used to calculate PWDB. */ priv->bCckHighPower = (u8)rtl8192_QueryBBReg(dev, @@ -847,7 +855,8 @@ static void rtl8192_BB_Config_ParaFile(struct net_device *dev) void rtl8192_BBConfig(struct net_device *dev) { rtl8192_InitBBRFRegDef(dev); - /* config BB&RF. As hardCode based initialization has not been well + /* + * config BB&RF. As hardCode based initialization has not been well * implemented, so use file first. * FIXME: should implement it for hardcode? */ @@ -1168,7 +1177,8 @@ bool rtl8192_SetRFPowerState(struct net_device *dev, case RF_8256: switch (pHalData->eRFPowerState) { case eRfOff: - /* If Rf off reason is from IPS, + /* + * If Rf off reason is from IPS, * LED should blink with no link */ if (pMgntInfo->RfOffReason == RF_CHANGE_BY_IPS) @@ -1179,7 +1189,8 @@ bool rtl8192_SetRFPowerState(struct net_device *dev, break; case eRfOn: - /* Turn on RF we are still linked, which might + /* + * Turn on RF we are still linked, which might * happen when we quickly turn off and on HW RF. */ if (pMgntInfo->bMediaConnect) @@ -1274,7 +1285,8 @@ static u8 rtl8192_phy_SwChnlStepByStep(struct net_device *dev, u8 channel, __func__, *stage, *step, channel); if (!is_legal_channel(priv->ieee80211, channel)) { RT_TRACE(COMP_ERR, "set to illegal channel: %d\n", channel); - /* return true to tell upper caller function this channel + /* + * return true to tell upper caller function this channel * setting is finished! Or it will in while loop. */ return true; @@ -1621,7 +1633,8 @@ void rtl8192_SetBWModeWorkItem(struct net_device *dev) break; } - /* Skip over setting of J-mode in BB register here. + /* + * Skip over setting of J-mode in BB register here. * Default value is "None J mode". */ -- 2.17.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: [PATCH 1/1] drivers/staging/rtl8129u: adjust block comments 2019-06-20 9:45 ` [PATCH 1/1] drivers/staging/rtl8129u: " Christian Müller @ 2019-06-20 11:33 ` Greg KH 2019-06-24 9:46 ` [PATCH 0/2] drivers/staging/rtl8192u: " Christian Müller 0 siblings, 1 reply; 12+ messages in thread From: Greg KH @ 2019-06-20 11:33 UTC (permalink / raw) To: Christian Müller Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, felix.trommer On Thu, Jun 20, 2019 at 11:45:34AM +0200, Christian Müller wrote: > As stated in coding-styles.rst multiline comments should be structured in a way, > that the actual comment starts on the second line of the commented portion. E.g: > > /* > * Multiline comments > * should look like > * this. > */ > > The comments in this file were of a format, that looked like this: > > /* Multiline comments previous > * to this patch > * looked like this. > */ > > There is an exception to files in /net and drivers/net, > where multiline comments are preferred to look like the second example above, > but since this file resides in a different directory, > this patch changes the style to match the preferred style. Ah. Hm. Turns out this is a networking driver, and some day, the goal would be for it to live under drivers/net/ If it were to move there, then these comments would be in the correct format already. So this patch isn't needed, sorry. greg k-h ^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH 0/2] drivers/staging/rtl8192u: adjust block comments 2019-06-20 11:33 ` Greg KH @ 2019-06-24 9:46 ` Christian Müller 2019-06-24 9:46 ` [PATCH 1/2] " Christian Müller 2019-06-24 9:46 ` [PATCH 2/2] drivers/staging/rtl8192u: adjust block comments Christian Müller 0 siblings, 2 replies; 12+ messages in thread From: Christian Müller @ 2019-06-24 9:46 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, felix.trommer, Christian Müller As per the last correspondence with Greg, he pointed out that the whole driver rtl8192u should be merged some day into drivers/net/ and thus implement different standards regarding multiline comments. Because of that, we did the exact opposite of what we did the last time, and changed comments such that they obey these standards. All multiline-comments in this file now look like the following example: /* Multiline comments * in r8192U_dm.c * now look like this. */ Christian Müller (2): drivers/staging/rtl8192u: adjust block comments drivers/staging/rtl8192u: adjust block comments drivers/staging/rtl8192u/r8192U_dm.c | 97 +++++++++++----------------- 1 file changed, 39 insertions(+), 58 deletions(-) -- 2.17.1 ^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH 1/2] drivers/staging/rtl8192u: adjust block comments 2019-06-24 9:46 ` [PATCH 0/2] drivers/staging/rtl8192u: " Christian Müller @ 2019-06-24 9:46 ` Christian Müller 2019-06-26 1:53 ` Greg KH 2019-06-24 9:46 ` [PATCH 2/2] drivers/staging/rtl8192u: adjust block comments Christian Müller 1 sibling, 1 reply; 12+ messages in thread From: Christian Müller @ 2019-06-24 9:46 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, felix.trommer, Christian Müller As stated in coding-styles.rst multiline comments should be structured in a way, that the actual comment starts on the second line of the commented portion. E.g: /* * Multiline comments * should look like * this. */ However, there is an exception to files in drivers/net/ and net/, where multiline comments are prefered to look like this: /* Mutliline comments for * drivers/net/ should look * like this. */ The comments in this file initially looked like the first example. But since this file is part of a networking driver and thus should be moved to drivers/net/ one day, this patch adjusts the comments such that they are fitting to the style imposed for drivers/net/. Signed-off-by: Christian Müller <muellerch-privat@web.de> Signed-off-by: Felix Trommer <felix.trommer@hotmail.de> --- drivers/staging/rtl8192u/r8192U_dm.c | 69 ++++++++++------------------ 1 file changed, 23 insertions(+), 46 deletions(-) diff --git a/drivers/staging/rtl8192u/r8192U_dm.c b/drivers/staging/rtl8192u/r8192U_dm.c index 2ba01041406b..86215fee8f0b 100644 --- a/drivers/staging/rtl8192u/r8192U_dm.c +++ b/drivers/staging/rtl8192u/r8192U_dm.c @@ -99,8 +99,7 @@ static void dm_dynamic_txpower(struct net_device *dev); static void dm_send_rssi_tofw(struct net_device *dev); static void dm_ctstoself(struct net_device *dev); /*---------------------------Define function prototype------------------------*/ -/* - * ================================================================================ +/* ================================================================================ * HW Dynamic mechanism interface. * ================================================================================ * @@ -178,8 +177,7 @@ void dm_CheckRxAggregation(struct net_device *dev) ulValue = (pHTInfo->UsbRxFwAggrEn<<24) | (pHTInfo->UsbRxFwAggrPageNum<<16) | (pHTInfo->UsbRxFwAggrPacketNum<<8) | (pHTInfo->UsbRxFwAggrTimeout); - /* - * If usb rx firmware aggregation is enabled, + /* If usb rx firmware aggregation is enabled, * when anyone of three threshold conditions above is reached, * firmware will send aggregated packet to driver. */ @@ -219,8 +217,7 @@ void hal_dm_watchdog(struct net_device *dev) #endif } /* HalDmWatchDog */ -/* - * Decide Rate Adaptive Set according to distance (signal strength) +/* Decide Rate Adaptive Set according to distance (signal strength) * 01/11/2008 MHC Modify input arguments and RATR table level. * 01/16/2008 MHC RF_Type is assigned in ReadAdapterInfo(). We must call * the function after making sure RF_Type. @@ -246,8 +243,7 @@ void init_rate_adaptive(struct net_device *dev) pra->ping_rssi_thresh_for_ra = 15; if (priv->rf_type == RF_2T4R) { - /* - * 07/10/08 MH Modify for RA smooth scheme. + /* 07/10/08 MH Modify for RA smooth scheme. * 2008/01/11 MH Modify 2T RATR table for different RSSI. 080515 porting by amy from windows code. */ pra->upper_rssi_threshold_ratr = 0x8f0f0000; @@ -387,8 +383,7 @@ static void dm_check_rate_adaptive(struct net_device *dev) } } - /* - * 2008.04.01 + /* 2008.04.01 * For RTL819X, if pairwisekey = wep/tkip, we support only MCS0~7. */ if (priv->ieee80211->GetHalfNmodeSupportByAPsHandler(dev)) @@ -683,8 +678,7 @@ static void dm_TXPowerTrackingCallback_ThermalMeter(struct net_device *dev) return; } - /* - * ========================== + /* ========================== * this is only for test, should be masked * ========================== */ @@ -850,8 +844,7 @@ static void dm_InitializeTXPowerTracking_TSSI(struct net_device *dev) priv->txbbgain_table[36].txbb_iq_amplifygain = -24; priv->txbbgain_table[36].txbbgain_value = 0x10000040; - /* - * ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 + /* ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 * This Table is for CH1~CH13 */ priv->cck_txbbgain_table[0].ccktxbb_valuearray[0] = 0x36; @@ -1061,8 +1054,7 @@ static void dm_InitializeTXPowerTracking_TSSI(struct net_device *dev) priv->cck_txbbgain_table[22].ccktxbb_valuearray[6] = 0x03; priv->cck_txbbgain_table[22].ccktxbb_valuearray[7] = 0x01; - /* - * ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 + /* ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 * This Table is for CH14 */ priv->cck_txbbgain_ch14_table[0].ccktxbb_valuearray[0] = 0x36; @@ -1282,8 +1274,7 @@ static void dm_InitializeTXPowerTracking_ThermalMeter(struct net_device *dev) { struct r8192_priv *priv = ieee80211_priv(dev); - /* - * Tx Power tracking by Thermal Meter requires Firmware R/W 3-wire. This mechanism + /* Tx Power tracking by Thermal Meter requires Firmware R/W 3-wire. This mechanism * can be enabled only when Firmware R/W 3-wire is enabled. Otherwise, frequent r/w * 3-wire by driver causes RF to go into a wrong state. */ @@ -1330,8 +1321,7 @@ static void dm_CheckTXPowerTracking_ThermalMeter(struct net_device *dev) } if (!TM_Trigger) { - /* - * Attention!! You have to write all 12bits of data to RF, or it may cause RF to crash + /* Attention!! You have to write all 12bits of data to RF, or it may cause RF to crash * actually write reg0x02 bit1=0, then bit1=1. * DbgPrint("Trigger ThermalMeter, write RF reg0x2 = 0x4d to 0x4f\n"); */ @@ -1773,8 +1763,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 1.3 Lower PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x00); @@ -1814,8 +1803,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( dm_digtable.dig_state = DM_STA_DIG_ON; /*DbgPrint("DIG ON\n\r");*/ - /* - * 2.1 Set initial gain. + /* 2.1 Set initial gain. * 2008/02/26 MH SD3-Jerry suggest to prevent dirty environment. */ if (reset_flag == 1) { @@ -1832,8 +1820,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 2.2 Higher PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x20); @@ -1850,8 +1837,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 2.3 Higher CS ratio for CCK. */ write_nic_byte(dev, 0xa0a, 0xcd); - /* - * 2.4 Lower EDCCA. + /* 2.4 Lower EDCCA. * 2008/01/11 MH 90/92 series are the same. */ /*PlatformEFIOWrite4Byte(pAdapter, rOFDM0_ECCAThreshold, 0x346);*/ @@ -1892,8 +1878,7 @@ static void dm_ctrl_initgain_byrssi_highpwr( (priv->undecorated_smoothed_pwdb < dm_digtable.rssi_high_power_highthresh)) return; - /* - * 3. When RSSI >75% or <70%, it is a high power issue. We have to judge if + /* 3. When RSSI >75% or <70%, it is a high power issue. We have to judge if * it is larger than a threshold and then execute the step below. * * 2008/02/05 MH SD3-Jerry Modify PD_TH for high power issue. @@ -2042,8 +2027,7 @@ static void dm_pd_th( if (dm_digtable.curpd_thstate == DIG_PD_AT_LOW_POWER) { /* Lower PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x00); @@ -2055,8 +2039,7 @@ static void dm_pd_th( } else if (dm_digtable.curpd_thstate == DIG_PD_AT_NORMAL_POWER) { /* Higher PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x20); @@ -2155,8 +2138,7 @@ static void dm_check_edca_turbo( unsigned long curTxOkCnt = 0; unsigned long curRxOkCnt = 0; - /* - * Do not be Turbo if it's under WiFi config and Qos Enabled, because the EDCA parameters + /* Do not be Turbo if it's under WiFi config and Qos Enabled, because the EDCA parameters * should follow the settings from QAP. By Bruce, 2007-12-07. */ if (priv->ieee80211->state != IEEE80211_LINKED) @@ -2188,8 +2170,7 @@ static void dm_check_edca_turbo( priv->bcurrent_turbo_EDCA = true; } else { - /* - * Turn Off EDCA turbo here. + /* Turn Off EDCA turbo here. * Restore original EDCA according to the declaration of AP. */ if (priv->bcurrent_turbo_EDCA) { @@ -2219,8 +2200,7 @@ static void dm_check_edca_turbo( write_nic_dword(dev, EDCAPARA_BE, u4bAcParam); - /* - * Check ACM bit. + /* Check ACM bit. * If it is set, immediately set ACM control bit to downgrading AC for passing WMM testplan. Annie, 2005-12-13. */ { @@ -2319,8 +2299,7 @@ static void dm_check_pbc_gpio(struct net_device *dev) return; if (tmp1byte & BIT(6) || tmp1byte & BIT(0)) { - /* - * Here we only set bPbcPressed to TRUE + /* Here we only set bPbcPressed to TRUE * After trigger PBC, the variable will be set to FALSE */ RT_TRACE(COMP_IO, "CheckPbcGPIO - PBC is pressed\n"); @@ -2529,8 +2508,7 @@ static void dm_rxpath_sel_byrssi(struct net_device *dev) } } - /* - * Set CCK Rx path + /* Set CCK Rx path * reg0xA07[3:2]=cck default rx path, reg0xa07[1:0]=cck optional rx path. */ update_cck_rx_path = 0; @@ -3049,8 +3027,7 @@ static void dm_send_rssi_tofw(struct net_device *dev) { struct r8192_priv *priv = ieee80211_priv(dev); - /* - * If we test chariot, we should stop the TX command ? + /* If we test chariot, we should stop the TX command ? * Because 92E will always silent reset when we send tx command. We use register * 0x1e0(byte) to notify driver. */ -- 2.17.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] drivers/staging/rtl8192u: adjust block comments 2019-06-24 9:46 ` [PATCH 1/2] " Christian Müller @ 2019-06-26 1:53 ` Greg KH 2019-06-27 8:33 ` [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line Christian Müller 0 siblings, 1 reply; 12+ messages in thread From: Greg KH @ 2019-06-26 1:53 UTC (permalink / raw) To: Christian Müller Cc: devel, felix.trommer, linux-kernel, linux-kernel, johnfwhitmore On Mon, Jun 24, 2019 at 11:46:39AM +0200, Christian Müller wrote: > As stated in coding-styles.rst multiline comments should be structured in a way, > that the actual comment starts on the second line of the commented portion. E.g: <snip> You sent 2 patches that did different things, yet have the identical subject line :( Please fix up and resend the series. thanks, greg k-h ^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line 2019-06-26 1:53 ` Greg KH @ 2019-06-27 8:33 ` Christian Müller 2019-06-27 8:33 ` [PATCH v2 2/2] drivers/staging/rtl8192u: style nonstyled comments Christian Müller 2019-06-27 16:45 ` [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line Greg KH 0 siblings, 2 replies; 12+ messages in thread From: Christian Müller @ 2019-06-27 8:33 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, Christian Müller, Felix Trommer As stated in coding-styles.rst multiline comments should be structured in a way, that the actual comment starts on the second line of the commented portion. E.g: /* * Multiline comments * should look like * this. */ However, there is an exception to files in drivers/net/ and net/, where multiline comments are prefered to look like this: /* Mutliline comments for * drivers/net/ should look * like this. */ The comments in this file initially looked like the first example. But since this file is part of a networking driver and thus should be moved to drivers/net/ one day, this patch adjusts the comments such that they are fitting to the style imposed for drivers/net/. Signed-off-by: Christian Müller <muellerch-privat@web.de> Signed-off-by: Felix Trommer <felix.trommer@hotmail.de> --- drivers/staging/rtl8192u/r8192U_dm.c | 69 ++++++++++------------------ 1 file changed, 23 insertions(+), 46 deletions(-) diff --git a/drivers/staging/rtl8192u/r8192U_dm.c b/drivers/staging/rtl8192u/r8192U_dm.c index 2ba01041406b..86215fee8f0b 100644 --- a/drivers/staging/rtl8192u/r8192U_dm.c +++ b/drivers/staging/rtl8192u/r8192U_dm.c @@ -99,8 +99,7 @@ static void dm_dynamic_txpower(struct net_device *dev); static void dm_send_rssi_tofw(struct net_device *dev); static void dm_ctstoself(struct net_device *dev); /*---------------------------Define function prototype------------------------*/ -/* - * ================================================================================ +/* ================================================================================ * HW Dynamic mechanism interface. * ================================================================================ * @@ -178,8 +177,7 @@ void dm_CheckRxAggregation(struct net_device *dev) ulValue = (pHTInfo->UsbRxFwAggrEn<<24) | (pHTInfo->UsbRxFwAggrPageNum<<16) | (pHTInfo->UsbRxFwAggrPacketNum<<8) | (pHTInfo->UsbRxFwAggrTimeout); - /* - * If usb rx firmware aggregation is enabled, + /* If usb rx firmware aggregation is enabled, * when anyone of three threshold conditions above is reached, * firmware will send aggregated packet to driver. */ @@ -219,8 +217,7 @@ void hal_dm_watchdog(struct net_device *dev) #endif } /* HalDmWatchDog */ -/* - * Decide Rate Adaptive Set according to distance (signal strength) +/* Decide Rate Adaptive Set according to distance (signal strength) * 01/11/2008 MHC Modify input arguments and RATR table level. * 01/16/2008 MHC RF_Type is assigned in ReadAdapterInfo(). We must call * the function after making sure RF_Type. @@ -246,8 +243,7 @@ void init_rate_adaptive(struct net_device *dev) pra->ping_rssi_thresh_for_ra = 15; if (priv->rf_type == RF_2T4R) { - /* - * 07/10/08 MH Modify for RA smooth scheme. + /* 07/10/08 MH Modify for RA smooth scheme. * 2008/01/11 MH Modify 2T RATR table for different RSSI. 080515 porting by amy from windows code. */ pra->upper_rssi_threshold_ratr = 0x8f0f0000; @@ -387,8 +383,7 @@ static void dm_check_rate_adaptive(struct net_device *dev) } } - /* - * 2008.04.01 + /* 2008.04.01 * For RTL819X, if pairwisekey = wep/tkip, we support only MCS0~7. */ if (priv->ieee80211->GetHalfNmodeSupportByAPsHandler(dev)) @@ -683,8 +678,7 @@ static void dm_TXPowerTrackingCallback_ThermalMeter(struct net_device *dev) return; } - /* - * ========================== + /* ========================== * this is only for test, should be masked * ========================== */ @@ -850,8 +844,7 @@ static void dm_InitializeTXPowerTracking_TSSI(struct net_device *dev) priv->txbbgain_table[36].txbb_iq_amplifygain = -24; priv->txbbgain_table[36].txbbgain_value = 0x10000040; - /* - * ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 + /* ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 * This Table is for CH1~CH13 */ priv->cck_txbbgain_table[0].ccktxbb_valuearray[0] = 0x36; @@ -1061,8 +1054,7 @@ static void dm_InitializeTXPowerTracking_TSSI(struct net_device *dev) priv->cck_txbbgain_table[22].ccktxbb_valuearray[6] = 0x03; priv->cck_txbbgain_table[22].ccktxbb_valuearray[7] = 0x01; - /* - * ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 + /* ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 * This Table is for CH14 */ priv->cck_txbbgain_ch14_table[0].ccktxbb_valuearray[0] = 0x36; @@ -1282,8 +1274,7 @@ static void dm_InitializeTXPowerTracking_ThermalMeter(struct net_device *dev) { struct r8192_priv *priv = ieee80211_priv(dev); - /* - * Tx Power tracking by Thermal Meter requires Firmware R/W 3-wire. This mechanism + /* Tx Power tracking by Thermal Meter requires Firmware R/W 3-wire. This mechanism * can be enabled only when Firmware R/W 3-wire is enabled. Otherwise, frequent r/w * 3-wire by driver causes RF to go into a wrong state. */ @@ -1330,8 +1321,7 @@ static void dm_CheckTXPowerTracking_ThermalMeter(struct net_device *dev) } if (!TM_Trigger) { - /* - * Attention!! You have to write all 12bits of data to RF, or it may cause RF to crash + /* Attention!! You have to write all 12bits of data to RF, or it may cause RF to crash * actually write reg0x02 bit1=0, then bit1=1. * DbgPrint("Trigger ThermalMeter, write RF reg0x2 = 0x4d to 0x4f\n"); */ @@ -1773,8 +1763,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 1.3 Lower PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x00); @@ -1814,8 +1803,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( dm_digtable.dig_state = DM_STA_DIG_ON; /*DbgPrint("DIG ON\n\r");*/ - /* - * 2.1 Set initial gain. + /* 2.1 Set initial gain. * 2008/02/26 MH SD3-Jerry suggest to prevent dirty environment. */ if (reset_flag == 1) { @@ -1832,8 +1820,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 2.2 Higher PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x20); @@ -1850,8 +1837,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 2.3 Higher CS ratio for CCK. */ write_nic_byte(dev, 0xa0a, 0xcd); - /* - * 2.4 Lower EDCCA. + /* 2.4 Lower EDCCA. * 2008/01/11 MH 90/92 series are the same. */ /*PlatformEFIOWrite4Byte(pAdapter, rOFDM0_ECCAThreshold, 0x346);*/ @@ -1892,8 +1878,7 @@ static void dm_ctrl_initgain_byrssi_highpwr( (priv->undecorated_smoothed_pwdb < dm_digtable.rssi_high_power_highthresh)) return; - /* - * 3. When RSSI >75% or <70%, it is a high power issue. We have to judge if + /* 3. When RSSI >75% or <70%, it is a high power issue. We have to judge if * it is larger than a threshold and then execute the step below. * * 2008/02/05 MH SD3-Jerry Modify PD_TH for high power issue. @@ -2042,8 +2027,7 @@ static void dm_pd_th( if (dm_digtable.curpd_thstate == DIG_PD_AT_LOW_POWER) { /* Lower PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x00); @@ -2055,8 +2039,7 @@ static void dm_pd_th( } else if (dm_digtable.curpd_thstate == DIG_PD_AT_NORMAL_POWER) { /* Higher PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x20); @@ -2155,8 +2138,7 @@ static void dm_check_edca_turbo( unsigned long curTxOkCnt = 0; unsigned long curRxOkCnt = 0; - /* - * Do not be Turbo if it's under WiFi config and Qos Enabled, because the EDCA parameters + /* Do not be Turbo if it's under WiFi config and Qos Enabled, because the EDCA parameters * should follow the settings from QAP. By Bruce, 2007-12-07. */ if (priv->ieee80211->state != IEEE80211_LINKED) @@ -2188,8 +2170,7 @@ static void dm_check_edca_turbo( priv->bcurrent_turbo_EDCA = true; } else { - /* - * Turn Off EDCA turbo here. + /* Turn Off EDCA turbo here. * Restore original EDCA according to the declaration of AP. */ if (priv->bcurrent_turbo_EDCA) { @@ -2219,8 +2200,7 @@ static void dm_check_edca_turbo( write_nic_dword(dev, EDCAPARA_BE, u4bAcParam); - /* - * Check ACM bit. + /* Check ACM bit. * If it is set, immediately set ACM control bit to downgrading AC for passing WMM testplan. Annie, 2005-12-13. */ { @@ -2319,8 +2299,7 @@ static void dm_check_pbc_gpio(struct net_device *dev) return; if (tmp1byte & BIT(6) || tmp1byte & BIT(0)) { - /* - * Here we only set bPbcPressed to TRUE + /* Here we only set bPbcPressed to TRUE * After trigger PBC, the variable will be set to FALSE */ RT_TRACE(COMP_IO, "CheckPbcGPIO - PBC is pressed\n"); @@ -2529,8 +2508,7 @@ static void dm_rxpath_sel_byrssi(struct net_device *dev) } } - /* - * Set CCK Rx path + /* Set CCK Rx path * reg0xA07[3:2]=cck default rx path, reg0xa07[1:0]=cck optional rx path. */ update_cck_rx_path = 0; @@ -3049,8 +3027,7 @@ static void dm_send_rssi_tofw(struct net_device *dev) { struct r8192_priv *priv = ieee80211_priv(dev); - /* - * If we test chariot, we should stop the TX command ? + /* If we test chariot, we should stop the TX command ? * Because 92E will always silent reset when we send tx command. We use register * 0x1e0(byte) to notify driver. */ -- 2.17.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH v2 2/2] drivers/staging/rtl8192u: style nonstyled comments 2019-06-27 8:33 ` [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line Christian Müller @ 2019-06-27 8:33 ` Christian Müller 2019-06-27 16:45 ` [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line Greg KH 1 sibling, 0 replies; 12+ messages in thread From: Christian Müller @ 2019-06-27 8:33 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, Christian Müller, Felix Trommer The coding-styles.rst states, that multiline comments should allways contain a leading "*" in each line. For multiline comments in general they /* * should look * like this. */ For multiline comments in either net/ or drivers/net/ however, they should /* omit * the first * empty line. */ Since this file is part of a networking driver, the goal for it would be to reside in drivers/net/ one day. This patch changes comments, that were in neither form of the two listed above, to have the style that is specified for drivers/net/. Signed-off-by: Christian Müller <muellerch-privat@web.de> Signed-off-by: Felix Trommer <felix.trommer@hotmail.de> --- drivers/staging/rtl8192u/r8192U_dm.c | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/drivers/staging/rtl8192u/r8192U_dm.c b/drivers/staging/rtl8192u/r8192U_dm.c index 86215fee8f0b..cb6c653e624d 100644 --- a/drivers/staging/rtl8192u/r8192U_dm.c +++ b/drivers/staging/rtl8192u/r8192U_dm.c @@ -332,9 +332,10 @@ static void dm_check_rate_adaptive(struct net_device *dev) ((bshort_gi_enabled) ? BIT(31) : 0); /* 2007/10/08 MH We support RA smooth scheme now. When it is the first - time to link with AP. We will not change upper/lower threshold. If - STA stay in high or low level, we must change two different threshold - to prevent jumping frequently. */ + * time to link with AP. We will not change upper/lower threshold. If + * STA stay in high or low level, we must change two different threshold + * to prevent jumping frequently. + */ if (pra->ratr_state == DM_RATR_STA_HIGH) { HighRSSIThreshForRA = pra->high2low_rssi_thresh_for_ra; LowRSSIThreshForRA = (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) ? @@ -1738,10 +1739,12 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( pHalData->UndecoratedSmoothedPWDB, DM_DigTable.RssiLowThresh, DM_DigTable.RssiHighThresh, DM_DigTable.Dig_State);*/ /* 1. When RSSI decrease, We have to judge if it is smaller than a threshold - and then execute the step below. */ + * and then execute the step below. + */ if (priv->undecorated_smoothed_pwdb <= dm_digtable.rssi_low_thresh) { /* 2008/02/05 MH When we execute silent reset, the DIG PHY parameters - will be reset to init value. We must prevent the condition. */ + * will be reset to init value. We must prevent the condition. + */ if (dm_digtable.dig_state == DM_STA_DIG_OFF && (priv->reset_count == reset_cnt)) { return; @@ -1786,7 +1789,8 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( } /* 2. When RSSI increase, We have to judge if it is larger than a threshold - and then execute the step below. */ + * and then execute the step below. + */ if (priv->undecorated_smoothed_pwdb >= dm_digtable.rssi_high_thresh) { u8 reset_flag = 0; @@ -2252,11 +2256,10 @@ static void dm_ctstoself(struct net_device *dev) pHTInfo->IOTAction &= ~HT_IOT_ACT_FORCED_CTS2SELF; return; } - /* - 1. Uplink - 2. Linksys350/Linksys300N - 3. <50 disable, >55 enable - */ + /* 1. Uplink + * 2. Linksys350/Linksys300N + * 3. <50 disable, >55 enable + */ if (pHTInfo->IOTPeer == HT_IOT_PEER_BROADCOM) { curTxOkCnt = priv->stats.txbytesunicast - lastTxOkCnt; @@ -2333,7 +2336,8 @@ void dm_rf_pathcheck_workitemcallback(struct work_struct *work) u8 rfpath = 0, i; /* 2008/01/30 MH After discussing with SD3 Jerry, 0xc04/0xd04 register will - always be the same. We only read 0xc04 now. */ + * always be the same. We only read 0xc04 now. + */ read_nic_byte(dev, 0xc04, &rfpath); /* Check Bit 0-3, it means if RF A-D is enabled. */ -- 2.17.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line 2019-06-27 8:33 ` [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line Christian Müller 2019-06-27 8:33 ` [PATCH v2 2/2] drivers/staging/rtl8192u: style nonstyled comments Christian Müller @ 2019-06-27 16:45 ` Greg KH 2019-07-01 8:27 ` [PATCH v3 " Christian Müller 1 sibling, 1 reply; 12+ messages in thread From: Greg KH @ 2019-06-27 16:45 UTC (permalink / raw) To: Christian Müller Cc: devel, Felix Trommer, linux-kernel, linux-kernel, johnfwhitmore On Thu, Jun 27, 2019 at 10:33:35AM +0200, Christian Müller wrote: > As stated in coding-styles.rst multiline comments should be structured in a way, > that the actual comment starts on the second line of the commented portion. E.g: > > /* > * Multiline comments > * should look like > * this. > */ > > However, there is an exception to files in drivers/net/ and net/, where > multiline comments are prefered to look like this: > > /* Mutliline comments for > * drivers/net/ should look > * like this. > */ > > The comments in this file initially looked like the first example. > But since this file is part of a networking driver and thus should > be moved to drivers/net/ one day, this patch adjusts the comments > such that they are fitting to the style imposed for drivers/net/. > > Signed-off-by: Christian Müller <muellerch-privat@web.de> > Signed-off-by: Felix Trommer <felix.trommer@hotmail.de> > --- > drivers/staging/rtl8192u/r8192U_dm.c | 69 ++++++++++------------------ > 1 file changed, 23 insertions(+), 46 deletions(-) What changed from v1? That always goes below the --- line. Please fix up and send v3. thanks, greg k-h ^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH v3 1/2] drivers/staging/rtl8192u: drop first comment line 2019-06-27 16:45 ` [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line Greg KH @ 2019-07-01 8:27 ` Christian Müller 2019-07-01 8:27 ` [PATCH v3 2/2] drivers/staging/rtl8192u: style nonstyled comments Christian Müller 0 siblings, 1 reply; 12+ messages in thread From: Christian Müller @ 2019-07-01 8:27 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, Christian Müller, Felix Trommer As stated in coding-styles.rst multiline comments should be structured in a way, that the actual comment starts on the second line of the commented portion. E.g: /* * Multiline comments * should look like * this. */ However, there is an exception to files in drivers/net/ and net/, where multiline comments are prefered to look like this: /* Mutliline comments for * drivers/net/ should look * like this. */ The comments in this file initially looked like the first example. But since this file is part of a networking driver and thus should be moved to drivers/net/ one day, this patch adjusts the comments such that they are fitting to the style imposed for drivers/net/. Signed-off-by: Christian Müller <muellerch-privat@web.de> Signed-off-by: Felix Trommer <felix.trommer@hotmail.de> --- v1 contains the initial patch. v2 contains the same patch, but with a different subject to better distinguish this patch from the other one in this patch series. v3 contains the same patch again, but this time with this changelog appended. drivers/staging/rtl8192u/r8192U_dm.c | 69 ++++++++++------------------ 1 file changed, 23 insertions(+), 46 deletions(-) diff --git a/drivers/staging/rtl8192u/r8192U_dm.c b/drivers/staging/rtl8192u/r8192U_dm.c index 2ba01041406b..86215fee8f0b 100644 --- a/drivers/staging/rtl8192u/r8192U_dm.c +++ b/drivers/staging/rtl8192u/r8192U_dm.c @@ -99,8 +99,7 @@ static void dm_dynamic_txpower(struct net_device *dev); static void dm_send_rssi_tofw(struct net_device *dev); static void dm_ctstoself(struct net_device *dev); /*---------------------------Define function prototype------------------------*/ -/* - * ================================================================================ +/* ================================================================================ * HW Dynamic mechanism interface. * ================================================================================ * @@ -178,8 +177,7 @@ void dm_CheckRxAggregation(struct net_device *dev) ulValue = (pHTInfo->UsbRxFwAggrEn<<24) | (pHTInfo->UsbRxFwAggrPageNum<<16) | (pHTInfo->UsbRxFwAggrPacketNum<<8) | (pHTInfo->UsbRxFwAggrTimeout); - /* - * If usb rx firmware aggregation is enabled, + /* If usb rx firmware aggregation is enabled, * when anyone of three threshold conditions above is reached, * firmware will send aggregated packet to driver. */ @@ -219,8 +217,7 @@ void hal_dm_watchdog(struct net_device *dev) #endif } /* HalDmWatchDog */ -/* - * Decide Rate Adaptive Set according to distance (signal strength) +/* Decide Rate Adaptive Set according to distance (signal strength) * 01/11/2008 MHC Modify input arguments and RATR table level. * 01/16/2008 MHC RF_Type is assigned in ReadAdapterInfo(). We must call * the function after making sure RF_Type. @@ -246,8 +243,7 @@ void init_rate_adaptive(struct net_device *dev) pra->ping_rssi_thresh_for_ra = 15; if (priv->rf_type == RF_2T4R) { - /* - * 07/10/08 MH Modify for RA smooth scheme. + /* 07/10/08 MH Modify for RA smooth scheme. * 2008/01/11 MH Modify 2T RATR table for different RSSI. 080515 porting by amy from windows code. */ pra->upper_rssi_threshold_ratr = 0x8f0f0000; @@ -387,8 +383,7 @@ static void dm_check_rate_adaptive(struct net_device *dev) } } - /* - * 2008.04.01 + /* 2008.04.01 * For RTL819X, if pairwisekey = wep/tkip, we support only MCS0~7. */ if (priv->ieee80211->GetHalfNmodeSupportByAPsHandler(dev)) @@ -683,8 +678,7 @@ static void dm_TXPowerTrackingCallback_ThermalMeter(struct net_device *dev) return; } - /* - * ========================== + /* ========================== * this is only for test, should be masked * ========================== */ @@ -850,8 +844,7 @@ static void dm_InitializeTXPowerTracking_TSSI(struct net_device *dev) priv->txbbgain_table[36].txbb_iq_amplifygain = -24; priv->txbbgain_table[36].txbbgain_value = 0x10000040; - /* - * ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 + /* ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 * This Table is for CH1~CH13 */ priv->cck_txbbgain_table[0].ccktxbb_valuearray[0] = 0x36; @@ -1061,8 +1054,7 @@ static void dm_InitializeTXPowerTracking_TSSI(struct net_device *dev) priv->cck_txbbgain_table[22].ccktxbb_valuearray[6] = 0x03; priv->cck_txbbgain_table[22].ccktxbb_valuearray[7] = 0x01; - /* - * ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 + /* ccktxbb_valuearray[0] is 0xA22 [1] is 0xA24 ...[7] is 0xA29 * This Table is for CH14 */ priv->cck_txbbgain_ch14_table[0].ccktxbb_valuearray[0] = 0x36; @@ -1282,8 +1274,7 @@ static void dm_InitializeTXPowerTracking_ThermalMeter(struct net_device *dev) { struct r8192_priv *priv = ieee80211_priv(dev); - /* - * Tx Power tracking by Thermal Meter requires Firmware R/W 3-wire. This mechanism + /* Tx Power tracking by Thermal Meter requires Firmware R/W 3-wire. This mechanism * can be enabled only when Firmware R/W 3-wire is enabled. Otherwise, frequent r/w * 3-wire by driver causes RF to go into a wrong state. */ @@ -1330,8 +1321,7 @@ static void dm_CheckTXPowerTracking_ThermalMeter(struct net_device *dev) } if (!TM_Trigger) { - /* - * Attention!! You have to write all 12bits of data to RF, or it may cause RF to crash + /* Attention!! You have to write all 12bits of data to RF, or it may cause RF to crash * actually write reg0x02 bit1=0, then bit1=1. * DbgPrint("Trigger ThermalMeter, write RF reg0x2 = 0x4d to 0x4f\n"); */ @@ -1773,8 +1763,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 1.3 Lower PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x00); @@ -1814,8 +1803,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( dm_digtable.dig_state = DM_STA_DIG_ON; /*DbgPrint("DIG ON\n\r");*/ - /* - * 2.1 Set initial gain. + /* 2.1 Set initial gain. * 2008/02/26 MH SD3-Jerry suggest to prevent dirty environment. */ if (reset_flag == 1) { @@ -1832,8 +1820,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 2.2 Higher PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x20); @@ -1850,8 +1837,7 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( /* 2.3 Higher CS ratio for CCK. */ write_nic_byte(dev, 0xa0a, 0xcd); - /* - * 2.4 Lower EDCCA. + /* 2.4 Lower EDCCA. * 2008/01/11 MH 90/92 series are the same. */ /*PlatformEFIOWrite4Byte(pAdapter, rOFDM0_ECCAThreshold, 0x346);*/ @@ -1892,8 +1878,7 @@ static void dm_ctrl_initgain_byrssi_highpwr( (priv->undecorated_smoothed_pwdb < dm_digtable.rssi_high_power_highthresh)) return; - /* - * 3. When RSSI >75% or <70%, it is a high power issue. We have to judge if + /* 3. When RSSI >75% or <70%, it is a high power issue. We have to judge if * it is larger than a threshold and then execute the step below. * * 2008/02/05 MH SD3-Jerry Modify PD_TH for high power issue. @@ -2042,8 +2027,7 @@ static void dm_pd_th( if (dm_digtable.curpd_thstate == DIG_PD_AT_LOW_POWER) { /* Lower PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x00); @@ -2055,8 +2039,7 @@ static void dm_pd_th( } else if (dm_digtable.curpd_thstate == DIG_PD_AT_NORMAL_POWER) { /* Higher PD_TH for OFDM. */ if (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) { - /* - * 2008/01/11 MH 40MHZ 90/92 register are not the same. + /* 2008/01/11 MH 40MHZ 90/92 register are not the same. * 2008/02/05 MH SD3-Jerry 92U/92E PD_TH are the same. */ write_nic_byte(dev, (rOFDM0_XATxAFE+3), 0x20); @@ -2155,8 +2138,7 @@ static void dm_check_edca_turbo( unsigned long curTxOkCnt = 0; unsigned long curRxOkCnt = 0; - /* - * Do not be Turbo if it's under WiFi config and Qos Enabled, because the EDCA parameters + /* Do not be Turbo if it's under WiFi config and Qos Enabled, because the EDCA parameters * should follow the settings from QAP. By Bruce, 2007-12-07. */ if (priv->ieee80211->state != IEEE80211_LINKED) @@ -2188,8 +2170,7 @@ static void dm_check_edca_turbo( priv->bcurrent_turbo_EDCA = true; } else { - /* - * Turn Off EDCA turbo here. + /* Turn Off EDCA turbo here. * Restore original EDCA according to the declaration of AP. */ if (priv->bcurrent_turbo_EDCA) { @@ -2219,8 +2200,7 @@ static void dm_check_edca_turbo( write_nic_dword(dev, EDCAPARA_BE, u4bAcParam); - /* - * Check ACM bit. + /* Check ACM bit. * If it is set, immediately set ACM control bit to downgrading AC for passing WMM testplan. Annie, 2005-12-13. */ { @@ -2319,8 +2299,7 @@ static void dm_check_pbc_gpio(struct net_device *dev) return; if (tmp1byte & BIT(6) || tmp1byte & BIT(0)) { - /* - * Here we only set bPbcPressed to TRUE + /* Here we only set bPbcPressed to TRUE * After trigger PBC, the variable will be set to FALSE */ RT_TRACE(COMP_IO, "CheckPbcGPIO - PBC is pressed\n"); @@ -2529,8 +2508,7 @@ static void dm_rxpath_sel_byrssi(struct net_device *dev) } } - /* - * Set CCK Rx path + /* Set CCK Rx path * reg0xA07[3:2]=cck default rx path, reg0xa07[1:0]=cck optional rx path. */ update_cck_rx_path = 0; @@ -3049,8 +3027,7 @@ static void dm_send_rssi_tofw(struct net_device *dev) { struct r8192_priv *priv = ieee80211_priv(dev); - /* - * If we test chariot, we should stop the TX command ? + /* If we test chariot, we should stop the TX command ? * Because 92E will always silent reset when we send tx command. We use register * 0x1e0(byte) to notify driver. */ -- 2.17.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH v3 2/2] drivers/staging/rtl8192u: style nonstyled comments 2019-07-01 8:27 ` [PATCH v3 " Christian Müller @ 2019-07-01 8:27 ` Christian Müller 0 siblings, 0 replies; 12+ messages in thread From: Christian Müller @ 2019-07-01 8:27 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, Christian Müller, Felix Trommer The coding-styles.rst states, that multiline comments should allways contain a leading "*" in each line. For multiline comments in general they /* * should look * like this. */ For multiline comments in either net/ or drivers/net/ however, they should /* omit * the first * empty line. */ Since this file is part of a networking driver, the goal for it would be to reside in drivers/net/ one day. This patch changes comments, that were in neither form of the two listed above, to have the style that is specified for drivers/net/. Signed-off-by: Christian Müller <muellerch-privat@web.de> Signed-off-by: Felix Trommer <felix.trommer@hotmail.de> --- v1 contains the initial patch. v2 contains the same patch, but with a different subject to better distinguish this patch from the other one in this patch series. v3 contains the same patch again, but this time with this changelog appended. drivers/staging/rtl8192u/r8192U_dm.c | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/drivers/staging/rtl8192u/r8192U_dm.c b/drivers/staging/rtl8192u/r8192U_dm.c index 86215fee8f0b..cb6c653e624d 100644 --- a/drivers/staging/rtl8192u/r8192U_dm.c +++ b/drivers/staging/rtl8192u/r8192U_dm.c @@ -332,9 +332,10 @@ static void dm_check_rate_adaptive(struct net_device *dev) ((bshort_gi_enabled) ? BIT(31) : 0); /* 2007/10/08 MH We support RA smooth scheme now. When it is the first - time to link with AP. We will not change upper/lower threshold. If - STA stay in high or low level, we must change two different threshold - to prevent jumping frequently. */ + * time to link with AP. We will not change upper/lower threshold. If + * STA stay in high or low level, we must change two different threshold + * to prevent jumping frequently. + */ if (pra->ratr_state == DM_RATR_STA_HIGH) { HighRSSIThreshForRA = pra->high2low_rssi_thresh_for_ra; LowRSSIThreshForRA = (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) ? @@ -1738,10 +1739,12 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( pHalData->UndecoratedSmoothedPWDB, DM_DigTable.RssiLowThresh, DM_DigTable.RssiHighThresh, DM_DigTable.Dig_State);*/ /* 1. When RSSI decrease, We have to judge if it is smaller than a threshold - and then execute the step below. */ + * and then execute the step below. + */ if (priv->undecorated_smoothed_pwdb <= dm_digtable.rssi_low_thresh) { /* 2008/02/05 MH When we execute silent reset, the DIG PHY parameters - will be reset to init value. We must prevent the condition. */ + * will be reset to init value. We must prevent the condition. + */ if (dm_digtable.dig_state == DM_STA_DIG_OFF && (priv->reset_count == reset_cnt)) { return; @@ -1786,7 +1789,8 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( } /* 2. When RSSI increase, We have to judge if it is larger than a threshold - and then execute the step below. */ + * and then execute the step below. + */ if (priv->undecorated_smoothed_pwdb >= dm_digtable.rssi_high_thresh) { u8 reset_flag = 0; @@ -2252,11 +2256,10 @@ static void dm_ctstoself(struct net_device *dev) pHTInfo->IOTAction &= ~HT_IOT_ACT_FORCED_CTS2SELF; return; } - /* - 1. Uplink - 2. Linksys350/Linksys300N - 3. <50 disable, >55 enable - */ + /* 1. Uplink + * 2. Linksys350/Linksys300N + * 3. <50 disable, >55 enable + */ if (pHTInfo->IOTPeer == HT_IOT_PEER_BROADCOM) { curTxOkCnt = priv->stats.txbytesunicast - lastTxOkCnt; @@ -2333,7 +2336,8 @@ void dm_rf_pathcheck_workitemcallback(struct work_struct *work) u8 rfpath = 0, i; /* 2008/01/30 MH After discussing with SD3 Jerry, 0xc04/0xd04 register will - always be the same. We only read 0xc04 now. */ + * always be the same. We only read 0xc04 now. + */ read_nic_byte(dev, 0xc04, &rfpath); /* Check Bit 0-3, it means if RF A-D is enabled. */ -- 2.17.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 2/2] drivers/staging/rtl8192u: adjust block comments 2019-06-24 9:46 ` [PATCH 0/2] drivers/staging/rtl8192u: " Christian Müller 2019-06-24 9:46 ` [PATCH 1/2] " Christian Müller @ 2019-06-24 9:46 ` Christian Müller 1 sibling, 0 replies; 12+ messages in thread From: Christian Müller @ 2019-06-24 9:46 UTC (permalink / raw) To: gregkh Cc: johnfwhitmore, devel, linux-kernel, linux-kernel, felix.trommer, Christian Müller The coding-styles.rst states, that multiline comments should allways contain a leading "*" in each line. For multiline comments in general they /* * should look * like this. */ For multiline comments in either net/ or drivers/net/ however, they should /* omit * the first * empty line. */ Since this file is part of a networking driver, the goal for it would be to reside in drivers/net/ one day. This patch changes comments, that were in neither form of the two listed above, to have the style that is specified for drivers/net/. Signed-off-by: Christian Müller <muellerch-privat@web.de> Signed-off-by: Felix Trommer <felix.trommer@hotmail.de> --- drivers/staging/rtl8192u/r8192U_dm.c | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/drivers/staging/rtl8192u/r8192U_dm.c b/drivers/staging/rtl8192u/r8192U_dm.c index 86215fee8f0b..cb6c653e624d 100644 --- a/drivers/staging/rtl8192u/r8192U_dm.c +++ b/drivers/staging/rtl8192u/r8192U_dm.c @@ -332,9 +332,10 @@ static void dm_check_rate_adaptive(struct net_device *dev) ((bshort_gi_enabled) ? BIT(31) : 0); /* 2007/10/08 MH We support RA smooth scheme now. When it is the first - time to link with AP. We will not change upper/lower threshold. If - STA stay in high or low level, we must change two different threshold - to prevent jumping frequently. */ + * time to link with AP. We will not change upper/lower threshold. If + * STA stay in high or low level, we must change two different threshold + * to prevent jumping frequently. + */ if (pra->ratr_state == DM_RATR_STA_HIGH) { HighRSSIThreshForRA = pra->high2low_rssi_thresh_for_ra; LowRSSIThreshForRA = (priv->CurrentChannelBW != HT_CHANNEL_WIDTH_20) ? @@ -1738,10 +1739,12 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( pHalData->UndecoratedSmoothedPWDB, DM_DigTable.RssiLowThresh, DM_DigTable.RssiHighThresh, DM_DigTable.Dig_State);*/ /* 1. When RSSI decrease, We have to judge if it is smaller than a threshold - and then execute the step below. */ + * and then execute the step below. + */ if (priv->undecorated_smoothed_pwdb <= dm_digtable.rssi_low_thresh) { /* 2008/02/05 MH When we execute silent reset, the DIG PHY parameters - will be reset to init value. We must prevent the condition. */ + * will be reset to init value. We must prevent the condition. + */ if (dm_digtable.dig_state == DM_STA_DIG_OFF && (priv->reset_count == reset_cnt)) { return; @@ -1786,7 +1789,8 @@ static void dm_ctrl_initgain_byrssi_by_fwfalse_alarm( } /* 2. When RSSI increase, We have to judge if it is larger than a threshold - and then execute the step below. */ + * and then execute the step below. + */ if (priv->undecorated_smoothed_pwdb >= dm_digtable.rssi_high_thresh) { u8 reset_flag = 0; @@ -2252,11 +2256,10 @@ static void dm_ctstoself(struct net_device *dev) pHTInfo->IOTAction &= ~HT_IOT_ACT_FORCED_CTS2SELF; return; } - /* - 1. Uplink - 2. Linksys350/Linksys300N - 3. <50 disable, >55 enable - */ + /* 1. Uplink + * 2. Linksys350/Linksys300N + * 3. <50 disable, >55 enable + */ if (pHTInfo->IOTPeer == HT_IOT_PEER_BROADCOM) { curTxOkCnt = priv->stats.txbytesunicast - lastTxOkCnt; @@ -2333,7 +2336,8 @@ void dm_rf_pathcheck_workitemcallback(struct work_struct *work) u8 rfpath = 0, i; /* 2008/01/30 MH After discussing with SD3 Jerry, 0xc04/0xd04 register will - always be the same. We only read 0xc04 now. */ + * always be the same. We only read 0xc04 now. + */ read_nic_byte(dev, 0xc04, &rfpath); /* Check Bit 0-3, it means if RF A-D is enabled. */ -- 2.17.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
end of thread, other threads:[~2019-07-01 8:27 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-06-20 9:45 [PATCH 0/1] drivers/staging/rtl8192u: adjust block comments Christian Müller 2019-06-20 9:45 ` [PATCH 1/1] drivers/staging/rtl8129u: " Christian Müller 2019-06-20 11:33 ` Greg KH 2019-06-24 9:46 ` [PATCH 0/2] drivers/staging/rtl8192u: " Christian Müller 2019-06-24 9:46 ` [PATCH 1/2] " Christian Müller 2019-06-26 1:53 ` Greg KH 2019-06-27 8:33 ` [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line Christian Müller 2019-06-27 8:33 ` [PATCH v2 2/2] drivers/staging/rtl8192u: style nonstyled comments Christian Müller 2019-06-27 16:45 ` [PATCH v2 1/2] drivers/staging/rtl8192u: drop first comment line Greg KH 2019-07-01 8:27 ` [PATCH v3 " Christian Müller 2019-07-01 8:27 ` [PATCH v3 2/2] drivers/staging/rtl8192u: style nonstyled comments Christian Müller 2019-06-24 9:46 ` [PATCH 2/2] drivers/staging/rtl8192u: adjust block comments Christian Müller
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).