From: "Kumar, Mahesh" <mahesh1.kumar@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 02/10] drm: crc: Introduce pre_crc_read function
Date: Wed, 27 Jun 2018 20:52:43 +0530 [thread overview]
Message-ID: <ffc8962a-4189-6559-2e9d-fe7b888fc178@intel.com> (raw)
In-Reply-To: <94f50de6-956b-3861-f599-b3d3b2562eba@linux.intel.com>
Hi,
On 6/27/2018 8:48 PM, Maarten Lankhorst wrote:
> Op 27-06-18 om 16:44 schreef Mahesh Kumar:
>> This patch implements a callback function "pre_crc_read" which will
>> be called before crc read. In this function driver can implement and
>> preparation work required for successfully reading CRC data.
>>
>> Signed-off-by: Mahesh Kumar <mahesh1.kumar@intel.com>
>> Cc: dri-devel@lists.freedesktop.org
>> ---
>> drivers/gpu/drm/drm_debugfs_crc.c | 8 ++++++++
>> include/drm/drm_crtc.h | 14 ++++++++++++++
>> 2 files changed, 22 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_debugfs_crc.c b/drivers/gpu/drm/drm_debugfs_crc.c
>> index c6a725b79ac6..2b4a737c5aeb 100644
>> --- a/drivers/gpu/drm/drm_debugfs_crc.c
>> +++ b/drivers/gpu/drm/drm_debugfs_crc.c
>> @@ -278,6 +278,14 @@ static ssize_t crtc_crc_read(struct file *filep, char __user *user_buf,
>> return 0;
>> }
>>
>> + if (crtc->funcs->pre_crc_read) {
>> + ret = crtc->funcs->pre_crc_read(crtc);
>> + if (ret) {
>> + spin_unlock_irq(&crc->lock);
>> + return ret;
>> + }
>> + }
>> +
>> /* Nothing to read? */
>> while (crtc_crc_data_count(crc) == 0) {
>> if (filep->f_flags & O_NONBLOCK) {
>> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
>> index 1a6dcbf91744..bae432469616 100644
>> --- a/include/drm/drm_crtc.h
>> +++ b/include/drm/drm_crtc.h
>> @@ -676,6 +676,20 @@ struct drm_crtc_funcs {
>> */
>> int (*verify_crc_source)(struct drm_crtc *crtc, const char *source,
>> size_t *values_cnt);
>> + /**
>> + * @pre_crc_read:
>> + *
>> + * Driver callback for performing any preparation work required by
>> + * driver before reading CRC
>> + *
>> + * This callback is optional if the driver does not support CRC
>> + * generation or no prework is required before reading the crc
>> + *
>> + * RETURNS:
>> + *
>> + * 0 on success or a negative error code on failure.
>> + */
>> + int (*pre_crc_read)(struct drm_crtc *crtc);
>>
>> /**
>> * @atomic_print_state:
> I think this patch might have to be dropped, or reordered after the revert in 10/10, because else in theory open could block. :)
>
> Or maybe just drop until we have upstream kernel users?
thanks,
Can reorder it after patch-10 and if others also vote to drop it will
take decision accordingly, atleast it should not block other patches :)
-Mahesh
>
> ~Maarten
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-27 15:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 14:44 [PATCH 00/10] Improve crc-core driver interface Mahesh Kumar
2018-06-27 14:44 ` [PATCH 01/10] drm: crc: Introduce verify_crc_source callback Mahesh Kumar
2018-06-27 14:44 ` [PATCH 02/10] drm: crc: Introduce pre_crc_read function Mahesh Kumar
2018-06-27 15:18 ` Maarten Lankhorst
2018-06-27 15:22 ` Kumar, Mahesh [this message]
2018-06-27 14:44 ` [PATCH 03/10] drm: crc: Introduce get_crc_sources callback Mahesh Kumar
2018-06-27 14:44 ` [PATCH 04/10] drm/rockchip/crc: Implement verify_crc_source callback Mahesh Kumar
2018-06-27 14:44 ` [PATCH 05/10] drm/amdgpu_dm/crc: " Mahesh Kumar
2018-06-27 14:44 ` [PATCH 06/10] drm/rcar-du/crc: " Mahesh Kumar
2018-06-27 14:44 ` [PATCH 07/10] drm/i915/crc: implement " Mahesh Kumar
2018-06-27 14:44 ` [PATCH 08/10] drm/i915/crc: implement get_crc_sources callback Mahesh Kumar
2018-06-27 14:44 ` [PATCH 09/10] drm/crc: Cleanup crtc_crc_open function Mahesh Kumar
2018-06-27 14:44 ` [PATCH 10/10] Revert "drm: crc: Wait for a frame before returning from open()" Mahesh Kumar
2018-06-27 15:23 ` Maarten Lankhorst
2018-06-27 17:46 ` ✗ Fi.CI.BAT: failure for Improve crc-core driver interface (rev3) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 6:22 [PATCH 00/10] Improve crc-core driver interface Mahesh Kumar
2018-06-26 6:22 ` [PATCH 02/10] drm: crc: Introduce pre_crc_read function Mahesh Kumar
2018-06-22 10:41 [PATCH 00/10] Improve crc-core driver interface Mahesh Kumar
2018-06-22 10:41 ` [PATCH 02/10] drm: crc: Introduce pre_crc_read function Mahesh Kumar
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=ffc8962a-4189-6559-2e9d-fe7b888fc178@intel.com \
--to=mahesh1.kumar@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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