Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3230110imm; Mon, 10 Sep 2018 13:13:13 -0700 (PDT) X-Google-Smtp-Source: ANB0Vda8tk87MqPiUTEiLTN4BKYEYlQiVZQGhSVUp5MXgWJfgdZOQ1uR8x/ryHulbvHCfEj2U2Iw X-Received: by 2002:a17:902:8a97:: with SMTP id p23-v6mr23435742plo.21.1536610393131; Mon, 10 Sep 2018 13:13:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536610393; cv=none; d=google.com; s=arc-20160816; b=z/v1fQPVPAoCVJnR9pNcERMsUZIAnrLFmXFYkFdoo4awxGibYy4U0GlFetyiVMEybh eyuFYZtuS60ij6xf/H6w9rEshfsDIOxAhXwi5AWL8aIVaDO4kbp/P27UYtYd3c1/uyre +oWYBtsnFGbnFEQBcVSKPvrSktcIwlk8Ravq2Al58k06Lcu4H7z8LKAokQBT8eBlrQ8v uffBGiIMZkEBMhdBK15ndZ8Qw001a3z/KAGzqmageYB+g3CcsO/U5tXEL8kc2nLzPMRK DUBRuKql1MfVJWQj6lOj4763TnFVN3BFXOf+UXUaAym0OPkWmTyTgBvKtH+0nkLs8LT7 SVxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=6MwDJlUHqmF2XEsEb1L94Aq5NS06o9G5wdxX5HbUGAw=; b=AVG3MH4c7+DiF+3PgM9Cegs0tc2OkZRQcebT8VZJTcEgQErfHtCoVxB64vlAbaN/EV U+wr6dicmT6+PLFWrsA6WWkfIyk4S3PRGZiRd0jY8VdZ7N6PMaEamJeKzMpLF9zEJgaP ofR1pn8qKoNNquO22VRNdA+usj8z09n1XJuoMLP/d+CJsIuazOl7tc0OZURJNy1JT2kh xd6SsuUklh7yqhdrI8ybdtsBh0Y/Oi10s5a+JjZs+gq6JWPa37O1yTAGjuNoRXfSelSk 6TyZYzxnVJ954oZswCwhxhbhYl3d1DlPdBmis+Rwh4JlW5IVDJbzVvHQgAsaS3MDbcLj VUmA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q8-v6si14992365pls.482.2018.09.10.13.12.55; Mon, 10 Sep 2018 13:13:13 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727125AbeIKBIL (ORCPT + 99 others); Mon, 10 Sep 2018 21:08:11 -0400 Received: from mail-oi0-f65.google.com ([209.85.218.65]:41794 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726481AbeIKBIK (ORCPT ); Mon, 10 Sep 2018 21:08:10 -0400 Received: by mail-oi0-f65.google.com with SMTP id k12-v6so42708684oiw.8; Mon, 10 Sep 2018 13:12:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=6MwDJlUHqmF2XEsEb1L94Aq5NS06o9G5wdxX5HbUGAw=; b=QyUW+Nmh6HzCnUtbneoQFj2izqi64DIslT4VmrurIRKKHOzSCePLvXynH9P0LJpRgV RWbuZ32qCUAVbvFlF7QEbs2uhjVpR8k5uAD5OU21Nm4ZWE3ST/c1TaW9JGALuG55eD8O V/HhkFlq/SEJNU/0kf9hFzbOyy4LdB9RPTsE3IgNCWM2TTGhHzJX2KghC7wa5X50lvcQ DYxFf/2rJoePkHfzmX+McaikJuOP2Uk0yGf63ToqTD6axaawkRvUDrAFaMUQSM4U9D5A 0pP6i411XefzvwhJOGTsdgub8bjmWayMXbHzwsl0mTVnXeD7y09QjpdfrA0AbvbecbTq 3DbA== X-Gm-Message-State: APzg51A0VwMc2PNdcmGDPw7aWJdl231qTQTmhAMhKOXqVoXJM0JiscD4 dmOtT55YqEIlep+k35lDDQ== X-Received: by 2002:aca:e214:: with SMTP id z20-v6mr24725884oig.95.1536610345674; Mon, 10 Sep 2018 13:12:25 -0700 (PDT) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id 1-v6sm17861801oir.19.2018.09.10.13.12.25 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 10 Sep 2018 13:12:25 -0700 (PDT) Date: Mon, 10 Sep 2018 15:12:24 -0500 From: Rob Herring To: Nava kishore Manne Cc: mark.rutland@arm.com, michal.simek@xilinx.com, p.zabel@pengutronix.de, rajanv@xilinx.com, jollys@xilinx.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v3 2/3] dt-bindings: reset: Add bindings for ZynqMP reset driver Message-ID: <20180910201224.GA31501@bogus> References: <1536131342-28041-1-git-send-email-nava.manne@xilinx.com> <1536131342-28041-3-git-send-email-nava.manne@xilinx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1536131342-28041-3-git-send-email-nava.manne@xilinx.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 05, 2018 at 12:39:01PM +0530, Nava kishore Manne wrote: > Add documentation to describe Xilinx ZynqMP reset driver > bindings. > > Signed-off-by: Nava kishore Manne > --- > Changes for v3: > -Corrected Commit Msg. > Changes for v2: > -Moved reset node as a child to firwmare > node. Why? There's no reason for that. The parent can be multiple providers. You only need child nodes if the sub functions have their own DT resources. > > .../firmware/xilinx/xlnx,zynqmp-firmware.txt | 142 +++++++++++++++++++++ > 1 file changed, 142 insertions(+) > > diff --git a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt > index 1b431d9..351b1bb 100644 > --- a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt > +++ b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt > @@ -17,6 +17,144 @@ Required properties: > - "smc" : SMC #0, following the SMCCC > - "hvc" : HVC #0, following the SMCCC > > +-------------------------------------------------------------------------- > + = Zynq UltraScale+ MPSoC reset driver binding = > +-------------------------------------------------------------------------- > +The Zynq UltraScale+ MPSoC has several different resets. > + > +See Chapter 36 of the Zynq UltraScale+ MPSoC TRM (UG) for more information > +about zynqmp resets. > + > +Please also refer to reset.txt in this directory for common reset > +controller binding usage. > + > +Required Properties: > +- compatible: "xlnx,zynqmp-reset" > +- #reset-cells: Specifies the number of cells needed to encode reset > + line, should be 1 > + > +Reset outputs: > + 0 :PCIE config reset. > + 1 :PCIE bridge block level reset (AXI interface). > + 2 :PCIE control block level,reset. > + 3 :Display Port block level reset (includes DPDMA). > + 4 :FPD WDT reset. > + 5 :AF_FM5 block level reset. > + 6 :AF_FM4 block level reset. > + 7 :AF_FM3 block level reset. > + 8 :AF_FM2 block level reset. > + 9 :AF_FM1 block level reset. > + 10 :AF_FM0 block level reset. > + 11 :GDMA block level reset. > + 12 :Pixel Processor (GPU_PP1) block level reset. > + 13 :Pixel Processor (GPU_PP0) block level reset. > + 14 :GPU block level reset. > + 15 :GT block level reset. > + 16 :Sata block level reset. > + 17 :ACPU3 power on reset. > + 18 :ACPU2 power on reset. > + 19 :ACPU1 power on reset. > + 20 :ACPU0 power on reset. > + 21 :APU L2 reset. > + 22 :ACPU3 reset. > + 23 :ACPU2 reset. > + 24 :ACPU1 reset. > + 25 :ACPU0 reset. > + 26 :DDR block level reset inside of the DDR Sub System. > + 27 :APM block level reset inside of the DDR Sub System. > + 28 :soft reset. > + 29 :GEM 0 reset. > + 30 :GEM 1 reset. > + 31 :GEM 2 reset. > + 32 :GEM 3 reset. > + 33 :qspi reset. > + 34 :uart0 reset. > + 35 :uart1 reset. > + 36 :spi0 reset. > + 37 :spi1 reset. > + 38 :sdio0 reset. > + 39 :sdio1 reset. > + 40 :can0 reset. > + 41 :can1 reset. > + 42 :i2c0 reset. > + 43 :i2c1 reset. > + 44 :ttc0 reset. > + 45 :ttc1 reset. > + 46 :ttc2 reset. > + 47 :ttc3 reset. > + 48 :swdt reset. > + 49 :nand reset. > + 50 :adma reset. > + 51 :gpio reset. > + 52 :iou_cc reset. > + 53 :timestamp reset. > + 54 :rpu_r50 reset. > + 55 :rpu r51 reset. > + 56 :rpu_amba reset. > + 57 :ocm reset. > + 58 :rpu_pge reset. > + 59 :usb0_core reset. > + 60 :usb1_core reset. > + 61 :usb0_hiber reset. > + 62 :usb1_hiber reset. > + 63 :usb0_apb reset. > + 64 :usb1_apb reset. > + 65 :ipi reset. > + 66 :apm reset. > + 67 :rtc reset. > + 68 :sysmon reset. > + 69 :afi_fm6 reset. > + 70 :lpd_swdt reset. > + 71 :fpd_reset. > + 72 :rpu_dbg1 reset. > + 73 :rpu_dbg0 reset. > + 74 :dbg_lpd reset. > + 75 :dbg_fpd reset. > + 76 :apll reset. > + 77 :dpll reset. > + 78 :vpll reset. > + 79 :iopll reset. > + 80 :rpll reset. > + 81 :gpio_pl_0 reset. > + 82 :gpio_pl_1 reset. > + 83 :gpio_pl_2 reset. > + 84 :gpio_pl_3 reset. > + 85 :gpio_pl_4 reset. > + 86 :gpio_pl_5 reset. > + 87 :gpio_pl_6 reset. > + 88 :gpio_pl_7 reset. > + 89 :gpio_pl_8 reset. > + 90 :gpio_pl_9 reset. > + 91 :gpio_pl_10 reset. > + 92 :gpio_pl_11 reset. > + 93 :gpio_pl_12 reset. > + 94 :gpio_pl_13 reset. > + 95 :gpio_pl_14 reset. > + 96 :gpio_pl_15 reset. > + 97 :gpio_pl_16 reset. > + 98 :gpio_pl_17 reset. > + 99 :gpio_pl_18 reset. > + 100 :gpio_pl_19 reset. > + 101 :gpio_pl_20 reset. > + 102 :gpio_pl_21 reset. > + 103 :gpio_pl_22 reset. > + 104 :gpio_pl_23 reset. > + 105 :gpio_pl_24 reset. > + 106 :gpio_pl_25 reset. > + 107 :gpio_pl_26 reset. > + 108 :gpio_pl_27 reset. > + 109 :gpio_pl_28 reset. > + 110 :gpio_pl_29 reset. > + 111 :gpio_pl_30 reset. > + 112 :gpio_pl_31 reset. > + 113 :rpu_ls reset. > + 114 :ps_only reset. > + 115 :pl reset. > + 116 :ps_pl0 reset > + 117 :ps_pl1 reset > + 118 :ps_pl2 reset > + 119 :ps_pl3 reset > + > ------- > Example > ------- > @@ -25,5 +163,9 @@ firmware { > zynqmp_firmware: zynqmp-firmware { > compatible = "xlnx,zynqmp-firmware"; > method = "smc"; > + reset-controller:reset-controller@0 { > + compatible = "xlnx,zynqmp-reset"; > + #reset-cells = <1>; > + }; > }; > }; > -- > 2.7.4 >