From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Igor Prusov <ivprusov@sberdevices.ru>,
Michal Simek <michal.simek@amd.com>,
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Chia-Wei Wang <chiawei_wang@aspeedtech.com>,
Aspeed BMC SW team <BMC-SW@aspeedtech.com>,
Joel Stanley <joel@jms.id.au>, Stefan Roese <sr@denx.de>,
Patrick Delaunay <patrick.delaunay@foss.st.com>
Cc: <prusovigor@gmail.com>, <kernel@sberdevices.ru>,
<u-boot@lists.denx.de>,
<uboot-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v3 4/7] clk: Add dump operation to clk_ops
Date: Mon, 28 Aug 2023 11:57:01 +0200 [thread overview]
Message-ID: <2421e072-58dc-e192-a4a3-9af98e996f3d@foss.st.com> (raw)
In-Reply-To: <20230714152444.24395-5-ivprusov@sberdevices.ru>
On 7/14/23 17:24, Igor Prusov wrote:
> This adds dump function to struct clk_ops which should replace
> soc_clk_dump. It allows clock drivers to provide custom dump
> implementation without overriding generic CCF dump function.
>
> Signed-off-by: Igor Prusov <ivprusov@sberdevices.ru>
> ---
> include/clk-uclass.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/clk-uclass.h b/include/clk-uclass.h
> index 65ebff9ed2..f29f4c0d01 100644
> --- a/include/clk-uclass.h
> +++ b/include/clk-uclass.h
> @@ -39,6 +39,9 @@ struct clk_ops {
> int (*set_parent)(struct clk *clk, struct clk *parent);
> int (*enable)(struct clk *clk);
> int (*disable)(struct clk *clk);
> +#if IS_ENABLED(CONFIG_CMD_CLK)
> + int (*dump)(struct udevice *dev);
> +#endif
> };
>
> #if 0 /* For documentation only */
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
Tested-by: Patrice Chotard <patrice.chotard@foss.st.com>
Thanks
Patrice
next prev parent reply other threads:[~2023-08-28 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 15:24 [PATCH v3 0/7] clk: Switch from soc_clk_dump to clk_ops function Igor Prusov
2023-07-14 15:24 ` [PATCH v3 1/7] clk: zynq: Move soc_clk_dump to Zynq clock driver Igor Prusov
2023-07-14 15:24 ` [PATCH v3 2/7] clk: ast2600: Move soc_clk_dump function Igor Prusov
2023-07-14 15:24 ` [PATCH v3 3/7] clk: k210: " Igor Prusov
2023-07-14 15:24 ` [PATCH v3 4/7] clk: Add dump operation to clk_ops Igor Prusov
2023-08-28 9:57 ` Patrice CHOTARD [this message]
2023-07-14 15:24 ` [PATCH v3 5/7] cmd: clk: Use dump function from clk_ops Igor Prusov
2023-08-28 9:56 ` Patrice CHOTARD
2023-07-14 15:24 ` [PATCH v3 6/7] clk: treewide: switch to clock dump " Igor Prusov
2023-08-28 9:56 ` Patrice CHOTARD
2023-07-14 15:24 ` [PATCH v3 7/7] cmd: clk: Make soc_clk_dump static Igor Prusov
2023-08-28 9:57 ` Patrice CHOTARD
2023-07-31 13:20 ` [PATCH v3 0/7] clk: Switch from soc_clk_dump to clk_ops function Igor Prusov
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=2421e072-58dc-e192-a4a3-9af98e996f3d@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=BMC-SW@aspeedtech.com \
--cc=chiawei_wang@aspeedtech.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=ivprusov@sberdevices.ru \
--cc=joel@jms.id.au \
--cc=kernel@sberdevices.ru \
--cc=lukma@denx.de \
--cc=michal.simek@amd.com \
--cc=patrick.delaunay@foss.st.com \
--cc=prusovigor@gmail.com \
--cc=ryan_chen@aspeedtech.com \
--cc=seanga2@gmail.com \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=uboot-stm32@st-md-mailman.stormreply.com \
/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