linux-kernel - Re: [PATCH] dt-bindings: dmaengine: qcom: gpi: Add minItems for interrupts

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: <Yl/iElIfHhmoOYOU@matsya>
Date:   Wed, 20 Apr 2022 16:06:02 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        linux-arm-msm@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        dmaengine@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: dmaengine: qcom: gpi: Add minItems for
 interrupts

On 14-04-22, 13:44, Krzysztof Kozlowski wrote:
> On 14/04/2022 12:25, Vinod Koul wrote:
> >>>        Interrupt lines for each GPI instance
> >>> +    minItems: 1
> >>
> >> This should be some real case minimum, not just 1. Unless really only
> >> one interrupt is also possible in existing variations?
> > 
> > So that depends on the channels available to use which can be worst case
> > of 1. Maximum is 13.. Most of the controllers are between 12-13, but we
> > dont want to change binding in future if controller has lesser channels
> > right?
> 
> If the choice is per SoC-controller, then the best would be to limit in
> allOf:if:then. However maybe the number of channels depends also on
> other factor (e.g. secure world configuration)?

That is quite right. So we wont know how many channels are made
available..

So is min 1 acceptable or do you have an alternate ?

-- 
~Vinod