From: Tejas Vipin <tejasvipin76@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de
Cc: dianders@chromium.org, airlied@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Tejas Vipin <tejasvipin76@gmail.com>
Subject: [PATCH 1/2] drm/mipi-dsi: Add quiet member to mipi_dsi_multi_context struct
Date: Wed, 24 Jul 2024 17:54:46 +0530 [thread overview]
Message-ID: <20240724122447.284165-2-tejasvipin76@gmail.com> (raw)
In-Reply-To: <20240724122447.284165-1-tejasvipin76@gmail.com>
A "quiet" member is added to mipi_dsi_multi_context which allows
silencing all the errors printed by the multi functions.
Signed-off-by: Tejas Vipin <tejasvipin76@gmail.com>
---
include/drm/drm_mipi_dsi.h | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/include/drm/drm_mipi_dsi.h b/include/drm/drm_mipi_dsi.h
index 0f520eeeaa8e..75855c1c7dae 100644
--- a/include/drm/drm_mipi_dsi.h
+++ b/include/drm/drm_mipi_dsi.h
@@ -217,6 +217,16 @@ struct mipi_dsi_multi_context {
* end to see if any of them failed.
*/
int accum_err;
+
+ /**
+ * @quiet: Controls if a function calls dev_err or not
+ *
+ * Init to 0. When the value of quiet is set to 0, the function
+ * will print error messages as required. If this is set to 1,
+ * the function will not print error messages, but will still
+ * change the value of accum_err.
+ */
+ int quiet;
};
#define MIPI_DSI_MODULE_PREFIX "mipi-dsi:"
--
2.45.2
next prev parent reply other threads:[~2024-07-24 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 12:24 [PATCH 0/2] Allow errors to be silenced in multi functions Tejas Vipin
2024-07-24 12:24 ` Tejas Vipin [this message]
2024-07-24 15:28 ` [PATCH 1/2] drm/mipi-dsi: Add quiet member to mipi_dsi_multi_context struct Jani Nikula
2024-07-24 12:24 ` [PATCH 2/2] drm/mipi-dsi: Change multi functions to use quiet member of mipi_dsi_multi_context Tejas Vipin
2024-07-24 15:32 ` Jani Nikula
2024-07-25 8:28 ` Maxime Ripard
2024-07-25 17:12 ` Doug Anderson
2024-07-26 9:15 ` Maxime Ripard
2024-07-26 14:49 ` Doug Anderson
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=20240724122447.284165-2-tejasvipin76@gmail.com \
--to=tejasvipin76@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.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