JEDEC JESD220-1A-2016 Universal Flash Storage (UFS) Unified Memory Extension Version 1 1.pdf

1、JEDEC STANDARD Universal Flash Storage (UFS) Unified Memory Extension Version 1.1 JESD220-1A (Revision of JESD220-1, September 2013) MARCH 2016 JEDEC SOLID STATE TECHNOLOGY ASSOCIATION NOTICE JEDEC standards and publications contain material that has been prepared, reviewed, and approved through the

2、 JEDEC Board of Directors level and subsequently reviewed and approved by the JEDEC legal counsel. JEDEC standards and publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of

3、 products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for use by those other than JEDEC members, whether the standard is to be used either domestically or internationally. JEDEC standards and publications are adopted without regard to whether or not

4、their adoption may involve patents or articles, materials, or processes. By such action JEDEC does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the JEDEC standards or publications. The information included in JEDEC standards and publica

5、tions represents a sound approach to product specification and application, principally from the solid state device manufacturer viewpoint. Within the JEDEC organization there are procedures whereby a JEDEC standard or publication may be further processed and ultimately become an ANSI standard. No c

6、laims to be in conformance with this standard may be made unless all requirements stated in the standard are met. Inquiries, comments, and suggestions relative to the content of this JEDEC standard or publication should be addressed to JEDEC at the address below, or refer to www.jedec.org under Stan

7、dards and Documents for alternative contact information. Published by JEDEC Solid State Technology Association 2016 3103 North 10th Street Suite 240 South Arlington, VA 22201-2107 This document may be downloaded free of charge; however JEDEC retains the copyright on this material. By downloading thi

8、s file the individual agrees not to charge for or resell the resulting material. PRICE: Contact JEDEC Printed in the U.S.A. All rights reserved PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by JEDEC and may not be reproduced without permission. For information, contact: JEDEC Solid Stat

9、e Technology Association 3103 North 10th Street Suite 240 South Arlington, VA 22201-2107 or refer to www.jedec.org under Standards-Documents/Copyright Information. JEDEC Standard No. 220-1A -i- UNIVERSAL FLASH STORAGE (UFS) UNIFIED MEMORY EXTENSION, VERSION 1.1 Contents Page 1 Scope . 1 2 Normative

10、Reference . 1 3 Terms and Definitions . 2 4 Introduction . 6 Overview . 6 4.1Purpose of Unified Memory Support 7 4.2Framework of Unified Memory 8 4.34.3.1 Host Memory Map 8 4.3.2 Configuration of Unified Memory 9 Speed Estimation . 9 4.45 Modified UFS Architecture Overview 11 Modified UFS Top level

11、Architecture . 11 5.1UFS Bus Master Transport Protocol (UBMTP) Layer 12 5.26 UFS UIC Layer: MIPI M-PHY and MIPI UniPro. 13 Overview . 13 6.1HIBERNATE 13 6.27 UFS Bus Master Transport Protocol (UBMTP) Layer 15 Overview . 15 7.1Unified Memory Protocol Information Unit . 15 7.27.2.1 UMPIU Transaction C

12、odes . 15 General Unified Memory Protocol Information Unit Format . 17 7.37.3.1 Overview . 17 7.3.2 Basic Header Format . 18 7.3.3 COPY DATA UMPIU 19 7.3.4 UM COPY DATA UMPIU . 21 7.3.5 ACKNOWLEDGE COPY UMPIU 22 7.3.6 ACCESS UM BUFFER UMPIU 23 7.3.7 WRITE UM BUFFER UMPIU . 25 7.3.8 ACKNOWLEDGE UM BU

13、FFER UMPIU . 26 7.3.9 UM DATA OUT UMPIU . 27 7.3.10 UM DATA IN UMPIU . 29 7.3.11 Unified Memory Basic Operations 31 7.3.12 SCSI Read / Write and Unified Memory Operations 34 8 UFS Functional Descriptions Related to Unified Memory . 41 UFS Boot with Unified Memory Support . 41 8.18.1.1 Introduction .

14、 41 8.1.2 Initialization of Unified Memory 41 UFS Cache in Unified Memory . 42 8.28.2.1 Example of How to Use Write Buffer Cache in Unified Memory 43 Host Device Interaction . 43 8.38.3.1 Background Operation Mode with Unified Memory 43 9 UFS Descriptors, Flags and Attributes 44 Device Descriptor 44

15、 9.1Flags 45 9.2Attributes . 46 9.3Annex A Differences between JESD220-1A and JESD220-1 47 JEDEC Standard No. 220-1A -ii- Contents (contd) Page Figures Figure 4.1 Conventional Memory Structure . 6 Figure 4.2 UMA Memory Structure . 6 Figure 4.3 Inter-Memory Communication of Device-Integrated RAM Buff

