From: Tejas Vipin <tejasvipin76@gmail.com>
To: Brigham Campbell <me@brighamcampbell.com>,
dianders@chromium.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 3/3] drm: docs: Remove completed task from drm TODO list
Date: Mon, 7 Jul 2025 22:35:44 +0530 [thread overview]
Message-ID: <c7296a36-0bdd-464d-a681-517c814afed7@gmail.com> (raw)
In-Reply-To: <20250707075659.75810-4-me@brighamcampbell.com>
Hi,
On 7/7/25 1:26 PM, Brigham Campbell wrote:
> Remove TODO item from drm documentation to transition away from using
> mipi_dsi_*_write_seq() macros now that the work is complete.
>
> Signed-off-by: Brigham Campbell <me@brighamcampbell.com>
> ---
> Documentation/gpu/todo.rst | 18 ------------------
> 1 file changed, 18 deletions(-)
>
> diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> index be8637da3fe9..76afb8a784e3 100644
> --- a/Documentation/gpu/todo.rst
> +++ b/Documentation/gpu/todo.rst
> @@ -497,24 +497,6 @@ Contact: Douglas Anderson <dianders@chromium.org>
>
> Level: Intermediate
>
> -Transition away from using mipi_dsi_*_write_seq()
> --------------------------------------------------
> -
> -The macros mipi_dsi_generic_write_seq() and mipi_dsi_dcs_write_seq() are
> -non-intuitive because, if there are errors, they return out of the *caller's*
> -function. We should move all callers to use mipi_dsi_generic_write_seq_multi()
> -and mipi_dsi_dcs_write_seq_multi() macros instead.
> -
> -Once all callers are transitioned, the macros and the functions that they call,
> -mipi_dsi_generic_write_chatty() and mipi_dsi_dcs_write_buffer_chatty(), can
> -probably be removed. Alternatively, if people feel like the _multi() variants
> -are overkill for some use cases, we could keep the mipi_dsi_*_write_seq()
> -variants but change them not to return out of the caller.
> -
> -Contact: Douglas Anderson <dianders@chromium.org>
> -
> -Level: Starter
> -
> Remove devm_drm_put_bridge()
> ----------------------------
>
Personally I think there's merit in keeping this TODO around until all
the other mipi_dsi functions are transitioned as well and removed
entirely. Maybe rewording it to reflect this could be better?
--
Tejas Vipin
prev parent reply other threads:[~2025-07-07 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 7:56 [PATCH 0/3] drm: docs: Remove deprecated MIPI DSI macro Brigham Campbell
2025-07-07 7:56 ` [PATCH 1/3] drm: panel: Replace usage of deprecated MIPI macro Brigham Campbell
2025-07-07 17:02 ` Tejas Vipin
2025-07-07 7:56 ` [PATCH 2/3] drm: Remove unused MIPI write seq and chatty functions Brigham Campbell
2025-07-07 7:56 ` [PATCH 3/3] drm: docs: Remove completed task from drm TODO list Brigham Campbell
2025-07-07 17:05 ` Tejas Vipin [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=c7296a36-0bdd-464d-a681-517c814afed7@gmail.com \
--to=tejasvipin76@gmail.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=me@brighamcampbell.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).