From: Aniket Limaye <a-limaye@ti.com>
To: Neha Malcom Francis <n-francis@ti.com>, <u-boot@lists.denx.de>,
<trini@konsulko.com>
Cc: <u-kumar1@ti.com>, <reidt@ti.com>, <m-chawdhry@ti.com>, <nm@ti.com>
Subject: Re: [PATCH 1/6] arm: dts: k3-j7200-r5-common: Add msmc clk to a72 node
Date: Wed, 23 Oct 2024 11:42:54 +0530 [thread overview]
Message-ID: <41bee479-47cf-4ea4-b628-05d265bc2bbc@ti.com> (raw)
In-Reply-To: <9a5dc591-a5ca-4d53-9465-242986f4a62e@ti.com>
On 17/10/24 16:00, Neha Malcom Francis wrote:
> Hi Aniket
>
> On 17/10/24 11:59, Aniket Limaye wrote:
>> From: Reid Tonking <reidt@ti.com>
>>
>> Define the MSMC clk in the a72 node
>
> The usage of MSMC and A72SS interchangeably in this series is confusing.
> Could you expand on it in the cover letter why in J7200 this clock is
> defined as part of the A72 node as opposed to devices that have MSMC as
> a separate module altogether with its own clock (like J721S2 and J784S4)?
Yeah sure. will elaborate in v2:
The msmc clock frequency needs to be updated as per selected OPP (in
PATCH 4). But we don't have a msmc node for j721e/j7200, unlike those in
j721s2/j784s4. So we are defining the msmc clock in the a72_0 node, such
that it's frequency can be updated along with core clock frequency when
OPP_LOW config is selected.
I am open to suggestions if this is not the right place for it.
Thanks for the reviews!
Regards,
Aniket
>>
>> Signed-off-by: Reid Tonking <reidt@ti.com>
>> Signed-off-by: Aniket Limaye <a-limaye@ti.com>
>> ---
>> arch/arm/dts/k3-j7200-r5-common-proc-board.dts | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/arm/dts/k3-j7200-r5-common-proc-board.dts
>> b/arch/arm/dts/k3-j7200-r5-common-proc-board.dts
>> index f096b102793..759a1e83456 100644
>> --- a/arch/arm/dts/k3-j7200-r5-common-proc-board.dts
>> +++ b/arch/arm/dts/k3-j7200-r5-common-proc-board.dts
>> @@ -23,11 +23,11 @@
>> <&k3_pds 202 TI_SCI_PD_EXCLUSIVE>,
>> <&k3_pds 4 TI_SCI_PD_EXCLUSIVE>;
>> resets = <&k3_reset 202 0>;
>> - clocks = <&k3_clks 61 1>, <&k3_clks 202 2>;
>> - clock-names = "gtc", "core";
>> - assigned-clocks = <&k3_clks 202 2>, <&k3_clks 61 1>,
>> <&k3_clks 323 0>;
>> - assigned-clock-parents= <0>, <0>, <&k3_clks 323 2>;
>> - assigned-clock-rates = <2000000000>, <200000000>;
>> + clocks = <&k3_clks 61 1>, <&k3_clks 4 1>, <&k3_clks 202 2> ;
>> + clock-names = "gtc", "msmc", "core";
>> + assigned-clocks = <&k3_clks 202 2>, <&k3_clks 61 1>,
>> <&k3_clks 4 1>, <&k3_clks 323 0>;
>> + assigned-clock-parents= <0>, <0>, <0>, <&k3_clks 323 2>;
>> + assigned-clock-rates = <2000000000>, <200000000>, <1000000000>;
>> ti,sci = <&dmsc>;
>> ti,sci-proc-id = <32>;
>> ti,sci-host-id = <10>;
>
next prev parent reply other threads:[~2024-10-23 6:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 6:29 [PATCH 0/6] Add OPP_LOW support for J7200 Aniket Limaye
2024-10-17 6:29 ` [PATCH 1/6] arm: dts: k3-j7200-r5-common: Add msmc clk to a72 node Aniket Limaye
2024-10-17 10:30 ` Neha Malcom Francis
2024-10-23 6:12 ` Aniket Limaye [this message]
2024-10-23 6:47 ` Neha Malcom Francis
2024-10-23 7:58 ` Aniket Limaye
2024-10-23 8:51 ` Neha Malcom Francis
2024-10-17 6:29 ` [PATCH 2/6] misc: k3_avs: Add OPP_LOW voltage and frequency to vd_data Aniket Limaye
2024-10-17 6:29 ` [PATCH 3/6] misc: k3_avs: Add k3_check_opp function Aniket Limaye
2024-10-17 10:36 ` Neha Malcom Francis
2024-10-22 12:55 ` Limaye, Aniket
2024-10-17 6:29 ` [PATCH 4/6] arm: mach-k3: j721e-init.c: J7200: Add support for CONFIG_K3_OPP_LOW Aniket Limaye
2024-10-17 10:40 ` Neha Malcom Francis
2024-10-22 12:57 ` Limaye, Aniket
2024-10-17 6:29 ` [PATCH 5/6] configs: j7200_evm_r5_defconfig: Define K3_OPP_LOW Aniket Limaye
2024-10-17 6:29 ` [PATCH 6/6] DONOTMERGE: For testing only Aniket Limaye
2024-10-17 7:22 ` Lothar Waßmann
2024-10-17 17:54 ` Tom Rini
2024-10-18 4:51 ` Aniket Limaye
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=41bee479-47cf-4ea4-b628-05d265bc2bbc@ti.com \
--to=a-limaye@ti.com \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=reidt@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@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