blob: c8077cb155235c403ae31c2f8f546a25a42e8f54 [file] [log] [blame]
AnilKumar Chimatae78789a2017-04-07 12:18:46 -07001* QCEDEV (QTI Crypto Engine Device)
2
3Required properties:
4 - compatible : should be "qcom,qcedev"
5 - reg : should contain crypto, BAM register map.
6 - reg-names : should contain the crypto and bam base register names.
7 - interrupts : should contain crypto BAM interrupt.
8 - qcom,bam-pipe-pair : should contain crypto BAM pipe pair index.
9 - qcom,ce-hw-instance : should contain crypto HW instance.
10 - qcom,msm_bus,name: Should be "qcedev-noc"
11 - qcom,msm_bus,num_cases: Depends on the use cases for bus scaling
12 - qcom,msm_bus,active-only: Boolean flag for context of request (actve/dual)
13 - qcom,msm_bus,num_paths: The paths for source and destination ports
14 - qcom,msm_bus,vectors: Vectors for bus topology.
15 - qcom,ce-device: Device number.
16 - qcom,ce-opp-freq: indicates the CE operating frequency in Hz, changes from target to target.
17
18Optional properties:
19 - qcom,ce-hw-shared : optional, indicates if the hardware is shared between EE.
20 - qcom,ce-hw-key : optional, indicates if the hardware supports use of HW KEY.
21 - qcom,support-core-clk-only : optional, indicates if the HW supports single crypto core clk.
22 - qcom,bsm-ee : optional, indicate the BAM EE value, changes from target to target. Default value is 1 if not specified.
23
24Example:
25
26 qcom,qcedev@fd440000 {
27 compatible = "qcom,qcedev";
28 reg = <0xfd440000 0x20000>,
29 <0xfd444000 0x8000>;
30 reg-names = "crypto-base","crypto-bam-base";
31 interrupts = <0 235 0>;
32 qcom,bam-pipe-pair = <0>;
33 qcom,ce-hw-instance = <1>;
34 qcom,ce-device = <0>;
35 qcom,ce-hw-shared;
36 qcom,msm-bus,name = "qcedev-noc";
37 qcom,msm-bus,num-cases = <2>;
38 qcom,msm-bus,num-paths = <1>;
39 qcom,msm-bus,vectors-KBps =
40 <56 512 0 0>,
41 <56 512 3936000 393600>,
42 qcom,ce-opp-freq = <100000000>;
43 };