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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220524022243.GA2625732-robh@kernel.org>
Date:   Mon, 23 May 2022 21:22:43 -0500
From:   Rob Herring <robh@...nel.org>
To:     Robert Marko <robimarko@...il.com>
Cc:     agross@...nel.org, bjorn.andersson@...aro.org, lgirdwood@...il.com,
        broonie@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, konrad.dybcio@...ainline.org,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v5 1/7] dt-bindings: regulator: qcom,spmi-regulator:
 Convert to dtschema

On Thu, May 19, 2022 at 03:30:09PM +0200, Robert Marko wrote:
> Convert the bindings of Qualcomm SPMI regulators to DT schema.
> 
> Signed-off-by: Robert Marko <robimarko@...il.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> ---
> Changes in v4:
> * Remove blank interrupts and interrupt-names as generic properties
> to only allow them per compatible
> 
> Changes in v3:
> * Remove quotes around refs
> * Use much stricter regex for regulator node matching
> * Add supply matching per compatible
> * Add blank interrupts and interrupt-names as generic properties
> 
> Changes in v2:
> * Remove the forgotten text bindings
> * Move allOf after patternProperties
> * Use my private email as the maintainer email
> 
> I am aware that syscon alone is not really acceptable, its converted
> directly from the old text bindings.
> 
> Any advice on how to solve this is appreciated.

Add a compatible for the block in question, but that means you have to 
have a schema for it. Or you can just drop the node. This binding isn't 
really about that node.

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