Linux Media Controller development
 help / color / mirror / Atom feed
From: Tomasz Figa <t.figa@samsung.com>
To: Vikas Sajjan <vikas.sajjan@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
	kgene.kim@samsung.com, inki.dae@samsung.com,
	s.nawrocki@samsung.com, m.szyprowski@samsung.com,
	tomasz.figa@gmail.com, robdclark@gmail.com, arun.kk@samsung.com,
	patches@linaro.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH V2] drm/exynos: Add fallback option to get non physically continous memory for fb
Date: Mon, 05 Aug 2013 16:20:15 +0200	[thread overview]
Message-ID: <1755621.zBhZbpqAGX@amdc1227> (raw)
In-Reply-To: <1375695882-16004-1-git-send-email-vikas.sajjan@linaro.org>

On Monday 05 of August 2013 15:14:42 Vikas Sajjan wrote:
> While trying to get boot-logo up on exynos5420 SMDK which has eDP panel
> connected with resolution 2560x1600, following error occured even with
> IOMMU enabled:
> [0.880000] [drm:lowlevel_buffer_allocate] *ERROR* failed to allocate
> buffer. [0.890000] [drm] Initialized exynos 1.0.0 20110530 on minor 0
> 
> To address the case where physically continous memory MAY NOT be a
> mandatory requirement for fb, the patch adds a feature to get non
> physically continous memory for fb if IOMMU is supported and if CONTIG
> memory allocation fails.
> 
> Signed-off-by: Vikas Sajjan <vikas.sajjan@linaro.org>
> Signed-off-by: Arun Kumar <arun.kk@samsung.com>
> ---
> changes since v1:
> 	 - Modified to add the fallback patch if CONTIG alloc fails as suggested
> by Rob Clark robdclark@gmail.com and Tomasz Figa
> <tomasz.figa@gmail.com>.
> 
> 	 - changed the commit message.
> ---
>  drivers/gpu/drm/exynos/exynos_drm_fbdev.c |   19 +++++++++++++++----
>  1 file changed, 15 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
> b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c index 8e60bd6..9a4b886
> 100644
> --- a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
> +++ b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
> @@ -16,6 +16,7 @@
>  #include <drm/drm_crtc.h>
>  #include <drm/drm_fb_helper.h>
>  #include <drm/drm_crtc_helper.h>
> +#include <drm/exynos_drm.h>
> 
>  #include "exynos_drm_drv.h"
>  #include "exynos_drm_fb.h"
> @@ -165,11 +166,21 @@ static int exynos_drm_fbdev_create(struct
> drm_fb_helper *helper,
> 
>  	size = mode_cmd.pitches[0] * mode_cmd.height;
> 
> -	/* 0 means to allocate physically continuous memory */
> -	exynos_gem_obj = exynos_drm_gem_create(dev, 0, size);
> +	exynos_gem_obj = exynos_drm_gem_create(dev, EXYNOS_BO_CONTIG, size);

You can put the fallback here like this:
	if (IS_ERR(exynos_gem_obj) && is_drm_iommu_supported(dev)) {
		/*
		 * If IOMMU is supported then try to get buffer from
		 * non-continous memory area
		 */
		dev_warn(&pdev->dev, "contiguous FB allocation failed, falling back to non-contiguous\n");
		exynos_gem_obj = exynos_drm_gem_create(dev,
										EXYNOS_BO_NONCONTIG, size);
	}

>  	if (IS_ERR(exynos_gem_obj)) {
> -		ret = PTR_ERR(exynos_gem_obj);
> -		goto err_release_framebuffer;

And then you can leave this original check untouched, reducing the
diffstat and unnecessary code indentation.

> +		/*
> +		 * If IOMMU is supported then try to get buffer from
> +		 * non-continous memory area
> +		 */
> +		if (is_drm_iommu_supported(dev))
> +			exynos_gem_obj = exynos_drm_gem_create(dev,
> +						EXYNOS_BO_NONCONTIG, size);
> +		if (IS_ERR(exynos_gem_obj)) {
> +			ret = PTR_ERR(exynos_gem_obj);
> +			goto err_release_framebuffer;
> +		}
> +		dev_warn(&pdev->dev, "exynos_gem_obj for FB is allocated with\n"
> +				"non physically continuous memory\n");

Please don't split messages into multiple lines, because this makes
grepping for them harder (and checkpatch complains).

Best regards,
Tomasz


      parent reply	other threads:[~2013-08-05 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05  9:44 [PATCH V2] drm/exynos: Add fallback option to get non physically continous memory for fb Vikas Sajjan
2013-08-05 14:13 ` Rob Clark
2013-08-05 14:20 ` Tomasz Figa [this message]

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=1755621.zBhZbpqAGX@amdc1227 \
    --to=t.figa@samsung.com \
    --cc=arun.kk@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=patches@linaro.org \
    --cc=robdclark@gmail.com \
    --cc=s.nawrocki@samsung.com \
    --cc=tomasz.figa@gmail.com \
    --cc=vikas.sajjan@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox