[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20220106012206.A2B6CC36AEB@smtp.kernel.org>
Date: Wed, 05 Jan 2022 17:22:05 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Alain Volmat <avolmat@...com>,
Michael Turquette <mturquette@...libre.com>,
Patrice Chotard <patrice.chotard@...s.st.com>,
Rob Herring <robh+dt@...nel.org>
Cc: Lee Jones <lee.jones@...aro.org>, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, Alain Volmat <avolmat@...com>
Subject: Re: [PATCH v2 2/2] clk: st: clkgen-mux: search reg within node or parent
Quoting Alain Volmat (2021-12-18 13:11:57)
> In order to avoid having duplicated addresses within the DT,
> only have one unit-address per clockgen and each driver within
> the clockgen should look at the parent node (overall clockgen)
> to figure out the reg property. Such behavior is already in
> place in other STi platform clock drivers such as clk-flexgen
> and clkgen-pll. Keep backward compatibility by first looking
> at reg within the node before looking into the parent node.
>
> Signed-off-by: Alain Volmat <avolmat@...com>
> ---
Applied to clk-next
Powered by blists - more mailing lists