From: Krzysztof Kozlowski <krzk@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>, linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] arm64: dts: qcom: sm6350: Add UFS nodes
Date: Sun, 20 Mar 2022 12:00:39 +0100 [thread overview]
Message-ID: <f61abc2b-3ce8-7b1f-3d28-8a4a03ec58eb@kernel.org> (raw)
In-Reply-To: <CIO22P1JZY5F.1BYJF4HT2OOUW@otso>
On 19/03/2022 19:29, Luca Weiss wrote:
> Hi Krzysztof,
>
> On Sat Mar 19, 2022 at 3:43 PM CET, Krzysztof Kozlowski wrote:
>> On 18/03/2022 19:30, Luca Weiss wrote:
>>> Add the necessary nodes for UFS and its PHY.
>>>
>>> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
>>> ---
>>> arch/arm64/boot/dts/qcom/sm6350.dtsi | 79 ++++++++++++++++++++++++++++
>>> 1 file changed, 79 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/sm6350.dtsi b/arch/arm64/boot/dts/qcom/sm6350.dtsi
>>> index d7c9edff19f7..c5c93b6bcd2a 100644
>>> --- a/arch/arm64/boot/dts/qcom/sm6350.dtsi
>>> +++ b/arch/arm64/boot/dts/qcom/sm6350.dtsi
>>> @@ -541,6 +541,85 @@ uart2: serial@98c000 {
>>> };
>>> };
>>>
>>> + ufs_mem_hc: ufshc@1d84000 {
>>
>> Generic node name, so ufs.
>
> With the node name changes UFS doesn't probe anymore.
>
> [ 1.893762] ufshcd-qcom 1d84000.ufs: ufshcd_variant_hba_init: variant qcom init failed err -19
> [ 1.902674] ufshcd-qcom 1d84000.ufs: Initialization failed
> [ 1.908391] ufshcd-qcom 1d84000.ufs: ufshcd_pltfrm_init() failed -19
>
> I didn't debug this in detail but it's likely from the
> androidboot.bootdevice=1d84000.ufshc parameter in cmdline that
> ufs-qcom.c uses to fail probe with -ENODEV for all UFS other than the
> selected one. Not sure why this behavior exists in mainline (didn't look
> into this either).
>
> This cmdline parameter (among many others) is added by the stock
> bootloader and as far as I know there's no way to turn that off.
I see now in the driver weird Android code like:
static char android_boot_dev[ANDROID_BOOT_DEV_MAX];
....
if (strlen(android_boot_dev) && strcmp(android_boot_dev, dev_name(dev)))
This is wrong. How is Android boot arguments needed for UFS? UFS is
independent of Android... what if you run it with different bootloader
and different system?
I understand that it is inconvenient for you to change the name, but
looking at driver code, I insist even more. :)
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-20 11:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 18:29 [PATCH 0/6] UFS support on SM6350 & FP4 Luca Weiss
2022-03-18 18:29 ` [PATCH 1/6] scsi: ufs: dt-bindings: Add SM6350 compatible string Luca Weiss
2022-03-19 14:38 ` Krzysztof Kozlowski
2022-03-19 14:41 ` Krzysztof Kozlowski
2022-03-21 11:48 ` Alim Akhtar
2022-03-18 18:30 ` [PATCH 2/6] dt-bindings: phy: qcom,qmp: Add SM6350 UFS PHY bindings Luca Weiss
2022-03-19 14:40 ` Krzysztof Kozlowski
2022-03-18 18:30 ` [PATCH 3/6] phy: qcom-qmp: Add SM6350 UFS PHY support Luca Weiss
2022-03-18 18:30 ` [PATCH 4/6] pinctrl: qcom: sm6350: fix order of UFS & SDC pins Luca Weiss
2022-04-17 23:38 ` Linus Walleij
2022-03-18 18:30 ` [PATCH 5/6] arm64: dts: qcom: sm6350: Add UFS nodes Luca Weiss
2022-03-19 14:43 ` Krzysztof Kozlowski
2022-03-19 18:29 ` Luca Weiss
2022-03-20 11:00 ` Krzysztof Kozlowski [this message]
2022-03-18 18:30 ` [PATCH 6/6] arm64: dts: qcom: sm7225-fairphone-fp4: Enable UFS Luca Weiss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f61abc2b-3ce8-7b1f-3d28-8a4a03ec58eb@kernel.org \
--to=krzk@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox