linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: Tony Lindgren <tony@atomide.com>, Andreas Fenkart <afenkart@gmail.com>
Cc: James Cameron <quozl@laptop.org>, Bing Zhao <bzhao@marvell.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
Subject: Re: mwifiex card reset
Date: Mon, 30 Jun 2014 21:30:09 +0200	[thread overview]
Message-ID: <53B1BAC1.3090902@zonque.org> (raw)
In-Reply-To: <20140630061912.GA2461@atomide.com>

Hi Tony, everyone,

Thanks Andreas for addressing this issue! So far, we've been using a
terrible hack in the hsmmc in order to bring the card into a workable
state, and we're looking for a nicer solution for awhile.

On 06/30/2014 08:19 AM, Tony Lindgren wrote:
> * Andreas Fenkart <afenkart@gmail.com> [140629 12:43]:
>> 2014-06-28 9:23 GMT+02:00 Tony Lindgren <tony@atomide.com>:
>>> * James Cameron <quozl@laptop.org> [140628 08:24]:

>>> Wouldn't it be best to have the mwifiex properly handle the
>>> reset GPIOs and idle status pins?
>>
>> doesn't work see ref 1) above
> 
> OK so we can't do much anything at mwifiex probe time on SDIO bus because
> it won't probe unless the pins are configured.
> 
> Maybe we should have a separate mwifiex-power helper module that just
> manages the reset/idle/regulator pins? Then mwifiex-reset can be always
> loaded and configure things so mwifiex-sdio can probe properly.
> 
> And mwifiex-reset helper can also provide the user space interfaces
> for the reset/idle/regulator pins.

Yes, a helper might be the best solution. It could even be a generic
one, that just takes any number of clocks, reset GPIOs and regulators
and takes care for sequencing them. However, we need to reference that
helper from the mwifiex driver, for two reasons.

a) we need to make sure the reset helper gets to do its job before the
mwifiex driver scans the SDIO bus, and

b) the reset helper needs to be called when the mmc host controller
wants to do a card reset.

Hence, we'll need some sort of internal API for this, and a phandle in
dts. I wonder whether that glue logic might be better off living in the
mmc core, as mwifiex might well be interfaced to other hosts?


Thanks,
Daniel


  reply	other threads:[~2014-06-30 19:30 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 [this message]
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
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=53B1BAC1.3090902@zonque.org \
    --to=daniel@zonque.org \
    --cc=afenkart@gmail.com \
    --cc=bzhao@marvell.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quozl@laptop.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).