From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Marcin Wojtas <mw@semihalf.com>, linux-kernel@vger.kernel.org,
        netdev@vger.kernel.org, thomas.petazzoni@free-electrons.com,
        andrew@lunn.ch, linux@arm.linux.org.uk, jason@lakedaemon.net,
        myair@marvell.com, jaz@semihalf.com, simon.guinot@sequanux.org,
        xswang@marvell.com, nadavh@marvell.com, alior@marvell.com,
        tn@semihalf.com, gregory.clement@free-electrons.com,
        nitroshift@yahoo.com, davem@davemloft.net,
        sebastian.hesselbarth@gmail.com
Subject: Re: [PATCH 07/13] bus: mvebu-mbus: provide api for obtaining IO and DRAM window information
Date: Sun, 22 Nov 2015 21:02:37 +0100
Message-ID: <5746764.cNlI6PeatM@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <1448178839-3541-8-git-send-email-mw@semihalf.com>
References: <1448178839-3541-1-git-send-email-mw@semihalf.com> <1448178839-3541-8-git-send-email-mw@semihalf.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 921
Lines: 23

On Sunday 22 November 2015 08:53:53 Marcin Wojtas wrote:
> This commit enables finding appropriate mbus window and obtaining its
> target id and attribute for given physical address in two separate
> routines, both for IO and DRAM windows. This functionality
> is needed for Armada XP/38x Network Controller's Buffer Manager and
> PnC configuration.
> 
> Signed-off-by: Marcin Wojtas <mw@semihalf.com>
> 
> [DRAM window information reference in LKv3.10]
> Signed-off-by: Evan Wang <xswang@marvell.com>
> 

It's too long ago to remember all the details, but I thought we
had designed this so the configuration can just be done by
describing it in DT. What am I missing?

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/