linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: sDMA on i.mx7d
Date: Wed, 15 Feb 2017 08:36:01 -0200	[thread overview]
Message-ID: <CAOMZO5B+7=JXdaefi9YRBEpe9ktV_oBN0Ogo2DFXUdvuZFvsYw@mail.gmail.com> (raw)
In-Reply-To: <e9c36a33f2a49df2a517db5869eaea7f@agner.ch>

Hi Alexandre,

On Wed, Feb 15, 2017 at 5:25 AM, Stefan Agner <stefan@agner.ch> wrote:
> Hi Alexandre,
>
> On 2017-02-14 14:24, Alexandre Belloni wrote:
>> Hi,
>>
>> I've been trying to get a PCM3168s codec with a Colibri iMX7 using TDM
>> on SAI2.
>> I've got it working properly with the 4.1.35 kernel from Toradex (based
>> on the 4.1.15 from Freescale).
>> It is working fine with and without providing a firmware to the sDMA.
>>
>> But, I couldn't get that to work with v4.9. I actually managed to
>> reproduce the issue using the SGTL5000 so I don't have any patch on top
>> of v4.9.
>
> I guess you are using the on module SGTL5000 to reproduce?
>
> When I added audio support I remember that the sound seemed to be ok to
> me. Is the corruption such that you can hear it?

I haven't noticed this issue on a warp7 board.

Could you please share your .wav files and reproduction steps?

Thanks

  reply	other threads:[~2017-02-15 10:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 22:24 sDMA on i.mx7d Alexandre Belloni
2017-02-15  7:25 ` Stefan Agner
2017-02-15 10:36   ` Fabio Estevam [this message]
2017-02-15 11:07   ` Alexandre Belloni
2017-02-15 22:44     ` Stefan Agner
2017-02-16 10:42       ` Alexandre Belloni
2017-02-16 15:36         ` Fabio Estevam
2017-02-16 16:40           ` Alexandre Belloni
2017-02-16 16:47             ` Lucas Stach
2017-02-16 17:08               ` Alexandre Belloni
2017-02-17  9:13                 ` EXT: " Han, Nandor (GE Healthcare)
2017-02-19 21:55                   ` Fabio Estevam
2017-02-20  8:27                     ` Han, Nandor (GE Healthcare)

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='CAOMZO5B+7=JXdaefi9YRBEpe9ktV_oBN0Ogo2DFXUdvuZFvsYw@mail.gmail.com' \
    --to=festevam@gmail.com \
    --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).