From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Alain Volmat <avolmat@me.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] clk: st: clkgen-mux: search reg within node or parent
Date: Mon, 20 Dec 2021 09:42:43 +0100 [thread overview]
Message-ID: <674eb592-ec2a-0ff9-bbf5-eb4f0aff4251@foss.st.com> (raw)
In-Reply-To: <20211218211157.188214-3-avolmat@me.com>
Hi Alain
On 12/18/21 10:11 PM, Alain Volmat wrote:
> 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@me.com>
> ---
> v2: identical to v1
>
> drivers/clk/st/clkgen-mux.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/st/clkgen-mux.c b/drivers/clk/st/clkgen-mux.c
> index ce583ded968a..ee39af7a0b72 100644
> --- a/drivers/clk/st/clkgen-mux.c
> +++ b/drivers/clk/st/clkgen-mux.c
> @@ -57,10 +57,17 @@ static void __init st_of_clkgen_mux_setup(struct device_node *np,
> const char **parents;
> int num_parents = 0;
>
> + /*
> + * First check for reg property within the node to keep backward
> + * compatibility, then if reg doesn't exist look at the parent node
> + */
> reg = of_iomap(np, 0);
> if (!reg) {
> - pr_err("%s: Failed to get base address\n", __func__);
> - return;
> + reg = of_iomap(of_get_parent(np), 0);
> + if (!reg) {
> + pr_err("%s: Failed to get base address\n", __func__);
> + return;
> + }
> }
>
> parents = clkgen_mux_get_parents(np, &num_parents);
>
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
Thanks
Patrice
next prev parent reply other threads:[~2021-12-20 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 21:11 [PATCH v2 0/2] clk: st: update to avoid DT warnings Alain Volmat
2021-12-18 21:11 ` [PATCH v2 1/2] clk: st: clkgen-fsyn: search reg within node or parent Alain Volmat
2021-12-20 8:42 ` Patrice CHOTARD
2022-01-06 1:21 ` Stephen Boyd
2021-12-18 21:11 ` [PATCH v2 2/2] clk: st: clkgen-mux: " Alain Volmat
2021-12-20 8:42 ` Patrice CHOTARD [this message]
2022-01-06 1:22 ` Stephen Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=674eb592-ec2a-0ff9-bbf5-eb4f0aff4251@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=avolmat@me.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).