From: Mateusz Holenko <mholenko@antmicro.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Stafford Horne <shorne@gmail.com>,
openrisc@lists.librecores.org
Cc: Karol Gugala <kgugala@antmicro.com>,
Mateusz Holenko <mholenko@antmicro.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Filip Kokosinski <fkokosinski@internships.antmicro.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Joel Stanley <joel@jms.id.au>
Subject: [PATCH 0/1] openrisc: LiteX+mor1kx platform
Date: Wed, 23 Oct 2019 11:54:33 +0200 [thread overview]
Message-ID: <20191023115427.23684-0-mholenko@antmicro.com> (raw)
This patchset adds a new LiteX SoC-based platform
configured for mor1kx (OpenRISC) CPU coupled with
LiteUART serial device.
Details about LiteX can be found at
https://github.com/enjoy-digital/litex.
This platform is intended for further extension
once drivers for other LiteX devices are merged
to the kernel.
NOTE:
This requires another patchset to be merged first:
https://lore.kernel.org/patchwork/cover/1143352/
Filip Kokosinski (1):
openrisc: add support for LiteX
MAINTAINERS | 1 +
arch/openrisc/boot/dts/or1klitex.dts | 49 +++++++++++++++++++++++
arch/openrisc/configs/or1klitex_defconfig | 18 +++++++++
3 files changed, 68 insertions(+)
create mode 100644 arch/openrisc/boot/dts/or1klitex.dts
create mode 100644 arch/openrisc/configs/or1klitex_defconfig
--
2.23.0
next reply other threads:[~2019-10-23 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 9:54 Mateusz Holenko [this message]
2019-10-23 9:54 ` [PATCH 1/1] openrisc: add support for LiteX Mateusz Holenko
2019-10-24 21:26 ` Stafford Horne
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=20191023115427.23684-0-mholenko@antmicro.com \
--to=mholenko@antmicro.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fkokosinski@internships.antmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=jonas@southpole.se \
--cc=kgugala@antmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=openrisc@lists.librecores.org \
--cc=paulmck@linux.ibm.com \
--cc=robh+dt@kernel.org \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
/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®