Received: by 10.223.176.5 with SMTP id f5csp4350512wra; Tue, 30 Jan 2018 06:06:51 -0800 (PST) X-Google-Smtp-Source: AH8x224m9Zo6+4VEDd0IXiWzEe5I1G/4O1YLzT5yuLJRyglbnqNz8CRNMTVGdC0gXH4rGPXGK4va X-Received: by 2002:a17:902:380c:: with SMTP id l12-v6mr24244988plc.8.1517321211747; Tue, 30 Jan 2018 06:06:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517321211; cv=none; d=google.com; s=arc-20160816; b=UCDSjbM/vrU44xVCpEQ4NtX3GSd9eftNVKXnzTjf3/ylz7sAaYfOuTw6Vi9GAyA2NL AZ2gTwXJKPlfgYKL0aXL83aIOzUyc84dZPXyzYYtOTlJ1kCSIP9lZ597Q9fo74UuHmol qVECzruBsOmE4+oE2umn2g9H2pbBQEzFIcCxyUNbNdmjHhGlrmfoCDFoQDfwT9FZ7ok5 GCfwvF/N1sbq1r0tqhTiPjwrX8jCDANQZxHAcGkMqEwLekbAnHgx6EcVPLm3oNWftvrF 9aV2WO129JhXEwfGS/pblDVL3AunZozqeGJydXlTK4SIecgo7FkfHEZj73/gmH2H6QMk ogQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=3oRRt0fdvZgCorP7ZRvPELCXIyefumoO9SPNICacxG4=; b=kkacAn4XnfAwtNx8Emf2l5CjIIVzhQIi7f+P4yZjvazoFaAt9l4lHsgLuPkdiUz6RS FV+lwSTFNRKcl3wiiQsW5Y+oU1+oeRCjdowJaK1oYel4GEMHOgryfEwxPTYSINHKdbB6 zmxFtwA7vDH3yWuY14EDDPu7/AocBqUj2Mh7jpdsGZvxvor4Jl7D1Mf1K8cgnOP7oPzD 2X02KyBPuryjg3abtN8w/CSmwfIYnrNN+Qy/erupQ7KuaCxevUkajuCKHRkW1CVRo0jV r6KlHAs/rW7QnYEo4HQ5V8QNmITc0NUTpb07hXW5pz1o7f4ig2kvIx8O7LCTYxCmaeNy BHYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=BQCLeMff; 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 o1-v6si1686637plk.621.2018.01.30.06.06.36; Tue, 30 Jan 2018 06:06:51 -0800 (PST) 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; dkim=fail header.i=@gmail.com header.s=20161025 header.b=BQCLeMff; 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 S1752797AbeA3N7n (ORCPT + 99 others); Tue, 30 Jan 2018 08:59:43 -0500 Received: from mail-qk0-f194.google.com ([209.85.220.194]:42052 "EHLO mail-qk0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751995AbeA3N7k (ORCPT ); Tue, 30 Jan 2018 08:59:40 -0500 Received: by mail-qk0-f194.google.com with SMTP id k201so10183922qke.9 for ; Tue, 30 Jan 2018 05:59:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=3oRRt0fdvZgCorP7ZRvPELCXIyefumoO9SPNICacxG4=; b=BQCLeMffqUeBM2KQnEJaUIkYjts+sbFJBTr2KDK1hndDs2idN0pQ7YsK+1jM/y5ct6 VVPW3AKFMPsFzXbmc+f5mG3AwuDlACmrfwPCQCE36cL7uq1PqGdo01hk0HtMhzbjXWty V42RkbSmPaLa4TjJbsdEK3ExuX1ODvbRjcIFgHg2uaDluGI05UpEFCBILKqT+yI514AA 8JJJbzSqYssaP171vLPXG5eb5KBUXVlnVTr3kn3qvOVI6eVmkm+vXoUL73V1GK2lkNFz 2ibzB/It18p6VTqWNjCf4eZE87obq38N2gA7zymV/hvASbnjJldc6kESKDBMzNI6QcTe McuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=3oRRt0fdvZgCorP7ZRvPELCXIyefumoO9SPNICacxG4=; b=sVCchNP3RlhA8eCxjjgEbh7RkYVwHOImx1lfGoR81M5gB2VIvrpoB2qGD6C2oveM29 NG64n7FsT8jZRj2kBnCeGfZeHxnYgUQnK5St1w3f04tGzVyYsgu5EuQOjVXUrI6E2hv/ uyvCippLmNEOvIvL7Zwr2JByNOKfx0WHNfhyasWisept/NkYgvpXTqD/L+WIggFjziO+ +PxVmqa3VbK5Hsi+QAx8KLRa7Hc1PHLbS0Ud9+kIkpFtvBGE+gWozSunsMPxKAlFaTVT NgRYnmkuUgIbjqv5LRqgC5XeRsg8hXceQT/xEc7ciFbzhfNkSZrlfJpwNtBGXL/1HcVi m3zg== X-Gm-Message-State: AKwxyteZxdf5Aunr1LCxNkrAX+bBgelTmXkV77UJZFluROlILQH741wx l4R7285yQWZ2+X85VfGQA/xDyg3c8nnNCzDIkGM= X-Received: by 10.55.209.137 with SMTP id o9mr40971313qkl.234.1517320779209; Tue, 30 Jan 2018 05:59:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.45.161 with HTTP; Tue, 30 Jan 2018 05:59:37 -0800 (PST) In-Reply-To: <20180130145626.7a108c64@bbrezillon> References: <1517318601-14793-1-git-send-email-geert@linux-m68k.org> <20180130144647.73a44b8d@xps13> <20180130145626.7a108c64@bbrezillon> From: Geert Uytterhoeven Date: Tue, 30 Jan 2018 14:59:37 +0100 X-Google-Sender-Auth: CBg5vZBfBED7ICWlV5SY8Cs5JGc Message-ID: Subject: Re: [PATCH] mtd: nand: MTD_NAND_MARVELL should depend on HAS_DMA To: Boris Brezillon Cc: Miquel Raynal , Richard Weinberger , MTD Maling List , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 30, 2018 at 2:56 PM, Boris Brezillon wrote: > On Tue, 30 Jan 2018 14:46:47 +0100 > Miquel Raynal wrote: >> On Tue, 30 Jan 2018 14:23:21 +0100 >> Geert Uytterhoeven wrote: >> >> > If NO_DMA=y: >> > >> > ERROR: "bad_dma_ops" [drivers/mtd/nand/marvell_nand.ko] undefined! >> > >> > Add a dependency on HAS_DMA to fix this. >> > >> > Fixes: 02f26ecf8c772751 ("mtd: nand: add reworked Marvell NAND controller driver") >> > Signed-off-by: Geert Uytterhoeven >> > --- >> > drivers/mtd/nand/Kconfig | 2 +- >> > 1 file changed, 1 insertion(+), 1 deletion(-) >> > >> > diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig >> > index e6b8c59f2c0da7c0..736ac887303c88ba 100644 >> > --- a/drivers/mtd/nand/Kconfig >> > +++ b/drivers/mtd/nand/Kconfig >> > @@ -328,7 +328,7 @@ config MTD_NAND_MARVELL >> > tristate "NAND controller support on Marvell boards" >> > depends on PXA3xx || ARCH_MMP || PLAT_ORION || ARCH_MVEBU || \ >> > COMPILE_TEST >> > - depends on HAS_IOMEM >> > + depends on HAS_IOMEM && HAS_DMA >> >> I think this is more a coding issue than a Kconfig issue. AFAIR, none >> of the ARCH_MVEBU SoCs use DMA in conjunction with the NAND controller. >> PXA SoCs may use DMA (NFCv1 only) but this is not a hard requirement and >> the driver is supposed to support PIO mode in all situations. >> >> Can you please share your setup, the SoC, the configuration, >> maybe also the DT? > > I don't think Geert is testing on a real board. He's just enabling > COMPILE_TEST and can then select your driver. Which means you really > need this depends on HAS_DMA. Correct. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds