Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4809949ybg; Tue, 29 Oct 2019 12:44:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqzGJ7NxUC41ZHOjTFBKfQz1hWoDUoYWdxnw2ellxLCI/LRYvWZ59606PrPL1h5QGXFKs+ay X-Received: by 2002:a17:906:4d16:: with SMTP id r22mr5221836eju.244.1572378241280; Tue, 29 Oct 2019 12:44:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572378241; cv=none; d=google.com; s=arc-20160816; b=FBm5KLWSokdQHPm7nYDDxnBbtQLq2taJ8k9F1h9hU/odC0lrlC4AB8NNKs3dq2vjyJ 3U1zveNPYel8S5k0UJ3G7jy/9INgLquHh5bGW2JN2w0WyEkRFl71oV7owqNPIwgNAEbH jv9uUCvU96UTlW076DDds1utBRaCXOpVDxKmRlrGAPEpf6TQm5G9tl+i8yI3jWlPLb6t XKs/zFzfyCbiBi1iX7MxS41oLbKB3QmxJvp2eGQGRz1MiFXDp7YEGczd1nOfRLeAn7Jx tUkw7KZaCHwBjeQYWLqzuXufe10BKZR/ULJjx3zDkkZTzxcBjgsDOPK2HLl5jH2cDNMJ acLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=Bi8sjT7OBKTWT/7vnNAmmNhzwZXBpT4PML1MZrl1xJU=; b=rI324u1X8pQUPqbaMTY+60kC41weHRyj7hRBYHIZhtc1yjM0exctAmlIHzozaWB5lm WC/0JIZcjdOQKgwTor4G8oNGh9I9WVdKC8L2kLq+vRsRU3O2W7GyTTmyG+ePWvIJXgnE 89sMHWRPgMBk9R/hKMbKo2S2GXk11e4rySpgk30cBJmP3EnQFXp3OPfdw5BAP0KP4AnL JQNZIsx4WYF1xMFloqblS35PZHBBw1kxsc7AMejuQwTUcrK7rjmg3PjWNs7i3Fbks2h4 sF79B496vZ02QiIOFlyPFFBDgoNFHtbUompMs8DNNgYpTJQgydQbqtHeIqD6DR6ue7SE 83Aw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f19si10872400eda.435.2019.10.29.12.43.37; Tue, 29 Oct 2019 12:44:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389956AbfJ2PPH (ORCPT + 99 others); Tue, 29 Oct 2019 11:15:07 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:47137 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731885AbfJ2PPH (ORCPT ); Tue, 29 Oct 2019 11:15:07 -0400 Received: from lupine.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:1a17] helo=lupine) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1iPTD3-0008Lu-NJ; Tue, 29 Oct 2019 16:15:01 +0100 Message-ID: <39ba2073ca02b391d6006a124ed29d9a57f12a25.camel@pengutronix.de> Subject: Re: [PATCH v2 1/3] dt-binding: reset: add NPCM reset controller documentation From: Philipp Zabel To: Tomer Maimon , robh+dt@kernel.org, mark.rutland@arm.com, yuenn@google.com, venture@google.com, benjaminfair@google.com, avifishman70@gmail.com, joel@jms.id.au Cc: openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Date: Tue, 29 Oct 2019 16:14:58 +0100 In-Reply-To: <20191028155403.134126-2-tmaimon77@gmail.com> References: <20191028155403.134126-1-tmaimon77@gmail.com> <20191028155403.134126-2-tmaimon77@gmail.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:1a17 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tomer, On Mon, 2019-10-28 at 17:54 +0200, Tomer Maimon wrote: > Added device tree binding documentation for Nuvoton BMC > NPCM reset controller. > > Signed-off-by: Tomer Maimon > --- > .../bindings/reset/nuvoton,npcm-reset.txt | 35 +++++++++++++++++++ > 1 file changed, 35 insertions(+) > create mode 100644 Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt > > diff --git a/Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt b/Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt > new file mode 100644 > index 000000000000..94793285a2ac > --- /dev/null > +++ b/Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt > @@ -0,0 +1,35 @@ > +Nuvoton NPCM Reset controller > + > +In the NPCM Reset controller boot the USB PHY, USB host > +and USB device initialize. Isn't this just a detail of the driver implementation? > +Required properties: > +- compatible : "nuvoton,npcm750-reset" for NPCM7XX BMC Is this driver expected to be reused for other SoCs? > +- reg : specifies physical base address and size of the register. > +- #reset-cells: must be set to 1 > + > +Optional property: > +- nuvoton,sw-reset-number - Contains the software reset number to restart the SoC. > + NPCM7xx contain four software reset that represent numbers 1 to 4. What's the difference between the four restart bits? Is this something that has to be configured per board? > + If 'nuvoton,sw-reset-number' is not specfied software reset is disabled. > + > +Example: > + rstc: rstc@f0801000 { > + compatible = "nuvoton,npcm750-reset"; > + reg = <0xf0801000 0x70>; > + #reset-cells = <1>; > + nuvoton,sw-reset-number = <2>; > + }; > + > +Specifying reset lines connected to IP NPCM7XX modules > +====================================================== > +example: > + > + spi0: spi@..... { > + ... > + resets = <&rstc NPCM7XX_RESET_PSPI1>; > + ... > + }; > + > +The index could be found in . regards Philipp