public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: Chris Brandt <chris.brandt@renesas.com>
Cc: cip-dev@lists.cip-project.org,
	Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>,
	Pavel Machek <pavel@nabladev.com>
Subject: Re: [PATCH 6.1.y-cip 2/7] drm: renesas: rz-du: Implement MIPI DSI host transfers
Date: Tue, 14 Apr 2026 11:30:56 +0200	[thread overview]
Message-ID: <ad4JUH9p71MPyIlK@duo.ucw.cz> (raw)
In-Reply-To: <20260413171831.3091144-2-chris.brandt@renesas.com>

[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]

Hi!

> commit 6f392f37165008cfb3f89d723aa019e372ee79b9 upstream.
> 
> Add support for sending MIPI DSI command packets from the host to a
> peripheral. This is required for panels that need configuration before
> they accept video data.

> Signed-off-by: Chris Brandt <chris.brandt@renesas.com>

> +++ b/drivers/gpu/drm/renesas/rz-du/rzg2l_mipi_dsi.c
> +static ssize_t rzg2l_mipi_dsi_read_response(struct rzg2l_mipi_dsi *dsi,
> +					    const struct mipi_dsi_msg *msg)
> +{
> +	u8 *msg_rx = msg->rx_buf;
> +	u8 datatype;
> +	u32 result;
> +	u16 size;
> +
> +	result = rzg2l_mipi_dsi_link_read(dsi, RXRSS0R);
> +	if (result & RXRSS0R_RXPKTDFAIL) {
> +		dev_err(dsi->dev, "packet rx data did not save correctly\n");
> +		return -EPROTO;
> +	}
> +
> +	if (result & RXRSS0R_RXFAIL) {
> +		dev_err(dsi->dev, "packet rx failure\n");
> +		return -EPROTO;
> +	}
> +
> +	if (!(result & RXRSS0R_RXSUC))
> +		return -EPROTO;

This probably should do dev_err or dev_dbg before returning.

> @@ -1274,6 +1453,11 @@ static int rzg2l_mipi_dsi_probe(struct platform_device *pdev)
>  	if (ret < 0)
>  		goto err_pm_disable;
> 
> +	dsi->dcs_buf_virt = dma_alloc_coherent(dsi->host.dev, RZG2L_DCS_BUF_SIZE,
> +					       &dsi->dcs_buf_phys, GFP_KERNEL);
> +	if (!dsi->dcs_buf_virt)
> +		return -ENOMEM;
> +
>  	return 0;
>

This probably should be { err = -ENOMEM; goto err_pm_disable; }

Thanks and best regards,
									Pavel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2026-04-14  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 17:18 [PATCH 6.1.y-cip 1/7] drm: renesas: rz-du: Add atomic_pre_enable Chris Brandt
2026-04-13 17:18 ` [PATCH 6.1.y-cip 2/7] drm: renesas: rz-du: Implement MIPI DSI host transfers Chris Brandt
2026-04-14  9:30   ` Pavel Machek [this message]
2026-04-14 11:33     ` Chris Brandt
2026-04-16 20:59       ` Pavel Machek
2026-04-13 17:18 ` [PATCH 6.1.y-cip 3/7] drm: renesas: rz-du: mipi_dsi: fix kernel panic when rebooting for some panels Chris Brandt
2026-04-13 17:18 ` [PATCH 6.1.y-cip 4/7] drm: renesas: rz-du: mipi_dsi: Set DSI divider Chris Brandt
2026-04-13 17:18 ` [PATCH 6.1.y-cip 5/7] clk: renesas: Use IS_ERR() for pointers that cannot be NULL Chris Brandt
2026-04-13 17:18 ` [PATCH 6.1.y-cip 6/7] clk: renesas: rzg2l: Remove DSI clock rate restrictions Chris Brandt
2026-04-13 17:18 ` [PATCH 6.1.y-cip 7/7] clk: renesas: Add missing log message terminators Chris Brandt
2026-04-16 20:57 ` [PATCH 6.1.y-cip 1/7] drm: renesas: rz-du: Add atomic_pre_enable Pavel Machek

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=ad4JUH9p71MPyIlK@duo.ucw.cz \
    --to=pavel@nabladev.com \
    --cc=chris.brandt@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    /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