162306a36Sopenharmony_ci// SPDX-License-Identifier: GPL-2.0-or-later 262306a36Sopenharmony_ci 362306a36Sopenharmony_ci#include "ste-dbx5x0.dtsi" 462306a36Sopenharmony_ci 562306a36Sopenharmony_ci/ { 662306a36Sopenharmony_ci cpus { 762306a36Sopenharmony_ci cpu@300 { 862306a36Sopenharmony_ci operating-points = <998400 0 962306a36Sopenharmony_ci 798720 0 1062306a36Sopenharmony_ci 399360 0 1162306a36Sopenharmony_ci 199680 0>; 1262306a36Sopenharmony_ci }; 1362306a36Sopenharmony_ci }; 1462306a36Sopenharmony_ci 1562306a36Sopenharmony_ci reserved-memory { 1662306a36Sopenharmony_ci #address-cells = <1>; 1762306a36Sopenharmony_ci #size-cells = <1>; 1862306a36Sopenharmony_ci ranges; 1962306a36Sopenharmony_ci 2062306a36Sopenharmony_ci /* 2162306a36Sopenharmony_ci * Initial Secure Software ISSW memory 2262306a36Sopenharmony_ci * 2362306a36Sopenharmony_ci * This is probably only used if the kernel tries 2462306a36Sopenharmony_ci * to actually call into trustzone to run secure 2562306a36Sopenharmony_ci * applications, which the mainline kernel probably 2662306a36Sopenharmony_ci * will not do on this old chipset. But you can never 2762306a36Sopenharmony_ci * be too careful, so reserve this memory anyway. 2862306a36Sopenharmony_ci */ 2962306a36Sopenharmony_ci ram@17f00000 { 3062306a36Sopenharmony_ci reg = <0x17f00000 0x00100000>; 3162306a36Sopenharmony_ci no-map; 3262306a36Sopenharmony_ci }; 3362306a36Sopenharmony_ci }; 3462306a36Sopenharmony_ci}; 35