From: Ninad Palsule <ninad@linux.ibm.com>
To: Jacky Chou <jacky_chou@aspeedtech.com>, Andrew Lunn <andrew@lunn.ch>
Cc: "andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"andrew@codeconstruct.com.au" <andrew@codeconstruct.com.au>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"eajames@linux.ibm.com" <eajames@linux.ibm.com>,
"edumazet@google.com" <edumazet@google.com>,
"joel@jms.id.au" <joel@jms.id.au>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"minyard@acm.org" <minyard@acm.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"ratbert@faraday-tech.com" <ratbert@faraday-tech.com>,
"robh@kernel.org" <robh@kernel.org>
Subject: Re: 回覆: 回覆: [PATCH v2 05/10] ARM: dts: aspeed: system1: Add RGMII support
Date: Fri, 10 Jan 2025 08:05:00 -0600 [thread overview]
Message-ID: <d80f5916-4918-4849-bf4e-2ef608ece09d@linux.ibm.com> (raw)
In-Reply-To: <SEYPR06MB5134A63DBE28AA1305967A0C9D1C2@SEYPR06MB5134.apcprd06.prod.outlook.com>
Hi Jacky,
On 1/10/25 03:15, Jacky Chou wrote:
> Hi Andrew,
>
> Thank you for your reply.
>
>>> I think the code already exist in the mainline:
>>> https://github.com/torvalds/linux/blob/master/drivers/clk/clk-ast2600.
>>> c#L595
>>>
>>> It is configuring SCU register in the ast2600 SOC to introduce delays.
>>> The mac is part of the SOC.
>> I could be reading this wrong, but that appears to create a gated clock.
>>
>> hw = clk_hw_register_gate(dev, "mac1rclk", "mac12rclk", 0,
>> scu_g6_base + ASPEED_MAC12_CLK_DLY, 29, 0,
>> &aspeed_g6_clk_lock);
>>
>> /**
>> * clk_hw_register_gate - register a gate clock with the clock framework
>> * @dev: device that is registering this clock
>> * @name: name of this clock
>> * @parent_name: name of this clock's parent
>> * @flags: framework-specific flags for this clock
>> * @reg: register address to control gating of this clock
>> * @bit_idx: which bit in the register controls gating of this clock
>> * @clk_gate_flags: gate-specific flags for this clock
>> * @lock: shared register lock for this clock */
>>
>> There is nothing here about writing a value into @reg at creation time to give
>> it a default value. If you look at the vendor code, it has extra writes, but i don't
>> see anything like that in mainline.
> Agree. You are right. This part is used to create a gated clock.
> We will configure these RGMII delay in bootloader like U-boot.
> Therefore, here does not configure delay again.
>
> Currently, the delay of RGMII is configured in SCU region not in ftgma100 region.
> And I studied ethernet-controller.yaml file, as you said, it has defined about rgmii
> delay property for MAC side to set.
> My plan is that I will move this delay setting to ftgmac100 driver from SCU.
> Add a SCU syscon property for ftgmac100 driver configures the RGMII delay.
>
> // aspeed-g6.dtsi
> mac0: ethernet@1e660000 {
> compatible = "aspeed,ast2600-mac", "faraday,ftgmac100";
> reg = <0x1e660000 0x180>;
> interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&syscon ASPEED_CLK_GATE_MAC1CLK>;
> aspeed,scu = <&syscon>; ------> add
> status = "disabled";
> };
>
> Because AST2600 MAC1/2 RGMII delay setting in scu region is combined to one 32-bit register,
> MAC3/4 is also. I will also use 'aliase' to get MAC index to set delay in scu.
>
> // aspeed-g6.dtsi
> aliases {
> ..........
> mac0 = &mac0;
> mac1 = &mac1;
> mac2 = &mac2;
> mac4 = &mac3;
> };
>
> Then, we can use rx-internal-delay-ps and tx-internal-delay-ps property to configure delay
> In ftgmac100 driver.
Thanks. When are you planning to push this change? I might need to hold
on to mac changes until then.
Regards,
Ninad
>
> If you have any questions, please let me know. Thank you.
>
> Thanks,
> Jacky
next prev parent reply other threads:[~2025-01-10 14:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 3:54 [PATCH v2 05/10] ARM: dts: aspeed: system1: Add RGMII support Jacky Chou
2025-01-08 17:52 ` Andrew Lunn
2025-01-08 19:14 ` Ninad Palsule
2025-01-08 20:17 ` Andrew Lunn
2025-01-08 22:31 ` Ninad Palsule
2025-01-08 23:08 ` Andrew Lunn
2025-01-09 10:33 ` 回覆: " Jacky Chou
2025-01-09 13:21 ` Andrew Lunn
2025-01-09 14:25 ` Ninad Palsule
2025-01-09 14:54 ` Andrew Lunn
2025-01-10 9:15 ` 回覆: " Jacky Chou
2025-01-10 14:04 ` Andrew Lunn
2025-01-10 14:54 ` Ninad Palsule
2025-01-10 15:38 ` Andrew Lunn
2025-01-22 13:07 ` Maxime Chevallier
2025-01-22 13:39 ` Andrew Lunn
2025-01-22 14:05 ` Maxime Chevallier
2025-01-13 6:18 ` 回覆: " Jacky Chou
2025-01-10 14:05 ` Ninad Palsule [this message]
2025-01-13 6:22 ` Jacky Chou
2025-01-13 14:26 ` Ninad Palsule
2025-01-13 14:38 ` Andrew Lunn
2025-01-15 2:57 ` 回覆: " Jacky Chou
2025-01-15 3:05 ` Andrew Lunn
2025-01-15 4:22 ` 回覆: " Jacky Chou
2025-01-15 13:30 ` Andrew Lunn
2025-01-20 6:59 ` 回覆: " Jacky Chou
2025-01-09 14:32 ` Ninad Palsule
2025-01-09 14:48 ` Andrew Lunn
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=d80f5916-4918-4849-bf4e-2ef608ece09d@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=edumazet@google.com \
--cc=jacky_chou@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pabeni@redhat.com \
--cc=ratbert@faraday-tech.com \
--cc=robh@kernel.org \
/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).