From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by mx.groups.io with SMTP id smtpd.web11.1152.1611707340543414322 for ; Tue, 26 Jan 2021 16:29:00 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@apple.com header.s=20180706 header.b=Xgzaj8GU; spf=pass (domain: apple.com, ip: 17.171.2.68, mailfrom: afish@apple.com) Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.42/8.16.0.42) with SMTP id 10R0OCd3007911; Tue, 26 Jan 2021 16:28:59 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : content-type : mime-version : subject : date : references : to : in-reply-to : message-id; s=20180706; bh=nEQawDA1uqb1g5rpTyQxb0/KQmeAnhtbgZkNJnty0aM=; b=Xgzaj8GUYvnguYdAreVOl8Ur03dlJJdQHd9VKztx02jkRopptDncRqq9QjSttsBalHp4 pC8gnn14DI6id6tgyfxsxMeDVIY50gbexZ0Cqbg56dIeZ/FMYAb/Jw2DvXJ5sjsIeXah o8rORTG1afxxedFKZavgDNhY9kam4K0JBLjvpBbrIdxmDyR0fCi+WCmJPZZi6SDzi28m G/hxr8hGsSjUPu/ikXQFUbxQ3trXu19nLYAhMB/gc+2iuIAdtYKnO1dH6Q6R2RAXXd3P dDEaO6ZhWgVpPTkwr4Pb0+mhm2XzIvNhQ3VpwGinrdL8kFvi9YriK00AMkhtJvglKWQ+ NQ== Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com [10.225.203.151]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 368hbwqna1-5 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 26 Jan 2021 16:28:59 -0800 Received: from rn-mailsvcp-mmp-lapp02.rno.apple.com (rn-mailsvcp-mmp-lapp02.rno.apple.com [17.179.253.15]) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPS id <0QNK00ZIYHC9S7I0@rn-mailsvcp-mta-lapp03.rno.apple.com>; Tue, 26 Jan 2021 16:28:57 -0800 (PST) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp02.rno.apple.com by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) id <0QNK00O00H5ZKB00@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Tue, 26 Jan 2021 16:28:57 -0800 (PST) X-Va-A: X-Va-T-CD: c46dc31de0c639b699dcbd3bcbd18efd X-Va-E-CD: ba55596b4c0f0364096f9f95198e05c7 X-Va-R-CD: 8442540bbe2b3990b8efd1a1ef1a5be2 X-Va-CD: 0 X-Va-ID: e84bc3a3-1972-46b9-b669-186dd587e37c X-V-A: X-V-T-CD: c46dc31de0c639b699dcbd3bcbd18efd X-V-E-CD: ba55596b4c0f0364096f9f95198e05c7 X-V-R-CD: 8442540bbe2b3990b8efd1a1ef1a5be2 X-V-CD: 0 X-V-ID: 0ecdc4e0-7831-4b5e-bd0a-88625a5afa46 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343,18.0.737 definitions=2021-01-26_11:2021-01-26,2021-01-26 signatures=0 Received: from [17.235.34.180] (unknown [17.235.34.180]) by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPSA id <0QNK00TP2HC8L900@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Tue, 26 Jan 2021 16:28:56 -0800 (PST) From: "Andrew Fish" MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.1\)) Subject: Re: [edk2-devel] Questions/doubts about UFS device on UEFI Date: Tue, 26 Jan 2021 16:28:56 -0800 References: To: edk2-devel-groups-io , renan.moraes2@fit-tecnologia.org.br In-reply-to: Message-id: <8875C8BD-DB26-448F-AA6D-796C5B1DA6A6@apple.com> X-Mailer: Apple Mail (2.3654.20.0.2.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343,18.0.737 definitions=2021-01-26_11:2021-01-26,2021-01-26 signatures=0 Content-type: multipart/alternative; boundary="Apple-Mail=_EAE77482-68FF-400C-9C52-AF63705637C1" --Apple-Mail=_EAE77482-68FF-400C-9C52-AF63705637C1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jan 26, 2021, at 9:23 AM, renan.moraes2 via groups.io wrote: >=20 > Good afternoon, > > We are studying how to communicate with Universal Flash Storage (UFS) de= vice on UEFI environment. The first step is identify the UFS device, we are= using the system Lenovo Flex 5G (It has Snapdragon processor + UFS device)= . > > We tried to identify the UFS device in three ways: > > 1 - Specific UEFI protocols (UFS_DEVICE_CONFIG_PROTOCOL / UFS_HOST_CONTR= OLLER_PROTOCOL) -> None of these protocols could be found on our test syste= ms, we compiled the EDK II 2020 (edk2-stable202005) available drivers (UfsP= assThru and UfsPciHc) and loaded them. However, these drivers can't detect = the UFS device. > > 2 - Device Path -> Tried to identify by its type (Type 3 =E2=80=93 Messa= ging Device Path) and subtype (Sub-Type 25 =E2=80=93 UFS), but could not fi= nd any matches. > > 3 - Pci bus -> Tried to identify by its class (01h - Mass Storage Contro= ller) and subclass (09h - Universal Flash Storage controller), but could no= t find any matches. > > We would like to know if there is an alternative UEFI UFS driver or othe= r methods to identify and communicate with this type of storage device. > Some times people chose to abstract devices more generically so for exampl= e just produce EFI_BLOCK_IO_PROTOCOL for a generic disk like device.=20 Some times people chose to not have EFI drivers for devices they don=E2=80= = =99t support booting from, it is firmware after all.=20 Sometimes on ARM devices the SoC just have MMIO devices at magic memory ad= dresses. So your best bet might be figuring out how the hardware works on y= our device from a data sheet.=20 Thanks, Andrew Fish > Thank you in advance. >=20 --Apple-Mail=_EAE77482-68FF-400C-9C52-AF63705637C1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Jan 26, 2021, at 9:23 AM= , renan.moraes2 via groups.io &= lt;renan.moraes2=3Dfit-tecnologia.org.br@groups.io> wrote:
=
Goo= d afternoon,
 
We are studying how to communicate with Universal Flash St= orage (UFS) device on UEFI environment. The first step is identify the UFS = device, we are using the system Lenovo Flex 5G (It has Snapdragon processor= + UFS device).
 
We tried to identify the UFS device in three ways:
 
1 - Specific UEFI protocols (UFS_DEVICE_CONFIG_PROTOCOL / = UFS_HOST_CONTROLLER_PROTOCOL) -> None of these protocols could be found = on our test systems, we compiled the EDK II 2020 (edk2-stable202005) availa= ble drivers (UfsPassThru and UfsPciHc) and loaded them. However, these driv= ers can't detect the UFS device.
 
2 - Device Path -> Tried to identify by its type (Type = 3 =E2=80=93 Messaging Device Path) and subtype (Sub-Type 25 =E2=80=93 UFS),= but could not find any matches.
 
3 - Pci bus -> Tried to identify by its class (01h - Ma= ss Storage Controller) and subclass (09h - Universal Flash Storage controll= er), but could not find any matches.
 
We would like to know if there is an alternative UEFI UFS = driver or other methods to identify and communicate with this type of stora= ge device.
 

<= div>Some times people chose to abstract devices more generically so for exa= mple just produce EFI_BLOCK_IO_PROTOCOL for a generic disk like device= . 

Some times people chose to not = have EFI drivers for devices they don=E2=80=99t support booting from, it is= firmware after all. 

Sometimes on= ARM devices the SoC just have MMIO devices at magic memory addresses. So y= our best bet might be figuring out how the hardware works on your device fr= om a data sheet. 

Thanks,

Andrew Fish

Thank you in advance.

--Apple-Mail=_EAE77482-68FF-400C-9C52-AF63705637C1--