Received: by 10.213.65.68 with SMTP id h4csp1591511imn; Thu, 29 Mar 2018 07:31:14 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/kVOPvmFpfXk/hmkYv2PvX2WGJskQtA2AJ1anty1CKiZNlr1CXNBLLyl9ti/XqNvkYvbZx X-Received: by 2002:a17:902:206:: with SMTP id 6-v6mr8600892plc.376.1522333874837; Thu, 29 Mar 2018 07:31:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522333874; cv=none; d=google.com; s=arc-20160816; b=WvtZgjvnlTVLkg1lorZ9I5ZjrYwkfHSyaw1uip0YjIenjnKpl2jx/70X3Hgf+lZLUe hqC0ngDxuz1rwicYabqNRLv93B7AtuiNkTfi26ImowFXh1kVQLNH4k8xzi5zrdjC+zAH 6QnHaWYgCBsVNXjNSLQ0tXLDRc1q8zyj3aJViFDTUqZ4a4qOuln5vHmvgtn1Lm25P+5A 7gnKQz5PeRSzziJoebSruJ1gU4nBovHJkxfptipxPLl+zD2a0C3HkuPMB7uF7DJ2X0Rd WPBXEs/yQoXnOmzPadHRxFwx/hD4OIuEiqkFOSLgFeJFdOl/yZPEFFrqqZt0febwuA3+ dVDw== 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=ptar7ApLb7fFzbXt0Ao+FEy/jF6ZKE3D3f0wX/nl0/A=; b=o08alYtkFFSgWTQViWvCXzNC267W3qDs3lwifGcgWbXS9WutR9BshhpV0ojKgCj9XA owr9b/2gI8/wQdU8oVDzzeMVRbQ98OT98qV+uxzCDfwPy/DZkTiEGXJ7yjoiq+QQRiO4 8HbvqHgAJcoRXH84gC19urT9Nbecsopktb8qJRU/k6v4M+yzPQxdzOnS33zInVQqNK4w oYjHmnvxGEZHb20EwR7WjY95DE5wXvRHBGG0BDw/Yf+aLJCa5Qc381ji5xh33baxLfwt iFdvI23fONTwJOzIRZTTZ/1DmXm3MYNQCW8RUK8LTb9kyPxsd65UpQNYGs9HjXCUuHwa q/2w== 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 x14si4542662pfk.119.2018.03.29.07.30.58; Thu, 29 Mar 2018 07:31:14 -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 S1751859AbeC2O3g (ORCPT + 99 others); Thu, 29 Mar 2018 10:29:36 -0400 Received: from mail.bootlin.com ([62.4.15.54]:42695 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750884AbeC2O3f (ORCPT ); Thu, 29 Mar 2018 10:29:35 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id D73CA2083E; Thu, 29 Mar 2018 16:29:33 +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, URIBL_BLOCKED shortcircuit=ham autolearn=disabled version=3.4.0 Received: from bbrezillon (LStLambert-657-1-97-87.w90-63.abo.wanadoo.fr [90.63.216.87]) by mail.bootlin.com (Postfix) with ESMTPSA id 746182037A; Thu, 29 Mar 2018 16:29:23 +0200 (CEST) Date: Thu, 29 Mar 2018 16:29:22 +0200 From: Boris Brezillon To: Nicolas Ferre Cc: Peter Rosin , , "wenyouya@gmail.com" , Josh Wu , Richard Weinberger , David Woodhouse , Brian Norris , Marek Vasut , Cyrille Pitchen , Alexandre Belloni , , Subject: Re: [PATCH] mtd: nand: raw: atmel: add module param to avoid using dma Message-ID: <20180329162922.5db7acd1@bbrezillon> In-Reply-To: <30d8bd45-4e5d-3703-5f41-07f5fc70f09d@microchip.com> References: <20180329131054.22506-1-peda@axentia.se> <30d8bd45-4e5d-3703-5f41-07f5fc70f09d@microchip.com> 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 Thu, 29 Mar 2018 16:20:38 +0200 Nicolas Ferre wrote: > On 29/03/2018 at 15:10, 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); > > We had the DT parameter "atmel,nand-has-dma" for this purpose and it was Actually, that was not my understanding of this property. To me it sounds like something to flag whether the platform supports DMA or not, no whether it should be enabled on a per-board basis. > associated with a module parameter as well (use_dma,). That's true for the use_dma module param, I didn't add it back when reworking the driver. > > Is it only managed by old DT binding? It is. I'm really not in favor of adding the DT prop back, but let's re-introduce the module param if you think it's needed. BTW, the module name has changed, so the param name will be different. -- Boris Brezillon, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com