From: Yash Shah <yash.shah@sifive.com>
To: robh+dt@kernel.org, paul.walmsley@sifive.com,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, palmer@sifive.com, aou@eecs.berkeley.edu,
sachin.ghadi@sifive.com, Yash Shah <yash.shah@sifive.com>
Subject: [PATCH v2] DT node for SiFive FU540 Ethernet Controller driver
Date: Fri, 21 Jun 2019 16:23:48 +0530 [thread overview]
Message-ID: <1561114429-29612-1-git-send-email-yash.shah@sifive.com> (raw)
This patch-set is based on 'riscv-for-v5.2/fixes-rc6' tag of
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
Tested on HiFive Unleashed board with additional patches required for
testing can be found at dev/yashs/ethernet_dt_v2 branch of:
https://github.com/yashshah7/riscv-linux.git
Change history:
v2:
- Set "status = disabled" in DTSI file and enable it in Board DTS file
- Move PHY related nodes into board DTS file
Yash Shah (1):
riscv: dts: Add DT node for SiFive FU540 Ethernet controller driver
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 16 ++++++++++++++++
arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts | 9 +++++++++
2 files changed, 25 insertions(+)
--
1.9.1
next reply other threads:[~2019-06-21 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 10:53 Yash Shah [this message]
2019-06-21 10:53 ` [PATCH v2] riscv: dts: Add DT node for SiFive FU540 Ethernet controller driver Yash Shah
2019-06-21 11:20 ` Anup Patel
2019-06-21 19:14 ` Atish Patra
[not found] ` <CAF5mof3QB8C7VjOyEvCsf9NEDkJhV3cBO5sBD+8z-GrWrnrAyg@mail.gmail.com>
[not found] ` <3f91c8032e113a19dcec10ca71b017af1427ef7e.camel@wdc.com>
2019-06-21 21:59 ` Atish Patra
2019-06-22 0:33 ` Troy Benjegerdes
2019-06-22 1:57 ` Troy Benjegerdes
2019-06-23 7:04 ` Atish Patra
2019-06-22 18:15 ` Troy Benjegerdes
2019-06-21 22:06 ` Paul Walmsley
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=1561114429-29612-1-git-send-email-yash.shah@sifive.com \
--to=yash.shah@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.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®