16、ering . 7 Figure 4.4 Inter-Memory Communication of UM Buffering 7 Figure 4.5 Host Memory Map (Physical) . 8 Figure 4.6 Definition of Latency 9 Figure 4.7 Definition of Multiple Outstanding . 10 Figure 5.1 Modified UFS Top Level Architecture . 11 Figure 6.1 Flag Manipulation before HIBERNATE . 14 Fig

17、ure 6.2 Flag Manipulation after HIBERNATE . 14 Figure 7.1 Unified Memory Read . 31 Figure 7.2 Unified Memory Write 32 Figure 7.3 Copy between System Memory and Unified Memory 33 Figure 7.4 Generic Copy in the Unified Memory . 33 Figure 7.5 SCSI Read (Non-Cached) and Subsequent Unified Memory Operati

18、ons . 35 Figure 7.6 SCSI Write (Non-Cached) and Subsequent Unified Memory Operations 35 Figure 7.7 SCSI Write (Cached) and Subsequent Unified Memory Operations . 36 Figure 7.8 SCSI Read (Cached) and subsequent Unified Memory Operations (Simple Single Read) . 37 Figure 7.9 SCSI Read (Cached) and subs

19、equent Unified Memory Operations (Large Data Read with Filling Missing Write Buffer) . 38 Figure 7.10 SCSI Read (Cached) and subsequent Unified Memory Operations (Large Data Read with Flushing Dirty Write Buffer) 39 Figure 7.11 L2P Table Operation . 40 Figure 8.1 Unified Memory Initialization Sequen

20、ce Diagram 42 Tables Table 7.1 UMPIU Transaction Codes . 15 Table 7.2 UMPIU Transaction Code Definitions . 16 Table 7.3 General Format of the Unified Memory Protocol Information Unit . 17 Table 7.4 Basic Header Format 18 Table 7.5 Transaction Type Format 18 Table 7.6 UMPIU Flags 18 Table 7.7 COPY DA

21、TA UMPIU 19 Table 7.8 Flags Definition of ACKNOWLEDGE COPY UMPIU . 20 Table 7.9 UM COPY DATA UMPIU 21 Table 7.10 ACKNOWLEDGE COPY UMPIU 22 Table 7.11 Flags Definition of ACKNOWLEDGE COPY UMPIU . 22 Table 7.12 ACCESS UM BUFFER UMPIU 23 Table 7.13 Flags Definition for ACCESS UM BUFFER UMPIU . 24 Table

22、 7.14 WRITE UM BUFFER UMPIU 25 Table 7.15 ACKNOWLEDGE UM BUFFER UMPIU 26 Table 7.16 Flags Definition for ACKNOWLEDGE UM BUFFER UMPIU . 26 Table 7.17 UM DATA OUT UMPIU . 27 Table 7.18 Flags Definition for UM DATA OUT UMPIU 28 Table 7.19 UM DATA IN UMPIU . 29 Table 9.1 Device Descriptor . 44 Table 9.2

23、 Flags . 45 Table 9.3 Attributes 46 JEDEC Standard No. 220-1A -iii- Foreword This Universal Flash Storage (UFS) Unified Memory Extension standard is an extension to JESD220, Universal Flash Storage (UFS) Standard. Introduction The UFS standard defines a managed storage device. UFS devices are design

24、ed to offer high performance with low power consumption. The UFS device contains features that support both high throughput for large data transfers and performance for small random data accesses. The UFS Unified Memory Extension standard describes the requirements to implement unified memory functi

25、onality in a UFS device. JEDEC Standard No. 220-1A -iv- JEDEC Standard No. 220-1A Page 1 UNIVERSAL FLASH STORAGE (UFS) UNIFIED MEMORY EXTENSION, Version 1.1 (From JEDEC Board Ballot, JCB-16-13, formulated under the cognizance of the JC-64.1 Subcommittee on Electrical Specifications and Command Proto

26、cols (Item 133.11).) 1 SCOPE This document provides a comprehensive definition of the unified memory support for UFS. It also provides some details in how to utilize the unified memory for realizing high performance in UFS devices. 2 NORMATIVE REFERENCE The following normative documents contain prov

27、isions that, through reference in this text, constitute provisions of this standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this standard are encouraged to investigate the possibility of applyin

28、g the most recent editions of the normative documents indicated below. For undated references, the latest edition of the normative document referred to applies. UFS, JEDEC JESD220C, Universal Flash Storage (UFS), Version 2.1. UFSHCI, JEDEC JESD223C, Universal Flash Storage Host Controller Interface

29、(UFSHCI), Version 2.1. UFSHCI-UME, JEDEC JESD223-1A, Universal Flash Storage Host Controller Interface (UFSHCI) Unified Memory Extension Version 1.1. JEDEC Standard No. 220-1A Page 2 3 TERMS AND DEFINITIONS For the purposes of this standard, the terms and definitions given in the document included i

