From: Yash Shah <yash.shah@sifive.com>
To: davem@davemloft.net, devicetree@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
nicolas.ferre@microchip.com, palmer@sifive.com,
aou@eecs.berkeley.edu, paul.walmsley@sifive.com, ynezz@true.cz,
sachin.ghadi@sifive.com, Yash Shah <yash.shah@sifive.com>
Subject: [PATCH v2 0/2] Add macb support for SiFive FU540-C000
Date: Mon, 17 Jun 2019 09:49:25 +0530 [thread overview]
Message-ID: <1560745167-9866-1-git-send-email-yash.shah@sifive.com> (raw)
On FU540, the management IP block is tightly coupled with the Cadence
MACB IP block. It manages many of the boundary signals from the MACB IP
This patchset controls the tx_clk input signal to the MACB IP. It
switches between the local TX clock (125MHz) and PHY TX clocks. This
is necessary to toggle between 1Gb and 100/10Mb speeds.
Future patches may add support for monitoring or controlling other IP
boundary signals.
This patchset is mostly based on work done by
Wesley Terpstra <wesley@sifive.com>
This patchset is based on Linux v5.2-rc1 and tested on HiFive Unleashed
board with additional board related patches needed for testing can be
found at dev/yashs/ethernet branch of:
https://github.com/yashshah7/riscv-linux.git
Change History:
V2:
- Change compatible string from "cdns,fu540-macb" to "sifive,fu540-macb"
- Add "MACB_SIFIVE_FU540" in Kconfig to support SiFive FU540 in macb
driver. This is needed because on FU540, the macb driver depends on
SiFive GPIO driver.
- Avoid writing the result of a comparison to a register.
- Fix the issue of probe fail on reloading the module reported by:
Andreas Schwab <schwab@suse.de>
Yash Shah (2):
macb: bindings doc: add sifive fu540-c000 binding
macb: Add support for SiFive FU540-C000
Documentation/devicetree/bindings/net/macb.txt | 3 +
drivers/net/ethernet/cadence/Kconfig | 6 ++
drivers/net/ethernet/cadence/macb_main.c | 129 +++++++++++++++++++++++++
3 files changed, 138 insertions(+)
--
1.9.1
next reply other threads:[~2019-06-17 4:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 4:19 Yash Shah [this message]
2019-06-17 4:19 ` [PATCH v2 1/2] macb: bindings doc: add sifive fu540-c000 binding Yash Shah
2019-06-17 8:56 ` Paul Walmsley
2019-06-17 4:19 ` [PATCH v2 2/2] macb: Add support for SiFive FU540-C000 Yash Shah
2019-06-17 15:58 ` Andrew Lunn
2019-06-18 4:04 ` Yash Shah
2019-06-17 4:43 ` [PATCH v2 0/2] Add macb " Yash Shah
2019-06-17 8:25 ` Andreas Schwab
2019-06-17 9:58 ` Paul Walmsley
2019-06-17 10:01 ` Andreas Schwab
2019-06-17 10:05 ` Paul Walmsley
2019-06-17 10:14 ` Andreas Schwab
2019-06-17 11:34 ` Paul Walmsley
2019-06-17 14:14 ` Troy Benjegerdes
2019-06-17 14:20 ` Paul Walmsley
2019-06-17 18:42 ` Alistair Francis
2019-06-18 3:26 ` Paul Walmsley
2019-06-18 9:32 ` Anup Patel
2019-06-18 16:49 ` Troy Benjegerdes
2019-06-18 23:40 ` Atish Patra
2019-06-18 23:11 ` Alistair Francis
2019-06-17 10:22 ` Yash Shah
2019-06-17 10:28 ` Paul Walmsley
2019-06-17 11:15 ` Yash Shah
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=1560745167-9866-1-git-send-email-yash.shah@sifive.com \
--to=yash.shah@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.com \
--cc=ynezz@true.cz \
/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).