From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: devicetree@vger.kernel.org, Remi Pommarel <repk@triplefau.lt>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Fix espressobin ethernet support on mainline u-boot
Date: Wed, 06 Feb 2019 00:22:58 +0100 [thread overview]
Message-ID: <87ef8l95wt.fsf@FE-laptop> (raw)
In-Reply-To: <20190128200728.17747-1-repk@triplefau.lt>
Hi Remi,
On lun., janv. 28 2019, Remi Pommarel <repk@triplefau.lt> wrote:
> This patchset fixes ethernet and mv88e6341 switch support on espressobin
> board when bootloader does not initialize needed registers.
>
> This patchset should be applied along with pinctrl fixes from [1] which
> have been merged in next branch of linux-pinctrl tree.
>
> [1] https://lkml.org/lkml/2018/12/21/507
>
> Remi Pommarel (2):
> arm64: dts: armada-3720-espressobin: Configure RGMII and SMI pins
> arm64: dts: armada-3720-espressobin: Set mv88e6341 cpu port as
> RGMII-ID
>
Both patches applied to mvebu/dt64
Thanks,
Gregory
> arch/arm64/boot/dts/marvell/armada-3720-espressobin.dts | 7 +++++++
> arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 5 +++++
> 2 files changed, 12 insertions(+)
>
> --
> 2.20.1
>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2019-02-05 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 20:07 [PATCH 0/2] Fix espressobin ethernet support on mainline u-boot Remi Pommarel
2019-01-28 20:07 ` [PATCH 1/2] arm64: dts: armada-3720-espressobin: Configure RGMII and SMI pins Remi Pommarel
2019-01-28 20:07 ` [PATCH 2/2] arm64: dts: armada-3720-espressobin: Set mv88e6341 cpu port as RGMII-ID Remi Pommarel
2019-01-28 20:21 ` Andrew Lunn
2019-02-05 23:22 ` Gregory CLEMENT [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=87ef8l95wt.fsf@FE-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=repk@triplefau.lt \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=will.deacon@arm.com \
/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).