From: Sudeep Holla <sudeep.holla@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: firmware: arm,scpi: Add missing maxItems to shmem property
Date: Wed, 16 Feb 2022 16:53:07 +0000 [thread overview]
Message-ID: <20220216165307.4z6muko6b2kq437c@bogus> (raw)
In-Reply-To: <CAMuHMdV6yWSAx3uNcjqmq-p90sVykZAzSHPt5EONzVkdTj1vvQ@mail.gmail.com>
Hi Geert,
On Wed, Feb 16, 2022 at 03:55:35PM +0100, Geert Uytterhoeven wrote:
>
> In the absence of maxItems, the validator assumes it is equal to minItems,
> so we do need a sensible maxItems value here.
Ah OK, makes sense.
> Any suggestions? 16? 64?
>
I did a quick look and only 2 platforms use it(juno/amlogic meson).
Juno can go upto max of 62 theoretically but I don't think we we go beyond 4
due to associated shmem limitation. So maxitem of 4 should work just fine
for now. Since it is obsolete spec, I don't see any new extensions or users.
So you can add my ACK for the value of 4. 2 must work too but since I have
tested juno with 4, I would like to keep that possibility.
--
Regards,
Sudeep
prev parent reply other threads:[~2022-02-16 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 13:21 [PATCH] dt-bindings: firmware: arm,scpi: Add missing maxItems to shmem property Geert Uytterhoeven
2022-02-16 13:34 ` Krzysztof Kozlowski
2022-02-16 13:42 ` Geert Uytterhoeven
2022-02-16 13:52 ` Krzysztof Kozlowski
2022-02-16 14:39 ` Sudeep Holla
2022-02-16 14:55 ` Geert Uytterhoeven
2022-02-16 16:53 ` Sudeep Holla [this message]
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=20220216165307.4z6muko6b2kq437c@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.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).