From: "Andrew F. Davis" <afd@ti.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, Suman Anna <s-anna@ti.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Add support for SYSCON reset
Date: Wed, 15 Jun 2016 10:48:23 -0500 [thread overview]
Message-ID: <576178C7.4040204@ti.com> (raw)
In-Reply-To: <20160601184125.20241-1-afd@ti.com>
On 06/01/2016 01:41 PM, Andrew F. Davis wrote:
> Some SoCs contain reset controls for modules that are memory-mapped to
> areas shared with other module configuration settings. This requires
> synchronization across all drivers accessing this memory area. This
> series adds a generic SYSCON reset driver to allow resets toggled
> by bits in memory-mapped registers through SYSCON.
>
> Changes from v2:
> - Rebased on v4.7-rc1
> - Removed the need to give reset specifier nodes an index address
>
> Changes from v1:
> - Reset control information is now described in the reset node, this
> keeps the reset information centralized for easy verification
> - Other small fixups
>
> Andrew F. Davis (2):
> Documentation: dt: reset: Add syscon reset binding
> reset: add a SYSCON based reset driver
>
> .../devicetree/bindings/reset/syscon-reset.txt | 105 ++++++++
> drivers/reset/Kconfig | 10 +
> drivers/reset/Makefile | 1 +
> drivers/reset/reset-syscon.c | 289 +++++++++++++++++++++
> include/dt-bindings/reset/syscon.h | 23 ++
> 5 files changed, 428 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reset/syscon-reset.txt
> create mode 100644 drivers/reset/reset-syscon.c
> create mode 100644 include/dt-bindings/reset/syscon.h
>
Is there any additional feedback for this driver? I normally try to
refrain from pings, but this may begin to block further upstreaming of
IPs that uses this reset if it can not be taken this cycle.
If there is still an objection to calling this a generic reset solution
we would not strongly object to relabeling this to something implying
more TI exclusivity.
Thanks,
Andrew
next prev parent reply other threads:[~2016-06-15 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 18:41 [PATCH v3 0/2] Add support for SYSCON reset Andrew F. Davis
2016-06-01 18:41 ` [PATCH v3 1/2] Documentation: dt: reset: Add syscon reset binding Andrew F. Davis
[not found] ` <20160601184125.20241-1-afd-l0cyMroinI0@public.gmane.org>
2016-06-01 18:41 ` [PATCH v3 2/2] reset: add a SYSCON based reset driver Andrew F. Davis
2016-06-15 16:51 ` Suman Anna
2016-06-15 16:52 ` Andrew F. Davis
2016-06-15 15:48 ` Andrew F. Davis [this message]
2016-06-15 16:45 ` [PATCH v3 0/2] Add support for SYSCON reset Philipp Zabel
2016-06-16 2:13 ` Rob Herring
[not found] ` <CAL_JsqKL+njqxTUB3MPgX=qJK72bmXXWH4gOuYMC2NFg5u7eqg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-20 18:44 ` Andrew F. Davis
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=576178C7.4040204@ti.com \
--to=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.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;
as well as URLs for NNTP newsgroup(s).