From: Vinod Koul <vkoul@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: dmaengine: qcom: gpi: Add minItems for interrupts
Date: Wed, 20 Apr 2022 16:06:02 +0530 [thread overview]
Message-ID: <Yl/iElIfHhmoOYOU@matsya> (raw)
In-Reply-To: <9d35e76e-5d98-b2d8-a22c-293adcbaadf0@linaro.org>
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
next prev parent reply other threads:[~2022-04-20 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 6:42 [PATCH] dt-bindings: dmaengine: qcom: gpi: Add minItems for interrupts Vinod Koul
2022-04-14 7:36 ` Krzysztof Kozlowski
2022-04-14 10:25 ` Vinod Koul
2022-04-14 11:44 ` Krzysztof Kozlowski
2022-04-20 10:36 ` Vinod Koul [this message]
2022-04-20 11:11 ` Krzysztof Kozlowski
2022-04-20 11:32 ` Vinod Koul
2022-04-20 12:06 ` Krzysztof Kozlowski
2022-04-20 12:41 ` Vinod Koul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yl/iElIfHhmoOYOU@matsya \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).