30、n section 2, Normative Reference, and the following apply. Acronyms 3.1CPORT A CPort is a Service Access Point on the UniPro Transport Layer (L4) within a Device that is used for Connection-oriented data transmission DMA Direct Memory Access GB Gigabyte HCI Host Controller Interface KB Kilobyte LUN

31、Logical Unit Number MB Megabyte MIPI Mobile Industry Processor Interface TB Terabyte TC Traffic Class UFS Universal Flash Storage UM Unified Memory UMA Unified Memory Architecture UME Unified Memory Extension UMPIU Unified Memory Protocol Information Unit UniPro Unified Protocol. UPIU UFS Protocol I

32、nformation Unit UTP UFS Transport Protocol JEDEC Standard No. 220-1A Page 3 Terms and Definitions 3.2Application Client: An entity that is the source of SCSI commands and task management function requests in the host. Byte: An 8bit data value with the most significant bit labeled as bit 7 and the le

33、ast significant bit as bit 0. Device Server: An entity in the device that processes SCSI commands and task management functions. Doubleword: A 32bit data value with the most significant bit labeled as bit 31 and the least significant bit as bit 0. Dword: A 32bit data value, a Doubleword. Gigabyte: 1

34、,073,741,824 or 230 bytes. Host: An entity or a device with the characteristics of a primary computing device that includes one or more SCSI initiator devices. Initiator Device: Within a transaction, the originator of a SCSI command request message to a target device. Kilobyte: 1024 or 210 bytes. Lo

35、gical Unit: A logical unit is an internal entity of a bus device that performs a certain function or addresses a particular space or configuration within a bus device. Logical Unit Number: A numeric value that identifies a logical unit within a device. Megabyte: 1,048,576 or 220 bytes. Quadword: A 6

36、4bit data value with the most significant bit labeled as bit 63 and the least significant bit as 0. Segment: A specified number of sequentially addressed bytes representing a data structure or section of a data structure. Target Device: Within a transaction, the recipient of a SCSI command request m

37、essage from an initiator device. Task: A task is a SCSI command which includes all transactions to complete all data transfers and a status response that will satisfy the requirements of the requested services of the command. Terabyte: 1.099.511.627.776 or 240 bytes. Transaction: A UFS bus primitive

38、 action which results in transmission of serial data packets between a target and initiator. UFS Protocol Information Unit: Information transfer (communication) between a UFS host and device is done through messages which are called UFS Protocol Information Units. These messages are UFS defined data

39、 structures that contain a number of sequentially addressed bytes arranged as various information fields. Word: A 16bit data value with the most significant bit labeled as bit 15 and the least significant bit as bit 0. JEDEC Standard No. 220-1A Page 4 Keywords 3.3Several keywords are used to differe

40、ntiate levels of requirements and options, as follow: Can - A keyword used for statements of possibility and capability, whether material, physical, or causal (can equals is able to). Expected - A keyword used to describe the behavior of the hardware or software in the design models assumed by this

41、standard. Other hardware and software design models may also be implemented. Ignored - A keyword that describes bits, bytes, quadlets, or fields whose values are not checked by the recipient. Mandatory - A keyword that indicates items required to be implemented as defined by this standard. May - A k

42、eyword that indicates a course of action permissible within the limits of the standard (may equals is permitted). Must - The use of the word must is deprecated and shall not be used when stating mandatory requirements; must is used only to describe unavoidable situations. Optional - A keyword that d

43、escribes features which are not required to be implemented by this standard. However, if any optional feature defined by the standard is implemented, it shall be implemented as defined by the standard. Reserved - A keyword used to describe objectsbits, bytes, and fieldsor the code values assigned to

44、 these objects in cases where either the object or the code value is set aside for future standardization. Usage and interpretation may be specified by future extensions to this or other standards. A reserved object shall be zeroed or, upon development of a future standard, set to a value specified

45、by such a standard. The recipient of a reserved object shall not check its value. The recipient of a defined object shall check its value and reject reserved code values. Shall - A keyword that indicates a mandatory requirement strictly to be followed in order to conform to the standard and from whi

46、ch no deviation is permitted (shall equals is required to). Designers are required to implement all such mandatory requirements to assure interoperability with other products conforming to this standard. Should - A keyword used to indicate that among several possibilities one is recommended as parti

47、cularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited (should equals is recommended that). Will - The use of the word will is d

48、eprecated and shall not be used when stating mandatory requirements; will is only used in statements of fact. Abbreviations 3.4etc. - And so forth (Latin: et cetera) e.g. - For example (Latin: exempli gratia) i.e. - That is (Latin: id est) JEDEC Standard No. 220-1A Page 5 Conventions 3.5UFS specific

49、ation follows some conventions used in SCSI documents since it adopts several SCSI standards. A binary number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 and 1 immediately followed by a lower-case b (e.g., 0101b). Spaces may be included in binary number representations to increase readability or delineate field boundaries (e.g., 0 0101 1010b). A hexadecimal number is represented in this standard by any sequence of digits consis