Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965349AbbLRB6u (ORCPT ); Thu, 17 Dec 2015 20:58:50 -0500 Received: from szxga02-in.huawei.com ([119.145.14.65]:7147 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753683AbbLRB6t (ORCPT ); Thu, 17 Dec 2015 20:58:49 -0500 Subject: Re: [PATCH v10 1/4] dt-binding:Documents of the mbigen bindings To: Mark Rutland References: <1450353397-47668-1-git-send-email-majun258@huawei.com> <1450353397-47668-2-git-send-email-majun258@huawei.com> <20151217135247.GD13389@leverpostej> CC: , , , , , , , , , , , , , , , , , , , , , From: "majun (F)" Message-ID: <5673683C.2080304@huawei.com> Date: Fri, 18 Dec 2015 09:58:20 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20151217135247.GD13389@leverpostej> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.177.235.245] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.56736856.001D,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: fa3c71419b774100eadce0a4142b56eb Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2805 Lines: 100 Hi Mark: 在 2015/12/17 21:52, Mark Rutland 写道: > On Thu, Dec 17, 2015 at 07:56:34PM +0800, MaJun wrote: >> From: Ma Jun [...] >> +- compatible: Should be "hisilicon,mbigen-v2" >> + >> +- reg: Specifies the base physical address and size of the Mbigen >> + registers. >> + >> +- interrupt controller: Identifies the node as an interrupt controller >> + >> +- msi-parent: Specifies the MSI controller this mbigen use. >> + For more detail information,please refer to the generic msi-parent binding in >> + Documentation/devicetree/bindings/interrupt-controller/msi.txt. >> + >> +- num-msis:Specifies the total number of interrupt this device has. > > Is this the number of pins implemented? Or the number of pins that are > in use? > > The latter feels like something we can derive. num-msis means the total number of pins implemented. > >> +- #interrupt-cells : Specifies the number of cells needed to encode an >> + interrupt source. The value must be 2. >> + >> + The 1st cell is hardware pin number of the interrupt.This number is local to >> + each mbigen chip and in the range from 0 to the maximum interrupts number >> + of the mbigen. > > Just to check: 0 - 63 represent the "reserved" pins, yes? Yes, you are right. > > Other than those questions, this looks good to me. Do i need to post a new patch to update these two questions? Thanks! MaJun > > Thanks, > Mark. > >> + >> + The 2nd cell is the interrupt trigger type. >> + The value of this cell should be: >> + 1: rising edge triggered >> + or >> + 4: high level triggered >> + >> +Examples: >> + >> + mbigen_device_gmac:intc { >> + compatible = "hisilicon,mbigen-v2"; >> + reg = <0x0 0xc0080000 0x0 0x10000>; >> + interrupt-controller; >> + msi-parent = <&its_dsa 0x40b1c>; >> + num-msis = <9>; >> + #interrupt-cells = <2>; >> + }; >> + >> +Devices connect to mbigen required properties: >> +---------------------------------------------------- >> +-interrupt-parent: Specifies the mbigen device node which device connected. >> + >> +-interrupts:Specifies the interrupt source. >> + For the specific information of each cell in this property,please refer to >> + the "interrupt-cells" description mentioned above. >> + >> +Examples: >> + gmac0: ethernet@c2080000 { >> + #address-cells = <1>; >> + #size-cells = <0>; >> + reg = <0 0xc2080000 0 0x20000>, >> + <0 0xc0000000 0 0x1000>; >> + interrupt-parent = <&mbigen_device_gmac>; >> + interrupts = <656 1>, >> + <657 1>; >> + }; >> + >> -- >> 1.7.1 >> >> > > . > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/