linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bibby.hsieh@mediatek.com (Bibby Hsieh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] drm: mediatek: change the variable type of rdma threshold
Date: Thu, 22 Jun 2017 10:21:04 +0800	[thread overview]
Message-ID: <1498098064.717.12.camel@mtksdaap41> (raw)
In-Reply-To: <1495431964.20811.8.camel@mtksdaap41>

Hi, CK,

Thanks for your review and comment.

On Mon, 2017-05-22 at 13:46 +0800, CK Hu wrote:
> Hi, Bibby:
> 
> One comment inline.
> 
> On Fri, 2017-05-19 at 17:57 +0800, Bibby Hsieh wrote:
> > For some greater resolution, the rdma threshold
> > variable will overflow.
> > 
> > Signed-off-by: Bibby Hsieh <bibby.hsieh@mediatek.com>
> > ---
> >  drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 7 ++++---
> >  1 file changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/mediatek/mtk_disp_rdma.c b/drivers/gpu/drm/mediatek/mtk_disp_rdma.c
> > index 0df05f9..9afdcd7 100644
> > --- a/drivers/gpu/drm/mediatek/mtk_disp_rdma.c
> > +++ b/drivers/gpu/drm/mediatek/mtk_disp_rdma.c
> > @@ -37,7 +37,7 @@
> >  #define DISP_REG_RDMA_FIFO_CON			0x0040
> >  #define RDMA_FIFO_UNDERFLOW_EN				BIT(31)
> >  #define RDMA_FIFO_PSEUDO_SIZE(bytes)			(((bytes) / 16) << 16)
> > -#define RDMA_OUTPUT_VALID_FIFO_THRESHOLD(bytes)		((bytes) / 16)
> > +#define RDMA_OUTPUT_VALID_FIFO_THRESHOLD(bytes) (((bytes) / 16) & 0x3ff)
> 
> I think it's not necessary to do this mask operation. Before calling
> RDMA_OUTPUT_VALID_FIFO_THRESHOLD(), you should make sure that width,
> height, and vrefresh matches the HW spec, so the result of threshold
> likely does not exceed 0x3ff. If width, height, and vrefresh matches the
> HW spec but threshold exceed 0x3ff, maybe you should limited it to 0x3ff
> rather than truncating it.
> 

Ok, It seems to me that I will refer Guenter's comment, add clamp_val()
to avoid unexpected value. Thanks.


Bibby

> Regards,
> CK
> 
> >  
> >  /**
> >   * struct mtk_disp_rdma - DISP_RDMA driver structure
> > @@ -109,7 +109,7 @@ static void mtk_rdma_config(struct mtk_ddp_comp *comp, unsigned int width,
> >  			    unsigned int height, unsigned int vrefresh,
> >  			    unsigned int bpc)
> >  {
> > -	unsigned int threshold;
> > +	unsigned long long threshold;
> >  	unsigned int reg;
> >  
> >  	rdma_update_bits(comp, DISP_REG_RDMA_SIZE_CON_0, 0xfff, width);
> > @@ -121,7 +121,8 @@ static void mtk_rdma_config(struct mtk_ddp_comp *comp, unsigned int width,
> >  	 * output threshold to 6 microseconds with 7/6 overhead to
> >  	 * account for blanking, and with a pixel depth of 4 bytes:
> >  	 */
> > -	threshold = width * height * vrefresh * 4 * 7 / 1000000;
> > +	threshold = (unsigned long long)width * height * vrefresh *
> > +		    4 * 7 / 1000000;
> >  	reg = RDMA_FIFO_UNDERFLOW_EN |
> >  	      RDMA_FIFO_PSEUDO_SIZE(SZ_8K) |
> >  	      RDMA_OUTPUT_VALID_FIFO_THRESHOLD(threshold);
> 
> 

-- 
Bibby

  reply	other threads:[~2017-06-22  2:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  9:57 [PATCH v2] drm: mediatek: change the variable type of rdma threshold Bibby Hsieh
2017-05-22  5:46 ` CK Hu
2017-06-22  2:21   ` Bibby Hsieh [this message]
2017-06-21 21:14 ` [v2] " Guenter Roeck
2017-06-22  2:25   ` Bibby Hsieh

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=1498098064.717.12.camel@mtksdaap41 \
    --to=bibby.hsieh@mediatek.com \
    --cc=linux-arm-kernel@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 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).