All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Christoph Fritz <chf.fritz@googlemail.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Shawn Guo <shawn.guo@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Lockups reading from i.MX51 SSI registers
Date: Fri, 10 Aug 2012 22:14:56 +0200	[thread overview]
Message-ID: <20120810201456.GL25520@pengutronix.de> (raw)
In-Reply-To: <20120810195638.GF1451@pengutronix.de>

Hi,

On Fri, Aug 10, 2012 at 09:56:38PM +0200, Sascha Hauer wrote:
> On Fri, Aug 10, 2012 at 08:50:08PM +0100, Mark Brown wrote:
> > I'm trying to use -next to test AC'97 register I/O on an i.MX51 board
> > but I'm seeing the CPU hang during probe at:
> > 
> > 	lreg = (reg & 0x7f) <<  12 ;
> > 	writel(lreg, base + SSI_SACADD);
> > 
> > in imx_ssi_ac97_read().  I'm somewhat suspicious this might be because
> > the IP block isn't clocked properly, I do notice the recent conversion
> > to the clock API which looks rather involved but it's possible something
> > else broke.  Does anyone have any bright ideas what might be going on
> > here?  The board doesn't have the reste functions defined so this is the
> > first interaction with the hardware block AFAICT.
> 
> No idea currently, just adding Uwe to Cc because I think he has seen
> something similar on an i.MX35 board recently.
I havn't debugged that yet, but one issue I think needs to be solved is
that since the clk conversion there are two ssi clocks. And from a quick
look the ssi driver only handles one of them.

Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

WARNING: multiple messages have this Message-ID (diff)
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Lockups reading from i.MX51 SSI registers
Date: Fri, 10 Aug 2012 22:14:56 +0200	[thread overview]
Message-ID: <20120810201456.GL25520@pengutronix.de> (raw)
In-Reply-To: <20120810195638.GF1451@pengutronix.de>

Hi,

On Fri, Aug 10, 2012 at 09:56:38PM +0200, Sascha Hauer wrote:
> On Fri, Aug 10, 2012 at 08:50:08PM +0100, Mark Brown wrote:
> > I'm trying to use -next to test AC'97 register I/O on an i.MX51 board
> > but I'm seeing the CPU hang during probe at:
> > 
> > 	lreg = (reg & 0x7f) <<  12 ;
> > 	writel(lreg, base + SSI_SACADD);
> > 
> > in imx_ssi_ac97_read().  I'm somewhat suspicious this might be because
> > the IP block isn't clocked properly, I do notice the recent conversion
> > to the clock API which looks rather involved but it's possible something
> > else broke.  Does anyone have any bright ideas what might be going on
> > here?  The board doesn't have the reste functions defined so this is the
> > first interaction with the hardware block AFAICT.
> 
> No idea currently, just adding Uwe to Cc because I think he has seen
> something similar on an i.MX35 board recently.
I havn't debugged that yet, but one issue I think needs to be solved is
that since the clk conversion there are two ssi clocks. And from a quick
look the ssi driver only handles one of them.

Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2012-08-10 19:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 19:50 Lockups reading from i.MX51 SSI registers Mark Brown
2012-08-10 19:50 ` Mark Brown
2012-08-10 19:56 ` Sascha Hauer
2012-08-10 19:56   ` Sascha Hauer
2012-08-10 20:14   ` Uwe Kleine-König [this message]
2012-08-10 20:14     ` Uwe Kleine-König
2012-08-10 21:06     ` Sascha Hauer
2012-08-10 21:06       ` Sascha Hauer
2012-08-17 19:08       ` Fabio Estevam
2012-08-17 19:08         ` [alsa-devel] " Fabio Estevam
2012-08-17 22:27         ` Mark Brown
2012-08-17 22:27           ` [alsa-devel] " Mark Brown
2012-08-17 23:35           ` Fabio Estevam
2012-08-17 23:35             ` [alsa-devel] " Fabio Estevam
2012-08-18  6:31             ` Christoph Fritz
2012-08-18  6:31               ` [alsa-devel] " Christoph Fritz
2012-08-20 13:18             ` Mark Brown
2012-08-20 13:18               ` [alsa-devel] " Mark Brown
2012-08-20 13:24               ` Fabio Estevam
2012-08-20 13:24                 ` [alsa-devel] " Fabio Estevam
2012-08-18  7:42           ` Uwe Kleine-König
2012-08-18  7:42             ` [alsa-devel] " Uwe Kleine-König
2012-08-18 14:53             ` Fabio Estevam
2012-08-18 14:53               ` [alsa-devel] " Fabio Estevam

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=20120810201456.GL25520@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=chf.fritz@googlemail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawn.guo@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 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.