Hi Mark On 2015年10月30日 22:03, Mark Rutland wrote: > On Fri, Oct 30, 2015 at 04:22:49PM +0800, Zain Wang wrote: >> Add DT bindings documentation for the rk3288 crypto drivers. >> >> Signed-off-by: Zain Wang <zain.w...@rock-chips.com> >> --- >> .../devicetree/bindings/crypto/rk-crypto.txt | 31 >> ++++++++++++++++++++++ >> 1 file changed, 31 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/crypto/rk-crypto.txt >> >> diff --git a/Documentation/devicetree/bindings/crypto/rk-crypto.txt >> b/Documentation/devicetree/bindings/crypto/rk-crypto.txt >> new file mode 100644 >> index 0000000..1e50768 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/crypto/rk-crypto.txt >> @@ -0,0 +1,31 @@ >> +Rockchip Electronics And Security Accelerator >> + >> +Required properties: >> +- compatible: should be "rockchip,crypto" > Choose a more specific name. Rockchip could easily come up with another > crypto accelerator later. ok! done. rk3288_crypto may be better than crypto. >> +- reg: base physical address of the engine and length of memory mapped >> + region. >> +- interrupts: interrupt number >> +- clocks: clock specifiers >> +- clock-names: "aclk_crypto" used to clock data >> + "hclk_crypto" used to clock data >> + "srst_crypto" used to clock crypto accelerator >> + "apb_pclk" used to clock dma >> +-status: Enable > No need to mention the status property. ok! done! > Thanks, > Mark. > >> + >> +Examples: >> + >> + crypto: cypto-controller@ff8a0000 { >> + compatible = "rockchip,crypto"; >> + reg = <0xff8a0000 0x4000>; >> + interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>; >> + clocks = <&cru ACLK_CRYPTO>, >> + <&cru HCLK_CRYPTO>, >> + <&cru SRST_CRYPTO>, >> + <&cru ACLK_DMAC1>; >> + >> + clock-names = "aclk_crypto", >> + "hclk_crypto", >> + "srst_crypto", >> + "apb_pclk"; >> + status = "okay"; >> + }; >> -- >> 1.9.1 >> >> > Thanks Zain
-- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html