From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?windows-1252?Q?Andreas_F=E4rber?= Subject: Re: [PATCH v4 5/6] Documentation: dt-bindings: Add binding info for X-Gene QMTM UIO driver Date: Sun, 16 Nov 2014 11:20:34 +0100 Message-ID: <54687A72.6060208@suse.de> References: <1415864722-2800-1-git-send-email-ankit.jindal@linaro.org> <1415864722-2800-6-git-send-email-ankit.jindal@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Ankit Jindal , Tushar Jagad Cc: Anup Patel , devicetree@vger.kernel.org, Varka Bhadram , Russell King - ARM Linux , Greg Kroah-Hartman , Guenter Roeck , "Hans J. Koch" , "linux-kernel@vger.kernel.org List" , patches , Rob Herring , Kumar Gala , linux-arm-kernel List-Id: devicetree@vger.kernel.org Am 16.11.2014 um 05:26 schrieb Anup Patel: > On Thu, Nov 13, 2014 at 1:15 PM, Ankit Jindal wrote: >> This patch adds device tree binding documentation for >> X-Gene QMTM UIO driver. >> >> Signed-off-by: Ankit Jindal >> Signed-off-by: Tushar Jagad >> --- >> .../devicetree/bindings/uio/uio_xgene_qmtm.txt | 51 +++++++++= +++++++++++ >> 1 file changed, 51 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/uio/uio_xgene_= qmtm.txt >> >> diff --git a/Documentation/devicetree/bindings/uio/uio_xgene_qmtm.tx= t b/Documentation/devicetree/bindings/uio/uio_xgene_qmtm.txt >> new file mode 100644 >> index 0000000..ed85bc6 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/uio/uio_xgene_qmtm.txt >> @@ -0,0 +1,51 @@ >> +APM X-Gene QMTM 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. >> + >> +Required properties: >> +- compatible: Should be "apm,xgene-qmtm" >> +- reg: Address and length of the register set for the device. It co= ntains the >> + information of registers in the same order as described by reg-na= mes. >> +- 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-memory: Points to the phandle of the node defining memory l= ocation for >> + creating QMTM queues. This must point to the reserved-memor= y node >> + (as-per reserved memory bindings). It is expected that size= and >> + location of qpool memory will be configurable via bootloade= r. >> +- 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 a= nd >> + device id) for the queues belonging to this device. >> + >> +Example: >> + qmtm1_uio_qpool: qmtm1_uio_qpool { >> + reg =3D <0x0 0x0 0x0 0x0> Trailing semicolon is missing. >> + }; >> + >> + qmtm1clk: qmtmclk@1f20c000 { >> + compatible =3D "apm,xgene-device-clock"; >> + clock-output-names =3D "qmtm1clk"; >> + status =3D "ok" "okay" and missing semicolon, but you could probably drop the status property here. >> + }; >> + >> + qmtm1_uio: qmtm_uio@1f200000 { >> + compatible =3D "apm,xgene-qmtm"; >> + status =3D "disabled"; >> + reg =3D <0x0 0x1f200000 0x0 0x10000>, >> + <0x0 0x1b000000 0x0 0x400000>; >> + reg-names =3D "csr", "fabric"; >> + qpool =3D <&qmtm1_uio_qpool>; >=20 > Small typo, this should be qpool-memory =3D <...>; >=20 >> + clocks =3D <&qmtm1clk 0>; >> + num-queues =3D <0x400>; >> + devid =3D <1>; >> + }; >> + >> + /* Board-specific peripheral configurations */ >> + &qmtm1_uio { >> + status =3D "ok"; "okay" as canonical spelling. >> + }; Regards, Andreas --=20 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 21284 AG N=FCrn= berg