All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: dt for v4.11 (#3)
Date: Tue, 07 Feb 2017 15:35:25 +0100	[thread overview]
Message-ID: <87vasmxe4y.fsf@free-electrons.com> (raw)
In-Reply-To: <3013051.dlCd81dF2f@wuerfel> (Arnd Bergmann's message of "Tue, 07 Feb 2017 15:14:15 +0100")

Hi Arnd,
 
 On mar., f?vr. 07 2017, Arnd Bergmann <arnd@arndb.de> wrote:

> On Tuesday, January 31, 2017 3:15:10 PM CET Gregory CLEMENT wrote:
>> ----------------------------------------------------------------
>> mvebu dt for 4.11 (part 3)
>> 
>> Add support for Marvell switches with integrated CPUs based on Armada XP
>> 
>> ----------------------------------------------------------------
>> Chris Packham (2):
>>       ARM: dts: mvebu: Add device tree for 98DX3236 SoCs
>>       ARM: dts: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards
>
> Pulled into next/dt, nice to see this getting added! Just for my information,
> do we also support the actual switch driver in Linux, or just the parts that
> are common with Armada?

Currently it is only the common parts with Armada XP. Adding switches
support seems a big task, see the answer of Chris Packham about it:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-January/476910.html

And also the switch of this family seems different of the one having
support in the dsa subsystem:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-January/477063.html

Thanks,

Gregory

>
> 	Arnd

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2017-02-07 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 14:15 [GIT PULL] ARM: mvebu: dt for v4.11 (#3) Gregory CLEMENT
2017-02-07 14:14 ` Arnd Bergmann
2017-02-07 14:35   ` Gregory CLEMENT [this message]
2017-02-07 14:44   ` Andrew Lunn

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=87vasmxe4y.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.