From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mahesh Kumar <mahesh1.kumar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 02/10] drm: crc: Introduce get_crc_sources callback
Date: Thu, 12 Jul 2018 14:28:36 +0300 [thread overview]
Message-ID: <3625362.x762MMtDWS@avalon> (raw)
In-Reply-To: <20180712083635.7472-3-mahesh1.kumar@intel.com>
Hi Mahesh,
Thank you for the patch.
On Thursday, 12 July 2018 11:36:27 EEST Mahesh Kumar wrote:
> This patch introduce a callback function "get_crc_sources" which
> will be called during read of control node. It is an optional
> callback function and if driver implements this callback, driver
> should return a constant pointer to an array of crc sources list
> and update count according to the number of source in the list.
>
> Changes Since V1: (Daniel)
> - return const pointer to an array of crc sources list
> - do validation of sources in CRC-core
> Changes Since V2:
> - update commit message
> - update callback documentation
> - print one source name per line
>
> Signed-off-by: Mahesh Kumar <mahesh1.kumar@intel.com>
> Cc: dri-devel@lists.freedesktop.org
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
> drivers/gpu/drm/drm_debugfs_crc.c | 23 ++++++++++++++++++++++-
> include/drm/drm_crtc.h | 22 ++++++++++++++++++++++
> 2 files changed, 44 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_debugfs_crc.c
> b/drivers/gpu/drm/drm_debugfs_crc.c index 1956acb61cc8..940b76a1ab71 100644
> --- a/drivers/gpu/drm/drm_debugfs_crc.c
> +++ b/drivers/gpu/drm/drm_debugfs_crc.c
> @@ -68,8 +68,29 @@ static int crc_control_show(struct seq_file *m, void
> *data) {
> struct drm_crtc *crtc = m->private;
>
> - seq_printf(m, "%s\n", crtc->crc.source);
> + if (crtc->funcs->get_crc_sources) {
> + size_t count;
> + const char *const *sources = crtc->funcs->get_crc_sources(crtc,
> + &count);
> + size_t values_cnt;
> + int i;
i only takes positive values, you can make it an unsigned int.
> + if (count == 0 || !sources)
> + goto out;
> +
> + for (i = 0; i < count; i++)
> + if (!crtc->funcs->verify_crc_source(crtc, sources[i],
> + &values_cnt)) {
> + if (strcmp(sources[i], crtc->crc.source))
> + seq_printf(m, "%s\n", sources[i]);
> + else
> + seq_printf(m, "%s*\n", sources[i]);
> + }
> + }
> + return 0;
>
> +out:
> + seq_printf(m, "%s*\n", crtc->crc.source);
> return 0;
> }
>
> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> index 3ce5d2fe133d..69886025e628 100644
> --- a/include/drm/drm_crtc.h
> +++ b/include/drm/drm_crtc.h
> @@ -699,6 +699,28 @@ struct drm_crtc_funcs {
> */
> int (*verify_crc_source)(struct drm_crtc *crtc, const char *source,
> size_t *values_cnt);
> + /**
> + * @get_crc_sources:
> + *
> + * Driver callback for getting a list of all the available sources for
> + * CRC generation. This callback depends upon verify_crc_source, So
s/So/so/
> + * verify_crc_source callback should be implemented before implementing
> + * this. Driver can pass full list of available crc sources, this
> + * callback does the verification on each crc-source before passing it
> + * to userspace.
> + *
> + * This callback is optional if the driver does not support exporting of
> + * possible CRC sources list.
> + *
> + * RETURNS:
> + *
> + * a constant character pointer to the list of all the available CRC
> + * sources. On failure driver should return NULL. count should be
> + * updated with number of sources in list. if zero we don't process any
s/if zero/If zero/
Apart from that,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> + * source from the list.
> + */
> + const char *const *(*get_crc_sources)(struct drm_crtc *crtc,
> + size_t *count);
>
> /**
> * @atomic_print_state:
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-12 11:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 8:36 [PATCH 00/10] Improve crc-core driver interface Mahesh Kumar
2018-07-12 8:36 ` [PATCH 01/10] drm: crc: Introduce verify_crc_source callback Mahesh Kumar
2018-07-12 11:06 ` Laurent Pinchart
2018-07-12 8:36 ` [PATCH 02/10] drm: crc: Introduce get_crc_sources callback Mahesh Kumar
2018-07-12 11:28 ` Laurent Pinchart [this message]
2018-07-12 8:36 ` [PATCH 03/10] drm/rockchip/crc: Implement verify_crc_source callback Mahesh Kumar
2018-07-12 8:36 ` [PATCH 04/10] drm/amdgpu_dm/crc: " Mahesh Kumar
2018-07-12 8:36 ` [PATCH 05/10] drm/rcar-du/crc: " Mahesh Kumar
2018-07-12 11:37 ` Laurent Pinchart
2018-07-12 8:36 ` [PATCH 06/10] drm/i915/crc: implement " Mahesh Kumar
2018-07-12 8:36 ` [PATCH 07/10] drm/i915/crc: implement get_crc_sources callback Mahesh Kumar
2018-07-12 8:36 ` [PATCH 08/10] drm/crc: Cleanup crtc_crc_open function Mahesh Kumar
2018-07-12 11:39 ` Laurent Pinchart
2018-07-12 8:36 ` [PATCH 09/10] Revert "drm: crc: Wait for a frame before returning from open()" Mahesh Kumar
2018-07-12 11:08 ` [PATCH 00/10] Improve crc-core driver interface Laurent Pinchart
2018-07-16 14:24 ` Kumar, Mahesh
[not found] <20180711151145.21010-1-mahesh1.kumar@intel.com>
2018-07-11 15:11 ` [PATCH 02/10] drm: crc: Introduce get_crc_sources callback Mahesh Kumar
-- strict thread matches above, loose matches on Subject: below --
2018-07-02 11:07 [PATCH 00/10] Improve crc-core driver interface Mahesh Kumar
2018-07-02 11:07 ` [PATCH 02/10] drm: crc: Introduce get_crc_sources callback Mahesh Kumar
2018-07-10 11:22 ` Laurent Pinchart
2018-07-10 12:01 ` Kumar, Mahesh
2018-07-10 12:09 ` Laurent Pinchart
2018-07-10 12:11 ` Kumar, Mahesh
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=3625362.x762MMtDWS@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mahesh1.kumar@intel.com \
/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).