Received: by 10.213.65.68 with SMTP id h4csp2731650imn; Mon, 2 Apr 2018 12:58:39 -0700 (PDT) X-Google-Smtp-Source: AIpwx48OykDMEYRqeoLJboG1nYLpFn0J97GIHe4VO0q7Wfs3eWyFvcIBCVQx6j61I148uk0Da7Xe X-Received: by 10.99.111.3 with SMTP id k3mr7198424pgc.135.1522699119929; Mon, 02 Apr 2018 12:58:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522699119; cv=none; d=google.com; s=arc-20160816; b=WRe6ogccTYa4En05YiEwAcklf1/5Wo9fNZmQJNRfzENUihDAv5g6eJvaUuopa2cXkf 2RCqNDVK6WfxlCf1n0sJwH7P/D/gdej6klS45W2UDgWtHfXQB1VeI8x86rD+nezDJqa7 x5ORX69+1qRDO8g1rZDbioYC3T4Z1WdTYb5zfBPwUMDsPapS27yQea6NH4R6QLrp5dQz W99IZ2lBN8ZTaTB56BSHqnj2+1/dhvWiBHdn98iVvhPQqA+omI04J0vKTwEq0siEjj+o MZwuZ6jHIzQoJT+YsZsPCpIgouw+4i0D9Y+PDi/la8AH38lEpKc4Suu5slTubAa/f3vF EZmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :arc-authentication-results; bh=uXCKWDq5URr75u+XrqZKyMxDPl8C/lCYGNzisRjWLCM=; b=oxhiqnQIbD5H+YLO6uQ42yid9/EgEu86Bu/TlilJKmoBXN7yEqd3V7AccbrIRU6RPA 0S9sz5KEyJ2pI6ZkAi7fzqlM1f8qF6MmYDOZVgSdGrJDo4rXj+8TgrSzkiBH3NU22BeN jyHZibcK/vfs8aV1Yk69aJDWLTrfidN5xpJvCroHRQoX7TlUBG14R6LCTXMwVMJXuH3z JFvSmW9Y4cJXbVZkZ1XZ6y2oC3ZVTcA26SwFJoG1YRwSL0dKEaaa/98P8I/tvPb7jN7+ UY9UQqr7qcL5geSZKbGuo/W56+cHV7rhhXPlIZSqzkbWn+KKxKEy8Povjh8oK8F58WLS kmwQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f9-v6si985055plo.664.2018.04.02.12.58.26; Mon, 02 Apr 2018 12:58:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756946AbeDBT25 (ORCPT + 99 others); Mon, 2 Apr 2018 15:28:57 -0400 Received: from mail.bootlin.com ([62.4.15.54]:57504 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754879AbeDBT24 (ORCPT ); Mon, 2 Apr 2018 15:28:56 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id AC8E720713; Mon, 2 Apr 2018 21:28:54 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.bootlin.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.0 Received: from bbrezillon (91-160-177-164.subs.proxad.net [91.160.177.164]) by mail.bootlin.com (Postfix) with ESMTPSA id 6142C20384; Mon, 2 Apr 2018 21:28:44 +0200 (CEST) Date: Mon, 2 Apr 2018 21:28:43 +0200 From: Boris Brezillon To: Peter Rosin Cc: Alexandre Belloni , Josh Wu , Cyrille Pitchen , linux-kernel@vger.kernel.org, Nicolas Ferre , Marek Vasut , linux-mtd@lists.infradead.org, Richard Weinberger , Brian Norris , David Woodhouse , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] mtd: nand: raw: atmel: add module param to avoid using dma Message-ID: <20180402212843.164d5d21@bbrezillon> In-Reply-To: References: <20180329131054.22506-1-peda@axentia.se> <20180329153322.5e2fc1e7@bbrezillon> <20180329154416.5c1a0013@bbrezillon> <20180402142249.7e076a64@bbrezillon> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2 Apr 2018 19:59:39 +0200 Peter Rosin wrote: > On 2018-04-02 14:22, Boris Brezillon wrote: > > On Thu, 29 Mar 2018 16:27:12 +0200 > > Peter Rosin wrote: > > > >> On 2018-03-29 15:44, Boris Brezillon wrote: > >>> On Thu, 29 Mar 2018 15:37:43 +0200 > >>> Peter Rosin wrote: > >>> > >>>> On 2018-03-29 15:33, Boris Brezillon wrote: > >>>>> On Thu, 29 Mar 2018 15:10:54 +0200 > >>>>> Peter Rosin wrote: > >>>>> > >>>>>> On a sama5d31 with a Full-HD dual LVDS panel (132MHz pixel clock) NAND > >>>>>> flash accesses have a tendency to cause display disturbances. Add a > >>>>>> module param to disable DMA from the NAND controller, since that fixes > >>>>>> the display problem for me. > >>>>>> > >>>>>> Signed-off-by: Peter Rosin > >>>>>> --- > >>>>>> drivers/mtd/nand/raw/atmel/nand-controller.c | 7 ++++++- > >>>>>> 1 file changed, 6 insertions(+), 1 deletion(-) > >>>>>> > >>>>>> diff --git a/drivers/mtd/nand/raw/atmel/nand-controller.c b/drivers/mtd/nand/raw/atmel/nand-controller.c > >>>>>> index b2f00b398490..2ff7a77c7b8e 100644 > >>>>>> --- a/drivers/mtd/nand/raw/atmel/nand-controller.c > >>>>>> +++ b/drivers/mtd/nand/raw/atmel/nand-controller.c > >>>>>> @@ -129,6 +129,11 @@ > >>>>>> #define DEFAULT_TIMEOUT_MS 1000 > >>>>>> #define MIN_DMA_LEN 128 > >>>>>> > >>>>>> +static bool atmel_nand_avoid_dma __read_mostly; > >>>>>> + > >>>>>> +MODULE_PARM_DESC(avoiddma, "Avoid using DMA"); > >>>>>> +module_param_named(avoiddma, atmel_nand_avoid_dma, bool, 0400); > >>>>> > >>>>> I'm not a big fan of those driver specific cmdline parameters. Can't we > >>>>> instead give an higher priority to HLCDC master using the bus matrix? > >>>> > >>>> I don't know if it will be enough, but we sure can try. However, I have > >>>> no idea how to do that. I will happily test stuff though... > >>> > >>> There's no interface to configure that from Linux, but you can try to > >>> tweak it with devmem and if that does the trick, maybe we can expose a > >>> way to configure that from Linux. For more details, see the "Bus Matrix > >>> (MATRIX)" section in Atmel datasheets. > >> > >> I don't seem to succeed in changing the registers I think I need to change. > >> I can poke the "Write Protection Mode Register" by writing MAT0 and MAT1 to > >> it. > > > > You mean 0x4D415400, right? ("MAT0" != 0x4D415400). > > Bits 1 through 7 do not matter, so even though not equal they are (or > should be) equivalent. But I did use 0x4d415400. I simply used the > shorter syntax since that was easier to type and conveyed the relevant > info. Ok. > > >> But when I try to write to "Priority Registers B For Slaves" it doesn't > >> take, regardless of write protect mode. > > > > Did you check MATRIX_WPSR after writing to MATRIX_PRXSY? > > No, but did it again and checked, see transcript below. I don't use devmem2. Is 'readback' information accurate or is it always what's been written? Because when you write 0x33 to 0xFFFFECBC, 0x33 is read back, but just after that, when you read it again it's 0. > BTW, how do I > know which master is in use for the LCD controller? 8 or 9? Both? It's configurable on a per-layer basis through the SIF bit in LCDC_CFG0. The driver tries to dispatch the load on those 2 AHB masters [1]. > And > which DDR slave is the target? 7, 8, 9 or 10? More than one? This, I don't know. I guess all of them can be used. > > Cheers, > Peter > > # devmem2 0xffffede4 w > /dev/mem opened. > Memory mapped at address 0xb6f50000. > Value at address 0xFFFFEDE4 (0xb6f50de4): 0x0 > # devmem2 0xffffede4 w 0x4d415401 > /dev/mem opened. > Memory mapped at address 0xb6f0d000. > Value at address 0xFFFFEDE4 (0xb6f0dde4): 0x0 > Written 0x4D415401; readback 0x4D415401 > # devmem2 0xffffede4 w > /dev/mem opened. > Memory mapped at address 0xb6f55000. > Value at address 0xFFFFEDE4 (0xb6f55de4): 0x1 > # devmem2 0xffffede4 w 0x4d415400 > /dev/mem opened. > Memory mapped at address 0xb6fb5000. > Value at address 0xFFFFEDE4 (0xb6fb5de4): 0x1 > Written 0x4D415400; readback 0x4D415400 > # devmem2 0xffffede4 w > /dev/mem opened. > Memory mapped at address 0xb6fef000. > Value at address 0xFFFFEDE4 (0xb6fefde4): 0x0 > > > # devmem2 0xffffede8 w > /dev/mem opened. > Memory mapped at address 0xb6fe9000. > Value at address 0xFFFFEDE8 (0xb6fe9de8): 0x0 > > > # devmem2 0xffffecbc w > /dev/mem opened. > Memory mapped at address 0xb6ff0000. > Value at address 0xFFFFECBC (0xb6ff0cbc): 0x0 > # devmem2 0xffffecbc w 0x33 > /dev/mem opened. > Memory mapped at address 0xb6f79000. > Value at address 0xFFFFECBC (0xb6f79cbc): 0x0 > Written 0x33; readback 0x33 > # devmem2 0xffffecbc w > /dev/mem opened. > Memory mapped at address 0xb6efe000. > Value at address 0xFFFFECBC (0xb6efecbc): 0x0 > > > # devmem2 0xffffede8 w > /dev/mem opened. > Memory mapped at address 0xb6f9e000. > Value at address 0xFFFFEDE8 (0xb6f9ede8): 0x0 > [1]https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c#L498 -- Boris Brezillon, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com