[0/5] ASoC: SOF: extended manifest support for 5.8

Message

Kai Vehmanen May 20, 2020, 4:59 p.m. UTC

Hello,

extended firmware manifest is a method to retrieve capabilities
directly from the firmware file instead of routing the information via
the DSP and reading it back via IPC (latter mechanism still supported
but will be deprecated).

This feature was briefly merged to 5.8 with the series sent on
2020-Apr-15, but due to a regression hit with exporting uapi headers,
the patches got dropped.

Here's an update with the uapi header issue fixed, rebased to latest
'for-5.8' and a few minor fixes. This has been sitting in sof-dev for
some weeks and no further issues have been found. We also added
a check for the uapi-export case to SOF CI, so such errors would
not slip through again in the future.

Tooling support to create firmware files with an extended header
is available in SOF firmware repository (see the rimage tool) and
this part is already merged.

Karol Trzcinski (5):
  ASoC: SOF: loader: Adjust validation condition for fw_offset
  ASoC: SOF: Introduce extended manifest
  ASoC: SOF: ext_manifest: parse firmware version
  ASoC: SOF: ext_manifest: parse windows
  ASoC: SOF: ext_manifest: parse compiler version

 include/sound/sof/ext_manifest.h |  95 +++++++++++++++++
 sound/soc/sof/intel/hda-loader.c |   2 +-
 sound/soc/sof/loader.c           | 176 ++++++++++++++++++++++++++++++-
 3 files changed, 269 insertions(+), 4 deletions(-)
 create mode 100644 include/sound/sof/ext_manifest.h

Comments

Mark Brown May 25, 2020, 2:56 p.m. UTC | #1

On Wed, 20 May 2020 19:59:06 +0300, Kai Vehmanen wrote:
> extended firmware manifest is a method to retrieve capabilities
> directly from the firmware file instead of routing the information via
> the DSP and reading it back via IPC (latter mechanism still supported
> but will be deprecated).
> 
> This feature was briefly merged to 5.8 with the series sent on
> 2020-Apr-15, but due to a regression hit with exporting uapi headers,
> the patches got dropped.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/5] ASoC: SOF: loader: Adjust validation condition for fw_offset
      commit: 523773b9ea9f430810332aa117ea48f8feafce9a
[2/5] ASoC: SOF: Introduce extended manifest
      commit: a80cf1987a6e728b4d5c8e5041132d46e89c7a45
[3/5] ASoC: SOF: ext_manifest: parse firmware version
      commit: 3e2a89d3ee052ef5346ba933e557c807333ced11
[4/5] ASoC: SOF: ext_manifest: parse windows
      commit: 8d809c15acf23bb2863ec08578ab72de860b3abc
[5/5] ASoC: SOF: ext_manifest: parse compiler version
      commit: 4c4a975178ef06324c80baef0e95209f431645a5

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark