From: James Cameron <quozl@laptop.org>
To: Bing Zhao <bzhao@marvell.com>
Cc: Daniel Mack <daniel@zonque.org>, Tony Lindgren <tony@atomide.com>,
Andreas Fenkart <afenkart@gmail.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: mwifiex card reset
Date: Tue, 1 Jul 2014 17:03:49 +1000 [thread overview]
Message-ID: <20140701070349.GN24891@us.netrek.org> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430FE5F3754E@SC-VEXCH1.marvell.com>
On Tue, Jul 01, 2014 at 12:02:25AM -0700, Bing Zhao wrote:
> Hi James,
>
> > On Mon, Jun 30, 2014 at 11:44:29PM -0700, Bing Zhao wrote:
> > > I may have missed something, but doesn't the MMC_POWER_OFF and
> > > MMC_POWER_ON|UP handling in controller driver help?
> > > Anyway the clocks/GPIOs/regulators are sort of platform dependent.
> > > Would it be better putting it in /arch/arm/mach-xxxxx/?
> >
> > Wouldn't device tree for mmc be better?
>
> Yes, device tree is better for defining clocks/GPIO/regulators, etc.
> But I guess the reset logic (making use of these definitions) cannot
> be device tree?
I think the reset logic can exist, but does nothing unless the device
tree definitions are present.
--
James Cameron
http://quozl.linux.org.au/
next prev parent reply other threads:[~2014-07-01 7:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 14:39 mwifiex card reset Andreas Fenkart
2014-06-28 5:22 ` James Cameron
2014-06-28 7:23 ` Tony Lindgren
2014-06-29 9:41 ` Andreas Fenkart
2014-06-30 6:19 ` Tony Lindgren
2014-06-30 19:30 ` Daniel Mack
2014-07-01 6:44 ` Bing Zhao
2014-07-01 6:57 ` James Cameron
2014-07-01 7:02 ` Bing Zhao
2014-07-01 7:03 ` James Cameron [this message]
2014-07-01 7:41 ` Tony Lindgren
2014-07-01 12:20 ` Yuvaraj Cd
2014-07-01 15:09 ` Doug Anderson
2014-07-15 13:25 ` Andreas Fenkart
2014-07-01 7:52 ` Daniel Mack
2014-07-01 8:44 ` Andreas Fenkart
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=20140701070349.GN24891@us.netrek.org \
--to=quozl@laptop.org \
--cc=afenkart@gmail.com \
--cc=bzhao@marvell.com \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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).