mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Luciano Coelho <coelho@ti.com>
Cc: <svenkatr@ti.com>, <linux-omap@vger.kernel.org>,
	<linux-mmc@vger.kernel.org>, <cjb@laptop.org>, <lrg@ti.com>,
	<broonie@opensource.wolfsonmicro.com>,
	<linux-kernel@vger.kernel.org>, <balbi@ti.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: 32kHz clock removal causes problems omap_hsmmc
Date: Tue, 18 Dec 2012 11:54:50 +0200	[thread overview]
Message-ID: <20121218095450.GB27751@arwen.pp.htv.fi> (raw)
In-Reply-To: <1352968293.10872.51.camel@cumari.coelho.fi>

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

Hi,

On Thu, Nov 15, 2012 at 10:31:33AM +0200, Luciano Coelho wrote:
> Since the 32KHz clock was removed from the twl-regulator (0e8e5c34
> regulator: twl: Remove references to 32kHz clock from DT bindings),
> we've been having problems with our wl12xx chip that is connected
> through the omap_hsmmc.
> 
> Our card simply doesn't get added to the system and we get lots of
> -ETIMEOUTs during mmc_attach.  If I revert 0e8e5c34 (plus a couple of
> associated patches), everything works fine.
> 
> I've been using a Blaze device with a WiLink 1283 chip connected in the
> COM (internal) port.  The funny thing is that I don't have the same
> problem with a WiLink 1853 chip (which is connected externally to
> another Blaze).
> 
> Does anyone know what the problem could and how to fix it?
> 
> This is a regression that has been there since 3.6-rc1.

damn, this is still part of our v3.7-rc kernel. Original commit was done
with no testing whatsoever and caused a big regression to (at least)
TI's WiFi driver which depend on SDIO to function.

Too bad things break and even when reported nobody gives a rat's ***
about them :-s

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-12-18 10:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15  8:31 Luciano Coelho
2012-12-18  9:54 ` Felipe Balbi [this message]
2012-12-19  9:45   ` Mark Brown
2012-12-19 10:00     ` Peter Ujfalusi
2012-12-19 10:09       ` Mark Brown
2012-12-19 10:18         ` Peter Ujfalusi
2012-12-19 10:32           ` Mark Brown
2012-12-19 10:45             ` Luciano Coelho
2012-12-19 10:56               ` Peter Ujfalusi
2012-12-19 11:00                 ` Peter Ujfalusi
2012-12-19 11:02                 ` Mark Brown
2012-12-19 11:07                 ` Luciano Coelho
2012-12-19 13:01                 ` Felipe Balbi
2012-12-19 13:51                   ` Benoit Cousson
2012-12-19 13:54                     ` Felipe Balbi
2012-12-19 13:58                     ` Mark Brown
2012-12-19 13:58                     ` Luciano Coelho
2012-12-19 14:04                       ` Benoit Cousson
2012-12-19 18:06                         ` R Sricharan
2012-12-19 14:31                   ` Peter Ujfalusi
2012-12-19 16:28           ` Tony Lindgren
2012-12-19 10:01     ` Luciano Coelho
2012-12-19 10:28       ` Mark Brown
2012-12-19 10:42         ` Luciano Coelho

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=20121218095450.GB27751@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cjb@laptop.org \
    --cc=coelho@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=svenkatr@ti.com \
    --cc=tony@atomide.com \
    /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

all inboxes | Powered by JetHome®