diff options
| author | Sam Day <me@samcday.com> | 2025-01-23 12:12:14 +0000 |
|---|---|---|
| committer | Caleb Connolly <caleb.connolly@linaro.org> | 2025-03-17 13:38:18 +0000 |
| commit | 11ff5a57e2fb82c8a8cef3aa8d2727452c282815 (patch) | |
| tree | f329353a49f1b73f7c66693c3f48a99d40c63f65 /test/py/tests/test_fs/test_basic.py | |
| parent | 2babb61428dcb55067a81f88bbc2124924807345 (diff) | |
mach-snapdragon: support parsing memory info from external FDT
qcom_parse_memory is updated to return a -ENODATA error if the passed
FDT does not contain a /memory node, or that node is incomplete (size=0)
board_fdt_blob_setup first tries to call qcom_parse_memory with the
internal FDT (if present+valid). If that fails, it tries again with the
external FDT (again, if present+valid).
When booting with an internal FDT from upstream, it's likely that this
change results in a slight performance hit, since virtually all upstream
qcom DTs lack a fully specified memory node. The impact should be
negligible, though.
qcom_parse_memory was given a detailed docstring adapted from Caleb's
original commit message that introduced the function.
Reviewed-by: Caleb Connolly <caleb.connolly@linaro.org>
Signed-off-by: Sam Day <me@samcday.com>
Link: https://lore.kernel.org/r/20250123-qcom-parse-memory-updates-v3-1-c5332b81ea9f@samcday.com
Signed-off-by: Caleb Connolly <caleb.connolly@linaro.org>
Diffstat (limited to 'test/py/tests/test_fs/test_basic.py')
0 files changed, 0 insertions, 0 deletions