On Sun, Mar 19, 2023 at 07:42:55PM +0000, Diogo Ivo wrote:
> Add the reserved-memory regions of the nominal and derated tables setup by
> the bootloader so that the EMC frequency change code can access them.
>
> Signed-off-by: Diogo Ivo <diogo.ivo@xxxxxxxxxxxxxxxxxx>
> ---
> arch/arm64/boot/dts/nvidia/tegra210-smaug.dts | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts b/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts
> index 709f3f417a19..a74826ae97b4 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts
> +++ b/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts
> @@ -30,6 +30,22 @@ memory {
> reg = <0x0 0x80000000 0x0 0xc0000000>;
> };
>
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + nominal: emc-table@f67cc000 {
> + compatible = "nvidia,tegra210-emc-table";
> + reg = <0x0 0xf67cc000 0x0 0xbea0>;
> + };
> +
> + derated: emc-table@f67d7ea0 {
> + compatible = "nvidia,tegra210-emc-table";
> + reg = <0x0 0xf67d7ea0 0x0 0xbea0>;
> + };
> + };
> +
These tables are typically generated by the firmware/bootloader at
runtime. Often they'll use heap allocations for these, so the addresses
are not guaranteed to be static.
Can you share a few details about what set of components you've used to
set this up? If we add these we want to be as specific as possible that
people use exactly the same set of firmware files.
Thierry
Attachment:
signature.asc
Description: PGP signature
