firmware: cs_dsp: Avoid using a u32 as a __be32 in cs_dsp_mock_mem_maps.c
Subsystems (2)
Richard Fitzgerald
maintainerPATCH 1/1 firmware: cs_dsp: Avoid using a u32 as a __be32 in cs_dsp_mock_mem_maps.c
In cs_dsp_mock_xm_header_drop_from_regmap_cache() for the ADSP2 case read the big-endian firmware word into a dedicated __be32 variable instead of using the same u32 for both the big-endian and cpu-endian value.
--- drivers/firmware/cirrus/test/cs_dsp_mock_mem_maps.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/firmware/cirrus/test/cs_dsp_mock_mem_maps.c +4 -3
@@ -526,7 +526,8 @@ void cs_dsp_mock_xm_header_drop_from_regmap_cache(struct cs_dsp_test *priv) {unsigned int xm =cs_dsp_mock_base_addr_for_mem (priv,WMFW_ADSP2_XM );unsigned int bytes; -u32 num_algs; +__be32 num_algs_be32; +unsigned int num_algs;switch (priv->dsp->type) {case WMFW_ADSP2 :
@@ -536,8 +537,8 @@ void cs_dsp_mock_xm_header_drop_from_regmap_cache(struct cs_dsp_test *priv)*/ regmap_raw_read (priv->dsp->regmap, xm + (offsetof(struct wmfw_adsp2_id_hdr , n_algs) /2 ), - &num_algs,sizeof (num_algs)); - num_algs =be32_to_cpu (num_algs); + &num_algs_be32,sizeof (num_algs_be32)); + num_algs =be32_to_cpu (num_algs_be32); bytes =sizeof (struct wmfw_adsp2_id_hdr ) + (num_algs *sizeof (struct wmfw_adsp2_alg_hdr )) +4 /* terminator word */ ;
Signature · 1 line
2.39.5
Quoted 5 lines · Richard Fitzgerald
In
cs_dsp_mock_xm_header_drop_from_regmap_cache()for the ADSP2 case read the big-endian firmware word into a dedicated__be32variable instead of using the same u32 for both the big-endian and cpu-endian value.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] firmware: cs_dsp: Avoid using a u32 as a __be32 in cs_dsp_mock_mem_maps.c
commit: a5bd108d4a57d6c00372041c83e633a26fb450de
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