Hello! > Booting with ACPI helps us to use generic Linux distribution > installers, but it is expected for users to switch to DT once the OS > is installed.
Thank you for clarification! Should I close my bugreport when Bjorn's "Qualcomm UFS device reset support" series will hit upstream, or I should wait for additional fix that applicable for ACPI boot as well? I don't know if this boot delay is Ok for generic installer image, and it's not up to me to decide this, which is why I ask. 02.09.2019, 16:12, "Lee Jones" <lee.jo...@linaro.org>: > On Fri, 30 Aug 2019, russianneuroman...@ya.ru wrote: > >> Hello! >> >> > I don't remember the exact splats seen, but I would suggest that this is >> > retested after applying the following series: >> > >> > >> https://lore.kernel.org/linux-arm-msm/20190828191756.24312-1-bjorn.anders...@linaro.org/T/#u >> >> Turns out this patches is already applied to kernel running on this device, >> but one line in dts was missing: >> >> https://github.com/aarch64-laptops/linux/pull/2 >> >> With this line issue is no longer reproducible with DT boot. Thank you! >> >> As I understand it's planned to eventually boot this devices via ACPI. >> >> @Lee Jones, is my understanding correct? > > No, not exactly. We can boot these devices using ACPI, but with > limited functionality (when compared with booting using DT). There > are too many black-boxes when booting with ACPI - something that can > only be resolved with Qualcomm's help. > > Booting with ACPI helps us to use generic Linux distribution > installers, but it is expected for users to switch to DT once the OS > is installed. > > -- > Lee Jones [李琼斯] > Linaro Services Technical Lead > Linaro.org │ Open source software for ARM SoCs > Follow Linaro: Facebook | Twitter | Blog
