Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3310891yba; Mon, 6 May 2019 22:07:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqyNoCWpJ2VgFpyCDR8/GrQmGNMvwPhCnytdhmMYEKJ3Ura62Xal/6e2T57jFKItiswdJ1k4 X-Received: by 2002:a65:51c5:: with SMTP id i5mr37546785pgq.189.1557205675970; Mon, 06 May 2019 22:07:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557205675; cv=none; d=google.com; s=arc-20160816; b=RvGLuDEITdsa/IRyYvpOSpRlt1EvyX75u9IrXtjICekPvpxw4mACIX5HeMOY0yhZTx UMgQdwWrSwU2+68aS16rRTmsOQP1shNmR53j+BB7NDFtzGKrpt/xrbdUU56IP1mLj2fY 755ehbVuQZ023R3uFXLGlePwRNjCDU6KsB1U/7okCdF0BGYB90IdB+QhvNYWzNHAXDyy Gw3u/frXya+YBy4xOocXMctavHO2TVz7S1cGhVB7BdfxbUAHSbeUqdwE8kcog6Fs7znV gDdSB+6LzqEl5hcfkly8XsD8u57DVXMTPB9C4K3I+JiaI8u19XgHPngXAdOc3nEq+Rex qYGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:cc:to:from:thread-topic:subject:dkim-signature; bh=UrV7zyLquGaGyp71Wl+1EFTpGEsSXpjTEyDgqzkJm58=; b=tyx7EdwI+K/MJ+vboKGLn+PkHzYa7x2mFuRSyl/t0RfG2IHIdEtGm/wwEihGIIJmCA dCuKVnMU8uLDqUdyceJ6fFGoNtt0ZUuTNZoExFiJI7rkP0Y8zZ0NeClhJ7ZGEPyyXpfm j3NpT8FXyErSnL9q9BoAnM/2eF5g10vI+53dAdshD9TJYsAlPSgfICzIrPoC7OeQQl2C 2mVDMc4rCnEeew0df291GiQhSumYVBsDV9xEex/GMslbqKpEwA9KpBnbnIOZghxCC19J yJkx30uyoOjWa4odpP7HOmovNfQZ5gN42W5tYkr7dANoM7RNPenBNc6Ykl4MceA9VIU9 vurA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@qti.qualcomm.com header.s=qcdkim header.b=uvlVH52D; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=qti.qualcomm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y6si16925485pgi.103.2019.05.06.22.07.30; Mon, 06 May 2019 22:07:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@qti.qualcomm.com header.s=qcdkim header.b=uvlVH52D; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=qti.qualcomm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726477AbfEGFF3 (ORCPT + 99 others); Tue, 7 May 2019 01:05:29 -0400 Received: from alexa-out-tai-01.qualcomm.com ([103.229.16.226]:40710 "EHLO alexa-out-tai-01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725839AbfEGFF1 (ORCPT ); Tue, 7 May 2019 01:05:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1557205525; x=1588741525; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=UrV7zyLquGaGyp71Wl+1EFTpGEsSXpjTEyDgqzkJm58=; b=uvlVH52D6SwjletGPX5xEpWQSPkYc267hEpHTQ2qbDJ0YbwoBMnr2WfV Qm7gGXvUmBLY2VMPdeEasewGLosaPB/3v62dnJw3peJ5ulboeEymV9Hp+ dEMGpXhT1kUR2NgeDbv8nJDXMLQE1wR322aOS8H9UOo9x+86ha3smjcXo g=; Subject: RE: [PATCH] ath10k: remove mmc_hw_reset while hif power down Thread-Topic: [PATCH] ath10k: remove mmc_hw_reset while hif power down Received: from ironmsg03-tai.qualcomm.com ([10.249.140.8]) by alexa-out-tai-01.qualcomm.com with ESMTP; 07 May 2019 13:05:24 +0800 X-IronPort-AV: E=McAfee;i="5900,7806,9249"; a="28693442" Received: from aptaiexm02f.ap.qualcomm.com ([10.249.150.16]) by ironmsg03-tai.qualcomm.com with ESMTP/TLS/AES256-SHA; 07 May 2019 13:05:24 +0800 Received: from aptaiexm02f.ap.qualcomm.com (10.249.150.16) by aptaiexm02f.ap.qualcomm.com (10.249.150.16) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 7 May 2019 13:05:22 +0800 Received: from aptaiexm02f.ap.qualcomm.com ([fe80::4152:1436:e436:faa1]) by aptaiexm02f.ap.qualcomm.com ([fe80::4152:1436:e436:faa1%19]) with mapi id 15.00.1395.000; Tue, 7 May 2019 13:05:22 +0800 From: Wen Gong To: Grant Grundler , Wen Gong CC: "linux-wireless@vger.kernel.org" , "ath10k@lists.infradead.org" Thread-Index: AQHVAdpJadKuEaUlO02aG5lsvSOAm6ZfCRng Date: Tue, 7 May 2019 05:05:21 +0000 Message-ID: <36950ff25c0747629e60ccb68819e93a@aptaiexm02f.ap.qualcomm.com> References: <1556417825-13713-1-git-send-email-wgong@codeaurora.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.249.136.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org > -----Original Message----- > From: ath10k On Behalf Of Grant > Grundler > Sent: Saturday, May 4, 2019 2:01 AM > To: Wen Gong > Cc: linux-wireless@vger.kernel.org; ath10k@lists.infradead.org > Subject: [EXT] Re: [PATCH] ath10k: remove mmc_hw_reset while hif power > down >=20 > [repeating comments I made in the gerrit review for Chrome OS : > https://chromium- > review.googlesource.com/c/chromiumos/third_party/kernel/+/1585667 > ] >=20 > On Sat, Apr 27, 2019 at 7:17 PM Wen Gong wrote: > > > > For sdio 3.0 chip, the clock will drop from 200M Hz to 50M Hz after loa= d > > ath10k driver, it is because mmc_hw_reset will reset the sdio's power, > > then mmc will consider it as sdio 2.0 and drop the clock. >=20 > Wen, > 5468e784c0600551ca03263f5255a375c05f88e7 commit message gives > reasons > for adding the mmc_hw_reset() call. The commit message for removing > gives different reason for removal. Both are good but second one is > incomplete. >=20 > The commit message for removal should ALSO explain why adding this > call wasn't necessary in the first place OR move the call to a > different code path. >=20 > > Remove mmc_hw_reset will avoid the drop of clock. >=20 > This commit message makes it clear the original patch introduced a new > problem. But the original patch fixed a different problem and that > this proposed change seems likely to re-introduce and the commit > message should explain why that isn't true (or how the original was > fixed differently) Hi Grant, The mmc_hw_reset's effect depends on the hardware layout/configure software's behavior, recently it will effect the clock of sdio for the plat= form I used. And it will still work well without mmc_hw_reset for the platform I Used currently.=20 If sdio cannot work on other platform, I think it can add flag in=20 ath10k_hw_params_list for the platform to call the mmc_hw_reset depends on the flag. >=20 > cheers, > grant