Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp782902ybg; Tue, 9 Jun 2020 12:42:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx7gCh51NY4kc6Sok5K2CQmtZICsxvnfeicS89n2HYWHiSFIzNbQFp6wo54xBS8qHnvWtBS X-Received: by 2002:a17:907:4096:: with SMTP id nm6mr20337ejb.4.1591731770087; Tue, 09 Jun 2020 12:42:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591731770; cv=none; d=google.com; s=arc-20160816; b=KQvqXvCZZ7GqZ2EVR29qacHDF28kyfdoGTpHmvQ6CxVLr4LGwU8JsNF4XOBHzJEl+1 /TxaMwlOcav2FxAx5RkiPZUnq1yzxVquVLH8NWPMoD2F94WpjYcL3Dj8YN+Rcjji8+os kiAIuqJYPsFpEymfZitDV4VotoW5wfzC9oyUjQl6ozMRx5N5Z7IYxHJQR6G4WmrfC52l 5YeE1DipQq64oP/zh8rixmz/sNM/NxTrw5EzoEsDtqJZO/jsadO/u75vsuOHR9bB2Lsa HSCpNfuc7o+Nb5iAirhH4pPuPKffzLEPIrj57zmEJvL9z3HJe9A6grVRloCqbxfr1Zej 1Myw== 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=fJY5qIk4CRY3g6L2P2phpxamyAVv/FuAlEYETdW0Tsk=; b=lJzzN1ASAKqSSiES5qyTwvHCVD9uCvTgNx9Xet8LIczqLyrqFTp60oOgvOgFET40Ss EavzCUxhFrVRLLyjsHGZqWkIA1qkRRLyOFfudAzzHaCcQxSYwtOSCd6FR9b3MhwHSR+8 8uvmACaVPwQVwpd9GeE6Ui/OkkruJFfOZX/z27jXVposA1RNRJ+arhszE6X0ZZCjJrTi wNeF5OJpBe8oUWNkArRg6JvS9dtCZmNuGtwf+UmJPFdpwdoQ2yEyfpV65SR2LA+PuR/h Y70Xho81t0JXkDOtwJCmome4UChHVdZlgoS62X19PAWUy8tOcZ5gxzk/gDgHF4W8f5mQ FHmw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o11si11925666ejc.714.2020.06.09.12.42.26; Tue, 09 Jun 2020 12:42:50 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731683AbgFIRRz (ORCPT + 99 others); Tue, 9 Jun 2020 13:17:55 -0400 Received: from alexa-out-sd-02.qualcomm.com ([199.106.114.39]:54520 "EHLO alexa-out-sd-02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728783AbgFIRRy (ORCPT ); Tue, 9 Jun 2020 13:17:54 -0400 Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30]) by alexa-out-sd-02.qualcomm.com with ESMTP; 09 Jun 2020 10:17:53 -0700 Received: from asutoshd-linux1.qualcomm.com ([10.46.160.39]) by ironmsg-SD-alpha.qualcomm.com with ESMTP; 09 Jun 2020 10:17:53 -0700 Received: by asutoshd-linux1.qualcomm.com (Postfix, from userid 92687) id 1EBFA20C1D; Tue, 9 Jun 2020 10:17:53 -0700 (PDT) From: Asutosh Das To: gregkh@google.com, cang@codeaurora.org, martin.petersen@oracle.com Cc: linux-scsi@vger.kernel.org, Asutosh Das , linux-kernel@vger.kernel.org (open list) Subject: [PATCH 1/1] Documentation:sysfs-ufs: Add WriteBooster documentation Date: Tue, 9 Jun 2020 10:17:46 -0700 Message-Id: <1591723067-22998-1-git-send-email-asutoshd@codeaurora.org> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Adds sysfs documentation for WriteBooster entries. Signed-off-by: Asutosh Das --- Documentation/ABI/testing/sysfs-driver-ufs | 136 +++++++++++++++++++++++++++++ 1 file changed, 136 insertions(+) diff --git a/Documentation/ABI/testing/sysfs-driver-ufs b/Documentation/ABI/testing/sysfs-driver-ufs index 016724e..d1a3521 100644 --- a/Documentation/ABI/testing/sysfs-driver-ufs +++ b/Documentation/ABI/testing/sysfs-driver-ufs @@ -883,3 +883,139 @@ Contact: Subhash Jadavani Description: This entry shows the target state of an UFS UIC link for the chosen system power management level. The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows if preserve user-space was configured + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the shared allocated units of WB buffer + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the configured WB type. + 0x1 for shared buffer mode. 0x0 for dedicated buffer mode. + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the total user-space decrease in shared + buffer mode. + The value of this parameter is 3 for TLC NAND when SLC mode + is used as WriteBooster Buffer. 2 for MLC NAND. + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the Maximum total WriteBooster Buffer size + which is supported by the entire device. + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the maximum number of luns that can support + WriteBooster. + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type +Date: June 2020 +Contact: Asutosh Das +Description: The supportability of user space reduction mode + and preserve user space mode. + 00h: WriteBooster Buffer can be configured only in + user space reduction type. + 01h: WriteBooster Buffer can be configured only in + preserve user space type. + 02h: Device can be configured in either user space + reduction type or preserve user space type. + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type +Date: June 2020 +Contact: Asutosh Das +Description: The supportability of WriteBooster Buffer type. + 00h: LU based WriteBooster Buffer configuration + 01h: Single shared WriteBooster Buffer + configuration + 02h: Supporting both LU based WriteBooster + Buffer and Single shared WriteBooster Buffer + configuration + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the status of WriteBooster. + 0: WriteBooster is not enabled. + 1: WriteBooster is enabled + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows if flush is enabled. + 0: Flush operation is not performed. + 1: Flush operation is performed. + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h8 +Date: June 2020 +Contact: Asutosh Das +Description: Flush WriteBooster Buffer during hibernate state. + 0: Device is not allowed to flush the + WriteBooster Buffer during link hibernate + state. + 1: Device is allowed to flush the + WriteBooster Buffer during link hibernate + state + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the amount of unused WriteBooster buffer + available. + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the amount of unused current buffer. + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the flush operation status. + 00h: idle + 01h: Flush operation in progress + 02h: Flush operation stopped prematurely. + 03h: Flush operation completed successfully + 04h: Flush operation general failure + The file is read only. + +What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows an indication of the WriteBooster Buffer + lifetime based on the amount of performed program/erase cycles + 01h: 0% - 10% WriteBooster Buffer life time used + ... + 0Ah: 90% - 100% WriteBooster Buffer life time used + The file is read only. + +What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units +Date: June 2020 +Contact: Asutosh Das +Description: This entry shows the configured size of WriteBooster buffer. + 0400h corresponds to 4GB. + The file is read only. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.