On 28.12.2022 12:55, Krzysztof Kozlowski wrote: > On 28/12/2022 12:37, Konrad Dybcio wrote: >> >> >> 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 <krzysztof.kozlowski@xxxxxxxxxx> >>> --- >> 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/ > > Best regards, > Krzysztof >
