All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@intel.com>
To: alsa-devel@alsa-project.org
Cc: Vinod Koul <vinod.koul@intel.com>,
	Jarkko Nikula <jarkko.nikula@intel.com>,
	Tyler Yeomans <tyeo098@gmail.com>
Subject: Re: Intel Baytrail Linux Audio
Date: Fri, 03 Jul 2015 09:51:02 +0100	[thread overview]
Message-ID: <1435913462.2478.14.camel@loki> (raw)
In-Reply-To: <20150702184035.GA1418140@phare.normalesup.org>

On Thu, 2015-07-02 at 20:40 +0200, Nicolas George wrote:
> Hi.
> 
> Tyler Yeomans:
> > I was able to recompile the distribution kernel after a long wait, and with
> > the changes that were made I was able to get some semblance of an audio
> > device registered.
> > 
> > I've attached the dmesg.
> > 
> > $ aplay -l
> > **** List of PLAYBACK Hardware Devices ****
> > card 0: bytrt5640 [byt-rt5640], device 0: Audio rt5640-aif1-0 []
> >   Subdevices: 1/1
> >   Subdevice #0: subdevice #0
> > 

Can you try the bytcr_rt5640 machine driver as the byt-rt5640 machine
driver will be getting deprecated (since it only works with a small
number of FWs). The bytcr_rt5640 driver works with a wider range of FW.

Thanks

Liam


---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

  reply	other threads:[~2015-07-03  8:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5589D025.7090700@gmail.com>
2015-06-24 10:11 ` Intel Baytrail Linux Audio Vinod Koul
2015-06-24 14:24   ` Tyler Yeomans
2015-06-24 16:03     ` Vinod Koul
2015-06-24 17:40       ` Tyler Yeomans
2015-06-25  6:38       ` Jarkko Nikula
2015-06-30 18:24         ` Tyler Yeomans
2015-06-30 22:57         ` Tyler Yeomans
2015-07-02 18:40           ` Nicolas George
2015-07-03  8:51             ` Liam Girdwood [this message]
2015-07-03  9:08               ` Antonio Ospite
2015-07-03  9:46                 ` Nicolas George
2015-07-03 10:32                   ` Antonio Ospite
2015-07-03 11:12                     ` Nicolas George
2015-07-03 12:10 Koul, Vinod
2015-07-03 12:36 ` Antonio Ospite
2015-07-03 13:06   ` Nicolas George
     [not found]     ` <559A90CE.2030105@gmail.com>
     [not found]       ` <20150707031950.GD11002@localhost>
2015-07-07 14:00         ` Tyler Yeomans
2015-07-07 17:08           ` Vinod Koul
2015-07-07 21:06             ` Tyler Yeomans
2015-07-08  3:36               ` Vinod Koul
2015-07-08  8:23                 ` Antonio Ospite
2015-07-08 14:30                   ` Tyler Yeomans
2015-07-08 16:21                     ` Antonio Ospite
2015-07-08 16:32                       ` Tyler Yeomans
2015-07-08 20:17                         ` Antonio Ospite
2015-07-08 20:24                           ` tyeo098
     [not found]                           ` <559EC436.30900@gmail.com>
2015-07-10  4:06                             ` Vinod Koul
2015-07-10 12:41                               ` Tyler Yeomans
2015-07-13 17:06                               ` Tyler Yeomans
2015-07-14  8:47                                 ` Vinod Koul
2015-07-23 15:24                                   ` Tyler Yeomans
2015-07-10  4:03                     ` Vinod Koul
2015-07-08 20:57                   ` Luka Karinja
     [not found]                   ` <559D88C1.3010504@bazdara.com>
2015-07-10  4:00                     ` Vinod Koul
2015-07-10 15:24                       ` Luka Karinja
  -- strict thread matches above, loose matches on Subject: below --
2015-07-03 13:43 Koul, Vinod

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=1435913462.2478.14.camel@loki \
    --to=liam.r.girdwood@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jarkko.nikula@intel.com \
    --cc=tyeo098@gmail.com \
    --cc=vinod.koul@intel.com \
    /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.