From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] SFF support for ZII CFU1 and devel C.
Date: Sun, 2 Sep 2018 18:29:10 +0200 [thread overview]
Message-ID: <1535905752-17730-1-git-send-email-andrew@lunn.ch> (raw)
Both the ZII CFU1 and Devel C have SFF modules. These patches add some
of them to the device tree description of these boards.
In order for the CFU1 to fully work, it requires patches submitted in
net-next. Without those patches, the link partner must already be up
when the SFF interface is configured up. There are no build time
dependencies, so merging them via different trees is not a problem.
Devel C generally has 2 SFF modules populated. The patch here adds
full support for SFF2. All the needed driver code is already present.
SFF3 is not yet supported by the mv88e6xxx driver. So the SFF3 device
itself is added to DT, but the module is not linked to a port.
Andrew Lunn (1):
ARM: dts: vf610-zii-cfu1: Add SFF interface to switch
Russell King (1):
ARM: dts: vf610-zii-dev-rev-c: add support for one SFF module
arch/arm/boot/dts/vf610-zii-cfu1.dts | 27 ++++++++++++++
arch/arm/boot/dts/vf610-zii-dev-rev-c.dts | 44 +++++++++++++----------
2 files changed, 52 insertions(+), 19 deletions(-)
--
2.19.0.rc1
next reply other threads:[~2018-09-02 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 16:29 Andrew Lunn [this message]
2018-09-02 16:29 ` [PATCH 1/2] ARM: dts: vf610-zii-cfu1: Add SFF interface to switch Andrew Lunn
2018-09-02 16:29 ` [PATCH 2/2] ARM: dts: vf610-zii-dev-rev-c: add support for one SFF module Andrew Lunn
2018-09-10 0:33 ` [PATCH 0/2] SFF support for ZII CFU1 and devel C Shawn Guo
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=1535905752-17730-1-git-send-email-andrew@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
/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).