From: Krzysztof Kozlowski <hidden> Date: 2022-12-28 11:25:08
The GCC bindings expect core_bi_pll_test_se clock input, even if it is
optional:
sm8350-mtp.dtb: clock-controller@100000: clock-names:2: 'core_bi_pll_test_se' was expected
Signed-off-by: Krzysztof Kozlowski <redacted>
---
arch/arm64/boot/dts/qcom/sm8350.dtsi | 2 ++
1 file changed, 2 insertions(+)
From: Krzysztof Kozlowski <hidden> Date: 2022-12-28 11:25:19
This board uses RPMH, specifies "regulator-allow-set-load" for LDOs,
but doesn't specify any modes with "regulator-allowed-modes":
sm8350-sony-xperia-sagami-pdx214.dtb: regulators-0: ldo5: 'regulator-allowed-modes' is a dependency of 'regulator-allow-set-load'
Signed-off-by: Krzysztof Kozlowski <redacted>
---
arch/arm64/boot/dts/qcom/sm8350-sony-xperia-sagami.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
From: Konrad Dybcio <hidden> Date: 2022-12-28 11:37:39
On 28.12.2022 12:24, Krzysztof Kozlowski wrote:
The GCC bindings expect core_bi_pll_test_se clock input, even if it is
optional:
sm8350-mtp.dtb: clock-controller@100000: clock-names:2: 'core_bi_pll_test_se' was expected
Signed-off-by: Krzysztof Kozlowski <redacted>
---
Is it even going to be used by anybody, or should we just drop
it on the driver side as per usual?
Konrad
From: Krzysztof Kozlowski <hidden> Date: 2022-12-28 11:55:49
On 28/12/2022 12:37, Konrad Dybcio wrote:
On 28.12.2022 12:24, Krzysztof Kozlowski wrote:
quoted
The GCC bindings expect core_bi_pll_test_se clock input, even if it is
optional:
sm8350-mtp.dtb: clock-controller@100000: clock-names:2: 'core_bi_pll_test_se' was expected
Signed-off-by: Krzysztof Kozlowski <redacted>
---
Is it even going to be used by anybody, or should we just drop
it on the driver side as per usual?
It's mentioned as possible parent, so there might be users somewhere...
Or you want to say that other binding and DTS users cannot use that clock?
Best regards,
Krzysztof
From: Konrad Dybcio <hidden> Date: 2022-12-28 12:26:58
On 28.12.2022 12:55, Krzysztof Kozlowski wrote:
On 28/12/2022 12:37, Konrad Dybcio wrote:
quoted
On 28.12.2022 12:24, Krzysztof Kozlowski wrote:
quoted
The GCC bindings expect core_bi_pll_test_se clock input, even if it is
optional:
sm8350-mtp.dtb: clock-controller@100000: clock-names:2: 'core_bi_pll_test_se' was expected
Signed-off-by: Krzysztof Kozlowski <redacted>
---
Is it even going to be used by anybody, or should we just drop
it on the driver side as per usual?
It's mentioned as possible parent, so there might be users somewhere...
Or you want to say that other binding and DTS users cannot use that clock?
There's no driver (even downstream) for a supplier of this clock and it's
(probably) only used for early validation by qcom folks. What we're
interested in, as far as debugging clocks goes, is handled by debugcc [1].
Konrad
[1] https://github.com/andersson/debugcc/
The GCC bindings expect core_bi_pll_test_se clock input, even if it is
optional:
sm8350-mtp.dtb: clock-controller@100000: clock-names:2: 'core_bi_pll_test_se' was expected
Signed-off-by: Krzysztof Kozlowski <redacted>
---
Is it even going to be used by anybody, or should we just drop
it on the driver side as per usual?
It's mentioned as possible parent, so there might be users somewhere...
Or you want to say that other binding and DTS users cannot use that clock?
Yes. In the past few months we have been removing the core_bi_pll_test from the old clock drivers (and new clock drivers mostly lack them). Let's remove it from the rest of clock drivers.
From: Krzysztof Kozlowski <hidden> Date: 2022-12-28 14:25:54
On 28/12/2022 13:50, Dmitry Baryshkov wrote:
On 28/12/2022 13:55, Krzysztof Kozlowski wrote:
quoted
On 28/12/2022 12:37, Konrad Dybcio wrote:
quoted
On 28.12.2022 12:24, Krzysztof Kozlowski wrote:
quoted
The GCC bindings expect core_bi_pll_test_se clock input, even if it is
optional:
sm8350-mtp.dtb: clock-controller@100000: clock-names:2: 'core_bi_pll_test_se' was expected
Signed-off-by: Krzysztof Kozlowski <redacted>
---
Is it even going to be used by anybody, or should we just drop
it on the driver side as per usual?
It's mentioned as possible parent, so there might be users somewhere...
Or you want to say that other binding and DTS users cannot use that clock?
Yes. In the past few months we have been removing the core_bi_pll_test
from the old clock drivers (and new clock drivers mostly lack them).
Let's remove it from the rest of clock drivers.
If you are going to start doing the same work, please at least share it
upfront.
Best regards,
Krzysztof
The GCC bindings expect core_bi_pll_test_se clock input, even if it is
optional:
sm8350-mtp.dtb: clock-controller@100000: clock-names:2: 'core_bi_pll_test_se' was expected
Signed-off-by: Krzysztof Kozlowski <redacted>
---
Is it even going to be used by anybody, or should we just drop
it on the driver side as per usual?
It's mentioned as possible parent, so there might be users somewhere...
Or you want to say that other binding and DTS users cannot use that clock?
Yes. In the past few months we have been removing the core_bi_pll_test
from the old clock drivers (and new clock drivers mostly lack them).
Let's remove it from the rest of clock drivers.
If you are going to start doing the same work, please at least share it
upfront.
On Wed, 28 Dec 2022 12:24:55 +0100, Krzysztof Kozlowski wrote:
The GCC bindings expect core_bi_pll_test_se clock input, even if it is
optional:
sm8350-mtp.dtb: clock-controller@100000: clock-names:2: 'core_bi_pll_test_se' was expected
Applied, thanks!
[2/2] arm64: dts: qcom: sm8350-sony-xperia-sagami: specify which LDO modes are allowed
commit: 8ea261588fe98d171fcecf477a9f27aea8a06fd0
Best regards,
--
Bjorn Andersson [off-list ref]