linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: noise issues when recording sound on i.MX28
Date: Thu, 11 Feb 2016 09:40:29 +0100	[thread overview]
Message-ID: <20160211084029.GE13664@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5D5H4F90nse9kyW9KvsJStN-sCGktup4FDPw_zTeNfS2g@mail.gmail.com>

On Wed, Feb 10, 2016 at 06:10:18PM -0200, Fabio Estevam wrote:
> Hi Uwe,
> 
> On Wed, Feb 10, 2016 at 1:03 PM, Uwe Kleine-K?nig
> <u.kleine-koenig@pengutronix.de> wrote:
> > Hello Fabio,
> >
> > On Tue, Feb 02, 2016 at 11:00:33AM -0200, Fabio Estevam wrote:
> >> On Wed, Jan 27, 2016 at 12:43 PM, Uwe Kleine-K?nig
> >> <u.kleine-koenig@pengutronix.de> wrote:
> >>
> >> > So you didn't hit the problem that resetting a saif didn't work, right?
> >>
> >> No, we haven't seen this reset issue.
> >>
> >> > Do you have a few more technical details here? A usecase of my machine
> >>
> >> Let me find out as it has been several years I worked on this problem.
> >> Will let you know.
> >
> > Anything new on your end? I know from Lothar that he invested quite some
> > time to debug his hardware setup, tested the codec instead of the i.MX28
> > as clock provider and several more things. I also spend some time on
> > this issue and we both hope that Freescale/NXP can help in better
> > understanding the issue and hopefully can come up with a recipe to make
> > concurrent recording and playback on i.MX28 work.
> >
> > Lothar is in contact with Freescale, too, but up to now with little
> > success. The company I'm working for at the moment would also welcome a
> > solution here.
> 
> Sorry for the delay. I have been on holidays.

I wonder who granted you to go on holidays given that we have
problems :-)

> Can you confirm you have both SAIF interfaces being clocked from ref_pll?

root at hostname:/sys/kernel/debug/clk find -name saif?_sel
./ref_xtal/pll0/saif0_sel
./ref_xtal/pll0/saif1_sel

root at hostname:/sys/kernel/debug/clk cat ./ref_xtal/pll0/saif?_sel/clk_rate 
480000000
480000000

This is based on 3.10 (but I hope to update soon to 4.4ish). I know that
Lothar uses 4.4. Also Lothar noticed that disabling one of these
saif_sel clocks doesn't make an impression on the interfaces, they just
continue to run. Maybe a clock is routed in a wrong way?

Best regards
Uwe

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

  reply	other threads:[~2016-02-11  8:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 10:56 noise issues when recording sound on i.MX28 Uwe Kleine-König
2016-01-27 11:53 ` Fabio Estevam
2016-01-27 14:43   ` Uwe Kleine-König
2016-01-28  6:38     ` Lothar Waßmann
2016-02-02 13:00     ` Fabio Estevam
2016-02-10 15:03       ` Uwe Kleine-König
2016-02-10 20:10         ` Fabio Estevam
2016-02-11  8:40           ` Uwe Kleine-König [this message]
2016-02-11 14:25             ` Lothar Waßmann
2016-02-16 15:01             ` Fabio Estevam
2016-02-16 19:35               ` Uwe Kleine-König
2016-02-17  7:55               ` Lothar Waßmann
2017-01-10 16:17                 ` Jörg Krause

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=20160211084029.GE13664@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).