From: Shawn Guo <shawnguo@kernel.org>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: leoyang.li@nxp.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, rmk+kernel@armlinux.org.uk,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] arch: dts: specify the MDC frequency on Layerscape DPAA2 devices
Date: Sat, 29 Oct 2022 20:31:53 +0800 [thread overview]
Message-ID: <20221029123153.GW125525@dragon> (raw)
In-Reply-To: <20221025144117.1010488-1-ioana.ciornei@nxp.com>
On Tue, Oct 25, 2022 at 05:41:14PM +0300, Ioana Ciornei wrote:
> Up until now, the external MDIO controller frequency values relied
> either on the default ones out of reset or on those setup by u-boot.
> Let's just properly specify the MDC frequency in the DTS so that even
> without u-boot's intervention Linux can drive the MDIO bus.
>
> This patch set adds the needed properties on all DPAA2 based SoCs.
>
> Ioana Ciornei (3):
> arm64: dts: lx2160a: specify clock frequencies for the MDIO
> controllers
> arm64: dts: ls1088a: specify clock frequencies for the MDIO
> controllers
> arm64: dts: ls208xa: specify clock frequencies for the MDIO
> controllers
Applied all, thanks!
prev parent reply other threads:[~2022-10-29 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 14:41 [PATCH 0/3] arch: dts: specify the MDC frequency on Layerscape DPAA2 devices Ioana Ciornei
2022-10-25 14:41 ` [PATCH 1/3] arm64: dts: lx2160a: specify clock frequencies for the MDIO controllers Ioana Ciornei
2022-10-25 14:41 ` [PATCH 2/3] arm64: dts: ls1088a: " Ioana Ciornei
2022-10-25 14:41 ` [PATCH 3/3] arm64: dts: ls208xa: " Ioana Ciornei
2022-10-29 12:31 ` Shawn Guo [this message]
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=20221029123153.GW125525@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh+dt@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).