All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Sandy Huang <hjc@rock-chips.com>
Cc: David Airlie <airlied@linux.ie>,
	linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/rockchip: vop: fixup linebuffer mode calc error
Date: Tue, 17 Apr 2018 13:14:08 +0200	[thread overview]
Message-ID: <2475172.s4GHAT5PDW@phil> (raw)
In-Reply-To: <1523960108-190541-1-git-send-email-hjc@rock-chips.com>

Hi Sandy,

Am Dienstag, 17. April 2018, 12:15:07 CEST schrieb Sandy Huang:
> When video width is bigger than 3840 the linebuffer mode
> should be LB_YUV_3840X5.

Can you explain that a bit better?

I.e. when looking at the code, the very first check is width > 2560.

So it seems your change targets some YUV mode with width > 3840
which should be mentioned in the commit message, so people like
me don't scratch their head in confusion ;-)

Similarly that check is actually width > 1280 to set LB_YUV_3840X5,
so I guess you're actually wanting any YUV mode bigger than
1280px should use LB_YUV_3840X5?


Heiko

> Signed-off-by: Sandy Huang <hjc@rock-chips.com>
> ---
>  drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.h b/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> index 56bbd2e..3e7501b 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> @@ -332,7 +332,7 @@ static inline int scl_vop_cal_lb_mode(int width, bool is_yuv)
>  
>  	if (width > 2560)
>  		lb_mode = LB_RGB_3840X2;
> -	else if (width > 1920)
> +	else if (!is_yuv && width > 1920)
>  		lb_mode = LB_RGB_2560X4;
>  	else if (!is_yuv)
>  		lb_mode = LB_RGB_1920X5;
> 


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/rockchip: vop: fixup linebuffer mode calc error
Date: Tue, 17 Apr 2018 13:14:08 +0200	[thread overview]
Message-ID: <2475172.s4GHAT5PDW@phil> (raw)
In-Reply-To: <1523960108-190541-1-git-send-email-hjc@rock-chips.com>

Hi Sandy,

Am Dienstag, 17. April 2018, 12:15:07 CEST schrieb Sandy Huang:
> When video width is bigger than 3840 the linebuffer mode
> should be LB_YUV_3840X5.

Can you explain that a bit better?

I.e. when looking at the code, the very first check is width > 2560.

So it seems your change targets some YUV mode with width > 3840
which should be mentioned in the commit message, so people like
me don't scratch their head in confusion ;-)

Similarly that check is actually width > 1280 to set LB_YUV_3840X5,
so I guess you're actually wanting any YUV mode bigger than
1280px should use LB_YUV_3840X5?


Heiko

> Signed-off-by: Sandy Huang <hjc@rock-chips.com>
> ---
>  drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.h b/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> index 56bbd2e..3e7501b 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> @@ -332,7 +332,7 @@ static inline int scl_vop_cal_lb_mode(int width, bool is_yuv)
>  
>  	if (width > 2560)
>  		lb_mode = LB_RGB_3840X2;
> -	else if (width > 1920)
> +	else if (!is_yuv && width > 1920)
>  		lb_mode = LB_RGB_2560X4;
>  	else if (!is_yuv)
>  		lb_mode = LB_RGB_1920X5;
> 

WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Sandy Huang <hjc@rock-chips.com>
Cc: dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/rockchip: vop: fixup linebuffer mode calc error
Date: Tue, 17 Apr 2018 13:14:08 +0200	[thread overview]
Message-ID: <2475172.s4GHAT5PDW@phil> (raw)
In-Reply-To: <1523960108-190541-1-git-send-email-hjc@rock-chips.com>

Hi Sandy,

Am Dienstag, 17. April 2018, 12:15:07 CEST schrieb Sandy Huang:
> When video width is bigger than 3840 the linebuffer mode
> should be LB_YUV_3840X5.

Can you explain that a bit better?

I.e. when looking at the code, the very first check is width > 2560.

So it seems your change targets some YUV mode with width > 3840
which should be mentioned in the commit message, so people like
me don't scratch their head in confusion ;-)

Similarly that check is actually width > 1280 to set LB_YUV_3840X5,
so I guess you're actually wanting any YUV mode bigger than
1280px should use LB_YUV_3840X5?


Heiko

> Signed-off-by: Sandy Huang <hjc@rock-chips.com>
> ---
>  drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.h b/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> index 56bbd2e..3e7501b 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.h
> @@ -332,7 +332,7 @@ static inline int scl_vop_cal_lb_mode(int width, bool is_yuv)
>  
>  	if (width > 2560)
>  		lb_mode = LB_RGB_3840X2;
> -	else if (width > 1920)
> +	else if (!is_yuv && width > 1920)
>  		lb_mode = LB_RGB_2560X4;
>  	else if (!is_yuv)
>  		lb_mode = LB_RGB_1920X5;
> 

  reply	other threads:[~2018-04-17 11:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 10:15 [PATCH] drm/rockchip: vop: fixup linebuffer mode calc error Sandy Huang
2018-04-17 10:15 ` Sandy Huang
2018-04-17 10:15 ` Sandy Huang
2018-04-17 11:14 ` Heiko Stuebner [this message]
2018-04-17 11:14   ` Heiko Stuebner
2018-04-17 11:14   ` Heiko Stuebner
2018-04-19 12:03   ` Sandy Huang
2018-04-19 13:14   ` Sandy Huang
2018-04-19 13:14     ` Sandy Huang
  -- strict thread matches above, loose matches on Subject: below --
2018-06-26  8:16 Sandy Huang
2018-06-26  8:16 ` Sandy Huang
2018-06-26  8:16 ` Sandy Huang
2018-06-26  8:22 ` Heiko Stübner
2018-06-26  8:22   ` Heiko Stübner
2018-06-26  8:22   ` Heiko Stübner
2018-06-27 13:10 ` Heiko Stuebner
2018-06-27 13:10   ` Heiko Stuebner
2018-06-27 13:10   ` Heiko Stuebner

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=2475172.s4GHAT5PDW@phil \
    --to=heiko@sntech.de \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hjc@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.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.