summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorDaniel Baluta <daniel.baluta@nxp.com>2019-07-22 09:13:47 -0500
committerMark Brown <broonie@kernel.org>2019-07-23 12:19:29 +0100
commitce8234a6357ec8f81b977d8536ff941dbd4162f3 (patch)
tree71f0b35476a35fcbde54fac44cd4b9ce7cfddd09 /tools/perf/scripts/python/bin
parentc9b54a3360166ca2fec11d55c86b5e685e56bab8 (diff)
downloadlinux-ce8234a6357ec8f81b977d8536ff941dbd4162f3.tar.gz
linux-ce8234a6357ec8f81b977d8536ff941dbd4162f3.zip
ASoC: SOF: Introduce snd_sof_dsp_get_bar_index ops
FW encapsulates information about section types (e.g DRAM, IRAM) inside module block header. This information can be used in order to correctly load the section to the appropriate place in memory. SOF Linux driver needs to know for each platform how to map the section type with the corresponding memory BAR. So, this patch introduces get_bar_index, a new operation inside snd_sof_dsp_ops. Intel platforms, usually load all the section in a contiguous memory area (usually denoted by sdev->mmio_bar) so things are relatively simple there. Anyhow, on i.MX8 IRAM and DRAM for example are mapped to distinct BARs. By default, if no get_bar function is provided the core implementation will always return sdev->mmio_bar so that there will be no need for a change to existing Intel code. Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> Link: https://lore.kernel.org/r/20190722141402.7194-7-pierre-louis.bossart@linux.intel.com Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions