Messages in this thread | | | Date | Mon, 21 Mar 2022 09:44:03 -0400 | From | Brian Masney <> | Subject | Re: [RFT] ufs: qcom: drop custom Android boot parameters |
| |
On Sun, Mar 20, 2022 at 12:06:16PM +0100, Krzysztof Kozlowski wrote: > The QCOM UFS driver requires an androidboot.bootdevice command line > argument matching the UFS device name. If the name is different, it > refuses to probe. Thise androidboot.bootdevice is provided by > stock/vendor (from an Android-based device) bootloader. > > This does not make sense from Linux point of view. Driver should be > able to boot regardless of bootloader. Driver should not depend on some > Android custom environment data. > > Cc: Luca Weiss <luca.weiss@fairphone.com> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
I encountered that same code a few months ago and thought then that this code doesn't belong here.
Reviewed-by: Brian Masney <bmasney@redhat.com>
| |