From: Ben Dooks <ben@trinity.fluff.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Violeta Menendez Gonzalez <violeta.menendez@codethink.co.uk>,
linux-kernel@lists.codethink.co.uk,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Ben Dooks <ben.dooks@codethink.co.uk>
Subject: Re: [alsa-devel] r8a7790 only has audio when clock is forced on
Date: Wed, 04 Jun 2014 09:38:18 +0000 [thread overview]
Message-ID: <20140604093818.GD19809@trinity.fluff.org> (raw)
In-Reply-To: <CAMuHMdUKL7T0xmwz_Ji+ycLm3=S75V7tJD1wkB_wrud4gzLPBA@mail.gmail.com>
On Wed, Jun 04, 2014 at 11:33:14AM +0200, Geert Uytterhoeven wrote:
> Hi Violeta,
>
> On Wed, Jun 4, 2014 at 11:17 AM, Violeta Menendez Gonzalez
> <violeta.menendez@codethink.co.uk> wrote:
> >> - Which kernel are you using ?
> >
> > 3.15-rc1
> >
> >> - Does your kernel booted from legacy code (= using board-lager.c)
> >> or from DT code (= using board-lager-referenct.c) ?
> >>
> > DT code
>
> Does applying commit 3c90c55dcde745bed81f6447f24ba96bda43d984
> ("drivers: sh: compile drivers/sh/pm_runtime.c if ARCH_SHMOBILE_MULTI")
> help?
We should have that in our tree (other things don't work). As a note,
we did include a debug output showing the clock driver is writing the
clock enables for these bits.
The system is also not showing any signs of external aborts, which is
indicative of trying to access an IP block when it is not clocked. I
will sit down and see if we can debug through this once we've had a
look at DMA.
--
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
prev parent reply other threads:[~2014-06-04 9:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <538E0487.1010700@codethink.co.uk>
2014-06-03 21:42 ` [alsa-devel] r8a7790 only has audio when clock is forced on Mark Brown
2014-06-04 0:26 ` Kuninori Morimoto
2014-06-04 9:02 ` Ben Dooks
2014-06-05 6:05 ` Kuninori Morimoto
2014-06-05 9:10 ` Violeta Menendez Gonzalez
2014-06-05 9:35 ` Kuninori Morimoto
2014-06-05 9:52 ` Ben Dooks
2014-06-05 10:39 ` Violeta Menendez Gonzalez
2014-06-06 5:54 ` Kuninori Morimoto
2014-06-06 6:42 ` Geert Uytterhoeven
2014-06-04 9:17 ` Violeta Menendez Gonzalez
2014-06-04 9:33 ` Geert Uytterhoeven
2014-06-04 9:38 ` Ben Dooks [this message]
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=20140604093818.GD19809@trinity.fluff.org \
--to=ben@trinity.fluff.org \
--cc=alsa-devel@alsa-project.org \
--cc=ben.dooks@codethink.co.uk \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
--cc=violeta.menendez@codethink.co.uk \
/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).