From: Joe Perches <joe@perches.com>
To: Shraddha Barke <shraddha.6596@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Senna Tschudin <peter.senna@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Platform: goldfish: goldfish_pipe.c: Add DMA support using managed version
Date: Fri, 12 Feb 2016 02:17:40 -0800 [thread overview]
Message-ID: <1455272260.13149.11.camel@perches.com> (raw)
In-Reply-To: <20160212072337.GA21805@shraddha-370R4E-370R4V-370R5E-3570RE-370R5V>
On Fri, 2016-02-12 at 12:53 +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.
trivia:
> diff --git a/drivers/platform/goldfish/goldfish_pipe.c b/drivers/platform/goldfish/goldfish_pipe.c
[]
> @@ -217,17 +218,18 @@ static int valid_batchbuffer_addr(struct goldfish_pipe_dev *dev,
> static int setup_access_params_addr(struct platform_device *pdev,
> struct goldfish_pipe_dev *dev)
> {
> - u64 paddr;
> + dma_addr_t dma_handle;
> struct access_params *aps;
>
> - aps = devm_kzalloc(&pdev->dev, sizeof(struct access_params), GFP_KERNEL);
> - if (!aps)
> - return -1;
> + aps = dmam_alloc_coherent(&pdev->dev, sizeof(struct access_params),
> + &dma_handle, GFP_KERNEL);
> + if (!aps) {
> + dev_err(&pdev->dev, "allocate buffer failed\n");
This is still an unnecessary allocation failure message.
There's already a generic OOM message and stack dump emitted.
next prev parent reply other threads:[~2016-02-12 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 7:23 Shraddha Barke
2016-02-12 10:17 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-06 5:06 Shraddha Barke
2016-02-08 5:27 ` Greg Kroah-Hartman
2016-01-22 19:51 Shraddha Barke
2016-01-22 19:58 ` Joe Perches
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=1455272260.13149.11.camel@perches.com \
--to=joe@perches.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--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
Powered by JetHome