From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: "Rob Herring" <robh+dt@kernel.org>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-actions@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Add Ethernet DTS for Actions Semi Owl S500 SoCs
Date: Fri, 11 Jun 2021 12:11:31 +0300 [thread overview]
Message-ID: <cover.1623401998.git.cristian.ciocaltea@gmail.com> (raw)
This patchset adds the required DTS changes for providing the ethernet
functionality on the Actions S500 SoCs family.
For the moment I have been able to test the Ethernet MAC on the RoseaplePi
SBC only.
Also, please note the patches depend on some clock changes that are
currently under review:
https://lore.kernel.org/lkml/cover.1623354574.git.cristian.ciocaltea@gmail.com/
Thanks,
Cristi
Changes in v2:
- Added Reviewed-by tag from Mani in patch 1/2
- Joined the groups sharing common function "eth_rmii" and switch the
order of "ref_clk-pinconf" and "phy_clk-pinmux", per Mani's review,
in patch 2/2
Cristian Ciocaltea (2):
ARM: dts: owl-s500: Add ethernet support
ARM: dts: owl-s500-roseapplepi: Add ethernet support
arch/arm/boot/dts/owl-s500-roseapplepi.dts | 45 ++++++++++++++++++++++
arch/arm/boot/dts/owl-s500.dtsi | 10 +++++
2 files changed, 55 insertions(+)
--
2.32.0
next reply other threads:[~2021-06-11 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 9:11 Cristian Ciocaltea [this message]
2021-06-11 9:11 ` [PATCH v2 1/2] ARM: dts: owl-s500: Add ethernet support Cristian Ciocaltea
2021-06-16 13:30 ` kernel test robot
2021-06-28 6:22 ` Manivannan Sadhasivam
2021-06-28 7:02 ` Cristian Ciocaltea
2021-06-28 7:31 ` Manivannan Sadhasivam
2021-06-11 9:11 ` [PATCH v2 2/2] ARM: dts: owl-s500-roseapplepi: " Cristian Ciocaltea
2021-06-14 11:27 ` Manivannan Sadhasivam
2021-06-14 11:28 ` [PATCH v2 0/2] Add Ethernet DTS for Actions Semi Owl S500 SoCs Manivannan Sadhasivam
2021-06-14 12:11 ` Cristian Ciocaltea
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=cover.1623401998.git.cristian.ciocaltea@gmail.com \
--to=cristian.ciocaltea@gmail.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--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).