From: Nishanth Menon <nm@ti.com>
To: Georgi Vlaev <g-vlaev@ti.com>
Cc: <ssantosh@kernel.org>, <mturquette@baylibre.com>,
<sboyd@kernel.org>, <robh+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <vigneshr@ti.com>
Subject: Re: [PATCH v2 2/2] clk: keystone: syscon-clk: Add support for AM62 epwm-tbclk
Date: Fri, 15 Apr 2022 14:20:48 -0500 [thread overview]
Message-ID: <20220415192048.mdkwqfs2ztz6vens@cherub> (raw)
In-Reply-To: <20220415190343.6284-3-g-vlaev@ti.com>
On 22:03-20220415, Georgi Vlaev wrote:
> AM62 has 3 instances of EPWM modules. Each EPWM module has
> an EPWM TBCLKEN module input used to individually enable or
> disable its EPWM time-base clock. The EPWM time-base clock
> enable input comes from the CTRLMMR_EPWM_TB_CLKEN register
> bits 0 to 2 in CTRL_MMR0 module (6.1.1.4.1.48 [1]). This
> is virtually the same setup as in AM64 but with 3 instead
> of 9 clock providers on AM62.
>
> Update the driver with the 3 instances of clocks associated
> to a new compatible: "ti,am62-epwm-tbclk".
>
> [1] https://www.ti.com/lit/pdf/spruiv7
>
> Signed-off-by: Georgi Vlaev <g-vlaev@ti.com>
> Tested-by: Vignesh Raghavendra <vigneshr@ti.com>
> ---
> drivers/clk/keystone/syscon-clk.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/clk/keystone/syscon-clk.c b/drivers/clk/keystone/syscon-clk.c
> index aae1a4076281..19198325b909 100644
> --- a/drivers/clk/keystone/syscon-clk.c
> +++ b/drivers/clk/keystone/syscon-clk.c
> @@ -162,6 +162,13 @@ static const struct ti_syscon_gate_clk_data am64_clk_data[] = {
> { /* Sentinel */ },
> };
>
> +static const struct ti_syscon_gate_clk_data am62_clk_data[] = {
> + TI_SYSCON_CLK_GATE("epwm_tbclk0", 0x0, 0),
> + TI_SYSCON_CLK_GATE("epwm_tbclk1", 0x0, 1),
> + TI_SYSCON_CLK_GATE("epwm_tbclk2", 0x0, 2),
Reviewed-by: Nishanth Menon <nm@ti.com>
Thanks for reordering.
> + { /* Sentinel */ },
> +};
> +
> static const struct of_device_id ti_syscon_gate_clk_ids[] = {
> {
> .compatible = "ti,am654-ehrpwm-tbclk",
> @@ -171,6 +178,10 @@ static const struct of_device_id ti_syscon_gate_clk_ids[] = {
> .compatible = "ti,am64-epwm-tbclk",
> .data = &am64_clk_data,
> },
> + {
> + .compatible = "ti,am62-epwm-tbclk",
> + .data = &am62_clk_data,
> + },
> { }
> };
> MODULE_DEVICE_TABLE(of, ti_syscon_gate_clk_ids);
> --
> 2.30.2
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2022-04-15 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 19:03 [PATCH v2 0/2] clk: keystone: Add support for AM62 specific ewpm-tbclk Georgi Vlaev
2022-04-15 19:03 ` [PATCH v2 1/2] dt-bindings: clock: ehrpwm: Add AM62 specific compatible Georgi Vlaev
2022-04-23 2:07 ` Stephen Boyd
2022-04-15 19:03 ` [PATCH v2 2/2] clk: keystone: syscon-clk: Add support for AM62 epwm-tbclk Georgi Vlaev
2022-04-15 19:20 ` Nishanth Menon [this message]
2022-04-23 2:07 ` 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=20220415192048.mdkwqfs2ztz6vens@cherub \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=g-vlaev@ti.com \
--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 \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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