netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anup Patel <anup@brainfault.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
	"palmer@sifive.com" <palmer@sifive.com>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
	"troy.benjegerdes@sifive.com" <troy.benjegerdes@sifive.com>,
	"jamez@wit.com" <jamez@wit.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"schwab@suse.de" <schwab@suse.de>,
	"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"sachin.ghadi@sifive.com" <sachin.ghadi@sifive.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"ynezz@true.cz" <ynezz@true.cz>,
	"yash.shah@sifive.com" <yash.shah@sifive.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	Atish Patra <atish.patra@wdc.com>, Bin Meng <bmeng.cn@gmail.com>,
	Lukas Auer <lukas.auer@aisec.fraunhofer.de>
Subject: Re: [PATCH v2 0/2] Add macb support for SiFive FU540-C000
Date: Tue, 18 Jun 2019 15:02:45 +0530	[thread overview]
Message-ID: <CAAhSdy3zODw=JFaN=2F4K5-umihJDivLO8J8LBdkFkuZgzu41Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1906172019040.15057@viisi.sifive.com>

On Tue, Jun 18, 2019 at 8:56 AM Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
> On Mon, 17 Jun 2019, Alistair Francis wrote:
>
> > > The legacy M-mode U-boot handles the phy reset already, and I’ve been
> > > able to load upstream S-mode uboot as a payload via TFTP, and then
> > > load and boot a 4.19 kernel.
> > >
> > > It would be nice to get this all working with 5.x, however there are
> > > still
> > > several missing pieces to really have it work well.
> >
> > Let me know what is still missing/doesn't work and I can add it. At the
> > moment the only known issue I know of is a missing SD card driver in U-
> > Boot.
>
> The DT data has changed between the non-upstream data that people
> developed against previously, vs. the DT data that just went upstream
> here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=72296bde4f4207566872ee355950a59cbc29f852
>
> and
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c35f1b87fc595807ff15d2834d241f9771497205
>
> So Upstream U-Boot is going to need several patches to get things working
> again.  Clock identifiers and Ethernet are two known areas.

Done.

I just send-out few patches to fix U-Boot SiFive Clock driver.

The U-Boot SiFive Clock driver fix series can be found in
riscv_unleashed_clk_sync_v1 branch of:
https://github.com/avpatel/u-boot.git

Users will also require OpenSBI DTB fix which can be found
in sifive_unleashed_dtb_fix_v1 branch of:
https://github.com/avpatel/opensbi.git

With above fixes, we can now use same DTB for both U-Boot
and Linux kernel (5.2-rc1). Although, users are free to pass a
different DTB to Linux kernel via TFTP.

I have tested SiFive serial and Cadance MACB ethernet on
both U-Boot and Linux (5.2-rc1)

Regards,
Anup

  reply	other threads:[~2019-06-18  9:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17  4:19 [PATCH v2 0/2] Add macb support for SiFive FU540-C000 Yash Shah
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 [this message]
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='CAAhSdy3zODw=JFaN=2F4K5-umihJDivLO8J8LBdkFkuZgzu41Q@mail.gmail.com' \
    --to=anup@brainfault.org \
    --cc=Alistair.Francis@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@wdc.com \
    --cc=bmeng.cn@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jamez@wit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lukas.auer@aisec.fraunhofer.de \
    --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=schwab@suse.de \
    --cc=troy.benjegerdes@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).