All of lore.kernel.org
 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: Wed, 27 Jan 2016 11:56:13 +0100	[thread overview]
Message-ID: <20160127105613.GC13664@pengutronix.de> (raw)

Hello,

I currently work with an i.MX28 based machine and occasionally when
recording sound with arecord but no microphone connected the result
contains much noise.

I found commits

	90ce77d4468e ENGR00285446-3 [MX28] SAIF: Bit Shift in SAIF RX Data
	1ea685a12f19 ENGR00285446-2 [MX28] SAIF: Bit Shift in SAIF RX Data
	1ca899221d8b ENGR00285446-1 [MX28] SAIF: Bit Shift in SAIF RX Data

in the Freescale vendor kernel (branch imx_2.6.35_maintain at
git://git.freescale.com/imx/linux-2.6-imx.git). The kernel running on
the machine in question is based on 3.10 with an impressive (that's
negative) patch stack on top. I think patches -2 and -3 are not relevant
for my setup because the two saif clocks are configured identically if
I'm not mistaken. However implementing the soft reset as is done in
patch -1 doesn't work here. When resetting saif1 (that is used for
recording with saif0 being it's master) the CLKGATE bit gets never set
and when breaking out of the loop the noise issue happend 5 out of 5
test runs in the first iteration.

Does this ring a bell for you? Even if there is something bad hidden in
the patch stack (or 3.10?) a reset should never fail, right?

Best regards
Uwe

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

             reply	other threads:[~2016-01-27 10:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 10:56 Uwe Kleine-König [this message]
2016-01-27 11:53 ` noise issues when recording sound on i.MX28 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
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=20160127105613.GC13664@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 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.