From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Antoine Tenart" <atenart@kernel.org>,
"Sam Shih" <sam.shih@mediatek.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
linux-crypto@vger.kernel.org, linux-mediatek@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH RFC] dt-bindings: crypto: inside-secure,safexcel: make eip/mem IRQs optional
Date: Tue, 2 Jan 2024 11:31:08 -0700 [thread overview]
Message-ID: <CAL_Jsq+hpOS-rdOYasJ1dzU6d_vVDWv2CseRhYmNHA2H_p=_pw@mail.gmail.com> (raw)
In-Reply-To: <20240101114432.28139-1-zajec5@gmail.com>
On Mon, Jan 1, 2024 at 4:45 AM Rafał Miłecki <zajec5@gmail.com> wrote:
>
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Binding for this cryptographic engine defined 6 interrupts since its
> beginning. It seems however only 4 rings IRQs are really required for
> operating this hardware. Linux driver doesn't use "eip" or "mem" IRQs
> and it isn't clear if they are always available (MT7986 SoC binding
> doesn't specify them).
>
> This deals with:
> arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: crypto@10320000: interrupts: [[0, 116, 4], [0, 117, 4], [0, 118, 4], [0, 119, 4]] is too short
> from schema $id: http://devicetree.org/schemas/crypto/inside-secure,safexcel.yaml#
> arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: crypto@10320000: interrupt-names: ['ring0', 'ring1', 'ring2', 'ring3'] is too short
> from schema $id: http://devicetree.org/schemas/crypto/inside-secure,safexcel.yaml#
Which platform does the schema currently match? None, because the
Marvell ones get these:
28 crypto@800000: interrupt-names:5: 'mem' was expected
28 crypto@800000: interrupt-names:4: 'eip' was expected
28 crypto@800000: interrupt-names:3: 'ring3' was expected
28 crypto@800000: interrupt-names:2: 'ring2' was expected
28 crypto@800000: interrupt-names:1: 'ring1' was expected
28 crypto@800000: interrupt-names:0: 'ring0' was expected
28 crypto@800000: 'dma-coherent' does not match any of the
regexes: 'pinctrl-[0-9]+'
(28 is the number of occurrences)
The existing list of names defines the order AND index. Since there
are 2 versions already in use, you have to define 2 lists.
>
> Cc: Antoine Tenart <atenart@kernel.org>
> Ref: ecc5287cfe53 ("arm64: dts: mt7986: add crypto related device nodes")
Not a documented tag. Don't make-up your own ones.
> Cc: Sam Shih <sam.shih@mediatek.com>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../devicetree/bindings/crypto/inside-secure,safexcel.yaml | 2 ++
> 1 file changed, 2 insertions(+)
prev parent reply other threads:[~2024-01-02 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 11:44 [PATCH RFC] dt-bindings: crypto: inside-secure,safexcel: make eip/mem IRQs optional Rafał Miłecki
2024-01-02 18:31 ` Rob Herring [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='CAL_Jsq+hpOS-rdOYasJ1dzU6d_vVDWv2CseRhYmNHA2H_p=_pw@mail.gmail.com' \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=atenart@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=rafal@milecki.pl \
--cc=sam.shih@mediatek.com \
--cc=zajec5@gmail.com \
/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).