Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5132246ybi; Tue, 28 May 2019 08:05:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqz2BRe/E0MrcxmHTOFiC1H5OO+aeP4C7U5nceVWDiA016oCoGBWXnk+EeZSQDWGJ6Fc0nFh X-Received: by 2002:a65:494a:: with SMTP id q10mr38394048pgs.201.1559055901157; Tue, 28 May 2019 08:05:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559055901; cv=none; d=google.com; s=arc-20160816; b=ibaQgXNRYCx4uTuMEeDU/EvxBDaHKbKnuo1bP7l50t/bJKkzNfE5rxtooXEiwcGb/Z 03N7V9RLp3dIIdkSfZ3Q/6e2jt48mpI23Sh/RV2V8vzk8vpB/D0b+vHmG8Oe7qz2Vieu NyU4qEus2RgPcVK6mYaWXkm0tYNk7dDFXFVzo+RCzk0ll8KOeziziJaulAdTCvm5UGze 4kx6rcHeJomVXPWYbdaOfXLED569r76ImrekyWpJmlrzGzexby3MKG1suIlQRrnUKB2C 2QfIIqO6DNnVuueU1/mnb8l+We9g+ehV2wm9hel+FKuLsXX4q+TUOpttowDoAUhJfYGo Fopw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject; bh=37vC+lD/sxorD27Re3O9gXxRDYOKkwoi2ybdliz5YVY=; b=G/yMu0/e6jc03Z9FhCpQvVDucw0jSspTBD7WqJ7vAcG/kiQvxx1H3HrH8uUg2l2gn/ y3geX+JEpBOZfPpiOlo1uiiLGjKQFHgrb05wcBxpKrLv90SKKe+9Wq8euldf47dTN0KN /xdjxOxJz63Idmh0Gl/L0718auXId3TWAgkGaDK6y+S9gSpaakRdJ20WnS0QOGX2ej0U l0YjSATs8Pte0eCDH2vBsXkSNI7It0sYGDi4+0xk9nbNyICdUeVTYlpfDsUDJFRXKJA/ RHTIiqCPkSC3yV5WU+PokLlcRS09IckGhdl2mh4GaoA7pBDviQJYuDDHBRAldnPriT9j q+Zw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k17si26348300pfd.278.2019.05.28.08.04.42; Tue, 28 May 2019 08:05:01 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726841AbfE1Lpg (ORCPT + 99 others); Tue, 28 May 2019 07:45:36 -0400 Received: from mga12.intel.com ([192.55.52.136]:10312 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726580AbfE1Lpg (ORCPT ); Tue, 28 May 2019 07:45:36 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 May 2019 04:45:36 -0700 X-ExtLoop1: 1 Received: from ahunter-desktop.fi.intel.com (HELO [10.237.72.198]) ([10.237.72.198]) by fmsmga006.fm.intel.com with ESMTP; 28 May 2019 04:45:31 -0700 Subject: Re: [PATCH 2/3] mmc: core: API for temporarily disabling auto-retuning due to errors To: Arend Van Spriel , Douglas Anderson , Ulf Hansson , Kalle Valo Cc: linux-rockchip@lists.infradead.org, Double Lo , briannorris@chromium.org, Madhan Mohan R , mka@chromium.org, Wright Feng , Chi-Hsien Lin , Jiong Wu , Ritesh Harjani , linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, Shawn Lin , Wolfram Sang , Avri Altman , Martin Hicks References: <20190517225420.176893-1-dianders@chromium.org> <20190517225420.176893-3-dianders@chromium.org> <05af228c-139b-2b7f-f626-36fb34634be5@broadcom.com> <4f39e152-04ba-a64e-985a-df93e6d15ff8@intel.com> From: Adrian Hunter Organization: Intel Finland Oy, Registered Address: PL 281, 00181 Helsinki, Business Identity Code: 0357606 - 4, Domiciled in Helsinki Message-ID: <2d6fa51d-27af-4f90-2bd6-144112ce75ad@intel.com> Date: Tue, 28 May 2019 14:45:16 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/05/19 2:21 PM, Arend Van Spriel wrote: > > > On 5/28/2019 12:04 PM, Adrian Hunter wrote: >> On 26/05/19 9:42 PM, Arend Van Spriel wrote: >>> On 5/18/2019 12:54 AM, Douglas Anderson wrote: >>>> Normally when the MMC core sees an "-EILSEQ" error returned by a host >>>> controller then it will trigger a retuning of the card.  This is >>>> generally a good idea. >>> >>> Probably a question for Adrian, but how is this retuning scheduled. I recall >>> seeing something in mmc_request_done. How about deferring the retuning upon >>> a release host or is that too sdio specific. >> >> Below is what I have been carrying the last 4 years.  But according to >> Douglas' >> patch, the release would need to be further down.  See 2nd diff below. >> Would that work? > > That makes sense. The loop is needed because the device can be a bit bone > headed. So indeed after the loop the device should be awake and able to > handle CMD19. What if tuning is needed to read SBSDIO_FUNC1_SLEEPCSR successfully?