From: ldewangan@nvidia.com (Laxman Dewangan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra_defconfig: enable APB DMA support
Date: Wed, 29 Aug 2012 14:49:36 +0530 [thread overview]
Message-ID: <503DDEA8.1000405@nvidia.com> (raw)
In-Reply-To: <1346230800-3167-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Wednesday 29 August 2012 02:30 PM, Uwe Kleine-K?nig wrote:
> Additionally DMADEVICES needs to be enabled as TEGRA20_APB_DMA depends
> on that.
>
> Signed-off-by: Uwe Kleine-K?nig<u.kleine-koenig@pengutronix.de>
> ---
> arch/arm/configs/tegra_defconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/configs/tegra_defconfig b/arch/arm/configs/tegra_defconfig
> index db22453..0d6bb73 100644
> --- a/arch/arm/configs/tegra_defconfig
> +++ b/arch/arm/configs/tegra_defconfig
> @@ -145,6 +145,8 @@ CONFIG_MMC_SDHCI_TEGRA=y
> CONFIG_RTC_CLASS=y
> CONFIG_RTC_DRV_EM3027=y
> CONFIG_RTC_DRV_TEGRA=y
> +CONFIG_DMADEVICES=y
> +CONFIG_TEGRA20_APB_DMA=y
> CONFIG_STAGING=y
> CONFIG_SENSORS_ISL29018=y
> CONFIG_SENSORS_ISL29028=y
Hi Uwe,
Tegra team is working on to enable the new dma drivr which is dmaengine
based. We have dma legacy driver as of now in mach-tegra. Some of the
tests are failing with new dmadriver and so we are not able to enable it.
The patch series which is posted against this is:
[PATCH 0/5] ARM: tegra: move all APB DMA client to dmaengine based driver
Thanks,
Laxman
next prev parent reply other threads:[~2012-08-29 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 9:00 [PATCH] ARM: tegra_defconfig: enable APB DMA support Uwe Kleine-König
2012-08-29 9:19 ` Laxman Dewangan [this message]
2012-08-29 9:49 ` Uwe Kleine-König
2012-08-29 17:34 ` Stephen Warren
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=503DDEA8.1000405@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).