[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <be229afd-fa06-4f91-8cb1-4534a91152d5@kernel.org>
Date: Fri, 16 Aug 2024 09:16:46 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Marcus Glocker <marcus@...gul.ch>, Abel Vesa <abel.vesa@...aro.org>
Cc: Bjorn Andersson <andersson@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Marijn Suijten <marijn.suijten@...ainline.org>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Johan Hovold <johan@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>
Subject: Re: [PATCH v3 4/6] arm64: dts: qcom: Add UFS node
On 15/08/2024 18:59, Marcus Glocker wrote:
>>> Getting the right DTB in, at least opens the possibility to continue
>>> development in the driver area to further support this new hardware.
>>>
>>> But I won't touch your drivers, not my goal.
>>
>> Presumably, you do have the UFS working on your Book4 laptop, right?
>
> That's right, but ...
>
>> If so, I would expect you do have the PHY working as well and therefore
>> a patch that adds the X Elite compatible, right?
>
> ... I'm not using Linux on that laptop but OpenBSD. Hence, my UFS
> driver patch will be useless for you. If one of your developers gets
> his hand on that laptop, enabling UFS based on that DTB should be
> fairly straight forward.
>
> The reason why we are interested to get new DTS' in your tree, is
> because we're using the Linux DTS tree as a base, and then patch over
> it as of our requirements. The less patches we need to apply, the
> easier the maintenance is.
That's fine. You do not need drivers implementing bindings and DTS in
general.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Best regards,
Krzysztof
Powered by blists - more mailing lists