linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Inki Dae <inki.dae@samsung.com>
To: Archit Taneja <architt@codeaurora.org>,
	dri-devel@lists.freedesktop.org, daniel@ffwll.ch
Cc: linux-arm-msm@vger.kernel.org, airlied@linux.ie,
	Joonyoung Shim <jy0922.shim@samsung.com>,
	Seung-Woo Kim <sw0312.kim@samsung.com>
Subject: Re: [PATCH 14/25] drm/exynos: Use new drm_fb_helper functions
Date: Tue, 11 Aug 2015 18:11:18 +0900	[thread overview]
Message-ID: <55C9BC36.2020502@samsung.com> (raw)
In-Reply-To: <55C9BAAF.4040907@samsung.com>

On 2015년 08월 11일 18:04, Inki Dae wrote:
> On 2015년 07월 13일 15:38, Archit Taneja wrote:
>> Use the newly created wrapper drm_fb_helper functions instead of calling
>> core fbdev functions directly. They also simplify the fb_info creation.
>>
>> COMPILE TESTED ONLY.
>>
>> Cc: Inki Dae <inki.dae@samsung.com>
>> Cc: Joonyoung Shim <jy0922.shim@samsung.com>
>> Cc: Seung-Woo Kim <sw0312.kim@samsung.com>
>>
>> Signed-off-by: Archit Taneja <architt@codeaurora.org>
>> ---
>>  drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 45 +++++++++----------------------
>>  1 file changed, 12 insertions(+), 33 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
>> index e0b085b..6975b70 100644
>> --- a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
>> +++ b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
>> @@ -65,9 +65,9 @@ static int exynos_drm_fb_mmap(struct fb_info *info,
>>  static struct fb_ops exynos_drm_fb_ops = {
>>  	.owner		= THIS_MODULE,
>>  	.fb_mmap        = exynos_drm_fb_mmap,
>> -	.fb_fillrect	= cfb_fillrect,
>> -	.fb_copyarea	= cfb_copyarea,
>> -	.fb_imageblit	= cfb_imageblit,
>> +	.fb_fillrect	= drm_fb_helper_cfb_fillrect,
>> +	.fb_copyarea	= drm_fb_helper_cfb_copyarea,
>> +	.fb_imageblit	= drm_fb_helper_cfb_imageblit,
>>  	.fb_check_var	= drm_fb_helper_check_var,
>>  	.fb_set_par	= drm_fb_helper_set_par,
>>  	.fb_blank	= drm_fb_helper_blank,
>> @@ -142,10 +142,10 @@ static int exynos_drm_fbdev_create(struct drm_fb_helper *helper,
>>  
>>  	mutex_lock(&dev->struct_mutex);
>>  
>> -	fbi = framebuffer_alloc(0, &pdev->dev);
>> -	if (!fbi) {
>> +	fbi = drm_fb_helper_alloc_fbi(helper);
>> +	if (IS_ERR(fbi)) {
>>  		DRM_ERROR("failed to allocate fb info.\n");
>> -		ret = -ENOMEM;
>> +		ret = PTR_ERR(fbi);
>>  		goto out;
>>  	}
>>  
>> @@ -165,7 +165,7 @@ static int exynos_drm_fbdev_create(struct drm_fb_helper *helper,
>>  
>>  	if (IS_ERR(exynos_gem_obj)) {
>>  		ret = PTR_ERR(exynos_gem_obj);
>> -		goto err_release_framebuffer;
>> +		goto err_release_fbi;
>>  	}
>>  
>>  	exynos_fbdev->exynos_gem_obj = exynos_gem_obj;
>> @@ -178,21 +178,13 @@ static int exynos_drm_fbdev_create(struct drm_fb_helper *helper,
>>  		goto err_destroy_gem;
>>  	}
>>  
>> -	helper->fbdev = fbi;
>> -
>>  	fbi->par = helper;
>>  	fbi->flags = FBINFO_FLAG_DEFAULT;
>>  	fbi->fbops = &exynos_drm_fb_ops;
>>  
>> -	ret = fb_alloc_cmap(&fbi->cmap, 256, 0);
>> -	if (ret) {
>> -		DRM_ERROR("failed to allocate cmap.\n");
>> -		goto err_destroy_framebuffer;
>> -	}
>> -
>>  	ret = exynos_drm_fbdev_update(helper, sizes, helper->fb);
>>  	if (ret < 0)
>> -		goto err_dealloc_cmap;
>> +		goto err_destroy_framebuffer;
> 
> With above change, err_dealloc_cmap label isn't used anymore so you need
> to remove below lines,
> 
> err_dealloc_cmap:
> 	fb_dealloc_cmap(&fbi->cmap);


Oops, Sorry. You already posted v2 and there is no warning.

Please ignore it.

Thanks,
Inki Dae

> 
> Thanks,
> Inki Dae
> 
>>  
>>  	mutex_unlock(&dev->struct_mutex);
>>  	return ret;
>> @@ -203,8 +195,8 @@ err_destroy_framebuffer:
>>  	drm_framebuffer_cleanup(helper->fb);
>>  err_destroy_gem:
>>  	exynos_drm_gem_destroy(exynos_gem_obj);
>> -err_release_framebuffer:
>> -	framebuffer_release(fbi);
>> +err_release_fbi:
>> +	drm_fb_helper_release_fbi(helper);
>>  
>>  /*
>>   * if failed, all resources allocated above would be released by
>> @@ -312,21 +304,8 @@ static void exynos_drm_fbdev_destroy(struct drm_device *dev,
>>  		}
>>  	}
>>  
>> -	/* release linux framebuffer */
>> -	if (fb_helper->fbdev) {
>> -		struct fb_info *info;
>> -		int ret;
>> -
>> -		info = fb_helper->fbdev;
>> -		ret = unregister_framebuffer(info);
>> -		if (ret < 0)
>> -			DRM_DEBUG_KMS("failed unregister_framebuffer()\n");
>> -
>> -		if (info->cmap.len)
>> -			fb_dealloc_cmap(&info->cmap);
>> -
>> -		framebuffer_release(info);
>> -	}
>> +	drm_fb_helper_unregister_fbi(fb_helper);
>> +	drm_fb_helper_release_fbi(fb_helper);
>>  
>>  	drm_fb_helper_fini(fb_helper);
>>  }
>>
> 

  reply	other threads:[~2015-08-11  9:11 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  6:37 [PATCH 00/25] drm: fb emulation: Step 1: Create new drm_fb_helper wrapper funcs Archit Taneja
2015-07-13  6:37 ` [PATCH 01/25] drm/fb_helper: Add drm_fb_helper functions to manage fb_info creation Archit Taneja
2015-07-13  6:37 ` [PATCH 02/25] drm/fb_helper: Create a wrapper for unlink_framebuffer Archit Taneja
2015-07-13  7:30   ` Daniel Vetter
2015-07-13  6:37 ` [PATCH 03/25] drm/fb_helper: Create wrappers for fb_sys_read/write funcs Archit Taneja
2015-07-13  7:31   ` Daniel Vetter
2015-07-13  9:59     ` Archit Taneja
2015-07-13  7:39   ` Daniel Vetter
2015-07-13  6:38 ` [PATCH 04/25] drm/fb_helper: Create wrappers for blit, copyarea and fillrect funcs Archit Taneja
2015-07-13  7:40   ` Daniel Vetter
2015-07-13  6:38 ` [PATCH 05/25] drm/fb_helper: Create a wrapper for fb_set_suspend Archit Taneja
2015-07-13  6:38 ` [PATCH 06/25] drm/fb_helper: Create a wrapper for remove_conflicting_framebuffers Archit Taneja
2015-07-13  6:38 ` [PATCH 07/25] drm/cirrus: Use new drm_fb_helper functions Archit Taneja
2015-07-13  6:38 ` [PATCH 08/25] drm/rockchip: " Archit Taneja
2015-07-13  6:38 ` [PATCH 09/25] drm/armada: " Archit Taneja
2015-07-13  6:38 ` [PATCH 10/25] drm/ast: " Archit Taneja
2015-07-13  6:38 ` [PATCH 11/25] drm/omap: " Archit Taneja
2015-07-13  6:38 ` [PATCH 12/25] drm/tegra: " Archit Taneja
2015-07-14  8:50   ` Thierry Reding
2015-07-14  9:11     ` Archit Taneja
2015-07-13  6:38 ` [PATCH 13/25] drm/msm: " Archit Taneja
2015-07-13  6:38 ` [PATCH 14/25] drm/exynos: " Archit Taneja
2015-08-11  9:04   ` Inki Dae
2015-08-11  9:11     ` Inki Dae [this message]
2015-07-13  6:38 ` [PATCH 15/25] drm/gma500: " Archit Taneja
2015-07-13  6:38 ` [PATCH 16/25] drm/mgag200: " Archit Taneja
2015-07-13  6:38 ` [PATCH 17/25] drm/radeon: " Archit Taneja
2015-07-13  6:38 ` [PATCH 18/25] drm/qxl: " Archit Taneja
2015-07-13  6:38 ` [PATCH 19/25] drm/i915: " Archit Taneja
2015-07-13  6:38 ` [PATCH 20/25] drm/nouveau: " Archit Taneja
2015-07-13  6:38 ` [PATCH 21/25] drm/udl: " Archit Taneja
2015-07-13  6:38 ` [PATCH 22/25] drm/boschs: " Archit Taneja
2015-07-13  6:38 ` [PATCH 23/25] drm/amdgpu: " Archit Taneja
2015-07-13  6:38 ` [PATCH 24/25] drm/virtio: " Archit Taneja
2015-07-13  6:38 ` [PATCH 25/25] drm/fb_cma_helper: " Archit Taneja
2015-07-13  8:07 ` [PATCH 00/25] drm: fb emulation: Step 1: Create new drm_fb_helper wrapper funcs Daniel Vetter
2015-07-13 10:29   ` Archit Taneja
2015-07-13 14:11     ` Daniel Vetter
2015-07-13 15:25 ` Alex Deucher

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=55C9BC36.2020502@samsung.com \
    --to=inki.dae@samsung.com \
    --cc=airlied@linux.ie \
    --cc=architt@codeaurora.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jy0922.shim@samsung.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=sw0312.kim@samsung.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).