ASoC: SOF: mediatek: mt8195: remove a redundant comparison of sram
Subsystems (4)
PATCH 1/1 ASoC: SOF: mediatek: mt8195: remove a redundant comparison of sram
DSP SRAM is not used for audio shared buffer between host and DSP so TOTAL_SIZE_SHARED_SRAM_FROM_TAIL is zero. Remove the definition and redundant comparison to fix coverity "unsigned compared against 0".
--- sound/soc/sof/mediatek/mt8195/mt8195.c | 5 ----- sound/soc/sof/mediatek/mt8195/mt8195.h | 2 -- 2 files changed, 7 deletions(-)
sound/soc/sof/mediatek/mt8195/mt8195.c +0 -5
@@ -215,11 +215,6 @@ static int platform_parse_resource(struct platform_device *pdev, void *data) adsp->pa_sram = (phys_addr_t )mmio->start; adsp->sramsize =resource_size (mmio); -if (adsp->sramsize <TOTAL_SIZE_SHARED_SRAM_FROM_TAIL ) { -dev_err (dev,"adsp SRAM(%#x) is not enough for share\n" , - adsp->sramsize); -return -EINVAL ; - }dev_dbg (dev,"sram pbase=%pa,%#x\n" , &adsp->pa_sram, adsp->sramsize);
sound/soc/sof/mediatek/mt8195/mt8195.h +0 -2
@@ -139,8 +139,6 @@ struct snd_sof_dev;#define DSP_MBOX1_BAR 6#define DSP_MBOX2_BAR 7 -#define TOTAL_SIZE_SHARED_SRAM_FROM_TAIL 0x0 -#define SIZE_SHARED_DRAM_DL 0x40000/*Shared buffer for Downlink*/ #define SIZE_SHARED_DRAM_UL 0x40000/*Shared buffer for Uplink*/
Signature · 1 line
2.18.0
Il 15/12/22 07:10, YC Hung ha scritto:
Quoted 5 lines
DSP SRAM is not used for audio shared buffer between host and DSP so
TOTAL_SIZE_SHARED_SRAM_FROM_TAILis zero. Remove the definition and redundant comparison to fix coverity "unsigned compared against 0".Signed-off-by YC Hung <[email protected]>
Mark Brown
maintainerQuoted 5 lines · YC Hung
DSP SRAM is not used for audio shared buffer between host and DSP so
TOTAL_SIZE_SHARED_SRAM_FROM_TAILis zero. Remove the definition and redundant comparison to fix coverity "unsigned compared against 0".
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SOF: mediatek: mt8195: remove a redundant comparison of sram
commit: 3f58ff6b53c11773b1bd564082fae37d48e0cc40
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