From: Atish Patra <Atish.Patra@wdc.com>
To: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"yash.shah@sifive.com" <yash.shah@sifive.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "sachin.ghadi@sifive.com" <sachin.ghadi@sifive.com>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"ynezz@true.cz" <ynezz@true.cz>,
"palmer@sifive.com" <palmer@sifive.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: Re: [PATCH v3 0/2] Add macb support for SiFive FU540-C000
Date: Tue, 18 Jun 2019 23:27:56 +0000 [thread overview]
Message-ID: <ecded54c9b7bb7c85f029920db225cf19e1ee325.camel@wdc.com> (raw)
In-Reply-To: <1560844568-4746-1-git-send-email-yash.shah@sifive.com>
On Tue, 2019-06-18 at 13:26 +0530, Yash Shah wrote:
> 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_v3 branch of:
> https://github.com/yashshah7/riscv-linux.git
>
> Change History:
> V3:
> - Revert "MACB_SIFIVE_FU540" config changes in Kconfig and driver
> code.
> The driver does not depend on SiFive GPIO driver.
>
> 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/macb_main.c | 123
> +++++++++++++++++++++++++
> 2 files changed, 126 insertions(+)
>
Can you also post the ethernet dt entry[1] along with this patch ?
I think it would be good to all the dt related stuff reviewed together.
[1]
https://github.com/yashshah7/riscv-linux/commit/6d3af64bc5efed3915d658dc3bfe82dc1dbfafb3
I am able to get networking up in latest kernel + your patches in
OpenSBI + U-Boot(with updated compatible string) + Linux bootflow.
Tested-by: Atish Patra <atish.patra@wdc.com>
Regards,
Atish
next prev parent reply other threads:[~2019-06-18 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 7:56 [PATCH v3 0/2] Add macb support for SiFive FU540-C000 Yash Shah
2019-06-18 7:56 ` [PATCH v3 1/2] macb: bindings doc: add sifive fu540-c000 binding Yash Shah
2019-06-18 7:56 ` [PATCH v3 2/2] macb: Add support for SiFive FU540-C000 Yash Shah
2019-06-18 23:27 ` Atish Patra [this message]
2019-06-19 2:02 ` [PATCH v3 0/2] Add macb " David Miller
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=ecded54c9b7bb7c85f029920db225cf19e1ee325.camel@wdc.com \
--to=atish.patra@wdc.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=yash.shah@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).