Skip to content

[qcom-next] WORKAROUND: arm: dts: talos-evk: drop pil_mem reservation - #138

Merged
Gopinath Sekar (g-sekar) merged 1 commit into
qualcomm-linux:qcom-nextfrom
balajiselvanathan:talos-reserved-drop-pil
Sep 11, 2026
Merged

Gopinath Sekar (g-sekar) merged 1 commit into
qualcomm-linux:qcom-nextfrom
balajiselvanathan:talos-reserved-drop-pil

Conversation

@balajiselvanathan

Copy link
Copy Markdown

The pil-reserved@84300000 node is a coarse carveout inherited from the downstream kernel. The upstream qcs615 board DTS already reserves the firmware-bearing parts of that range with fine-grained per-subsystem nodes. The remaining span of the blanket holds no firmware and does not need reserving in U-Boot.

Drop the redundant blanket node so U-Boot can use the DRAM the per-subsystem reservations don't claim.

Since the reserved mem changes are downstream, there is no upstram submission for this.

@g-sekar Gopinath Sekar (g-sekar) left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add workaround tag to commit message

The pil-reserved@84300000 node is a coarse carveout inherited
from the downstream kernel. The upstream qcs615 board DTS
already reserves the firmware-bearing parts of that range with
fine-grained per-subsystem nodes. The remaining span of the blanket
holds no firmware and does not need reserving in U-Boot.

Drop the redundant blanket node so U-Boot can use the DRAM the
per-subsystem reservations don't claim.

Signed-off-by: Balaji Selvanathan <balaji.selvanathan@oss.qualcomm.com>
@balajiselvanathan balajiselvanathan changed the title [qcom-next] arm: dts: talos-evk: drop pil_mem reservation [qcom-next] WORKAROUND: arm: dts: talos-evk: drop pil_mem reservation Sep 11, 2026
@balajiselvanathan

Copy link
Copy Markdown
Author

Can you add workaround tag to commit message

Added.

@g-sekar
Gopinath Sekar (g-sekar) merged commit fb659ff into qualcomm-linux:qcom-next Sep 11, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants