From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Andrew Lunn <andrew@lunn.ch>, Bartosz Wawrzyniak <bwawrzyn@cisco.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <claudiu.beznea@microchip.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<xe-linux-external@cisco.com>, <danielwa@cisco.com>,
<olicht@cisco.com>, <mawierzb@cisco.com>
Subject: Re: [PATCH] net: macb: Set MDIO clock divisor for pclk higher than 160MHz
Date: Fri, 17 Mar 2023 15:02:35 +0100 [thread overview]
Message-ID: <3a625bc5-80ed-925d-2e16-bc3535320963@microchip.com> (raw)
In-Reply-To: <7f3d0f2c-8bf9-41aa-8a7f-79407753df3b@lunn.ch>
Andrew,
On 16/03/2023 at 20:34, Andrew Lunn wrote:
> On Thu, Mar 16, 2023 at 10:03:39AM +0000, Bartosz Wawrzyniak wrote:
>> Currently macb sets clock divisor for pclk up to 160 MHz.
>> Function gem_mdc_clk_div was updated to enable divisor
>> for higher values of pclk.
>>
>> Signed-off-by: Bartosz Wawrzyniak <bwawrzyn@cisco.com>
>> ---
>> drivers/net/ethernet/cadence/macb.h | 2 ++
>> drivers/net/ethernet/cadence/macb_main.c | 6 +++++-
>> 2 files changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/cadence/macb.h b/drivers/net/ethernet/cadence/macb.h
>> index 14dfec4db8f9..c1fc91c97cee 100644
>> --- a/drivers/net/ethernet/cadence/macb.h
>> +++ b/drivers/net/ethernet/cadence/macb.h
>> @@ -692,6 +692,8 @@
>> #define GEM_CLK_DIV48 3
>> #define GEM_CLK_DIV64 4
>> #define GEM_CLK_DIV96 5
>> +#define GEM_CLK_DIV128 6
>> +#define GEM_CLK_DIV224 7
>
> Do these divisors exist for all variants? I'm just wondering why these
> are being added now, rather than back in 2011-03-09.
I see them existing in all variants of "GEM" controller and the older
"MACB" uses a different path so I think that we are save enabling these
values.
The values were not added back in the days because the SoC where the
controller was used didn't reach the frequencies that we are observing
today for pclk. Divisors weren't needed and field even not completely
described in Microchip datasheets.
Hope that this sheds some light. Best regards,
Nicolas
--
Nicolas Ferre
next prev parent reply other threads:[~2023-03-17 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 10:03 Bartosz Wawrzyniak
2023-03-16 10:35 ` Michal Kubiak
2023-03-16 16:11 ` Nicolas Ferre
2023-03-16 19:34 ` Andrew Lunn
2023-03-17 14:02 ` Nicolas Ferre [this message]
2023-03-17 14:28 ` Andrew Lunn
2023-03-19 8:50 ` patchwork-bot+netdevbpf
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=3a625bc5-80ed-925d-2e16-bc3535320963@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=andrew@lunn.ch \
--cc=bwawrzyn@cisco.com \
--cc=claudiu.beznea@microchip.com \
--cc=danielwa@cisco.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mawierzb@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=olicht@cisco.com \
--cc=pabeni@redhat.com \
--cc=xe-linux-external@cisco.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®