Hello Greg k-h, On 2/13/2019 5:47 PM, Greg KH wrote: > On Wed, Feb 13, 2019 at 05:00:51PM +0000, Pedro Sousa wrote: >> Hi, >> >> On 2/13/2019 9:30 AM, Avri Altman wrote: >>>> >>>> I can see the issue, there is no straightforward way of having "ufs-bsg" >>>> without >>>> a device attached? >>> Right. >>> >>>> >>>> This or any other method of talking with UniPro and MPhy layers when there >>>> is no >>>> device are necessary for us. Do you see some good way of doing this? >>> I don't really know. >>> If you have access to the bootloader, then implement it there, >>> And call this functionality via fastboot getvar or fastboot oem. >> For us would be better if we manage to use it through the driver. >> >> Until now, from this thread I think there are two scenarios: >> >> When there's a device, through ufs-bsg: >> - ufs-utils: using the current ufs_bsg interface will have the capability to >> cover most of the scenarios that I can think of and will be the standard way to >> interact with the ufs driver. >> >> During bring up/debug without link to device: >> >> - My proposal is to create a debugFS interface: >> uic-cmd/ >> ├── dme-get >> ├── dme-set >> ├── dme-enable >> ├── dme-reset >> └── ... >> test-feature/ >> ├── PA_tf >> └── ... >> error-dump/ >> ├── UECPA >> ├── UECDL >> └── ... >> ... >> >> I kindly request the ecosystem feedback. > > Don't ever put anything in debugfs that you need for a "real" system > that you rely on, as it should not normally be present or mounted at > all. > > It's for debugging stuff only, please be aware of that. > > greg k-h > Thank you for the feedback. This interface is to be used for bring up scenarios or debug only when the bsg interface is not available. Pedro
