From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Mahesh Kumar <mahesh1.kumar@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 10/10] Revert "drm: crc: Wait for a frame before returning from open()"
Date: Fri, 22 Jun 2018 17:03:07 +0200 [thread overview]
Message-ID: <b63b5f6d-ea09-ccf9-a7a9-ec3d845b323f@collabora.com> (raw)
In-Reply-To: <0570ec3e-2e0a-da7b-faac-0ae94f911812@linux.intel.com>
On 06/22/2018 02:30 PM, Maarten Lankhorst wrote:
> Op 22-06-18 om 12:41 schreef Mahesh Kumar:
>> This reverts commit e8fa5671183c80342d520ad81d14fa79a9d4a680.
>>
>> Don't wait for first CRC during crtc_crc_open. It avoids one frame wait
>> during open. If application want to wait after read call, it can use
>> poll/read blocking read() call.
Hi,
unfortunately I don't remember why that was deemed undesirable, and I
failed to explain so in the commit message.
My only comment is that it would be good to make the motivation for this
revert explicit, in case someone else in the future wonders.
I would also test it in a machine with eDP, IGT should be able to test there.
Thanks,
Tomeu
>> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Mahesh Kumar <mahesh1.kumar@intel.com>
>> ---
>> drivers/gpu/drm/drm_debugfs_crc.c | 16 ----------------
>> 1 file changed, 16 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_debugfs_crc.c b/drivers/gpu/drm/drm_debugfs_crc.c
>> index 834bc7ee5550..69ec2728727e 100644
>> --- a/drivers/gpu/drm/drm_debugfs_crc.c
>> +++ b/drivers/gpu/drm/drm_debugfs_crc.c
>> @@ -211,24 +211,8 @@ static int crtc_crc_open(struct inode *inode, struct file *filep)
>> if (ret)
>> goto err;
>>
>> - spin_lock_irq(&crc->lock);
>> - /*
>> - * Only return once we got a first frame, so userspace doesn't have to
>> - * guess when this particular piece of HW will be ready to start
>> - * generating CRCs.
>> - */
>> - ret = wait_event_interruptible_lock_irq(crc->wq,
>> - crtc_crc_data_count(crc),
>> - crc->lock);
>> - spin_unlock_irq(&crc->lock);
>> -
>> - if (ret)
>> - goto err_disable;
>> -
>> return 0;
>>
>> -err_disable:
>> - crtc->funcs->set_crc_source(crtc, NULL);
>> err:
>> spin_lock_irq(&crc->lock);
>> crtc_crc_cleanup(crc);
>
> Adding Tomeu Vizoso to the cc.
>
> Can you resend the series, and add dri-devel@lists.freedesktop.org and the driver maintainers to the cc? You'll need to get acks from the maintainers to merge this through drm-misc. :)
>
> ~Maarten
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-06-22 15:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 10:41 [PATCH 00/10] Improve crc-core driver interface Mahesh Kumar
2018-06-22 10:41 ` [PATCH 01/10] drm: crc: Introduce verify_crc_source callback Mahesh Kumar
2018-06-25 15:38 ` Daniel Vetter
2018-06-22 10:41 ` [PATCH 02/10] drm: crc: Introduce pre_crc_read function Mahesh Kumar
2018-06-22 10:41 ` [PATCH 03/10] drm: crc: Introduce get_crc_sources callback Mahesh Kumar
2018-06-22 10:41 ` [PATCH 04/10] drm/rockchip/crc: Implement verify_crc_source callback Mahesh Kumar
2018-06-22 10:41 ` [PATCH 05/10] drm/amdgpu_dm/crc: " Mahesh Kumar
2018-06-22 10:41 ` [PATCH 06/10] drm/rcar-du/crc: " Mahesh Kumar
2018-06-22 10:41 ` [PATCH 07/10] drm/i915/crc: implement " Mahesh Kumar
2018-06-22 10:41 ` [PATCH 08/10] drm/i915/crc: implement get_crc_sources callback Mahesh Kumar
2018-06-22 10:41 ` [PATCH 09/10] drm/crc: Cleanup crtc_crc_open function Mahesh Kumar
2018-06-22 10:41 ` [PATCH 10/10] Revert "drm: crc: Wait for a frame before returning from open()" Mahesh Kumar
2018-06-22 12:30 ` Maarten Lankhorst
2018-06-22 15:03 ` Tomeu Vizoso [this message]
2018-06-22 10:46 ` ✗ Fi.CI.CHECKPATCH: warning for Improve crc-core driver interface Patchwork
2018-06-22 11:01 ` ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 6:22 [PATCH 00/10] " Mahesh Kumar
2018-06-26 6:22 ` [PATCH 10/10] Revert "drm: crc: Wait for a frame before returning from open()" Mahesh Kumar
2018-06-27 14:44 [PATCH 00/10] Improve crc-core driver interface 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
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=b63b5f6d-ea09-ccf9-a7a9-ec3d845b323f@collabora.com \
--to=tomeu.vizoso@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--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