From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 0/8 v4] RISC-V: add LiteX SoC support
Date: Tue, 17 Aug 2021 13:10:21 +0300 [thread overview]
Message-ID: <20210817131021.674041b1630520e20dbe6995@gmail.com> (raw)
In-Reply-To: <20210817100435.114756-1-antonynpavlov@gmail.com>
On Tue, 17 Aug 2021 13:04:27 +0300
Antony Pavlov <antonynpavlov@gmail.com> wrote:
I have used git format-patch in a inproper way. Sorry!
I'll resend the patchseries.
> Changes since v3:
>
> * rebased on top of next branch;
> * the "console: support set baudrate for fixed baudrate drivers" patch
> is introduced so the "litex serial: add setbrg callback" patch is dropped;
> * update mac0 IP-block base addresses in litex dts according to latest
> SoC configuration.
>
> Changes since v2:
>
> * rebase on top of master branch (f873c7ff2497) +
> "RISC-V: extend multi-image to support both S- and M-Mode"
> (http://lists.infradead.org/pipermail/barebox/2021-May/036086.html).
> * "litex serial: add setbrg callback" patch by Marek Czerski is added
> for review;
> * fix "clocksource: timer-riscv: select CSR from device tree" patch;
> * change gpio IP-block base addresses in litex dts;
> * gpio-74xx-mmio uses device_get_match_data() now.
>
> Changes since v1:
>
> * rebased on top of next branch;
> * new patches are introduced:
> * clocksource: timer-riscv: select CSR from device tree
> * RISC-V: make RISCV_SBI and RISCV_M_MODE explicitly mutually exclusive
> * RISC-V: make it possible to build RV32I multi-image with DEBUG_LL=n
> * almost all of Ahmad's notes are fixed (e.g. unused header files inclusions are dropped);
> * NOT FIXED: gpio-74xx-mmio still uses dev_get_drvdata(), not device_get_match_data()
>
>
> Antony Pavlov (8):
> clocksource: timer-riscv: select CSR from device tree
> serial: add litex UART driver
> console: support set baudrate for fixed baudrate drivers
> gpio: add driver for 74xx-ICs with MMIO access
> spi: add litex spiflash driver
> net: add LiteEth driver
> RISC-V: add LiteX SoC and linux-on-litex-vexriscv support
> RISC-V: add litex_linux_defconfig
>
> arch/riscv/Kconfig.socs | 14 +
> arch/riscv/boards/Makefile | 1 +
> arch/riscv/boards/litex-linux/Makefile | 3 +
> arch/riscv/boards/litex-linux/lowlevel.c | 22 ++
> arch/riscv/configs/litex_linux_defconfig | 75 +++++
> arch/riscv/dts/Makefile | 1 +
> arch/riscv/dts/erizo.dtsi | 2 +
> arch/riscv/dts/litex-linux.dts | 92 ++++++
> arch/riscv/dts/litex_soc_linux.dtsi | 49 +++
> arch/riscv/include/asm/debug_ll.h | 3 +
> arch/riscv/include/asm/debug_ll_litex.h | 123 ++++++++
> common/Kconfig | 4 +
> common/console.c | 10 +-
> drivers/clocksource/timer-riscv.c | 24 +-
> drivers/gpio/Kconfig | 14 +
> drivers/gpio/Makefile | 1 +
> drivers/gpio/gpio-74xx-mmio.c | 165 ++++++++++
> drivers/net/Kconfig | 8 +
> drivers/net/Makefile | 1 +
> drivers/net/liteeth.c | 376 +++++++++++++++++++++++
> drivers/serial/Makefile | 1 +
> drivers/serial/serial_litex.c | 96 ++++++
> drivers/spi/Kconfig | 3 +
> drivers/spi/Makefile | 1 +
> drivers/spi/litex_spiflash.c | 241 +++++++++++++++
> images/Makefile.riscv | 4 +
> 26 files changed, 1318 insertions(+), 16 deletions(-)
> create mode 100644 arch/riscv/boards/litex-linux/Makefile
> create mode 100644 arch/riscv/boards/litex-linux/lowlevel.c
> create mode 100644 arch/riscv/configs/litex_linux_defconfig
> create mode 100644 arch/riscv/dts/litex-linux.dts
> create mode 100644 arch/riscv/dts/litex_soc_linux.dtsi
> create mode 100644 arch/riscv/include/asm/debug_ll_litex.h
> create mode 100644 drivers/gpio/gpio-74xx-mmio.c
> create mode 100644 drivers/net/liteeth.c
> create mode 100644 drivers/serial/serial_litex.c
> create mode 100644 drivers/spi/litex_spiflash.c
>
> --
> 2.32.0
>
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2021-08-17 10:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 10:04 Antony Pavlov
2021-08-17 10:04 ` [PATCH 1/8] clocksource: timer-riscv: select CSR from device tree Antony Pavlov
2021-08-17 10:04 ` [PATCH 2/8] serial: add litex UART driver Antony Pavlov
2021-08-17 10:04 ` [PATCH 3/8] console: support set baudrate for fixed baudrate drivers Antony Pavlov
2021-08-17 10:04 ` [PATCH 4/8] gpio: add driver for 74xx-ICs with MMIO access Antony Pavlov
2021-08-17 10:04 ` [PATCH 5/8] spi: add litex spiflash driver Antony Pavlov
2021-08-17 10:04 ` [PATCH 6/8] net: add LiteEth driver Antony Pavlov
2021-08-17 10:04 ` [PATCH 7/8] RISC-V: add LiteX SoC and linux-on-litex-vexriscv support Antony Pavlov
2021-08-17 10:04 ` [PATCH 8/8] RISC-V: add litex_linux_defconfig Antony Pavlov
2021-08-17 10:10 ` Antony Pavlov [this message]
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=20210817131021.674041b1630520e20dbe6995@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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