From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
"'Chanho Park'" <chanho61.park@samsung.com>
Cc: <linux-samsung-soc@vger.kernel.org>
Subject: RE: ExynosAutov9 SDAK UFS phy dtbs check error
Date: Wed, 6 Jul 2022 16:36:24 +0530 [thread overview]
Message-ID: <02d101d89128$6f90ce70$4eb26b50$@samsung.com> (raw)
In-Reply-To: <f1e03b78-f844-6eec-2ace-d177af59f0c9@linaro.org>
>-----Original Message-----
>From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@linaro.org]
>Sent: Wednesday, July 6, 2022 3:25 PM
>To: Chanho Park <chanho61.park@samsung.com>; Alim Akhtar
><alim.akhtar@samsung.com>
>Cc: linux-samsung-soc@vger.kernel.org
>Subject: Re: ExynosAutov9 SDAK UFS phy dtbs check error
>
>On 06/07/2022 11:53, Krzysztof Kozlowski wrote:
>> Hi Chanho,
>>
>> When running dtbs_check I found:
>> arch/arm64/boot/dts/exynos/exynosautov9-sadk.dtb: phy@17e04000: clocks:
>> [[10]] is too short
>>
>> From schema: Documentation/devicetree/bindings/phy/samsung,ufs-
>phy.yaml
>>
>> arch/arm64/boot/dts/exynos/exynosautov9-sadk.dtb: phy@17e04000:
>> clock-names: ['ref_clk'] is too short
>>
>> From schema: Documentation/devicetree/bindings/phy/samsung,ufs-
>phy.yaml
>>
>>
>> and so on. It seems you miss there clocks.
>
>+Cc Alim.
>
Thanks Krzysztof adding me and for reporting.
>Tesla FSD has the same problem:
>tesla/fsd-evb.dtb: ufs-phy@15124000: clocks: [[35, 2]] is too short
>
We need to update the binding for the newer SoCs which does not have PHY-(rx,tx)-symbol-clocks.
Phy-ref clock is only required for all the SoC and based on the SoC compatible phy-{rx,tx}-symoble clocks can be selected.
>
>Best regards,
>Krzysztof
prev parent reply other threads:[~2022-07-06 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 9:53 ExynosAutov9 SDAK UFS phy dtbs check error Krzysztof Kozlowski
2022-07-06 9:54 ` Krzysztof Kozlowski
2022-07-06 10:54 ` Chanho Park
2022-07-06 11:15 ` Alim Akhtar
2022-07-07 0:45 ` Chanho Park
2022-07-06 15:03 ` Krzysztof Kozlowski
2022-07-07 0:46 ` Chanho Park
2022-07-06 11:06 ` Alim Akhtar [this message]
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='02d101d89128$6f90ce70$4eb26b50$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.