From: Kumar Gala <galak@kernel.crashing.org>
To: Li Yang <leoli@freescale.com>
Cc: dan.j.williams@intel.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsldma: add support to 36-bit physical address
Date: Tue, 21 Sep 2010 07:55:22 -0500 [thread overview]
Message-ID: <877FD0B5-19A7-4A16-831E-369B80B104EA@kernel.crashing.org> (raw)
In-Reply-To: <1285066638-7473-1-git-send-email-leoli@freescale.com>
On Sep 21, 2010, at 5:57 AM, Li Yang wrote:
> Signed-off-by: Li Yang <leoli@freescale.com>
> ---
We really should have a sentence about how or why this works to address 36-bit addressing.
> drivers/dma/fsldma.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/dma/fsldma.c b/drivers/dma/fsldma.c
> index cea08be..9163552 100644
> --- a/drivers/dma/fsldma.c
> +++ b/drivers/dma/fsldma.c
> @@ -1,7 +1,7 @@
> /*
> * Freescale MPC85xx, MPC83xx DMA Engine support
> *
> - * Copyright (C) 2007 Freescale Semiconductor, Inc. All rights reserved.
> + * Copyright (C) 2007-2009 Freescale Semiconductor, Inc. All rights reserved.
> *
> * Author:
> * Zhang Wei <wei.zhang@freescale.com>, Jul 2007
> @@ -1338,6 +1338,7 @@ static int __devinit fsldma_of_probe(struct platform_device *op,
> fdev->common.device_control = fsl_dma_device_control;
> fdev->common.dev = &op->dev;
>
> + dma_set_mask(&op->dev, DMA_BIT_MASK(36));
> dev_set_drvdata(&op->dev, fdev);
>
> /*
> --
> 1.6.6-rc1.GIT
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2010-09-21 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 10:57 Li Yang
2010-09-21 12:55 ` Kumar Gala [this message]
2010-09-21 21:24 ` Timur Tabi
2010-09-21 21:34 ` Scott Wood
2010-09-21 21:43 ` Timur Tabi
2010-09-21 21:49 ` Scott Wood
2010-09-21 22:04 ` Timur Tabi
2010-09-21 22:05 ` Dan Malek
2010-09-21 22:08 ` Timur Tabi
2010-09-21 22:17 ` Scott Wood
2010-09-21 22:34 ` Timur Tabi
2010-09-22 5:41 ` Kumar Gala
2010-09-23 22:11 ` Dan Williams
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=877FD0B5-19A7-4A16-831E-369B80B104EA@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=dan.j.williams@intel.com \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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
all inboxes | Powered by JetHome®