From: Joe Perches <joe@perches.com>
To: Shraddha Barke <shraddha.6596@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-kernel@vger.kernel.org
Cc: Peter Senna Tschudin <peter.senna@gmail.com>,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH v2] Platform: goldfish: goldfish_pipe.c: Add DMA support using managed version
Date: Fri, 22 Jan 2016 12:45:43 -0800 [thread overview]
Message-ID: <1453495543.13870.39.camel@perches.com> (raw)
In-Reply-To: <1453495090-20994-1-git-send-email-shraddha.6596@gmail.com>
On Sat, 2016-01-23 at 02:08 +0530, Shraddha Barke wrote:
> setup_access_params_addr has 2 goals-
>
> -Initialize the access_params field so that it can be used to send and read
> commands from the device in access_with_param
> -Get a bus address for the allocated memory to transfer to the device.
>
> Replace the combination of devm_kzalloc and _pa() with dmam_alloc_coherent.
> Coherent mapping guarantees that the device and CPU are in sync.
[]
> diff --git a/drivers/platform/goldfish/goldfish_pipe.c b/drivers/platform/goldfish/goldfish_pipe.c
[]
> @@ -217,17 +218,17 @@ static int valid_batchbuffer_addr(struct goldfish_pipe_dev *dev,
[]
> - /* FIXME */
> - paddr = __pa(aps);
> - writel((u32)(paddr >> 32), dev->base + PIPE_REG_PARAMS_ADDR_HIGH);
> - writel((u32)paddr, dev->base + PIPE_REG_PARAMS_ADDR_LOW);
> + writel(upper_32_bits(dma_handle), dev->base +
> + PIPE_REG_PARAMS_ADDR_HIGH);
> + writel(lower_32_bits(dma_handle), dev->base + PIPE_REG_PARAMS_ADDR_LOW);
If you were going for style points, it would have been
nicer to use the same style for each writel
writel(upper_32_bits(dma_handle),
dev->base + PIPE_REG_PARAMS_ADDR_HIGH);
writel(lower_32_bits(dma_handle),
dev->base +
PIPE_REG_PARAMS_ADDR_LOW);
or just ignore 80 column limits and use single lines.
next prev parent reply other threads:[~2016-01-22 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 20:38 Shraddha Barke
2016-01-22 20:45 ` Joe Perches [this message]
2016-02-12 10:41 Shraddha Barke
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=1453495543.13870.39.camel@perches.com \
--to=joe@perches.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.senna@gmail.com \
--cc=shraddha.6596@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
all inboxes | Powered by JetHome®