All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
	Ben Peddell <klightspeed@killerwolves.net>,
	Jason Cooper <jason@lakedaemon.net>,
	pawel.moll@arm.com, devicetree@vger.kernel.org,
	Ian Campbell <ijc@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/4] ARM: Kirkwood: Add support for many Synology NAS devices
Date: Thu, 6 Feb 2014 18:03:33 +0100	[thread overview]
Message-ID: <20140206170333.GK29860@lunn.ch> (raw)
In-Reply-To: <107057891.kz6j7UkZNk@wuerfel>

On Thu, Feb 06, 2014 at 05:38:28PM +0100, Arnd Bergmann wrote:
> On Thursday 06 February 2014 17:01:26 Andrew Lunn wrote:
> 
> > , but this is, imho,
> > > over-fragmenting.  I'm sure there's a reason you chose this path, but
> > > you haven't explained why in your commit log. So I'm left guessing...
> > 
> > Synology seem to build there devices like lego. They have two
> > different RTC blocks. They have three different fan alarm blocks, four
> > different led blocks, etc. And to build a product, the just select a
> > group of blocks and put them together.
> 
> I guess the Armada-370 and newer based ds213j and dsx14 will also be
> able to reuse some of the blocks, right?

Hi Arnd

I've not looked at any sources for those yet. I guess the RTC .dtsi
files should be reusable. The ethernet driver on 370 is different so
no re-use there. Maybe the fan controller, but the rest will depend on
what GPIO lines they have used, if they are compatible.

     Andrew

WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: Kirkwood: Add support for many Synology NAS devices
Date: Thu, 6 Feb 2014 18:03:33 +0100	[thread overview]
Message-ID: <20140206170333.GK29860@lunn.ch> (raw)
In-Reply-To: <107057891.kz6j7UkZNk@wuerfel>

On Thu, Feb 06, 2014 at 05:38:28PM +0100, Arnd Bergmann wrote:
> On Thursday 06 February 2014 17:01:26 Andrew Lunn wrote:
> 
> > , but this is, imho,
> > > over-fragmenting.  I'm sure there's a reason you chose this path, but
> > > you haven't explained why in your commit log. So I'm left guessing...
> > 
> > Synology seem to build there devices like lego. They have two
> > different RTC blocks. They have three different fan alarm blocks, four
> > different led blocks, etc. And to build a product, the just select a
> > group of blocks and put them together.
> 
> I guess the Armada-370 and newer based ds213j and dsx14 will also be
> able to reuse some of the blocks, right?

Hi Arnd

I've not looked at any sources for those yet. I guess the RTC .dtsi
files should be reusable. The ethernet driver on 370 is different so
no re-use there. Maybe the fan controller, but the rest will depend on
what GPIO lines they have used, if they are compatible.

     Andrew

  reply	other threads:[~2014-02-06 17:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 21:05 [PATCH 0/4] DT support for kirkwood based Synology NAS boxes Andrew Lunn
2014-02-05 21:05 ` [PATCH 1/4] Power: Reset: Generalize qnap-poweroff to with on Synology devices Andrew Lunn
2014-02-06 15:12   ` Jason Cooper
2014-02-05 21:05 ` [PATCH 2/4] DT: Vendor prefixes: Add ricoh, ssi and synology Andrew Lunn
     [not found]   ` <1391634309-3123-3-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2014-02-06 15:19     ` Jason Cooper
2014-02-06 15:19       ` Jason Cooper
2014-02-06 15:49   ` Rob Herring
2014-02-05 21:05 ` [PATCH 3/4] DT: i2c: Trivial: Add sii,s35390a Andrew Lunn
     [not found]   ` <1391634309-3123-4-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2014-02-06 15:21     ` Jason Cooper
2014-02-06 15:21       ` Jason Cooper
2014-02-05 21:05 ` [PATCH 4/4] ARM: Kirkwood: Add support for many Synology NAS devices Andrew Lunn
2014-02-06 15:39   ` Jason Cooper
2014-02-06 15:39     ` Jason Cooper
2014-02-06 16:01     ` Andrew Lunn
2014-02-06 16:01       ` Andrew Lunn
2014-02-06 16:38       ` Arnd Bergmann
2014-02-06 16:38         ` Arnd Bergmann
2014-02-06 17:03         ` Andrew Lunn [this message]
2014-02-06 17:03           ` Andrew Lunn
     [not found]           ` <20140206170333.GK29860-g2DYL2Zd6BY@public.gmane.org>
2014-02-06 17:26             ` Jason Cooper
2014-02-06 17:26               ` Jason Cooper
     [not found]       ` <20140206160126.GH29860-g2DYL2Zd6BY@public.gmane.org>
2014-02-07  7:44         ` Ben Peddell
2014-02-07  7:44           ` Ben Peddell
2014-02-10 11:41         ` Ian Campbell
2014-02-10 11:41           ` Ian Campbell
2014-02-06 16:39     ` Ian Campbell
2014-02-06 16:39       ` Ian Campbell
     [not found]       ` <1391704765.2162.7.camel-ommiHX4a84BXesXXhkcM7miJhflN2719@public.gmane.org>
2014-02-06 16:50         ` Andrew Lunn
2014-02-06 16:50           ` Andrew Lunn
2014-02-06 16:52           ` Ian Campbell
2014-02-06 16:52             ` Ian Campbell

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=20140206170333.GK29860@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc@hellion.org.uk \
    --cc=jason@lakedaemon.net \
    --cc=klightspeed@killerwolves.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@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 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.