Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754040AbcJDNCw (ORCPT <rfc822;w@1wt.eu>);
        Tue, 4 Oct 2016 09:02:52 -0400
Received: from mail-pf0-f174.google.com ([209.85.192.174]:35605 "EHLO
        mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751498AbcJDNCu (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 4 Oct 2016 09:02:50 -0400
From: Kevin Hilman <khilman@baylibre.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Sekhar Nori <nsekhar@ti.com>,
        Bartosz Golaszewski <bgolaszewski@baylibre.com>,
        Michael Turquette <mturquette@baylibre.com>,
        Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
        Russell King <linux@armlinux.org.uk>,
        LKML <linux-kernel@vger.kernel.org>,
        arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 6/6] ARM: da850: adjust memory settings for tilcdc
Organization: BayLibre
References: <1475166715-7857-1-git-send-email-bgolaszewski@baylibre.com>
        <1475166715-7857-7-git-send-email-bgolaszewski@baylibre.com>
        <4e089d20-d00f-ff54-7c54-85aa061e23c2@ti.com>
        <CAMpxmJXafyT5G8ZyD8RBAtzD6R9HmvyS0NBpz5i2fJ0SwOhXBA@mail.gmail.com>
        <91db8934-bfd6-8fc4-74e3-4844ef3bd3e7@ti.com>
        <948c3f9e-f11b-092c-e002-e2ef4436197f@ti.com>
        <0125defa-5c34-85d0-f62a-133235c5094c@ti.com>
Date: Tue, 04 Oct 2016 06:02:48 -0700
In-Reply-To: <0125defa-5c34-85d0-f62a-133235c5094c@ti.com> (Peter Ujfalusi's
        message of "Mon, 3 Oct 2016 10:13:25 +0300")
Message-ID: <7hvax8ferr.fsf@baylibre.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 713
Lines: 21

Peter Ujfalusi <peter.ujfalusi@ti.com> writes:

> On 10/01/16 12:24, Sekhar Nori wrote:

[...]

>> In any case, to configure the PBBR, you will have to introduce a driver
>> for it in drivers/memory. Then you can set it up per board using a DT
>> parameter.
>
> and we can reuse the introduced bindings for am335x and OMAP1/2 as well. On
> OMAP the legacy DMA API provided a call to raise the priority of the sDMA in
> EMIF :o That needs to be removed and replaced.

Can you point us to the bindings you're referring to?

Also, a new driver in drivers/memory is fine for setting the PBBR, but
what about the SYSCFG0 registers.  Are you OK with leaving those in the
init code as proposed in $SUBJECT patch?

Kevin