All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
To: David Airlie <airlied@linux.ie>
Cc: Tejun Heo <tj@kernel.org>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH] drm/radeon: Remove deprecated create_singlethread_workqueue
Date: Tue, 28 Jun 2016 22:56:01 +0530	[thread overview]
Message-ID: <20160628172601.GA6046@Karyakshetra> (raw)

alloc_workqueue replaces deprecated create_singlethread_workqueue().

A dedicated workqueue has been used since work items need to be flushed
as a group rather than individually.

Since the flip_queue workqueue is involved in page-flipping and is not
being used on a memory reclaim path, WQ_MEM_RECLAIM has not been set.

Since there are only a fixed number of work items, explicit concurrency
limit is unnecessary here.

Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
---
 drivers/gpu/drm/radeon/radeon_display.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/radeon/radeon_display.c b/drivers/gpu/drm/radeon/radeon_display.c
index 6a41b49..bbb29c7 100644
--- a/drivers/gpu/drm/radeon/radeon_display.c
+++ b/drivers/gpu/drm/radeon/radeon_display.c
@@ -711,7 +711,7 @@ static void radeon_crtc_init(struct drm_device *dev, int index)

 	drm_mode_crtc_set_gamma_size(&radeon_crtc->base, 256);
 	radeon_crtc->crtc_id = index;
-	radeon_crtc->flip_queue = create_singlethread_workqueue("radeon-crtc");
+	radeon_crtc->flip_queue = alloc_workqueue("radeon-crtc", 0, 0);
 	rdev->mode_info.crtcs[index] = radeon_crtc;

 	if (rdev->family >= CHIP_BONAIRE) {
--
2.1.4

             reply	other threads:[~2016-06-28 17:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 17:26 Bhaktipriya Shridhar [this message]
2016-06-28 17:44 ` [PATCH] drm/radeon: Remove deprecated create_singlethread_workqueue Bhaktipriya Shridhar
  -- strict thread matches above, loose matches on Subject: below --
2016-07-02 11:03 Bhaktipriya Shridhar
2016-07-02 13:46 ` Tejun Heo
2016-07-02 13:46   ` Tejun Heo
2016-07-04  3:58   ` Michel Dänzer
2016-07-04  3:58     ` Michel Dänzer
2016-07-05 21:06     ` Tejun Heo
2016-07-05 21:06       ` Tejun Heo
2016-07-06  3:12       ` Michel Dänzer
2016-07-06  3:12         ` Michel Dänzer
2016-07-06 13:45         ` Tejun Heo
2016-07-06 13:45           ` Tejun Heo
2016-07-07  3:32           ` Michel Dänzer
2016-07-07  3:32             ` Michel Dänzer
2016-07-07  7:43             ` Christian König
2016-07-07  7:43               ` Christian König
2016-07-08  5:52               ` Michel Dänzer
2016-07-08  5:52                 ` Michel Dänzer
2016-07-12 17:52                 ` Tejun Heo
2016-07-12 17:52                   ` Tejun Heo

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=20160628172601.GA6046@Karyakshetra \
    --to=bhaktipriya96@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /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 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.