From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 04/12] ASoC: SOF: Add support for IPC IO between DSP and Host
Date: Tue, 04 Sep 2018 14:15:50 +0100 [thread overview]
Message-ID: <c8e92ab38c6f8bbe719344a92db8ed21ad30251e.camel@linux.intel.com> (raw)
In-Reply-To: <20180903155300.GQ10302@sirena.org.uk>
On Mon, 2018-09-03 at 16:53 +0100, Mark Brown wrote:
> On Fri, Aug 31, 2018 at 04:19:02PM +0100, Liam Girdwood wrote:
>
> > +/* SSP Configuration Request - SOF_IPC_DAI_SSP_CONFIG */
> > +struct sof_ipc_dai_ssp_params {
> > + /* MCLK */
> > + uint32_t mclk_direction;
> > + uint32_t mclk_keep_active;
> > + uint32_t bclk_keep_active;
> > + uint32_t fs_keep_active;
>
> Is this assuming a 1:1 relationship between the serial port and the
> MCLK?
Yes just for SSP atm.
> That's not going to be true for all systems. This definition
> does feel a bit specific to the SSP (or I guess just general serial
> ports used for audio as opposed to fixed function I2S/PCM controllers).
> I don't know if it's worth splitting up though.
>
Yeah, that's the intention is that we have a different structure for each DAI IP
type. We currently have :-
struct sof_ipc_dai_config {
struct sof_ipc_hdr hdr;
enum sof_ipc_dai_type type;
...
union {
struct dai_type_X;
struct dai_type_Y;
};
};
So we can add future DAI IPs as part of this union alongside a new type ID.
> > + uint16_t frame_pulse_width;
> > + uint32_t quirks; // FIXME: is 32 bits enough ?
>
> Better go for 640K to be sure :) ...
Yep, you never know :)
>
> > +/* HDA Configuration Request - SOF_IPC_DAI_HDA_CONFIG */
> > +struct sof_ipc_dai_hda_params {
> > + struct sof_ipc_hdr hdr;
> > + /* TODO */
> > +} __attribute__((packed));
>
> ...more seriously I do notice a bunch of these FIXME and TODO comments
> in here, given that it's an ABI it seems like those all need sorting
> before things are merged. In this case perhaps just delete the HDA
> stuff until someone works out what to do?
Will do.
Liam
next prev parent reply other threads:[~2018-09-04 13:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 15:18 [PATCH v2 00/12] Sound Open Firmware Core Liam Girdwood
2018-08-31 15:18 ` [PATCH v2 01/12] ASoC: SOF: Add Sound Open Firmware driver core Liam Girdwood
2018-09-03 15:07 ` Mark Brown
2018-08-31 15:19 ` [PATCH v2 02/12] ASoC: SOF: Add Sound Open Firmware KControl support Liam Girdwood
2018-08-31 15:19 ` [PATCH v2 03/12] ASoC: SOF: Add driver debug support Liam Girdwood
2018-08-31 15:19 ` [PATCH v2 04/12] ASoC: SOF: Add support for IPC IO between DSP and Host Liam Girdwood
2018-09-03 15:53 ` Mark Brown
2018-09-04 13:15 ` Liam Girdwood [this message]
2018-08-31 15:19 ` [PATCH v2 05/12] ASoC: SOF: Add PCM operations support Liam Girdwood
2018-08-31 15:19 ` [PATCH v2 06/12] ASoC: SOF: Add support for loading topologies Liam Girdwood
2018-09-03 16:19 ` Mark Brown
2018-08-31 15:19 ` [PATCH v2 07/12] ASoC: SOF: Add DSP firmware trace event support Liam Girdwood
2018-09-03 16:25 ` Mark Brown
2018-09-04 13:21 ` Liam Girdwood
2018-09-04 15:03 ` Mark Brown
2018-09-04 15:28 ` Liam Girdwood
2018-09-04 15:46 ` Mark Brown
2018-09-20 16:02 ` Liam Girdwood
2018-08-31 15:19 ` [PATCH v2 08/12] ASoC: SOF: Add DSP HW abstraction operations Liam Girdwood
2018-08-31 15:19 ` [PATCH v2 09/12] ASoC: SOF: Add firmware loader support Liam Girdwood
2018-08-31 15:19 ` [PATCH v2 10/12] ASoC: SOF: Add PM support Liam Girdwood
2018-08-31 15:19 ` [PATCH v2 11/12] ASoC: SOF: Add userspace ABI support Liam Girdwood
2018-08-31 15:19 ` [PATCH v2 12/12] ASoC: SOF: Add Build support for SOF core Liam Girdwood
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=c8e92ab38c6f8bbe719344a92db8ed21ad30251e.camel@linux.intel.com \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.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).