From: neil.armstrong@linaro.org
To: Tejas Vipin <tejasvipin76@gmail.com>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
lujianhua000@gmail.com
Cc: quic_jesszhan@quicinc.com, dianders@chromium.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
asrivats@redhat.com
Subject: Re: [PATCH v2 1/2] drm/mipi-dsi: Add mipi_dsi_dual_msleep
Date: Fri, 7 Mar 2025 11:03:30 +0100 [thread overview]
Message-ID: <4bdeab38-d884-4864-8654-c6a70ef06288@linaro.org> (raw)
In-Reply-To: <20250307091519.245889-2-tejasvipin76@gmail.com>
On 07/03/2025 10:15, Tejas Vipin wrote:
> Introduces mipi_dsi_dual_msleep to make it easier to use msleep in the
> case of a double-DSI panel.
>
> Signed-off-by: Tejas Vipin <tejasvipin76@gmail.com>
> ---
> include/drm/drm_mipi_dsi.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/drm/drm_mipi_dsi.h b/include/drm/drm_mipi_dsi.h
> index bd40a443385c..d9bc0d79dd82 100644
> --- a/include/drm/drm_mipi_dsi.h
> +++ b/include/drm/drm_mipi_dsi.h
> @@ -306,6 +306,12 @@ ssize_t mipi_dsi_generic_read(struct mipi_dsi_device *dsi, const void *params,
> usleep_range(min, max); \
> } while (0)
>
> +#define mipi_dsi_dual_msleep(ctx1, ctx2, delay) \
> + do { \
> + if ((!(ctx1)->accum_err) || (!(ctx2)->accum_err)) \
> + msleep(delay); \
> + } while (0)
> +
> /**
> * enum mipi_dsi_dcs_tear_mode - Tearing Effect Output Line mode
> * @MIPI_DSI_DCS_TEAR_MODE_VBLANK: the TE output line consists of V-Blanking
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
next prev parent reply other threads:[~2025-03-07 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 9:15 [PATCH v2 0/2] Add mipi_dsi_dual_msleep and use multi functions in novatek-nt36523 Tejas Vipin
2025-03-07 9:15 ` [PATCH v2 1/2] drm/mipi-dsi: Add mipi_dsi_dual_msleep Tejas Vipin
2025-03-07 10:03 ` neil.armstrong [this message]
2025-03-07 9:15 ` [PATCH v2 2/2] drm/panel: novatek-nt36523: transition to mipi_dsi wrapped functions Tejas Vipin
2025-03-07 10:05 ` neil.armstrong
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=4bdeab38-d884-4864-8654-c6a70ef06288@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=airlied@gmail.com \
--cc=asrivats@redhat.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lujianhua000@gmail.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=quic_jesszhan@quicinc.com \
--cc=simona@ffwll.ch \
--cc=tejasvipin76@gmail.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®