From: Philipp Zabel <p.zabel@pengutronix.de> To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: kernel@pengutronix.de, Roger Quadros <rogerq@ti.com>, Mark Rutland <mark.rutland@arm.com>, Maxime Ripard <maxime.ripard@free-electrons.com>, Stephen Warren <swarren@wwwdotorg.org>, Arnd Bergmann <arnd@arndb.de>, Philipp Zabel <p.zabel@pengutronix.de> Subject: [PATCH v3 1/2] Documentation: Add GPIO reset binding to reset binding documentation Date: Wed, 8 Jan 2014 12:11:03 +0100 [thread overview] Message-ID: <1389179464-11963-1-git-send-email-p.zabel@pengutronix.de> (raw) This patch adds documentation clarifying the reset GPIO bindings most commonly in use (reset-gpios and <name>-reset-gpios properties). Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> --- Documentation/devicetree/bindings/reset/reset.txt | 26 +++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/reset/reset.txt b/Documentation/devicetree/bindings/reset/reset.txt index 31db6ff..51f9e35 100644 --- a/Documentation/devicetree/bindings/reset/reset.txt +++ b/Documentation/devicetree/bindings/reset/reset.txt @@ -2,8 +2,8 @@ This binding is intended to represent the hardware reset signals present internally in most IC (SoC, FPGA, ...) designs. Reset signals for whole -standalone chips are most likely better represented as GPIOs, although there -are likely to be exceptions to this rule. +standalone chips are most likely better represented as GPIOs, ideally using a +common scheme as described below. Hardware blocks typically receive a reset signal. This signal is generated by a reset provider (e.g. power management or clock module) and received by a @@ -56,6 +56,20 @@ reset-names: List of reset signal name strings sorted in the same order as the resets property. Consumers drivers will use reset-names to match reset signal names with reset specifiers. += GPIO Reset consumers = + +For the common case of reset lines controlled by GPIOs, the GPIO binding +documented in devicetree/bindings/gpio/gpio.txt should be used: + +Required properties: +reset-gpios or Reset GPIO using standard GPIO bindings, +<name>-reset-gpios: optionally named to specify the reset line + +Optional properties: +reset-boot-asserted or Boolean. If set, the corresponding reset is +<name>-reset-boot-asserted: initially asserted and should be kept that way + until released by the driver. + For example: device { @@ -65,6 +79,14 @@ For example: This represents a device with a single reset signal named "reset". + device2 { + reset-gpios = <&gpio3 15 GPIO_ACTIVE_LOW>; + reset-boot-asserted; + }; + +This represents a device with a single reset signal, controlled +by an active-low GPIO, which is initally kept in reset. + bus { resets = <&rst 10> <&rst 11> <&rst 12> <&rst 11>; reset-names = "i2s1", "i2s2", "dma", "mixer"; -- 1.8.5.2
WARNING: multiple messages have this Message-ID (diff)
From: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org, Roger Quadros <rogerq-l0cyMroinI0@public.gmane.org>, Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>, Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>, Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>, Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>, Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> Subject: [PATCH v3 1/2] Documentation: Add GPIO reset binding to reset binding documentation Date: Wed, 8 Jan 2014 12:11:03 +0100 [thread overview] Message-ID: <1389179464-11963-1-git-send-email-p.zabel@pengutronix.de> (raw) This patch adds documentation clarifying the reset GPIO bindings most commonly in use (reset-gpios and <name>-reset-gpios properties). Signed-off-by: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> --- Documentation/devicetree/bindings/reset/reset.txt | 26 +++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/reset/reset.txt b/Documentation/devicetree/bindings/reset/reset.txt index 31db6ff..51f9e35 100644 --- a/Documentation/devicetree/bindings/reset/reset.txt +++ b/Documentation/devicetree/bindings/reset/reset.txt @@ -2,8 +2,8 @@ This binding is intended to represent the hardware reset signals present internally in most IC (SoC, FPGA, ...) designs. Reset signals for whole -standalone chips are most likely better represented as GPIOs, although there -are likely to be exceptions to this rule. +standalone chips are most likely better represented as GPIOs, ideally using a +common scheme as described below. Hardware blocks typically receive a reset signal. This signal is generated by a reset provider (e.g. power management or clock module) and received by a @@ -56,6 +56,20 @@ reset-names: List of reset signal name strings sorted in the same order as the resets property. Consumers drivers will use reset-names to match reset signal names with reset specifiers. += GPIO Reset consumers = + +For the common case of reset lines controlled by GPIOs, the GPIO binding +documented in devicetree/bindings/gpio/gpio.txt should be used: + +Required properties: +reset-gpios or Reset GPIO using standard GPIO bindings, +<name>-reset-gpios: optionally named to specify the reset line + +Optional properties: +reset-boot-asserted or Boolean. If set, the corresponding reset is +<name>-reset-boot-asserted: initially asserted and should be kept that way + until released by the driver. + For example: device { @@ -65,6 +79,14 @@ For example: This represents a device with a single reset signal named "reset". + device2 { + reset-gpios = <&gpio3 15 GPIO_ACTIVE_LOW>; + reset-boot-asserted; + }; + +This represents a device with a single reset signal, controlled +by an active-low GPIO, which is initally kept in reset. + bus { resets = <&rst 10> <&rst 11> <&rst 12> <&rst 11>; reset-names = "i2s1", "i2s2", "dma", "mixer"; -- 1.8.5.2 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-01-08 11:11 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-08 11:11 Philipp Zabel [this message] 2014-01-08 11:11 ` [PATCH v3 1/2] Documentation: Add GPIO reset binding to reset binding documentation Philipp Zabel 2014-01-08 11:11 ` [PATCH v3 2/2] reset: Add GPIO support to reset controller framework Philipp Zabel 2014-01-08 11:11 ` Philipp Zabel 2014-01-08 16:08 ` [PATCH v3 1/2] Documentation: Add GPIO reset binding to reset binding documentation Arnd Bergmann 2014-01-08 16:08 ` Arnd Bergmann 2014-01-10 11:25 ` Philipp Zabel 2014-01-10 11:25 ` Philipp Zabel 2014-02-06 15:44 ` Philipp Zabel 2014-02-06 15:44 ` Philipp Zabel 2014-02-14 10:20 ` Philipp Zabel 2014-02-14 10:20 ` Philipp Zabel
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1389179464-11963-1-git-send-email-p.zabel@pengutronix.de \ --to=p.zabel@pengutronix.de \ --cc=arnd@arndb.de \ --cc=devicetree@vger.kernel.org \ --cc=kernel@pengutronix.de \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=maxime.ripard@free-electrons.com \ --cc=rogerq@ti.com \ --cc=swarren@wwwdotorg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.