From: Dong Aisheng <b29396@freescale.com>
To: Huang Shijie <shijie8@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
Artem.Bityutskiy@linux.intel.com, b32955@freescale.com,
linux-mtd@lists.infradead.org, kernel@pengutronix.de,
shawn.guo@linaro.org, Fabio Estevam <festevam@gmail.com>,
dwmw2@infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] ARM: imx_v6_v7_defconfig: Select MXS_DMA
Date: Thu, 26 Jul 2012 10:29:30 +0800 [thread overview]
Message-ID: <20120726022930.GB3396@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <CAMiH66FUxiw0B8iD5rYi=nUX0VYZBzOKifXKfTqd1RmSHhC80g@mail.gmail.com>
On Thu, Jul 26, 2012 at 10:24:41AM +0800, Huang Shijie wrote:
> On Wed, Jul 25, 2012 at 11:23 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Wed, Jul 25, 2012 at 12:05 PM, Huang Shijie <shijie8@gmail.com> wrote:
> >
> >> Is this patch needed? The mxs-dma only has one user, the gpmi-nand in mx6q.
> >> this patch makes the kernel built-in the mxs-dma, even the gpmi-nand
> >> is not enabled.
> >
> > Well, as the driver currently stands: yes, it is needed.
> >
> > Without CONFIG_MXS_DMA, the GPMI driver cannot even be built.
> But you have added "depend on MXS_DMA". So If you do not select the
> mxs-dma, you can not see the
> gpmi-nand.
> that's why i think this patch is not needed.
>
How about using 'select MXS_DMA'?
diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
index 31bb7e5..e7c3dcf 100644
--- a/drivers/mtd/nand/Kconfig
+++ b/drivers/mtd/nand/Kconfig
@@ -481,6 +481,7 @@ config MTD_NAND_NANDSIM
config MTD_NAND_GPMI_NAND
bool "GPMI NAND Flash Controller driver"
depends on MTD_NAND && (SOC_IMX23 || SOC_IMX28 || SOC_IMX6Q)
+ select MXS_DMA
help
Then we do not need this patch and does not have the issue that MXS_DMA is
still compiled even GPMI_NAND is not selected.
Regards
Dong Aisheng
next prev parent reply other threads:[~2012-07-26 2:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 11:18 [PATCH v2 1/3] mtd: nand: Include IMX6 in the list of supported SoCs Fabio Estevam
2012-07-25 11:18 ` [PATCH v2 2/3] mtd: nand: Let MTD_NAND_GPMI_NAND depend on MXS_DMA Fabio Estevam
2012-07-26 2:27 ` Huang Shijie
2012-07-26 10:35 ` Fabio Estevam
2012-07-27 9:28 ` Richard Zhao
2012-08-03 10:07 ` Sascha Hauer
2012-08-05 6:36 ` Dirk Behme
2012-07-25 11:18 ` [PATCH v2 3/3] ARM: imx_v6_v7_defconfig: Select MXS_DMA Fabio Estevam
2012-07-25 15:05 ` Huang Shijie
2012-07-25 15:23 ` Fabio Estevam
2012-07-26 2:24 ` Huang Shijie
2012-07-26 2:29 ` Dong Aisheng [this message]
2012-07-26 10:38 ` Fabio Estevam
2012-07-28 13:02 ` Shawn Guo
2012-07-26 10:45 ` David Woodhouse
2012-07-26 10:53 ` Fabio Estevam
2012-07-26 10:56 ` Huang Shijie
2012-07-26 11:08 ` Fabio Estevam
2012-07-26 11:32 ` Huang Shijie
2012-07-27 9:26 ` Richard Zhao
2012-07-27 9:30 ` Dirk Behme
2012-07-27 10:21 ` Huang Shijie
2012-07-26 11:54 ` David Woodhouse
2012-08-03 8:40 ` Dirk Behme
2012-08-03 8:59 ` Huang Shijie
2012-07-27 9:30 ` [PATCH v2 1/3] mtd: nand: Include IMX6 in the list of supported SoCs Richard Zhao
2012-07-27 10:12 ` Huang Shijie
2012-08-17 15:52 ` Artem Bityutskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120726022930.GB3396@shlinux2.ap.freescale.net \
--to=b29396@freescale.com \
--cc=Artem.Bityutskiy@linux.intel.com \
--cc=b32955@freescale.com \
--cc=dwmw2@infradead.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shawn.guo@linaro.org \
--cc=shijie8@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox