From: Vinod Koul <vinod.koul@intel.com>
To: Dan O'Donovan <dan@emutex.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: CherryTrail SST firmware limitations query
Date: Thu, 28 Jan 2016 21:54:16 +0530 [thread overview]
Message-ID: <20160128162416.GR11130@localhost> (raw)
In-Reply-To: <56A1657A.5060600@emutex.com>
On Thu, Jan 21, 2016 at 11:10:50PM +0000, Dan O'Donovan wrote:
> (Sorry, re-sending as I wasn't subscribed to the alsa-devel mailing
> list on my previous attempt)
>
> Hi Vinod
>
> I am currently attempting to use the SSP0 port on an Intel X5-Z8300
> SoC (Cherry Trail) with a new codec.
>
> I have seen that you have committed SST firmware 'fw_sst_22a8.bin'
> and related SST audio soc drivers in the past, so I hope you don't
> mind if I ask you some questions about it here.
>
> Primarily, I am wondering if there are any limitations imposed by
> that firmware binary that I need to be aware of. I haven't been able
> to find much information about what this firmware does or doesn't
> support.
That binary is not for CHT. Each Bin is specfic to a platform. I have
the BYT and BSW versions, but not CHT
>
> For example, existing CHT SST machine drivers suggest that the PCM
> bit clock is fixed at 19.2MHz.
Yes, the MCLK will be 19.2 here
> Also, I am wondering if all SSP ports on the SoC are supported by
> that firmware, or if it is limited to just SSP2?
SSP2, for SSP0 we need to get a new version
> 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
HTH
--
~Vinod
next prev parent reply other threads:[~2016-01-28 16:20 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 [this message]
2016-01-28 17:23 ` Dan O'Donovan
2016-01-28 18:05 ` Pierre-Louis Bossart
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=20160128162416.GR11130@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=dan@emutex.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).