RE: [PATCH V3 2/2] Documentation: crypto: Add DT binding info for the img hw hash accelerator

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Andrew

> -----Original Message-----
> From: abrestic@xxxxxxxxxx [mailto:abrestic@xxxxxxxxxx] On Behalf Of
> Andrew Bresticker
> Sent: 06 March 2015 21:50
> To: James Hartley
> Cc: linux-crypto@xxxxxxxxxxxxxxx
> Subject: Re: [PATCH V3 2/2] Documentation: crypto: Add DT binding info for
> the img hw hash accelerator
> 
> Hi James,
> 
> On Thu, Mar 5, 2015 at 7:01 PM, James Hartley <james.hartley@xxxxxxxxxx>
> wrote:
> > This adds the binding documentation for the Imagination Technologies
> > hash accelerator that provides hardware acceleration for
> > SHA1/SHA224/SHA256/MD5 hashes.  This hardware will be present in the
> > upcoming pistachio SoC.
> >
> > Signed-off-by: James Hartley <james.hartley@xxxxxxxxxx>
> 
> > diff --git a/Documentation/devicetree/bindings/crypto/img-hash.txt
> > b/Documentation/devicetree/bindings/crypto/img-hash.txt
> > new file mode 100644
> > index 0000000..7adc519
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/crypto/img-hash.txt
> > @@ -0,0 +1,27 @@
> > +Imagination Technologies hardware hash accelerator
> > +
> > +The hash accelerator provides hardware hashing acceleration for SHA1,
> > +SHA224, SHA256 and MD5 hashes
> > +
> > +Required properties:
> > +
> > +- compatible : "img,hash-accelerator"
> > +- reg : Offset and length of the register set for the module, and the
> > +DMA port
> > +- interrupts : The designated IRQ line for the hashing module.
> > +- dmas : DMA specifier as per
> > +Documentation/devicetree/bindings/dma/dma.txt
> > +- dma-names : Should be "tx"
> > +- clocks : Clock specifiers
> > +- clock-names : "hash_clk" Used to clock data through the accelerator
> > +               "hash_reg_clk" Used to clock the hash block registers
> 
> For the other IMG drivers that have been submitted, we've been  using "sys"
> as the name for the register gate clock.  Maybe we should do that here too to
> be consistent?

Yes, good idea

> 
> > +Example:
> > +
> > +       hash: hash@18149600 {
> > +       compatible = "img,hash-accelerator";
> > +               reg = <0x18149600 0x100, 0x18101100 0x4>;
> > +               interrupts = <GIC_SHARED 59 IRQ_TYPE_LEVEL_HIGH>;
> > +               dmas = <&dma 8 0xffffffff>;
> > +               dma-names = "tx";
> > +               clocks = <&cr_periph SYS_CLK_HASH>, <&clk_periph
> PERIPH_CLK_ROM>;
> > +               clock-names = "hash_clk, hash_reg_clk";
> 
> I think these are flipped (and you're missing some quotation marks).

Fixed. 

> 
> Otherwise this looks good to me.
> 
> -Andrew

Thanks for the review,

James
��.n��������+%������w��{.n�����{���{ay�ʇڙ���f���h������_�(�階�ݢj"��������G����?���&��





[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux