From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] dt: describe base reset signal binding
Date: Mon, 29 Oct 2012 11:32:33 -0700 [thread overview]
Message-ID: <20121029183233.18780.11964@nucleus> (raw)
In-Reply-To: <1351028756-22309-1-git-send-email-swarren@wwwdotorg.org>
Quoting Stephen Warren (2012-10-23 14:45:56)
> What do people think of this? Does it sound like a good idea to go ahead
> with a reset subsystem? Should we simply add a new API to the common clock
> subsystem instead (and assume that reset and clock domains match 1:1).
> Should this be implemented as part of the generic power management domains;
> see include/linux/pm_domain.h instead?
>
Hi Stephen,
I'm not sure a "reset subsystem" is necessary, but I also do not like
using clocks as the keys for IP reset. I think it is more common to map
IPs to struct device, no?
And of course for clocks shared by multiple users this will not scale.
Regards,
Mike
WARNING: multiple messages have this Message-ID (diff)
From: Mike Turquette <mturquette@ti.com>
To: Stephen Warren <swarren@wwwdotorg.org>,
Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: [RFC PATCH] dt: describe base reset signal binding
Date: Mon, 29 Oct 2012 11:32:33 -0700 [thread overview]
Message-ID: <20121029183233.18780.11964@nucleus> (raw)
In-Reply-To: <1351028756-22309-1-git-send-email-swarren@wwwdotorg.org>
Quoting Stephen Warren (2012-10-23 14:45:56)
> What do people think of this? Does it sound like a good idea to go ahead
> with a reset subsystem? Should we simply add a new API to the common clock
> subsystem instead (and assume that reset and clock domains match 1:1).
> Should this be implemented as part of the generic power management domains;
> see include/linux/pm_domain.h instead?
>
Hi Stephen,
I'm not sure a "reset subsystem" is necessary, but I also do not like
using clocks as the keys for IP reset. I think it is more common to map
IPs to struct device, no?
And of course for clocks shared by multiple users this will not scale.
Regards,
Mike
next prev parent reply other threads:[~2012-10-29 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 21:45 [RFC PATCH] dt: describe base reset signal binding Stephen Warren
2012-10-23 21:45 ` Stephen Warren
2012-10-29 18:32 ` Mike Turquette [this message]
2012-10-29 18:32 ` Mike Turquette
2012-10-30 18:02 ` Stephen Warren
2012-10-30 18:02 ` Stephen Warren
2012-10-31 10:32 ` Mike Turquette
2012-10-31 10:32 ` Mike Turquette
2012-10-31 22:47 ` Stephen Warren
2012-10-31 22:47 ` Stephen Warren
2012-10-31 22:47 ` Stephen Warren
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=20121029183233.18780.11964@nucleus \
--to=mturquette@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 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.