Re: [PATCH v3 7/8] memory: of: parse max-freq property
From: Dmitry Osipenko
Date: Sun Feb 06 2022 - 10:33:56 EST
06.02.2022 16:58, Krzysztof Kozlowski пишет:
> Passing the memory timings maximum frequency as an unit address was
> a workaround and instead 'max-freq' is preferred. Look for 'max-freq'
> first and then fallback to 'reg'.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxx>
> ---
> drivers/memory/of_memory.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/memory/of_memory.c b/drivers/memory/of_memory.c
> index b94408954d85..bac5c7f34936 100644
> --- a/drivers/memory/of_memory.c
> +++ b/drivers/memory/of_memory.c
> @@ -212,8 +212,10 @@ static int of_lpddr3_do_get_timings(struct device_node *np,
> {
> int ret;
>
> - /* The 'reg' param required since DT has changed, used as 'max-freq' */
> - ret = of_property_read_u32(np, "reg", &tim->max_freq);
> + ret = of_property_read_u32(np, "max-freq", &tim->max_freq);
> + if (ret)
> + /* Deprecated way of passing max-freq as 'reg' */
> + ret = of_property_read_u32(np, "reg", &tim->max_freq);
> ret |= of_property_read_u32(np, "min-freq", &tim->min_freq);
> ret |= of_property_read_u32(np, "tRFC", &tim->tRFC);
> ret |= of_property_read_u32(np, "tRRD", &tim->tRRD);
Reviewed-by: Dmitry Osipenko <digetx@xxxxxxxxx>