From: Sean Anderson <seanga2@gmail.com>
To: Samuel Holland <samuel@sholland.org>,
Lukasz Majewski <lukma@denx.de>, Simon Glass <sjg@chromium.org>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Jean-Jacques Hiblot <jjhiblot@ti.com>,
Michal Suchanek <msuchanek@suse.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Peng Fan <peng.fan@nxp.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 5/6] clk: Remove an unneeded check from clk_get_parent_rate()
Date: Mon, 20 Feb 2023 11:12:12 -0500 [thread overview]
Message-ID: <855bc6c9-98bd-a7d4-b96b-6faceee72f62@gmail.com> (raw)
In-Reply-To: <20230220055940.41890-6-samuel@sholland.org>
On 2/20/23 00:59, Samuel Holland wrote:
> There is no need to check the parent clock's ops. The following call to
> clk_get_rate() does that already.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
>
> drivers/clk/clk-uclass.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/clk/clk-uclass.c b/drivers/clk/clk-uclass.c
> index 9d052e5a814..53cfd819779 100644
> --- a/drivers/clk/clk-uclass.c
> +++ b/drivers/clk/clk-uclass.c
> @@ -504,7 +504,6 @@ struct clk *clk_get_parent(struct clk *clk)
>
> ulong clk_get_parent_rate(struct clk *clk)
> {
> - const struct clk_ops *ops;
> struct clk *pclk;
>
> debug("%s(clk=%p)\n", __func__, clk);
> @@ -515,10 +514,6 @@ ulong clk_get_parent_rate(struct clk *clk)
> if (IS_ERR(pclk))
> return -ENODEV;
>
> - ops = clk_dev_ops(pclk->dev);
> - if (!ops->get_rate)
> - return -ENOSYS;
> -
> /* Read the 'rate' if not already set or if proper flag set*/
> if (!pclk->rate || IS_ERR_VALUE(pclk->rate) ||
> pclk->flags & CLK_GET_RATE_NOCACHE)
Reviewed-by: Sean Anderson <seanga2@gmail.com>
next prev parent reply other threads:[~2023-02-20 16:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 5:59 [PATCH 0/6] clk: uclass fixes and improvements Samuel Holland
2023-02-20 5:59 ` [PATCH 1/6] clk: Handle error pointers in clk_valid() Samuel Holland
2023-02-20 10:46 ` Michal Suchánek
2023-02-20 15:57 ` Sean Anderson
2023-02-20 19:42 ` Michal Suchánek
2023-03-04 19:54 ` Samuel Holland
2023-03-04 20:43 ` Michal Suchánek
2023-02-20 5:59 ` [PATCH 2/6] clk: Fix error handling in clk_get_rate() Samuel Holland
2023-02-20 10:37 ` Michal Suchánek
2023-02-20 16:08 ` Sean Anderson
2023-02-20 17:27 ` Michal Suchánek
2023-02-20 17:58 ` Sean Anderson
2023-02-20 5:59 ` [PATCH 3/6] clk: Fix error handling in clk_get_parent() Samuel Holland
2023-02-20 10:39 ` Michal Suchánek
2023-03-04 19:58 ` Samuel Holland
2023-03-04 20:46 ` Michal Suchánek
2023-03-04 21:25 ` Sean Anderson
2023-02-20 5:59 ` [PATCH 4/6] clk: Fix rate caching in clk_get_parent_rate() Samuel Holland
2023-02-20 10:41 ` Michal Suchánek
2023-02-20 16:11 ` Sean Anderson
2023-03-04 20:01 ` Samuel Holland
2023-02-20 5:59 ` [PATCH 5/6] clk: Remove an unneeded check from clk_get_parent_rate() Samuel Holland
2023-02-20 10:49 ` Michal Suchánek
2023-02-20 16:12 ` Sean Anderson [this message]
2023-02-20 5:59 ` [PATCH 6/6] clk: Add a .get_parent operation Samuel Holland
2023-02-20 16:13 ` Sean Anderson
2023-02-20 16:21 ` Simon Glass
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=855bc6c9-98bd-a7d4-b96b-6faceee72f62@gmail.com \
--to=seanga2@gmail.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=jjhiblot@ti.com \
--cc=lukma@denx.de \
--cc=msuchanek@suse.de \
--cc=neil.armstrong@linaro.org \
--cc=peng.fan@nxp.com \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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