From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
Arnd Bergmann Arnd Bergmann <arnd@arndb.de>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Mark Rutland <mark.rutland@arm.com>,
Roger Quadros <rogerq@ti.com>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH v4 2/2] reset: Add GPIO support to reset controller framework
Date: Mon, 14 Apr 2014 11:57:58 +0100 [thread overview]
Message-ID: <20140414115758.2c0c8a9d@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <1397463709-19405-2-git-send-email-p.zabel@pengutronix.de>
> This adds support for GPIO controlled reset pins on peripheral ICs to the reset
> controller framework. Currently there is no support for specifying a delay
> between assertion and de-assertion of the reset signal, so this has to be
> handled by the drivers.
Lots of GPIO controllers are doing posted writes to the fabric so surely
your delay will be wrong ?
Alan
next prev parent reply other threads:[~2014-04-14 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 8:21 [PATCH v4 1/2] Documentation: Add GPIO reset binding to reset binding documentation Philipp Zabel
2014-04-14 8:21 ` [PATCH v4 2/2] reset: Add GPIO support to reset controller framework Philipp Zabel
2014-04-14 10:57 ` One Thousand Gnomes [this message]
2014-04-15 8:35 ` Philipp Zabel
[not found] ` <1397463709-19405-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-04-17 11:58 ` [PATCH v4 1/2] Documentation: Add GPIO reset binding to reset binding documentation Maxime Ripard
2014-04-30 8:54 ` Philipp Zabel
[not found] ` <1398848062.19894.38.camel-+qGW7pzALmz7o/J7KWpOmN53zsg1cpMQ@public.gmane.org>
2014-04-30 18:29 ` Maxime Ripard
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=20140414115758.2c0c8a9d@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=p.zabel@pengutronix.de \
--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: 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).