From: Cyril Chemparathy <cyril@ti.com>
To: R Sricharan <r.sricharan@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
santosh.shilimkar@ti.com,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [RFC PATCH] ARM: mm: ADD descriptor string to CONFIG_DMA_ADDR_64BIT_T
Date: Wed, 12 Sep 2012 08:46:18 -0400 [thread overview]
Message-ID: <5050841A.7030203@ti.com> (raw)
In-Reply-To: <1347429006-10879-1-git-send-email-r.sricharan@ti.com>
On 9/12/2012 1:50 AM, R Sricharan wrote:
> Even if CONFIG_DMA_ADDR_64BIT_T is enabled by the defconfig,
> the feature is not getting selected.
> Adding a string description in the Kconfig resolves this.
>
> But not sure if this is the right way to fix this.
>
Shouldn't you be selecting this in your 64-bit dma address capable arch
instead?
> Signed-off-by: R Sricharan <r.sricharan@ti.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> ---
> arch/arm/mm/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig
> index 101b968..90c5ea4 100644
> --- a/arch/arm/mm/Kconfig
> +++ b/arch/arm/mm/Kconfig
> @@ -601,7 +601,7 @@ config ARCH_PHYS_ADDR_T_64BIT
> def_bool ARM_LPAE
>
> config ARCH_DMA_ADDR_T_64BIT
> - bool
> + bool "64bit capable DMA device"
>
> config ARM_THUMB
> bool "Support Thumb user binaries"
>
--
Thanks
- Cyril
next prev parent reply other threads:[~2012-09-12 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 5:50 [RFC PATCH] ARM: mm: ADD descriptor string to CONFIG_DMA_ADDR_64BIT_T R Sricharan
2012-09-12 12:46 ` Cyril Chemparathy [this message]
2012-09-12 12:56 ` Catalin Marinas
2012-09-12 12:57 ` Shilimkar, Santosh
2012-09-12 13:19 ` Catalin Marinas
2012-09-12 13:25 ` Shilimkar, Santosh
2012-09-12 13:29 ` R, Sricharan
2012-09-12 13:20 ` R, Sricharan
2012-09-12 14:55 ` Russell King - ARM Linux
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=5050841A.7030203@ti.com \
--to=cyril@ti.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=r.sricharan@ti.com \
--cc=santosh.shilimkar@ti.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;
as well as URLs for NNTP newsgroup(s).