From: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: srinivas kandagatla <srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
Cc: Maxime Coquelin <maxime.coquelin-qxv4g6HH51o@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stephen.gallimore-qxv4g6HH51o@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 0/6] ARM: STi reset controller support
Date: Mon, 24 Feb 2014 16:16:22 +0100 [thread overview]
Message-ID: <1393254982.3091.44.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <530B514A.4070209-qxv4g6HH51o@public.gmane.org>
Hi Srinivas,
Am Montag, den 24.02.2014, 14:03 +0000 schrieb srinivas kandagatla:
> Thanks Philipp for your comments,
>
> On 24/02/14 10:33, Philipp Zabel wrote:
> >> > Did Srini's explanations convinced you?
> >> >
> >> > If so, could you queue the series for v3.15?
> > to be honest, I'm not comfortable with this explanation. If the
> > "powerdown" bits only gate the clocks to those modules, calling it a
> > reset control is clearly the wrong abstraction. If that is the case,
> > couldn't you handle those bits via the clock framework?
> I just had a re-look at the IPs specs for more information on where
> these power-down signals are actually terminating on the IP side.
>
> For example: ST-Synopsis Ethernet GMAC IP has two pins
> power_down_req[IN] and power_down_ack[OUT]. power_down_req is used by
> the software to either put the IP in powerdown or bring it out of
> powerdown state.
Now I'm a bit confused. There is no mention of GMAC in your patches,
and for ETH[01] they contain only the SOFTRESET bits. I have no issue
with the SOFTRESETs.
> The IP itself drives power_down_ack to indicate when the power down
> request is successfully finished. For power_down/power_up request the IP
> will change the internal state accordingly including powering up/down
> its internal blocks and/or clock gating.
>
> > If on the other hand these powerdown bits also trigger reset machinery,
> > such that asserting and deasserting that bit will change the module's
> > internal state, I could be convinced to queue them like this.
> This is true with ST IPs, these lines change the state of the IP as
> described above. Reset framework seems to fits in very well with this
> behavior rather than power-domains or clock framework.
If you put the IP in power down when it is idle, and then power it up
again, will the IP registers have kept their previous state?
regards
Philipp
--
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 prev parent reply other threads:[~2014-02-24 15:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 10:50 [PATCH v1 0/6] STi reset controller suppport Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 1/6] drivers: reset: STi SoC system configuration reset controller support Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 2/6] drivers: reset: Reset controller driver for STiH415 Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 3/6] drivers: reset: Reset controller driver for STiH416 Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 4/6] drivers: reset: stih415: add softreset controller Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 5/6] drivers: reset: stih416: " Srinivas Kandagatla
2014-01-14 10:51 ` [PATCH v1 6/6] ARM: STi: Add reset controller support to mach-sti Kconfig Srinivas Kandagatla
2014-02-03 14:27 ` [PATCH v2 0/6] ARM: STi reset controller support srinivas.kandagatla
2014-02-03 14:28 ` [PATCH v2 1/6] drivers: reset: STi SoC system configuration " srinivas.kandagatla
2014-02-03 14:28 ` [PATCH v2 2/6] drivers: reset: Reset controller driver for STiH415 srinivas.kandagatla
[not found] ` <1391437665-11913-1-git-send-email-srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
2014-02-03 14:28 ` [PATCH v2 3/6] drivers: reset: Reset controller driver for STiH416 srinivas.kandagatla-qxv4g6HH51o
2014-02-03 14:28 ` [PATCH v2 4/6] drivers: reset: stih415: add softreset controller srinivas.kandagatla-qxv4g6HH51o
2014-02-03 14:28 ` [PATCH v2 5/6] drivers: reset: stih416: " srinivas.kandagatla
2014-02-03 14:29 ` [PATCH v2 6/6] ARM: STi: Add reset controller support to mach-sti Kconfig srinivas.kandagatla
2014-02-05 9:28 ` [PATCH v2 0/6] ARM: STi reset controller support Philipp Zabel
2014-02-07 12:54 ` srinivas kandagatla
2014-02-19 13:57 ` Maxime Coquelin
[not found] ` <5304B849.2080806-qxv4g6HH51o@public.gmane.org>
2014-02-24 10:33 ` Philipp Zabel
2014-02-24 14:03 ` srinivas kandagatla
[not found] ` <530B514A.4070209-qxv4g6HH51o@public.gmane.org>
2014-02-24 15:16 ` Philipp Zabel [this message]
2014-02-25 9:08 ` srinivas kandagatla
[not found] ` <530C5D8C.1080809-qxv4g6HH51o@public.gmane.org>
2014-02-25 9:47 ` Philipp Zabel
2014-02-25 10:56 ` srinivas kandagatla
[not found] ` <530C76F0.8000909-qxv4g6HH51o@public.gmane.org>
2014-02-25 11:15 ` 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=1393254982.3091.44.camel@pizza.hi.pengutronix.de \
--to=p.zabel-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=maxime.coquelin-qxv4g6HH51o@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=srinivas.kandagatla-qxv4g6HH51o@public.gmane.org \
--cc=stephen.gallimore-qxv4g6HH51o@public.gmane.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).