From: Alain Volmat <alain.volmat@foss.st.com> To: Hugues Fruchet <hugues.fruchet@foss.st.com>, Alain Volmat <alain.volmat@foss.st.com>, Mauro Carvalho Chehab <mchehab@kernel.org>, Maxime Coquelin <mcoquelin.stm32@gmail.com>, Alexandre Torgue <alexandre.torgue@foss.st.com> Cc: Hans Verkuil <hverkuil@xs4all.nl>, Sakari Ailus <sakari.ailus@iki.fi>, <linux-media@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH] media: stm32-dcmipp: correct kerneldoc issues in dcmipp-common Date: Tue, 28 Nov 2023 21:14:03 +0100 [thread overview] Message-ID: <20231128201404.237856-1-alain.volmat@foss.st.com> (raw) Correct kerneldoc issues regarding: - dcmipp_ent_sd_register - dcmipp_pads_init - dcmipp_colorimetry_clamp Rename as well dcmipp_pads_init parameter from pads_flag to pads_flags. Signed-off-by: Alain Volmat <alain.volmat@foss.st.com> --- .../media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c | 4 ++-- .../media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h | 6 ++++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c b/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c index d4f149f7e1b7..562933e08d62 100644 --- a/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c +++ b/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c @@ -14,7 +14,7 @@ #include "dcmipp-common.h" /* Helper function to allocate and initialize pads */ -struct media_pad *dcmipp_pads_init(u16 num_pads, const unsigned long *pads_flag) +struct media_pad *dcmipp_pads_init(u16 num_pads, const unsigned long *pads_flags) { struct media_pad *pads; unsigned int i; @@ -27,7 +27,7 @@ struct media_pad *dcmipp_pads_init(u16 num_pads, const unsigned long *pads_flag) /* Initialize the pads */ for (i = 0; i < num_pads; i++) { pads[i].index = i; - pads[i].flags = pads_flag[i]; + pads[i].flags = pads_flags[i]; } return pads; diff --git a/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h b/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h index 5fd26d6f857a..69cfa67ffeeb 100644 --- a/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h +++ b/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h @@ -33,7 +33,7 @@ #define DCMIPP_XFER_FUNC_DEFAULT V4L2_XFER_FUNC_DEFAULT /** - * struct dcmipp_colorimetry_clamp - Adjust colorimetry parameters + * dcmipp_colorimetry_clamp() - Adjust colorimetry parameters * * @fmt: the pointer to struct v4l2_pix_format or * struct v4l2_mbus_framefmt @@ -103,7 +103,7 @@ struct dcmipp_ent_device { * Helper functions to allocate/initialize pads */ struct media_pad *dcmipp_pads_init(u16 num_pads, - const unsigned long *pads_flag); + const unsigned long *pads_flags); /** * dcmipp_pads_cleanup - free pads @@ -130,6 +130,8 @@ static inline void dcmipp_pads_cleanup(struct media_pad *pads) * @pads_flag: flags to use in each pad * @sd_int_ops: pointer to &struct v4l2_subdev_internal_ops * @sd_ops: pointer to &struct v4l2_subdev_ops. + * @handler: func pointer of the irq handler + * @thread_fn: func pointer of the threaded irq handler * * Helper function initialize and register the struct dcmipp_ent_device and * struct v4l2_subdev which represents a subdev node in the topology -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Alain Volmat <alain.volmat@foss.st.com> To: Hugues Fruchet <hugues.fruchet@foss.st.com>, Alain Volmat <alain.volmat@foss.st.com>, Mauro Carvalho Chehab <mchehab@kernel.org>, Maxime Coquelin <mcoquelin.stm32@gmail.com>, Alexandre Torgue <alexandre.torgue@foss.st.com> Cc: Hans Verkuil <hverkuil@xs4all.nl>, Sakari Ailus <sakari.ailus@iki.fi>, <linux-media@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH] media: stm32-dcmipp: correct kerneldoc issues in dcmipp-common Date: Tue, 28 Nov 2023 21:14:03 +0100 [thread overview] Message-ID: <20231128201404.237856-1-alain.volmat@foss.st.com> (raw) Correct kerneldoc issues regarding: - dcmipp_ent_sd_register - dcmipp_pads_init - dcmipp_colorimetry_clamp Rename as well dcmipp_pads_init parameter from pads_flag to pads_flags. Signed-off-by: Alain Volmat <alain.volmat@foss.st.com> --- .../media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c | 4 ++-- .../media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h | 6 ++++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c b/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c index d4f149f7e1b7..562933e08d62 100644 --- a/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c +++ b/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.c @@ -14,7 +14,7 @@ #include "dcmipp-common.h" /* Helper function to allocate and initialize pads */ -struct media_pad *dcmipp_pads_init(u16 num_pads, const unsigned long *pads_flag) +struct media_pad *dcmipp_pads_init(u16 num_pads, const unsigned long *pads_flags) { struct media_pad *pads; unsigned int i; @@ -27,7 +27,7 @@ struct media_pad *dcmipp_pads_init(u16 num_pads, const unsigned long *pads_flag) /* Initialize the pads */ for (i = 0; i < num_pads; i++) { pads[i].index = i; - pads[i].flags = pads_flag[i]; + pads[i].flags = pads_flags[i]; } return pads; diff --git a/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h b/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h index 5fd26d6f857a..69cfa67ffeeb 100644 --- a/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h +++ b/drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-common.h @@ -33,7 +33,7 @@ #define DCMIPP_XFER_FUNC_DEFAULT V4L2_XFER_FUNC_DEFAULT /** - * struct dcmipp_colorimetry_clamp - Adjust colorimetry parameters + * dcmipp_colorimetry_clamp() - Adjust colorimetry parameters * * @fmt: the pointer to struct v4l2_pix_format or * struct v4l2_mbus_framefmt @@ -103,7 +103,7 @@ struct dcmipp_ent_device { * Helper functions to allocate/initialize pads */ struct media_pad *dcmipp_pads_init(u16 num_pads, - const unsigned long *pads_flag); + const unsigned long *pads_flags); /** * dcmipp_pads_cleanup - free pads @@ -130,6 +130,8 @@ static inline void dcmipp_pads_cleanup(struct media_pad *pads) * @pads_flag: flags to use in each pad * @sd_int_ops: pointer to &struct v4l2_subdev_internal_ops * @sd_ops: pointer to &struct v4l2_subdev_ops. + * @handler: func pointer of the irq handler + * @thread_fn: func pointer of the threaded irq handler * * Helper function initialize and register the struct dcmipp_ent_device and * struct v4l2_subdev which represents a subdev node in the topology -- 2.34.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-11-28 20:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-28 20:14 Alain Volmat [this message] 2023-11-28 20:14 ` [PATCH] media: stm32-dcmipp: correct kerneldoc issues in dcmipp-common Alain Volmat 2023-11-29 9:35 ` Sakari Ailus 2023-11-29 9:35 ` Sakari Ailus
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=20231128201404.237856-1-alain.volmat@foss.st.com \ --to=alain.volmat@foss.st.com \ --cc=alexandre.torgue@foss.st.com \ --cc=hugues.fruchet@foss.st.com \ --cc=hverkuil@xs4all.nl \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=mchehab@kernel.org \ --cc=mcoquelin.stm32@gmail.com \ --cc=sakari.ailus@iki.fi \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.