On Wed, 15 Sep 2021 15:21:04 +0300, Peter Ujfalusi wrote:
The direct use of 'bar' as address regions in SOF can limit portability and makes assumption that all platforms are using memory mapped regions or BARs to communicate with the DSP.
The core API should not use 'bar' in it's parameter lists or make assumption that the platform needs to comply with this system integration.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/12] ASoC: SOF: Intel: bdw: Set the mailbox offset directly in bdw_probe commit: 6375dbdbde67725220f2a07e428259c944d4c42d [02/12] ASoC: SOF: ipc: Remove snd_sof_dsp_mailbox_init() commit: b295818346aa7140dac865054a6c5efe8d4ec3ae [03/12] ASoC: SOF: imx: Do not initialize the snd_sof_dsp_ops.read64 commit: 098a68f2c5735b2fa8051ffe854b94b6d5b0a6a8 [04/12] ASoC: SOF: imx: imx8: Bar index is only valid for IRAM and SRAM types commit: 10d93a98190aec2c3ff98d9472ab1bf0543aa02c [05/12] ASoC: SOF: imx: imx8m: Bar index is only valid for IRAM and SRAM types commit: d9be4a88c3627c270bbe032b623dc43f3b764565 [06/12] ASoC: SOF: loader: No need to export snd_sof_fw_parse_ext_data() commit: 4ff134e2f90ee2816ca5a8069802ff5cb602a2f1 [07/12] ASoC: SOF: core: Do not use 'bar' as parameter for block_read/write commit: 4624bb2f03d3c153e00d21c1baa1da34cfc19afd [08/12] ASoC: SOF: debug: Add generic API and ops for DSP regions commit: 07e833b473e417f13c5a62aa6f63dbbd3028d277 [09/12] ASoC: SOF: imx: Provide debugfs_add_region_item ops for core commit: ff2f99b078a839c973434bcc9c1094814a38ae76 [10/12] ASoC: SOF: Intel: Provide debugfs_add_region_item ops for core commit: fe509b34b745d2284c3026abae8aaf02413a0594 [11/12] ASoC: SOF: loader: Use the generic ops for region debugfs handling commit: 55dfc2a74d8e8d34d6f562a1e4173e711bbd916d [12/12] ASoC: SOF: debug: No need to export the snd_sof_debugfs_io_item() commit: bde4f08cff47632f0a52e15a613365e26608d003
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