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 07/12] ASoC: SOF: Add DSP firmware trace event support
Date: Tue, 04 Sep 2018 16:28:49 +0100 [thread overview]
Message-ID: <fe9e199c8e9c3f688cc84393b85e1a390ace3c7b.camel@linux.intel.com> (raw)
In-Reply-To: <20180904150333.GF12993@sirena.org.uk>
On Tue, 2018-09-04 at 16:03 +0100, Mark Brown wrote:
> On Tue, Sep 04, 2018 at 02:21:20PM +0100, Liam Girdwood wrote:
> > On Mon, 2018-09-03 at 17:25 +0100, Mark Brown wrote:
> > > Should this be integrated into the Linux trace event mechanism rather
> > > than open coded? It would at least be nice to not call this a trace
> > > event buffer - when I initially read this I was expecting it to be for
> > > the standard Linux stuff which obviously it isn't.
> > Your right, I'll rename. The eventual aim is to make it more like Linux
> > trace
> > but we are constrained somewhat as some DSPs only 96kB or instruction RAM,
> > hence
> > it's a simple and raw trace infrastructure.
>
> I was thinking the code could read it like it's doing now and then just
> have a trace event to dump it into the core trace infrastructure as it
> reads things in.
Most of the data is binary atm, so we were decoding in userspace. Any objection
to decoding in the kernel as different trace events ?
Thanks
Liam
next prev parent reply other threads:[~2018-09-04 15:28 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
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 [this message]
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=fe9e199c8e9c3f688cc84393b85e1a390ace3c7b.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).