From: Violeta Menendez Gonzalez <violeta.menendez@codethink.co.uk>
To: linux-sh@vger.kernel.org
Cc: linux-kernel@lists.codethink.co.uk,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: r8a7790 only has audio when clock is forced on
Date: Tue, 03 Jun 2014 18:23:19 +0100 [thread overview]
Message-ID: <538E0487.1010700@codethink.co.uk> (raw)
Hi all,
We have a problem where audio on r8a7790 is not working due to it not
sending interrupts.
We've verified that the pins and the clocks are working and correctly
configured. The codec is starting and producing correct bit and word
clock signals
We've made a hack to force /mstp10_clks /on that makes the audio work.
Further investigation showed that it's only needed to force SSI(ALL) on,
but, as far as we know, the manual doesn't say anything about it having
to be kept on.
We've also debugged this hack and saw that the registers have correct
values. These are some of the debugging messages we have when the audio
fails:
Playing WAVE '../audio/r.wav' : Signed 16 bit Little Endian, Rate 44100
Hz, Stereo
cpg_mstp_clock_endisable: index 5, enable 1
cpg_mstp_clock_endisable: index 5, value read from group->smstpcr 0002ffe0
cpg_mstp_clock_endisable: index 5, value write in group->smstpcr 0002ffc0
cpg_mstp_clock_endisable: index 15, enable 1
cpg_mstp_clock_endisable: index 15, value read from group->smstpcr 0002ffc0
cpg_mstp_clock_endisable: index 15, value written in group->smstpcr 00027fc0
aplay: pcm_writecpg_mstp_clock_endisable: index 15, enable 0
cpg_mstp_clock_endisable: index 15, value read from group->smstpcr 00027fc0
cpg_mstp_clock_endisable: index 15, value write in group->smstpcr 0002ffc0
:1710: write errcpg_mstp_clock_endisable: index 5, enable 0
cpg_mstp_clock_endisable: index 5, value read from group->smstpcr 0002ffc0
cpg_mstp_clock_endisable: index 5, value write in group->smstpcr 0002ffe0
or: Input/output error
This shows that the SSI (ALL) clock in bit 5 being enabled before the
SSI0 and that it is also disabled in the reverse sequence as expected.
Not sure what to do next or what the problem could be.
Any new ideas are welcome,
Thanks!
--
Violeta Menéndez González http://www.codethink.co.uk/
Software Engineer Codethink - Providing Genius
next reply other threads:[~2014-06-03 17:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 17:23 Violeta Menendez Gonzalez [this message]
2014-06-03 21:42 ` [alsa-devel] r8a7790 only has audio when clock is forced on Mark Brown
2014-06-03 21:42 ` Mark Brown
2014-06-04 0:26 ` Kuninori Morimoto
2014-06-04 0:26 ` Kuninori Morimoto
2014-06-04 9:02 ` Ben Dooks
2014-06-04 9:02 ` Ben Dooks
2014-06-05 6:05 ` Kuninori Morimoto
2014-06-05 6:05 ` Kuninori Morimoto
2014-06-05 9:10 ` Violeta Menendez Gonzalez
2014-06-05 9:10 ` Violeta Menendez Gonzalez
2014-06-05 9:35 ` Kuninori Morimoto
2014-06-05 9:35 ` Kuninori Morimoto
2014-06-05 9:52 ` Ben Dooks
2014-06-05 9:52 ` Ben Dooks
2014-06-05 10:39 ` Violeta Menendez Gonzalez
2014-06-05 10:39 ` Violeta Menendez Gonzalez
2014-06-06 5:54 ` Kuninori Morimoto
2014-06-06 5:54 ` Kuninori Morimoto
2014-06-06 6:42 ` Geert Uytterhoeven
2014-06-06 6:42 ` Geert Uytterhoeven
2014-06-04 9:17 ` Violeta Menendez Gonzalez
2014-06-04 9:17 ` Violeta Menendez Gonzalez
2014-06-04 9:33 ` Geert Uytterhoeven
2014-06-04 9:33 ` Geert Uytterhoeven
2014-06-04 9:38 ` Ben Dooks
2014-06-04 9:38 ` Ben Dooks
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=538E0487.1010700@codethink.co.uk \
--to=violeta.menendez@codethink.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-sh@vger.kernel.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.