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: Wed, 27 Jun 2018 15:10:12 +0200 [thread overview]
Message-ID: <2037317.Zy9BHlEm4Q@phil> (raw)
In-Reply-To: <1530001004-25036-1-git-send-email-hjc@rock-chips.com>
Hi Sandy,
Am Dienstag, 26. Juni 2018, 10:16:44 CEST schrieb Sandy Huang:
> linebuffer mode should be LB_YUV_3840X5 when width is bigger
> than 1280 in yuv mode.
> seperate yuv and rgb case make the scl_vop_cal_lb_mode() logic
> is clearer.
>
> Signed-off-by: Sandy Huang <hjc@rock-chips.com>
applied to drm-misc-next
Heiko
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: Wed, 27 Jun 2018 15:10:12 +0200 [thread overview]
Message-ID: <2037317.Zy9BHlEm4Q@phil> (raw)
In-Reply-To: <1530001004-25036-1-git-send-email-hjc@rock-chips.com>
Hi Sandy,
Am Dienstag, 26. Juni 2018, 10:16:44 CEST schrieb Sandy Huang:
> linebuffer mode should be LB_YUV_3840X5 when width is bigger
> than 1280 in yuv mode.
> seperate yuv and rgb case make the scl_vop_cal_lb_mode() logic
> is clearer.
>
> Signed-off-by: Sandy Huang <hjc@rock-chips.com>
applied to drm-misc-next
Heiko
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: Wed, 27 Jun 2018 15:10:12 +0200 [thread overview]
Message-ID: <2037317.Zy9BHlEm4Q@phil> (raw)
In-Reply-To: <1530001004-25036-1-git-send-email-hjc@rock-chips.com>
Hi Sandy,
Am Dienstag, 26. Juni 2018, 10:16:44 CEST schrieb Sandy Huang:
> linebuffer mode should be LB_YUV_3840X5 when width is bigger
> than 1280 in yuv mode.
> seperate yuv and rgb case make the scl_vop_cal_lb_mode() logic
> is clearer.
>
> Signed-off-by: Sandy Huang <hjc@rock-chips.com>
applied to drm-misc-next
Heiko
next prev parent reply other threads:[~2018-06-27 13:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 8:16 [PATCH] drm/rockchip: vop: fixup linebuffer mode calc error 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 [this message]
2018-06-27 13:10 ` Heiko Stuebner
2018-06-27 13:10 ` Heiko Stuebner
-- strict thread matches above, loose matches on Subject: below --
2018-04-17 10:15 Sandy Huang
2018-04-17 10:15 ` Sandy Huang
2018-04-17 10:15 ` Sandy Huang
2018-04-17 11:14 ` Heiko Stuebner
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
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=2037317.Zy9BHlEm4Q@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.