Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp202006imm; Mon, 2 Jul 2018 10:01:48 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfTdbknw/QwPMbtF9mfU5/LMX2F8s8nAW1h6fgSDQG7j0X5Uum2FKAJQFUmUDlB0zCaagUE X-Received: by 2002:a62:1f8c:: with SMTP id l12-v6mr17613441pfj.143.1530550908161; Mon, 02 Jul 2018 10:01:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530550908; cv=none; d=google.com; s=arc-20160816; b=Aujv5xNphg4nsYqV6Xl9wNSwHenpLR+vIu0AcrkJQzKwyaJVr6Ug9JbzPwbOGiA1ql b2bexytuH3xVr2y/IfLLsKhbzqV1Wrpc4nxCf4fg2AMTaKVWcnLy/e3Ynau/PhwG1BQc csOYq4ri3nl/Ym9WhRpyPNPrT4BX9DwdCWx8Zq4jDcp/cOtNPY3HQyVT0RulvxOSqRYh LKbhAeZFLuEezEDlLEkDniLP4VJleNfg/qxTQNrboaaU37CYQ25qTD4HErO+d7XfN9Ub bPyLDSkWpwC6Ui+dg4wxxu3vO+lqgq2C2du+OklUwdQdAuKLABWnr8Qwlfr27p12x+SF 2F8g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=I+u58XWIlYuHmYzWNPSgoCLOzMQzWwK/OkSVwvLQASM=; b=lhL2El9A8GdVeA++tiqOVTTwz6ppwkgE/SKKZRH5wTMJaZ4bem33c2FAr1ORC3kXMN epzYuOs6ZeGPh0iUpvJqcMRO92sRexZ7lVjLEpwjk3ym1YE+wfgMMlLI/P+sAnaonxqX DQJeEJXMYDm9IfJ4RmEE8PFicesVGmwhAZ2gjTr7BFXnEM5VVadEpECraAxPnszXXsWq STLhnDVAJYMXCIZkUSUq9CTtEXA8WxbCvd/XYPiUvJ0DFI7Hk0U3WqogDRx7L189cb7E O0hsT9lI51W0z+eqrIKv9dAp0dactCSvtuE3VoMv3Cc5xplgSHH9uaf/7GiLC8+Bofz+ vpNw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@google.com header.s=20161025 header.b=LnMvJUpc; dkim=fail header.i=@chromium.org header.s=google header.b=d9uO6dAA; 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=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o26-v6si14834294pge.307.2018.07.02.10.01.32; Mon, 02 Jul 2018 10:01:48 -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; dkim=fail header.i=@google.com header.s=20161025 header.b=LnMvJUpc; dkim=fail header.i=@chromium.org header.s=google header.b=d9uO6dAA; 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=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753130AbeGBRAf (ORCPT + 99 others); Mon, 2 Jul 2018 13:00:35 -0400 Received: from mail-ua0-f193.google.com ([209.85.217.193]:33697 "EHLO mail-ua0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752813AbeGBRAX (ORCPT ); Mon, 2 Jul 2018 13:00:23 -0400 Received: by mail-ua0-f193.google.com with SMTP id g18-v6so7752205uak.0 for ; Mon, 02 Jul 2018 10:00:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=I+u58XWIlYuHmYzWNPSgoCLOzMQzWwK/OkSVwvLQASM=; b=LnMvJUpchRyHT64/O5UcQc3J1gMplNKrYp3UXThfLYg5RJW+3i7X9JncJalWrdwTQW yRzg6L7/SiE1LrOUfV9+airYx8BqScK0zuBOl/fE14OvynaylN8H+zz2426sinU6ocCD EBqtJRSHgJWVe9cGDMp0Xz6S7mnFTBEr0t8Tk0deL+LU5XRG96oV54dCfoTDWCI+r9Uc GNKnAhN++ok5EclNOKdJ+ie/ZfBUriMfCfrRk/s4GsW2fGmJVKRuHRO/DviPgQxlEoT8 mSTniuZbihvsxFsM44ircVrbYbG73se6O4ogJJrG9Nv3ttMeU7U4iuA0OOMT8pa7wmHJ +RZA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=I+u58XWIlYuHmYzWNPSgoCLOzMQzWwK/OkSVwvLQASM=; b=d9uO6dAAGER/ap/II3WK2YAVpJdqg2kuCzWuK3mYhuS7jbeDG2e2gcFgWOLiPBN9oz AOMikudObGxjDdIZtYV35V4gIyDUoQ6c1UBbPM3bwD7DgNxL1dIt8msFvseiKM03aYAL P0ee7Pm5MyQcfU3SvQf6+i+zQihYfEUkA0kO0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=I+u58XWIlYuHmYzWNPSgoCLOzMQzWwK/OkSVwvLQASM=; b=ERmLPriJI0IGSgb2GRRXDHGqU+fyDmwvmUfPuzcdRnsJ9eKYlOC72PJTZFDq+KSMl3 heYAvPgnnsQaF1g/ihdVAJwayN9ZM6zwyWDw1ywPsjIV1scz0BXdKe/jC2j5L+DpVbTb AES1Yo3SFuWV44RnWsRfthnlRohD06HeO+C3GMrc0le+ec9/dftykgxciipKVkhela4U q6nyQdmN0D00UU6X8sIEhI8qW4CWxAxk24q2VjqP0C1oRPCdNxMzr9c46BYl271r81qY 4yQ1lzirnhYAgZxwvGmUmepdkdjcgUDilKsq/WLQIxpzFP98Z+sT+uY6RD2P6ONjw/P8 tVEA== X-Gm-Message-State: APt69E3TyRrKAm8pIKkLJY0NNAG69qHU3wLpchwDAqFhqsXyqNyCXKj8 gkNh6GssmS+Bey3OTjb/zKJlNZL0DmKFpcCkR6LXXA== X-Received: by 2002:ab0:11dd:: with SMTP id q29-v6mr16192664uac.191.1530550821566; Mon, 02 Jul 2018 10:00:21 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1f:9495:0:0:0:0:0 with HTTP; Mon, 2 Jul 2018 10:00:20 -0700 (PDT) In-Reply-To: <08a08d60-8176-df54-ff0e-ffc195f40d6c@rock-chips.com> References: <1527590335-171787-1-git-send-email-xiaqing17@hisilicon.com> <08a08d60-8176-df54-ff0e-ffc195f40d6c@rock-chips.com> From: Doug Anderson Date: Mon, 2 Jul 2018 10:00:20 -0700 X-Google-Sender-Auth: _ZeiE68PeqsdKB3v-j0fVaBXe9E Message-ID: Subject: Re: [PATCH] mmc: dw_mmc: fix card threshold control configuration To: Shawn Lin Cc: Ulf Hansson , Evgeniy Didin , Jaehoon Chung , Qing Xia , "linux-mmc@vger.kernel.org" , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, Jun 11, 2018 at 7:17 AM, Shawn Lin wrote: > On 2018/6/11 20:20, Ulf Hansson wrote: >> >> + Shawn Lin, Evgeniy Didin, Doug Andersson >> >> On 29 May 2018 at 12:38, Qing Xia wrote: >>> >>> From: x00270170 >>> >>> Card write threshold control is supposed to be set since controller >>> version 2.80a for data write in HS400 mode and data read in >>> HS200/HS400/SDR104 mode. However the current code returns without >>> configuring it in the case of data writing in HS400 mode. >>> Meanwhile the patch fixes that the current code goes to >>> 'disable' when doing data reading in HS400 mode. >>> > > I'm more or less unable to review this, as I don't have 2.80a databook, > nor a such platform to verify it. :( Sorry for not responding earlier. I didn't have a lot of context here so reviewing it never made it to the top of my queue. ...but quickly checking what I can... I'm in almost the same boat as Shawn. I don't have any HS400 hardware using dw_mmc available to me, but I do seem to have the 2.80a databook hanging around and it agrees that we need to enable the card write threshold for HS400 writes. That also matches the comments, so the patch seems right to me. Probably Jaehoon would make a better reviewer since he submitted the original code and also has more familiarity with HS400 on dw_mmc. I don't think I have enough context to give a full Reviewed-by, but in the very least I can confirm that the patch seems sane. -Doug