mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-15 16:53:54 +08:00
8a42d3fc9d
meson_mx_efuse_read calculates the address internal to the eFuse based
on the offset and the word size. This works fine with any given offset.
However, the offset is also included when writing to the output buffer.
This means that reading 4 bytes at offset 500 tries to write beyond the
array allocated by the nvmem core as it wants to write the 4 bytes to
"buffer address + offset (500)".
This issue did not show up in the previous tests since no driver uses
any value from the eFuse yet and reading the eFuse via sysfs simply
reads the whole eFuse, starting at offset 0.
Fix this by only including the offset in the internal address
calculation.
Fixes:
|
||
|---|---|---|
| .. | ||
| bcm-ocotp.c | ||
| core.c | ||
| imx-iim.c | ||
| imx-ocotp.c | ||
| Kconfig | ||
| lpc18xx_eeprom.c | ||
| lpc18xx_otp.c | ||
| Makefile | ||
| meson-efuse.c | ||
| meson-mx-efuse.c | ||
| mtk-efuse.c | ||
| mxs-ocotp.c | ||
| qfprom.c | ||
| rockchip-efuse.c | ||
| snvs_lpgpr.c | ||
| sunxi_sid.c | ||
| uniphier-efuse.c | ||
| vf610-ocotp.c | ||