alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: alsa-devel@alsa-project.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Antonio Ospite <ao2@ao2.it>,
	Ramesh Babu K V <Ramesh.Babu@intel.com>,
	Omair Mohammed Abdullah <omair.m.abdullah@intel.com>,
	Harsha Priya <priya.harsha@intel.com>,
	"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Subject: Re: Intel SST on a Bay Trail tablet
Date: Wed, 24 Jun 2015 15:46:13 +0530	[thread overview]
Message-ID: <20150624101613.GK19530@localhost> (raw)
In-Reply-To: <552D1EE3.6090707@linux.intel.com>

On Tue, Apr 14, 2015 at 05:06:27PM +0300, Jarkko Nikula wrote:
> My 2c below.
> 
> On 04/14/2015 04:02 PM, Antonio Ospite wrote:
> >On Wed, 4 Mar 2015 17:02:18 +0100
> >Antonio Ospite <ao2@ao2.it> wrote:
> 
> >I realized than I needed to set up the path between the FrontEnd DAI
> >and the BackEnd one, and in fact the error below goes away and I can
> >_start_ some playback after switching on these controls:
> >	codec_out1 mix 0 pcm0_in Switch
> >	media0_out mix 0 media1_in Switch
> >which AFAICS constitute the playback path.
> >
> >However there is still no sound, and the playback stalls, and the
> >interrupt count suddenly stops for the intel_sst_driver IRQ
> >(in /proc/interrupts).
> >
> What comes to my mind did you change .acpi_ipc_irq_index = 5 to 0
> zero in sound/soc/intel/sst/sst_acpi.c: byt_rvp_res_info structure?
> 
> According to Teclast's DSDT table the DSP-host interrupt is at first
> interrupt resource index.
> 
> >By looking at /sys/kernel/debug under Android it looks like the
> >codec is connected to SSP2, and not SSP0 as we imagined before:
> >/sys/kernel/debug/asoc/baytrailaudio/sst-platform/dapm/ssp2 playback
> >/sys/kernel/debug/asoc/baytrailaudio/sst-platform/dapm/ssp2 Capture
> >
> >So now I'd like to make sure the mixer settings are OK before looking
> >elsewhere again.
> >
> >Vinod, Subhransu, or anyone else, can you share some working alsa state
> >files for the baytrailcraudio device in linux mainline?
> >
> Question to Vinod et all too:
> 
> I don't find above "ssp2 playback" and "ssp2 Capture" stream names
> from sound/soc/intel/sst-mfld-platform-pcm.c so I guess it has been
> evolved a bit from those original Android drivers.
The upstream code is subset of one in Android but base stuff is still the
same

> 
> Which makes me thinking how does those strings describe the SSP port
> setup? E.g. do they reflect what port is actually used or could it
> be possible that those are just driver strings but firmware could
> have been tuned for SSP0? If I looked at earlier right, Teclast has
> the low pin-count Baytrail without SSP2 but I'm not sure about that.
The FW doesnt provide way to changes ports from driver in this, so this
doesnt mean much. If we are sure it is not ssp2, I can provide ssp1 fw for
test
> 
> >JFTR I am running a 64bit kernel, is this OK on BayTrail?
> >I guess it is, but I just wanted to mention this to be sure.
> >
> Generally yes. I've used both 32- and 64-bit kernels when developing
> the sound/soc/intel/sst-baytrail-* but I haven't tested
> sound/soc/intel/sst/. Vinod, I guess that should be 64-bit safe too?
Yup tested on both :)

-- 
~Vinod

  parent reply	other threads:[~2015-06-24 10:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 17:39 Intel SST on a Bay Trail tablet Antonio Ospite
2015-03-03 14:16 ` Antonio Ospite
2015-03-03 14:54   ` Jarkko Nikula
2015-03-03 16:17     ` Vinod Koul
2015-03-03 16:25       ` Babu, Ramesh
2015-03-04 16:02     ` Antonio Ospite
2015-03-12 13:45       ` Antonio Ospite
2015-03-12 14:30         ` Jarkko Nikula
2015-03-13  6:33           ` Vinod Koul
2015-03-13 14:36             ` Antonio Ospite
2015-04-03 13:34       ` Antonio Ospite
2015-04-14 13:02         ` Antonio Ospite
2015-04-14 14:06           ` Jarkko Nikula
2015-04-16 15:21             ` Antonio Ospite
2015-04-16 15:21             ` Antonio Ospite
2015-06-24 10:16             ` Vinod Koul [this message]
2015-06-24 11:25               ` Antonio Ospite
2015-06-25  5:50               ` Vinod Koul
2015-06-25 10:21                 ` Antonio Ospite
2015-06-25 16:47                   ` Vinod Koul
2015-06-26 13:05                     ` Antonio Ospite
2015-06-27 14:47                       ` Vinod Koul
2015-07-15 10:11                         ` Istvan Sandor
2015-09-18  0:41                         ` LemonZou
  -- strict thread matches above, loose matches on Subject: below --
2015-08-24 13:29 Michele Curti
2015-08-24 14:26 ` Vinod Koul
2015-08-24 15:05   ` Luka Karinja
2015-08-24 15:37     ` Pierre-Louis Bossart
2015-08-24 15:38     ` Michele Curti
2015-08-24 18:17   ` Michele Curti
2015-08-24 19:28     ` Pierre-Louis Bossart
2015-08-25  8:06       ` Michele Curti
2015-09-17 20:54         ` Luka Karinja
2015-09-21  7:14           ` Michele Curti

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=20150624101613.GK19530@localhost \
    --to=vinod.koul@intel.com \
    --cc=Ramesh.Babu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ao2@ao2.it \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=omair.m.abdullah@intel.com \
    --cc=priya.harsha@intel.com \
    --cc=subhransu.s.prusty@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 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).