Messages in this thread | | | Date | Tue, 22 Mar 2022 19:14:46 +0100 | From | 'Krzysztof Kozlowski' <> | Subject | Re: [PATCH v2] ufs: qcom: drop custom Android boot parameters |
| |
On 21/03/2022 16:40, Alim Akhtar wrote: > > >> -----Original Message----- >> From: Krzysztof Kozlowski [mailto:krzk@kernel.org] >> Sent: Monday, March 21, 2022 8:49 PM >> To: Andy Gross <agross@kernel.org>; Bjorn Andersson >> <bjorn.andersson@linaro.org>; Alim Akhtar <alim.akhtar@samsung.com>; >> Avri Altman <avri.altman@wdc.com>; James E.J. Bottomley >> <jejb@linux.ibm.com>; Martin K. Petersen <martin.petersen@oracle.com>; >> linux-arm-msm@vger.kernel.org; linux-scsi@vger.kernel.org; linux- >> kernel@vger.kernel.org >> Cc: Krzysztof Kozlowski <krzk@kernel.org>; Amit Pundir >> <amit.pundir@linaro.org>; Luca Weiss <luca.weiss@fairphone.com>; Brian >> Masney <bmasney@redhat.com> >> Subject: [PATCH v2] ufs: qcom: drop custom Android boot parameters >> >> 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. This 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. >> >> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> >> Tested-by: Amit Pundir <amit.pundir@linaro.org> >> Tested-by: Luca Weiss <luca.weiss@fairphone.com> >> Reviewed-by: Brian Masney <bmasney@redhat.com> >> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org> >> > > Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
Ah, sorry, I think I missed your Rb from v1.
Best regards, Krzysztof
| |