From patchwork Thu Mar 14 16:02:39 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Javier Martinez Canillas X-Patchwork-Id: 2272281 Return-Path: X-Original-To: patchwork-linux-arm@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) by patchwork2.kernel.org (Postfix) with ESMTP id 106C5DFB79 for ; Thu, 14 Mar 2013 16:06:05 +0000 (UTC) Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1UGAca-0004QU-RC; Thu, 14 Mar 2013 16:03:12 +0000 Received: from mail-ie0-x232.google.com ([2607:f8b0:4001:c03::232]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1UGAcP-0004MM-01 for linux-arm-kernel@lists.infradead.org; Thu, 14 Mar 2013 16:03:05 +0000 Received: by mail-ie0-f178.google.com with SMTP id c13so3170523ieb.37 for ; Thu, 14 Mar 2013 09:02:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=MYH44S9K2Q2mHVxQQY20VqRMwVzxgyLnsYxmyyqYMzI=; b=mkYB4sMnq973auS1oa5YSnleMmPu3DtKV9+TU5EHvoEr3AZAtBOIybV9caKvSUVf4w qB8ufCcB1crscTgDugjI5h0Fktz8vSs7CH49jJMC/fc3mlE4W/YeFuoV6QmrVNs2HyM7 GRrrAMwfBTlQ7MNpBwZBuZ0IdHkOeVAVflWoBeFw6KHnKFI3ZEK36UrtKXwRn8eL7XNK g+pT7m5huka5YCDPY++ETiVIxcmLzr36eM9G9z0fy4wqtx0oIgmRtIjkKQBC/VA061cV MPr9rUacygzYtQdMlFLggjhAjqlcC8aYa8Z027mmwMBESsdN/BV2tQWKBM7W5L3KF+um /hKA== X-Received: by 10.50.51.226 with SMTP id n2mr2822220igo.25.1363276979520; Thu, 14 Mar 2013 09:02:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.71.2 with HTTP; Thu, 14 Mar 2013 09:02:39 -0700 (PDT) In-Reply-To: <5141E55E.9040801@ti.com> References: <1362763654-9660-1-git-send-email-jon-hunter@ti.com> <5141E55E.9040801@ti.com> From: Javier Martinez Canillas Date: Thu, 14 Mar 2013 17:02:39 +0100 Message-ID: Subject: Re: [PATCH 0/9] ARM: dts: Various OMAP2+ device-tree updates To: Benoit Cousson X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20130314_120301_226872_9E04C3D2 X-CRM114-Status: GOOD ( 23.14 ) X-Spam-Score: -2.0 (--) X-Spam-Report: SpamAssassin version 3.3.2 on merlin.infradead.org summary: Content analysis details: (-2.0 points) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (martinez.javier[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Cc: Tony Lindgren , device-tree , linux-omap , Jon Hunter , linux-arm X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org On Thu, Mar 14, 2013 at 3:57 PM, Benoit Cousson wrote: > Salut Jon, > > On 03/08/2013 06:27 PM, Jon Hunter wrote: >> Various OMAP device-tree updates for PMU, DMA, GPIO, GPMC and boards. >> >> The DMA, PMU and OMAP3430 SDP board changes have been sent before >> individually but re-sending here as a complete series for v3.10. >> >> This is based upon v3.9-rc1 and the OMAP3 GPMC binding from Florian >> Vaussard [1] and OMAP5 DT SPI patch from Felipe Balbi [2]. >> >> [1] https://patchwork.kernel.org/patch/2057111/ > > I've tried to follow the series review, and it seems that Florian was > considering sending some other patches. It is not clear if this is a new > version of the series or some additional patches. > Hi Benoit, According to [1] Jon suggested that it was not necessary to map all the 16MB for the GPMC mapped register address space since in practice is a very small fraction of that size is used. I had the following patch but I did never post it because Jon said that the I/O memory mapping is page-aligned and the minimum page size for ARM is 4KB anyways, so there is no functional difference between using 0x1000 or 0x02d0. But now reading [2] I see that you prefer to do what the documentation said and don't assume any the page size / alignment. [2]: https://patchwork.kernel.org/patch/2239741/ From 68edff5a102bb8fc81e006738baa456eb69f080a Mon Sep 17 00:00:00 2001 From: Javier Martinez Canillas Date: Wed, 27 Feb 2013 02:30:51 +0100 Subject: [PATCH] ARM: dts: OMAP3: reduce GPMC mapped registers address space Currently the OMAP General-Purpose Memory Controller (GPMC) device node maps 16 MB of address space for its hardware registers. This is because the OMAP Technical Reference Manual says that the GPMC module register address space size is 16 MB. But in practice the maximum address offset used by a GPMC register is 0x02d0. So, there is no need to map such a big address space for GPMC regs. This change was suggested by Jon Hunter [1]. [1]: https://patchwork.kernel.org/patch/2057111/ Signed-off-by: Javier Martinez Canillas Acked-by: Jon Hunter --- arch/arm/boot/dts/omap3.dtsi | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi index 2ddae38..a60eaf1 100644 --- a/arch/arm/boot/dts/omap3.dtsi +++ b/arch/arm/boot/dts/omap3.dtsi @@ -407,7 +407,7 @@ gpmc: gpmc@6e000000 { compatible = "ti,omap3430-gpmc"; ti,hwmods = "gpmc"; - reg = <0x6e000000 0x1000000>; + reg = <0x6e000000 0x02d0>; interrupts = <20>; gpmc,num-cs = <8>; gpmc,num-waitpins = <4>;