linux-kernel - Re: [PATCH v4 02/32] devicetree: bindings: scsi: HiSi SAS

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 16 Nov 2015 07:56:19 -0600
From:	Rob Herring <robh@...nel.org>
To:	John Garry <john.garry@...wei.com>
Cc:	JBottomley@...n.com, pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org, arnd@...db.de,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, linuxarm@...wei.com,
	john.garry2@...l.dcu.ie, hare@...e.de, xuwei5@...ilicon.com,
	zhangfei.gao@...aro.org
Subject: Re: [PATCH v4 02/32] devicetree: bindings: scsi: HiSi SAS

On Mon, Nov 16, 2015 at 09:05:48PM +0800, John Garry wrote:
> Add devicetree bindings for HiSilicon SAS driver.
> 
> Signed-off-by: John Garry <john.garry@...wei.com>
> Signed-off-by: Zhangfei Gao <zhangfei.gao@...aro.org>

Acked-by: Rob Herring <robh@...nel.org>

> ---
>  .../devicetree/bindings/scsi/hisilicon-sas.txt     | 69 ++++++++++++++++++++++
>  1 file changed, 69 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/scsi/hisilicon-sas.txt
> 
> diff --git a/Documentation/devicetree/bindings/scsi/hisilicon-sas.txt b/Documentation/devicetree/bindings/scsi/hisilicon-sas.txt
> new file mode 100644
> index 0000000..f67e761
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/scsi/hisilicon-sas.txt
> @@ -0,0 +1,69 @@
> +* HiSilicon SAS controller
> +
> +The HiSilicon SAS controller supports SAS/SATA.
> +
> +Main node required properties:
> +  - compatible : value should be as follows:
> +	(a) "hisilicon,hip05-sas-v1" for v1 hw in hip05 chipset
> +  - sas-addr : array of 8 bytes for host SAS address
> +  - reg : Address and length of the SAS register
> +  - hisilicon,sas-syscon: phandle of syscon used for sas control
> +  - ctrl-reset-reg : offset to controller reset register in ctrl reg
> +  - ctrl-reset-sts-reg : offset to controller reset status register in ctrl reg
> +  - ctrl-clock-ena-reg : offset to controller clock enable register in ctrl reg
> +  - queue-count : number of delivery and completion queues in the controller
> +  - phy-count : number of phys accessible by the controller
> +  - interrupts : Interrupts for phys, completion queues, and fatal
> +		sources; the interrupts are ordered in 3 groups, as follows:
> +			- Phy interrupts
> +			- Completion queue interrupts
> +			- Fatal interrupts
> +		Phy interrupts : Each phy has 3 interrupt sources:
> +			- broadcast
> +			- phyup
> +			- abnormal
> +		The phy interrupts are ordered into groups of 3 per phy
> +		(broadcast, phyup, and abnormal) in increasing order.
> +		Completion queue interrupts : each completion queue has 1
> +			interrupt source.
> +			The interrupts are ordered in increasing order.
> +		Fatal interrupts : the fatal interrupts are ordered as follows:
> +			- ECC
> +			- AXI bus
> +
> +Example:
> +	sas0: sas@...00000 {
> +		compatible = "hisilicon,hip05-sas-v1";
> +		sas-addr = [50 01 88 20 16 00 00 0a];
> +		reg = <0x0 0xc1000000 0x0 0x10000>;
> +		hisilicon,sas-syscon = <&pcie_sas>;
> +		ctrl-reset-reg = <0xa60>;
> +		ctrl-reset-sts-reg = <0x5a30>;
> +		ctrl-clock-ena-reg = <0x338>;
> +		queue-count = <32>;
> +		phy-count = <8>;
> +		dma-coherent;
> +		interrupt-parent = <&mbigen_dsa>;
> +		interrupts =    <259 4>,<263 4>,<264 4>,/* phy0 */
> +				<269 4>,<273 4>,<274 4>,/* phy1 */
> +				<279 4>,<283 4>,<284 4>,/* phy2 */
> +				<289 4>,<293 4>,<294 4>,/* phy3 */
> +				<299 4>,<303 4>,<304 4>,/* phy4 */
> +				<309 4>,<313 4>,<314 4>,/* phy5 */
> +				<319 4>,<323 4>,<324 4>,/* phy6 */
> +				<329 4>,<333 4>,<334 4>,/* phy7 */
> +				<336 1>,<337 1>,<338 1>,/* cq0-2 */
> +				<339 1>,<340 1>,<341 1>,/* cq3-5 */
> +				<342 1>,<343 1>,<344 1>,/* cq6-8 */
> +				<345 1>,<346 1>,<347 1>,/* cq9-11 */
> +				<348 1>,<349 1>,<350 1>,/* cq12-14 */
> +				<351 1>,<352 1>,<353 1>,/* cq15-17 */
> +				<354 1>,<355 1>,<356 1>,/* cq18-20 */
> +				<357 1>,<358 1>,<359 1>,/* cq21-23 */
> +				<360 1>,<361 1>,<362 1>,/* cq24-26 */
> +				<363 1>,<364 1>,<365 1>,/* cq27-29 */
> +				<366 1>,<367 1>/* cq30-31 */
> +				<376 4>,/* fatal ecc */
> +				<381 4>;/* fatal axi */
> +		status = "disabled";
> +	};
> -- 
> 1.9.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
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/