From: Shawn Guo <shawnguo@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
David Jander <david@protonic.nl>
Subject: Re: [PATCH v1] ARM: dts: imx6qp-prtwd3: configure ENET_REF clock to 125MHz
Date: Sat, 14 Aug 2021 13:53:29 +0800 [thread overview]
Message-ID: <20210814055328.GZ30984@dragon> (raw)
In-Reply-To: <20210811073835.32082-1-o.rempel@pengutronix.de>
On Wed, Aug 11, 2021 at 09:38:35AM +0200, Oleksij Rempel wrote:
> By default ENET_REF is configured to 50MHz, which is usable for the RMII
> link. In case RGMII is used, we need 125MHz clock.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
David Jander <david@protonic.nl>
Subject: Re: [PATCH v1] ARM: dts: imx6qp-prtwd3: configure ENET_REF clock to 125MHz
Date: Sat, 14 Aug 2021 13:53:29 +0800 [thread overview]
Message-ID: <20210814055328.GZ30984@dragon> (raw)
In-Reply-To: <20210811073835.32082-1-o.rempel@pengutronix.de>
On Wed, Aug 11, 2021 at 09:38:35AM +0200, Oleksij Rempel wrote:
> By default ENET_REF is configured to 50MHz, which is usable for the RMII
> link. In case RGMII is used, we need 125MHz clock.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Applied, thanks!
next prev parent reply other threads:[~2021-08-14 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 7:38 [PATCH v1] ARM: dts: imx6qp-prtwd3: configure ENET_REF clock to 125MHz Oleksij Rempel
2021-08-11 7:38 ` Oleksij Rempel
2021-08-14 5:53 ` Shawn Guo [this message]
2021-08-14 5:53 ` Shawn Guo
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=20210814055328.GZ30984@dragon \
--to=shawnguo@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.