From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
davem@davemloft.net, smueller@chronox.de, mark.rutland@arm.com,
devicetree@vger.kernel.org, linuxarm@huawei.com,
xuzaibo@huwei.com, fanghao11@huawei.com, liguozhu@hisilicon.com,
wangxiongfeng2@huawei.com
Subject: Re: [PATCH 1/3] dt-bindings: Add bindings for Hisilicon SEC crypto accelerators.
Date: Fri, 20 Jul 2018 17:38:44 +0100 [thread overview]
Message-ID: <20180720173844.000029a8@huawei.com> (raw)
In-Reply-To: <20180720163010.GA8047@rob-hp-laptop>
On Fri, 20 Jul 2018 10:30:10 -0600
Rob Herring <robh@kernel.org> wrote:
> On Mon, Jul 16, 2018 at 11:43:40AM +0100, Jonathan Cameron wrote:
> > The hip06 and hip07 SoCs contain a number of these crypto units which
> > accelerate AES and DES operations.
> >
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > ---
> > .../bindings/crypto/hisilicon,hip07-sec.txt | 69 ++++++++++++++++++++++
> > 1 file changed, 69 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/crypto/hisilicon,hip07-sec.txt b/Documentation/devicetree/bindings/crypto/hisilicon,hip07-sec.txt
> > new file mode 100644
> > index 000000000000..00b838706c98
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/crypto/hisilicon,hip07-sec.txt
> > @@ -0,0 +1,69 @@
> > +* Hisilicon hip07 Security Accelerator (SEC)
> > +
> > +Required properties:
> > +- compatible: Must contain one of
> > + - "hisilicon,hip06-sec"
> > + - "hisilicon,hip07-sec"
> > +- reg: Memory addresses and lengths of the memory regions used by the driver.
>
> You know my feelings about the word "driver" in bindings. :)
Oops. Will fix. Oddly rare I actually write one of these docs so making newbie
mistakes :(
>
> > + Region 0 has registers to control the backend processing engines.
> > + Region 1 has registers for functionality common to all queues.
> > + Regions 2-18 have registers for the individual queues which are isolated
> > + both in hardware and within the driver.
>
> It's always 16 queues? Might state that somewhere.
Technically complex because some of them may be in use by the secure world
and hence not available and not seen in the DT.
Right now the driver doesn't support that, and it's not happening on any
existing platforms but I was trying to avoid stating there were definitely
16 available. I guess if that happens I'll fix the binding when they do it.
(moderately unlikely to happen now given age of this platform, but you never
know).
>
> > +- interrupts: Interrupt specifiers.
> > + Refer to interrupt-controller/interrupts.txt for generic interrupt client node
> > + bindings.
> > + Interrupt 0 is for the SEC unit error queue.
> > + Interrupt 2N + 1 is the completion interrupt for queue N.
> > + Interrupt 2N + 2 is the error interrupt for queue N.
> > +- dma-coherent: The driver assumes coherent dma is possible.
> > +
> > +Optional properties:
> > +- iommus: The SEC units are behind smmu-v3 iommus.
> > + Refer to iommu/arm,smmu-v3.txt for more information.
> > +
> > +Example:
> > +Second socket, first unit chosen to illustrate need for 64 bit addresses.
>
> I don't follow the 64-bit address comment.
Without it the address is in the 32bit range so internal review raised
the question of why we needed to provide 64 bit registers as 32 bit ones
are more compact.
reg = <0xd000000 0x10000
etc
>
> > +
> > +p1_sec_a: sec@d2000000 {
>
> crypto@...
>
> The unit-address should be from the 1st reg entry and why isn't the
> 0x400 part included?
Will fix here an obviously in the DT patch itself.
>
> > + compatible = "hisilicon,hip07-sec";
> > + #address-cells = <2>;
> > + #size-cells = <2>;
>
> These aren't needed here as there are no child nodes.
Oops I always forget those.
>
> > + reg = <0x400 0xd0000000 0x0 0x10000
> > + 0x400 0xd2000000 0x0 0x10000
> > + 0x400 0xd2010000 0x0 0x10000
> > + 0x400 0xd2020000 0x0 0x10000
> > + 0x400 0xd2030000 0x0 0x10000
> > + 0x400 0xd2040000 0x0 0x10000
> > + 0x400 0xd2050000 0x0 0x10000
> > + 0x400 0xd2060000 0x0 0x10000
> > + 0x400 0xd2070000 0x0 0x10000
> > + 0x400 0xd2080000 0x0 0x10000
> > + 0x400 0xd2090000 0x0 0x10000
> > + 0x400 0xd20a0000 0x0 0x10000
> > + 0x400 0xd20b0000 0x0 0x10000
> > + 0x400 0xd20c0000 0x0 0x10000
> > + 0x400 0xd20d0000 0x0 0x10000
> > + 0x400 0xd20e0000 0x0 0x10000
> > + 0x400 0xd20f0000 0x0 0x10000
> > + 0x400 0xd2100000 0x0 0x10000>;
> > + interrupt-parent = <&p1_mbigen_sec_a>;
> > + iommus = <&p1_smmu_alg_a 0x600>;
> > + dma-coherent;
> > + interrupts = <576 4>,
> > + <577 1>,<578 4>,
>
> space needed after the comma.
>
> > + <579 1>,<580 4>,
> > + <581 1>,<582 4>,
> > + <583 1>,<584 4>,
> > + <585 1>,<586 4>,
> > + <587 1>,<588 4>,
> > + <589 1>,<590 4>,
> > + <591 1>,<592 4>,
> > + <593 1>,<594 4>,
> > + <595 1>,<596 4>,
> > + <597 1>,<598 4>,
> > + <599 1>,<600 4>,
> > + <601 1>,<602 4>,
> > + <603 1>,<604 4>,
> > + <605 1>,<606 4>,
> > + <607 1>,<608 4>;
> > +};
> > --
> > 2.16.2
Thanks Rob.
Jonathan
> >
> >
next prev parent reply other threads:[~2018-07-20 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 10:43 [PATCH 0/3] Hisilicon SEC crypto driver (hip06 / hip07) Jonathan Cameron
2018-07-16 10:43 ` [PATCH 1/3] dt-bindings: Add bindings for Hisilicon SEC crypto accelerators Jonathan Cameron
2018-07-20 16:30 ` Rob Herring
2018-07-20 16:38 ` Jonathan Cameron [this message]
2018-07-16 10:43 ` [PATCH 2/3] crypto: hisilicon SEC security accelerator driver Jonathan Cameron
2018-07-20 18:17 ` Stephan Müller
2018-07-23 14:33 ` Jonathan Cameron
2018-07-16 10:43 ` [PATCH 3/3] arm64: dts: hisi: add SEC crypto accelerator nodes for hip07 SoC Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2018-07-23 15:49 [PATCH V2 0/3] Hisilicon SEC crypto driver (hip06 / hip07) Jonathan Cameron
2018-07-23 15:49 ` [PATCH 1/3] dt-bindings: Add bindings for Hisilicon SEC crypto accelerators Jonathan Cameron
2018-07-31 21:41 ` Rob Herring
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=20180720173844.000029a8@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fanghao11@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=liguozhu@hisilicon.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=smueller@chronox.de \
--cc=wangxiongfeng2@huawei.com \
--cc=xuzaibo@huwei.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).