linux-kernel - Re: [PATCH] dt-bindings: soc: samsung: Fix I2C clocks order in USI binding example

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 15 Dec 2021 08:36:38 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To:     Sam Protsenko <semen.protsenko@...aro.org>,
        Rob Herring <robh+dt@...nel.org>
Cc:     devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: soc: samsung: Fix I2C clocks order in USI
 binding example

On 14/12/2021 18:09, Sam Protsenko wrote:
> Now that HSI2C binding [1] is converted to dt-schema format, it reveals
> incorrect HSI2C clocks order in USI binding example:
> 
>     .../exynos-usi.example.dt.yaml:
>     i2c@...20000: clock-names:0: 'hsi2c' was expected
>     From schema: .../i2c-exynos5.yaml
> 
>     .../exynos-usi.example.dt.yaml:
>     i2c@...20000: clock-names:1: 'hsi2c_pclk' was expected
>     From schema: .../i2c-exynos5.yaml
> 
> Change HSI2C clock order in USI binding example to satisfy HSI2C binding
> requirements and fix above warnings.
> 
> [1] Documentation/devicetree/bindings/i2c/i2c-exynos5.yaml
> 
> Signed-off-by: Sam Protsenko <semen.protsenko@...aro.org>
> ---
> NOTE: If possible, it can be squashed into "dt-bindings: soc: samsung:
>       Add Exynos USI bindings" patch (already applied in Krzysztof tree)
> 

I already merged it between branches, so no squashing.

Best regards,
Krzysztof