Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2898145pxb; Tue, 19 Jan 2021 08:38:42 -0800 (PST) X-Google-Smtp-Source: ABdhPJxYqiS7Wdg1OQazK3txKJCXaJqViqnEoaUcgD/6r6RoeyJCK0JKO69Dby2DjVybBT5YoT/A X-Received: by 2002:aa7:d386:: with SMTP id x6mr4241812edq.194.1611074322686; Tue, 19 Jan 2021 08:38:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611074322; cv=none; d=google.com; s=arc-20160816; b=y2NHWRjP7QVoTP45gV4ejU6z8Fi7AD3U26mGaN5YsONh3yLwYeClmottMnX9G00r8Y A3g/ODB4lKX9Ka/pXOlRA08gVbUv//YUI9e44265338NE29mrcjKonCAX6JGq5ueglZY m2sS6GnnOAPyEKsT9f+7DmaMnVsCt6MsMViSMUwXEVr2TwhmwlA6jVq9RFwvDuMbPXIV Yucmdttsy18KnYRE5M6CC4pjOtB11tJxF6HSAIGMeLQ9s9DCqIDRF1vZmDyzD+9fw6Bs ausw/ZTdpPLrHE7jYFH5gcLSdZqT56XS5RH9J5WLvZDpaTng2HUC+Zi8ToEAEq/Eg4bw W8mg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=C+NDxqcVq/gZ4wgLmYCGjXjhQkRMK4EGpwM/xyan4pU=; b=0FXlrnWrY7rxLKd5zdKZ61weFDntknKVa+YEV0sX3k0Jj09x7mhieS5h7n+suG21UF Df6tUzGhWV+f2kKISSbxoNwmUG8RUIPTDag22Ep3Nxpds/85RQAxkieDDVqHNw4OzI6n vAiRC7Wl165L3FryaLdc/idGCAk7dy36Gv8Cik3uvuXo7QW/ea3AlA6mdwVGGT0UmiA8 9s0j3dbtdzKTX/Eq8ABstX2YdEYnsnlRarEA8vh0OevpcBoSCmoDbBi1RLbRB5B55m9G UEhbwY+m4719vS0SLUeTXf+NaVGzqfi9p6j/PNRTYxTQhQFG6X62iEw6rG+8WV1CLKcY dkGw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b="IXa3p/V0"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f18si8509955ejb.475.2021.01.19.08.38.19; Tue, 19 Jan 2021 08:38:42 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b="IXa3p/V0"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729132AbhASQgK (ORCPT + 99 others); Tue, 19 Jan 2021 11:36:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50866 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730158AbhASQc3 (ORCPT ); Tue, 19 Jan 2021 11:32:29 -0500 Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3DB9DC061757; Tue, 19 Jan 2021 08:31:49 -0800 (PST) Received: by mail-ed1-x52a.google.com with SMTP id d22so11260190edy.1; Tue, 19 Jan 2021 08:31:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=C+NDxqcVq/gZ4wgLmYCGjXjhQkRMK4EGpwM/xyan4pU=; b=IXa3p/V0Pkgy7Fe4C9/I4iR2+SgQ/8eNXSJ/7q50BxaE2M5vfhY/0ZrSSlWPOOZy1b Nm+bBTdfXzvS5MlYpL3qgp6bv5vel8al9W7CU3hSIdOlbfaWlgZR3M0nNTAqVtEv4v5o TlHIfnFhQ6vB8dbyALLF10syipIIpfd654oY2nvNoLvJNq6UcUZPggoM2aluiU2i6vWX j5EvwJfTRzcsAG5vBlRPbSwpTOSswqUz6TN06leM6rpxLEOGzGdJEf5JFKsR/lhTK0BN +Xd9tQdDb6HSsYKeMKeUO+lyKEcZFmE1zzaz6KBkRbUYTRtHvM/kkYkkJuigdBXAL3c9 syfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=C+NDxqcVq/gZ4wgLmYCGjXjhQkRMK4EGpwM/xyan4pU=; b=SQ1/iDWka0wL+sQ2nWqfoDccKNKBVhB9qkU20LVQPLFqt7qLexR8FZ8wC8n5JTpQbB sqUACb7mo/fwBLpSDYXg9ArFtLZkI20ctCMexVCozzibaC3z/AeV7HM8CcE7yMc9+HDM OcBYFXd7jRuJ0cRResh/zq8IuO/ziCoohuoETo60ahfC7UDbJG2xvj51wlYsDmssAN6m E3EPtHnkH0sA1kf1asr/CtIhW1+2auvIQ4CQ0vmdIDITSZcE9hIFO1f+PydWBCGzrMvW CuIIxw+orHd8pvB/CGpwWEe14uoyhrNJ6+lNh1f5i5IX/iZw9Ajbmqwyy112OR7H1Ley LDQA== X-Gm-Message-State: AOAM530YGdJPvrzzEbTxSVa1v8JtaTC5nyN8DKFcSpE7bd1kEnQoEp0m CoaxXWBqhcyIg5zCP4+jJzI= X-Received: by 2002:a50:8004:: with SMTP id 4mr4041262eda.155.1611073908036; Tue, 19 Jan 2021 08:31:48 -0800 (PST) Received: from ubuntu-laptop (ip5f5bee1b.dynamic.kabel-deutschland.de. [95.91.238.27]) by smtp.googlemail.com with ESMTPSA id h12sm11297196ejx.81.2021.01.19.08.31.46 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 19 Jan 2021 08:31:47 -0800 (PST) Message-ID: <0fb16957375cc5916b61aa6ea2c13c64455f1d35.camel@gmail.com> Subject: Re: [PATCH v6 1/6] scsi: ufs: Add "wb_on" sysfs node to control WB on/off From: Bean Huo To: Adrian Hunter , alim.akhtar@samsung.com, avri.altman@wdc.com, asutoshd@codeaurora.org, jejb@linux.ibm.com, martin.petersen@oracle.com, stanley.chu@mediatek.com, beanhuo@micron.com, bvanassche@acm.org, tomas.winkler@intel.com, cang@codeaurora.org Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Date: Tue, 19 Jan 2021 17:31:45 +0100 In-Reply-To: <9ad2cf1a-68df-47ef-9fe7-01954d2d6181@intel.com> References: <20210118201039.2398-1-huobean@gmail.com> <20210118201039.2398-2-huobean@gmail.com> <0a9971aa-e508-2aaa-1379-fb898471a252@intel.com> <9ad2cf1a-68df-47ef-9fe7-01954d2d6181@intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2021-01-19 at 12:00 +0200, Adrian Hunter wrote: > > > Is it so, that after a full reset, WB is always enabled again? > > > Is > > > that > > > intended? > > > > Hello Adrian > > Good questions. yes, after a full reset, the UFS device side by > > default > > is wb disabled, then WB will be always enabled agaion in > > ufshcd_wb_config(hba). but, for the platform which > > supports UFSHCD_CAP_CLK_SCALING, wb will be disabled again while > > clk > > scaling down and enabled while clk scaling up. > > > > Regarding the last question, I think OEM wants to do that. maybe > > they > > suppose there will be a lot of writing after reset?? From the UFS > > device's point of view, the control of WB is up to the user. > > If it is by design enabled after reset, then perhaps it should be > mentioned > in the sysfs documentation. ok, will add it in the next version. thanks, Bean