From: Roger Quadros <rogerq@kernel.org>
To: MD Danish Anwar <danishanwar@ti.com>,
conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
ssantosh@kernel.org, nm@ti.com,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, s-anna@ti.com, kristo@kernel.org,
srk@ti.com
Subject: Re: [PATCH v3 1/2] dt-bindings: soc: ti: pruss: Add clocks for ICSSG
Date: Thu, 21 Nov 2024 15:10:23 +0200 [thread overview]
Message-ID: <1c755fb4-964a-4c7b-819f-f5cf54baddfb@kernel.org> (raw)
In-Reply-To: <20241113110955.3876045-2-danishanwar@ti.com>
On 13/11/2024 13:09, MD Danish Anwar wrote:
> The ICSSG module has 7 clocks for each instance.
>
> These clocks are ICSSG0_CORE_CLK, ICSSG0_IEP_CLK, ICSSG0_ICLK,
> ICSSG0_UART_CLK, RGMII_MHZ_250_CLK, RGMII_MHZ_50_CLK and RGMII_MHZ_5_CLK
> These clocks are described in AM64x TRM Section 6.4.3 Table 6-398.
>
> Add these clocks to the dt binding of ICSSG.
>
> Link: https://www.ti.com/lit/pdf/spruim2 (AM64x TRM)
> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
Reviewed-by: Roger Quadros <rogerq@kernel.org>
next prev parent reply other threads:[~2024-11-21 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 11:09 [PATCH v3 0/2] Add Clocks " MD Danish Anwar
2024-11-13 11:09 ` [PATCH v3 1/2] dt-bindings: soc: ti: pruss: Add clocks " MD Danish Anwar
2024-11-14 20:11 ` Conor Dooley
2024-11-18 13:33 ` Roger Quadros
2024-11-18 13:52 ` Roger Quadros
2024-11-19 6:12 ` Vignesh Raghavendra
2024-11-19 10:45 ` Roger Quadros
2024-11-20 13:23 ` Anwar, Md Danish
2024-11-21 13:08 ` Roger Quadros
2024-11-21 13:10 ` Roger Quadros [this message]
2024-11-13 11:09 ` [PATCH v3 2/2] arm64: dts: ti: k3-am64-main: Switch ICSSG clock to core clock MD Danish Anwar
2024-11-19 10:47 ` Roger Quadros
2024-11-20 12:52 ` Wadim Egorov
2024-11-21 13:13 ` Roger Quadros
2024-12-16 10:23 ` [PATCH v3 0/2] Add Clocks for ICSSG MD Danish Anwar
2024-12-26 20:31 ` Nishanth Menon
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=1c755fb4-964a-4c7b-819f-f5cf54baddfb@kernel.org \
--to=rogerq@kernel.org \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-anna@ti.com \
--cc=srk@ti.com \
--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
all inboxes | Powered by JetHome®