mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, daniel.vetter@ffwll.ch,
	jianwei.wang.chn@gmail.com, alison.wang@freescale.com,
	meng.yi@nxp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] drm/fsl-dcu: fix register initialization
Date: Thu, 25 Feb 2016 16:00:07 -0800	[thread overview]
Message-ID: <1a7b0c205b074613d7b7080742712669@agner.ch> (raw)
In-Reply-To: <1454461578-8649-1-git-send-email-stefan@agner.ch>

On 2016-02-02 17:06, Stefan Agner wrote:
> The layer enumeration start with 0 (0-15 for LS1021a and 0-63 for
> Vybrid) whereas the register enumeration start from 1 (1-10 for
> LS1021a and 1-9 for Vybrid). The loop started off from 0 for both
> iterations and initialized the number of layers inclusive, which
> is one layer too many.
> 
> All extensively written registers seem to be unassigned, it seems
> that the write to those registers did not do any harm in practice.
> 
> Signed-off-by: Stefan Agner <stefan@agner.ch>

Applied.

> ---
> This two patches apply cleanly on top of my earlier DCU fixes         
>
> patchset:                                                             
>
> https://lkml.org/lkml/2015/11/18/953
> 
> Changes since v1:
> - (none)
> 
>  drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c
> b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c
> index db69725..3c92889 100644
> --- a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c
> +++ b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c
> @@ -169,8 +169,8 @@ int fsl_dcu_drm_crtc_create(struct
> fsl_dcu_drm_device *fsl_dev)
>  		reg_num = LS1021A_LAYER_REG_NUM;
>  	else
>  		reg_num = VF610_LAYER_REG_NUM;
> -	for (i = 0; i <= fsl_dev->soc->total_layer; i++) {
> -		for (j = 0; j < reg_num; j++)
> +	for (i = 0; i < fsl_dev->soc->total_layer; i++) {
> +		for (j = 1; j <= reg_num; j++)
>  			regmap_write(fsl_dev->regmap, DCU_CTRLDESCLN(i, j), 0);
>  	}
>  	regmap_update_bits(fsl_dev->regmap, DCU_DCU_MODE,

      parent reply	other threads:[~2016-02-26  0:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03  1:06 Stefan Agner
2016-02-03  1:06 ` [PATCH v2 2/2] drm/fsl-dcu: use flat regmap cache Stefan Agner
2016-02-12  0:29   ` Stefan Agner
2016-02-26  0:00 ` Stefan Agner [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=1a7b0c205b074613d7b7080742712669@agner.ch \
    --to=stefan@agner.ch \
    --cc=airlied@linux.ie \
    --cc=alison.wang@freescale.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jianwei.wang.chn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meng.yi@nxp.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

all inboxes | Powered by JetHome®