From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Dan O'Donovan <dan@emutex.com>, Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: CherryTrail SST firmware limitations query
Date: Thu, 28 Jan 2016 10:05:38 -0800 [thread overview]
Message-ID: <56AA5872.3020809@linux.intel.com> (raw)
In-Reply-To: <56AA4EA7.6060801@emutex.com>
>>> Are there any other limitations that I may need to be aware of in
>>> the firmware (or in the SSP back-end driver) when attempting to
>>> connect a new codec (TI PCM5122 initially) to SSP0.
>> Bigger pole will be getting the firmware. Usually we support I2S and TDM
>> modes
> Thanks very much for your reply, Vinod! That probably explains why I'm
> seeing clock signals from SSP0 but no audio data.
> Can you tell me who I could contact to request SST firmware for CHT with
> SSP0 support?
This doesn't make sense to me. To the best of my knowledge the firmware
does support SSP0 but in a limited configuration compared to SSP0. It
should work for regular 48kHz audio in I2S mode but not in TDM mode. If
you see clock signals on SSP0 and no data then it's probably because the
DSP routing controls are incorrect.
The best fix would be to use SSP2 really to get all the functionality.
next prev parent reply other threads:[~2016-01-28 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56A162A1.1070602@emutex.com>
2016-01-21 23:10 ` CherryTrail SST firmware limitations query Dan O'Donovan
2016-01-28 16:24 ` Vinod Koul
2016-01-28 17:23 ` Dan O'Donovan
2016-01-28 18:05 ` Pierre-Louis Bossart [this message]
2016-01-28 21:20 ` Dan O'Donovan
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=56AA5872.3020809@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=dan@emutex.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.