mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org, David Airlie <airlied@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Maxime Ripard <mripard@kernel.org>,
	Simona Vetter <simona@ffwll.ch>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>,
	linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] drm/rcar-du: dsi: Implement DSI command TX using AXI memory access
Date: Thu, 20 Aug 2026 19:39:04 +0200	[thread overview]
Message-ID: <f9f77c44-a36c-4b5e-afcb-78a5b5eb84ce@mailbox.org> (raw)
In-Reply-To: <20260810100451.GA2940644@killaraus.ideasonboard.com>

On 8/10/26 12:04 PM, Laurent Pinchart wrote:

Hello Laurent,

[...]

>> @@ -1276,6 +1295,13 @@ static int rcar_mipi_dsi_probe(struct platform_device *pdev)
>>   	dsi->dev = &pdev->dev;
>>   	dsi->info = of_device_get_match_data(&pdev->dev);
>>   
>> +	dsi->cmd_axi_cpu = dma_alloc_coherent(&pdev->dev, SZ_4K, &dsi->cmd_axi_dma,
>> +					      GFP_KERNEL | GFP_DMA32);
> 
> I think setting the DMA mask for the device is preferred over using
> GFP_DMA32.

I will do so.

>> +	if (!dsi->cmd_axi_cpu) {
>> +		return dev_err_probe(&pdev->dev, -ENOMEM,
>> +				     "Failed to allocate DSI AXI Access command buffer\n");
>> +	}
> 
> No need for curly braces.

Are branckets { } not required for multi-line code ?
If this was a oneliner, I would drop them.

>> +
>>   	ret = rcar_mipi_dsi_parse_dt(dsi);
> 
> The allocated memory is leaking in error paths.

Fixed in V2, thanks !

[...]

-- 
Best regards,
Marek Vasut

      reply	other threads:[~2026-08-20 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09 19:58 Marek Vasut
2026-08-10 10:04 ` Laurent Pinchart
2026-08-20 17:39   ` Marek Vasut [this message]

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=f9f77c44-a36c-4b5e-afcb-78a5b5eb84ce@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=magnus.damm@gmail.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tomi.valkeinen+renesas@ideasonboard.com \
    --cc=tzimmermann@suse.de \
    /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®