From: Stephen Boyd <sboyd@kernel.org>
To: Georgi Vlaev <g-vlaev@ti.com>,
mturquette@baylibre.com, robh+dt@kernel.org, ssantosh@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, nm@ti.com, vigneshr@ti.com,
Georgi Vlaev <g-vlaev@ti.com>
Subject: Re: [PATCH v2 2/2] clk: keystone: syscon-clk: Add support for AM62 epwm-tbclk
Date: Fri, 22 Apr 2022 19:07:34 -0700 [thread overview]
Message-ID: <20220423020737.5BCD6C385A4@smtp.kernel.org> (raw)
In-Reply-To: <20220415190343.6284-3-g-vlaev@ti.com>
Quoting Georgi Vlaev (2022-04-15 12:03:43)
> 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>
> ---
Applied to clk-next
prev parent reply other threads:[~2022-04-23 2:07 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
2022-04-23 2:07 ` Stephen Boyd [this message]
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=20220423020737.5BCD6C385A4@smtp.kernel.org \
--to=sboyd@kernel.org \
--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=nm@ti.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).