Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5438144yba; Wed, 10 Apr 2019 20:32:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqw5htbtAEnYjiseZV3X+4IWeGv6gwEV+K/WBRrr73LVrKZlg+bBSpkDb9JVolKuNrdVY78n X-Received: by 2002:a17:902:a704:: with SMTP id w4mr45925389plq.51.1554953561889; Wed, 10 Apr 2019 20:32:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554953561; cv=none; d=google.com; s=arc-20160816; b=hd2dIkie5YWa3Pr6TCFoJXbDgMJeoNhqiHdDh5FEQHhauxbCKKrakm2N0njn1YOSuK BUhcNONKeyubi7SIFwGiOh6fIb6wqUlOGcWqplYPoUdr4HtMB7kSlmIrOgbr4jKbpm5Z 363QieUQXOei2b5tVt8QvqofXxkJBKEJTrRaF58/ZCUR9PHL/8PS6Tq3fHgh3GQGF4CN HpIYPxB7Ma0d1W3yh+4hWgd/SNffcEkT5/plPLiki9wFM1y2a35LOzz3uNG/hRL0+ste H8wSpt0OS3S4HpqfLpPzClWXLHvVc1RPR59aE4AcjSrgQOPT47CZpagAlGkOO+uTMWiD mcoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=2SOaxIsxCZWz5onq19ag6Q5WDCyzgL62UDsFQ6FgmtI=; b=SEuLENp+NeHOcL2f5MrcnQlDNTfrkpb1c0TwKVdtXjyxwfS/N6lKskYyt9VVAGdzX0 ynFkf/9uGOULckelN31fzajVBGcPXGyBnJZ/kCAJIZuYhZPiIyVRPw9JqC34ic66ppPe vOAz9Gs62n0m+3VUu+TCEZayULIEbEtaPgqKFAW8+NlBlLzjy9VCUXuTOVuL30UbdkQn P02HbeCm18VZy0/kV9kraIRdmFMOkYp4YpV1317a0TWKjlt6LvUEnl6hwFRKrfBVKAIO +Ob4qjjWQAbwSfxy5zDbEsixqLcWkeN8P/5wWsoOQzeua8qxQvukJOkxaJhH9CYkoUSI HQUA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k76si18411125pfj.199.2019.04.10.20.32.25; Wed, 10 Apr 2019 20:32:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726646AbfDKDbt (ORCPT + 99 others); Wed, 10 Apr 2019 23:31:49 -0400 Received: from www.osadl.org ([62.245.132.105]:35486 "EHLO www.osadl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725782AbfDKDbs (ORCPT ); Wed, 10 Apr 2019 23:31:48 -0400 Received: from localhost.localdomain (178.115.242.59.static.drei.at [178.115.242.59]) by www.osadl.org (8.13.8/8.13.8/OSADL-2007092901) with ESMTP id x3B3VOEJ016044; Thu, 11 Apr 2019 05:31:24 +0200 From: Nicholas Mc Guire To: Adham Abozaeid Cc: Ajay Singh , Greg Kroah-Hartman , linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, Nicholas Mc Guire Subject: [PATCH V2] staging: wilc1000: give usleep_range a range Date: Thu, 11 Apr 2019 05:31:21 +0200 Message-Id: <1554953481-51340-1-git-send-email-hofrat@opentech.at> X-Mailer: git-send-email 2.1.4 X-Spam-Status: No, score=-1.9 required=6.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on www.osadl.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Nicholas Mc Guire usleep_range() is called in non-atomic context so there is little point in setting min==max as the jitter of hrtimer is determined by interruptions anyway. usleep_range can only perform the intended coalescence if some room for placing the hrtimer is provided. Given the range of milliseconds the delay will be 2+ anyway - so make it 2-2.5 ms which gives hrtimers space to optimize without negatively impacting performance. Signed-off-by: Nicholas Mc Guire --- Problem located with an experimental coccinelle script ./drivers/staging/wilc1000/wilc_wlan.c:411:4-16: WARNING: inefficient usleep_range with range 0 (min==max) ./drivers/staging/wilc1000/wilc_wlan.c:426:4-16: WARNING: inefficient usleep_range with range 0 (min==max) V2: Based on feedback from Adham Abozaeid that since this is in the transmit path 5ms could impact throughput but adding 500 microseconds should be tolerable. Patch was compile tested with: x86_64_defconfig + Staging=y, WILC1000_SDIO=m, WILC1000_SPI=m, WILC1000=m Patch is against 5.1-rc4 (localversion-next is -next-20190410) drivers/staging/wilc1000/wilc_wlan.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/wilc1000/wilc_wlan.c b/drivers/staging/wilc1000/wilc_wlan.c index c238969..42da533 100644 --- a/drivers/staging/wilc1000/wilc_wlan.c +++ b/drivers/staging/wilc1000/wilc_wlan.c @@ -408,7 +408,7 @@ void chip_wakeup(struct wilc *wilc) wilc->hif_func->hif_write_reg(wilc, 1, reg & ~BIT(1)); do { - usleep_range(2 * 1000, 2 * 1000); + usleep_range(2000, 2500); wilc_get_chipid(wilc, true); } while (wilc_get_chipid(wilc, true) == 0); } while (wilc_get_chipid(wilc, true) == 0); @@ -423,7 +423,7 @@ void chip_wakeup(struct wilc *wilc) &clk_status_reg); while ((clk_status_reg & 0x1) == 0) { - usleep_range(2 * 1000, 2 * 1000); + usleep_range(2000, 2500); wilc->hif_func->hif_read_reg(wilc, 0xf1, &clk_status_reg); -- 2.1.4