mbox series

[0/3] ASoC: SOF: Intel: Add fw_regs area to debugfs map for IPC4

Message ID 20240409113349.21623-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: Intel: Add fw_regs area to debugfs map for IPC4 | expand

Message

Peter Ujfalusi April 9, 2024, 11:33 a.m. UTC 
Hi,

The beginning of the first SRAM window contains various fw registers and
additional information which can be very beneficial to read to gather
information on the current states to debug issues.

Regards,
Peter
---
Peter Ujfalusi (3):
  ASoC: SOF: Intel: tgl: Add fw_regs area to debugfs map for IPC4
  ASoC: SOF: Intel: mtl: Add fw_regs area to debugfs map
  ASoC: SOF: Intel: lnl: Add fw_regs area to debugfs map

 sound/soc/sof/intel/lnl.c |  1 +
 sound/soc/sof/intel/mtl.c |  1 +
 sound/soc/sof/intel/tgl.c | 15 +++++++++++----
 3 files changed, 13 insertions(+), 4 deletions(-)

Comments

Mark Brown April 9, 2024, 11:34 p.m. UTC | #1 
On Tue, 09 Apr 2024 14:33:46 +0300, Peter Ujfalusi wrote:
> The beginning of the first SRAM window contains various fw registers and
> additional information which can be very beneficial to read to gather
> information on the current states to debug issues.
> 
> Regards,
> Peter
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: SOF: Intel: tgl: Add fw_regs area to debugfs map for IPC4
      commit: 25ab9c40e77ed4d73995fb6eef514e2e9c421dab
[2/3] ASoC: SOF: Intel: mtl: Add fw_regs area to debugfs map
      commit: d33a369ddad522eff40c6b9687db1488e19729d6
[3/3] ASoC: SOF: Intel: lnl: Add fw_regs area to debugfs map
      commit: 61faefa220262de60d652dd6b91fdcb7ecae2258

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