From: Rob Herring <robh@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Philipp Zabel <philipp.zabel@gmail.com>,
Paul Parsons <lost.distance@yahoo.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, Dave Gerlach <d-gerlach@ti.com>,
Mark Rutland <mark.rutland@arm.com>, Nishant Menon <nm@ti.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Suman Anna <s-anna@ti.com>, Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCHv2] reset: ti-rstctrl: use the reset-simple driver
Date: Wed, 7 Mar 2018 20:48:06 -0600 [thread overview]
Message-ID: <20180308024806.vombsjullqw5gpmz@rob-hp-laptop> (raw)
In-Reply-To: <20180307182143.58383-1-tony@atomide.com>
On Wed, Mar 07, 2018 at 10:21:43AM -0800, Tony Lindgren wrote:
> We can support the RSTCTRL reset registers on many TI SoCs with
> reset-simple.
>
> Note that some devices will also need to check the RSTST bits
> for reset reason. Support for these could be possibly added to
> the reset controller framework later on.
>
> Cc: Dave Gerlach <d-gerlach@ti.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Nishant Menon <nm@ti.com>
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Suman Anna <s-anna@ti.com>
> Cc: Tero Kristo <t-kristo@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
>
> Changes since v1:
> - Update patch description to mention the unhandled RSTST bits
> - Rebase against Linux next
>
> ---
> .../devicetree/bindings/reset/ti-rstctrl.txt | 20 ++++++++++++++++++++
> drivers/reset/Kconfig | 3 ++-
> drivers/reset/reset-simple.c | 1 +
> 3 files changed, 23 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/reset/ti-rstctrl.txt
>
> diff --git a/Documentation/devicetree/bindings/reset/ti-rstctrl.txt b/Documentation/devicetree/bindings/reset/ti-rstctrl.txt
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/reset/ti-rstctrl.txt
> @@ -0,0 +1,20 @@
> +TI RSTCTRL Reset Controller
> +
> +Required properties:
> +- compatible : "ti,rstctrl"
> +- reg : Should contain 1 register ranges(address and length)
> +- #reset-cells: 1
> +
> +Example:
> + prm_gfx: prm@1100 {
> + compatible = "simple-bus";
What's a PRM?
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0 0x1100 0x100>;
And what else is in this range?
> +
> + gfx_rstctrl: rstctrl@4 {
> + compatible = "ti,rstctrl";
> + reg = <0x4 0x4>;
Anytime I see a single register in DT I worry about scaling. How many of
these in an SoC?
> + #reset-cells = <1>;
> + };
> + };
next prev parent reply other threads:[~2018-03-08 2:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 18:21 [PATCHv2] reset: ti-rstctrl: use the reset-simple driver Tony Lindgren
2018-03-08 2:48 ` Rob Herring [this message]
2018-03-08 16:02 ` Tony Lindgren
2018-03-08 22:25 ` Rob Herring
2018-03-09 15:10 ` Tony Lindgren
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=20180308024806.vombsjullqw5gpmz@rob-hp-laptop \
--to=robh@kernel.org \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lost.distance@yahoo.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=philipp.zabel@gmail.com \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox