lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 30 Sep 2014 09:56:08 +0530 From: Ankit Jindal <ankit.jindal@...aro.org> To: linux-kernel@...r.kernel.org Cc: "Hans J. Koch" <hjk@...sjkoch.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, patches@....com, linux-arm-kernel@...ts.infradead.org, Rob Herring <robh+dt@...nel.org>, Tushar Jagad <tushar.jagad@...aro.org>, Russell King - ARM Linux <linux@....linux.org.uk>, devicetree@...r.kernel.org, Ankit Jindal <ankit.jindal@...aro.org> Subject: [PATCH v2 5/6] Documentation: dt-bindings: Add binding info for X-Gene QMTM UIO driver This patch adds device tree binding documentation for X-Gene QMTM UIO driver. Signed-off-by: Ankit Jindal <ankit.jindal@...aro.org> Signed-off-by: Tushar Jagad <tushar.jagad@...aro.org> --- .../devicetree/bindings/uio/uio_xgene_qmtm.txt | 53 ++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 Documentation/devicetree/bindings/uio/uio_xgene_qmtm.txt diff --git a/Documentation/devicetree/bindings/uio/uio_xgene_qmtm.txt b/Documentation/devicetree/bindings/uio/uio_xgene_qmtm.txt new file mode 100644 index 0000000..288ed92 --- /dev/null +++ b/Documentation/devicetree/bindings/uio/uio_xgene_qmtm.txt @@ -0,0 +1,53 @@ +APM X-Gene QMTM UIO nodes + +The Applied Micro X-Gene SOC has on-chip QMTM (Queue manager +and Traffic manager). It is a device for managing hardware queues. +It also implements QoS among hardware queues hence term "traffic" +manager is present in its name. QMTM UIO nodes are defined for user +space access to this device using UIO framework. + +Required properties: +- compatible: Should be "apm,xgene-qmtm" +- reg: Address and length of the register set for the device. It contains the + information of registers in the same order as described by reg-names. +- reg-names: Should contain the register set names + - "csr": QMTM control and status register address space. + - "fabric": QMTM memory mapped access to queue states. +- qpool: Points to the phandle of the node defining memory location for + creating QMTM queues. This could point either to the reserved-memory + node (as-per reserved memory bindings) or to the node of on-chip + SRAM etc. It is expected that size and location of qpool memory will + be configurable via bootloader. +- clocks: Reference to the clock entry. +- num-queues: Number of queues under this QMTM device. +- devid: QMTM identification number for the system having multiple QMTM devices. + This is used to form a unique id (a tuple of queue number and + device id) for the queues belonging to this device. + +Example: + qmtm1_uio_qpool: qmtm1_uio_qpool { + reg = <0x0 0x0 0x0 0x0> + }; + + qmtm1clk: qmtmclk@...0c000 { + compatible = "apm,xgene-device-clock"; + clock-output-names = "qmtm1clk"; + status = "ok"; + }; + + qmtm1_uio: qmtm_uio@...00000 { + compatible = "apm,xgene-qmtm"; + status = "disabled"; + reg = <0x0 0x1f200000 0x0 0x10000>, + <0x0 0x1b000000 0x0 0x400000>; + reg-names = "csr", "fabric"; + qpool = <&qmtm1_uio_qpool>; + clocks = <&qmtm1clk 0>; + num-queues = <0x400>; + devid = <1>; + }; + + /* Board-specific peripheral configurations */ + &qmtm1_uio { + status = "ok"; + }; -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists