From: Stefan Agner <stefan@agner.ch> To: dri-devel@lists.freedesktop.org, meng.yi@nxp.com Cc: alison.wang@freescale.com, jianwei.wang.chn@gmail.com, linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch> Subject: [PATCH 4/4] drm/fsl-dcu: do not update when modifying irq registers Date: Mon, 5 Sep 2016 21:02:33 -0700 [thread overview] Message-ID: <20160906040233.32471-5-stefan@agner.ch> (raw) In-Reply-To: <20160906040233.32471-1-stefan@agner.ch> The IRQ status and mask registers are not "double buffered" according to the reference manual. Hence, there is no extra transfer/update write needed when modifying these registers. Signed-off-by: Stefan Agner <stefan@agner.ch> --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c index 092aaec..4e700bc4 100644 --- a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c +++ b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c @@ -59,8 +59,6 @@ static int fsl_dcu_drm_irq_init(struct drm_device *dev) regmap_write(fsl_dev->regmap, DCU_INT_STATUS, 0); regmap_write(fsl_dev->regmap, DCU_INT_MASK, ~0); - regmap_write(fsl_dev->regmap, DCU_UPDATE_MODE, - DCU_UPDATE_MODE_READREG); return ret; } @@ -139,8 +137,6 @@ static irqreturn_t fsl_dcu_drm_irq(int irq, void *arg) drm_handle_vblank(dev, 0); regmap_write(fsl_dev->regmap, DCU_INT_STATUS, int_status); - regmap_write(fsl_dev->regmap, DCU_UPDATE_MODE, - DCU_UPDATE_MODE_READREG); return IRQ_HANDLED; } -- 2.9.3
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Agner <stefan@agner.ch> To: dri-devel@lists.freedesktop.org, meng.yi@nxp.com Cc: jianwei.wang.chn@gmail.com, linux-kernel@vger.kernel.org, alison.wang@freescale.com Subject: [PATCH 4/4] drm/fsl-dcu: do not update when modifying irq registers Date: Mon, 5 Sep 2016 21:02:33 -0700 [thread overview] Message-ID: <20160906040233.32471-5-stefan@agner.ch> (raw) In-Reply-To: <20160906040233.32471-1-stefan@agner.ch> The IRQ status and mask registers are not "double buffered" according to the reference manual. Hence, there is no extra transfer/update write needed when modifying these registers. Signed-off-by: Stefan Agner <stefan@agner.ch> --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c index 092aaec..4e700bc4 100644 --- a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c +++ b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c @@ -59,8 +59,6 @@ static int fsl_dcu_drm_irq_init(struct drm_device *dev) regmap_write(fsl_dev->regmap, DCU_INT_STATUS, 0); regmap_write(fsl_dev->regmap, DCU_INT_MASK, ~0); - regmap_write(fsl_dev->regmap, DCU_UPDATE_MODE, - DCU_UPDATE_MODE_READREG); return ret; } @@ -139,8 +137,6 @@ static irqreturn_t fsl_dcu_drm_irq(int irq, void *arg) drm_handle_vblank(dev, 0); regmap_write(fsl_dev->regmap, DCU_INT_STATUS, int_status); - regmap_write(fsl_dev->regmap, DCU_UPDATE_MODE, - DCU_UPDATE_MODE_READREG); return IRQ_HANDLED; } -- 2.9.3 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-06 4:02 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-06 4:02 [PATCH 0/4] drm/fsl-dcu: add overlay and cursor plane support Stefan Agner 2016-09-06 4:02 ` Stefan Agner 2016-09-06 4:02 ` [PATCH 1/4] drm/fsl-dcu: support overlay and cursor planes Stefan Agner 2016-09-06 4:02 ` Stefan Agner 2016-09-06 4:02 ` [PATCH 2/4] drm/fsl-dcu: respect pos/size register sizes Stefan Agner 2016-09-06 4:02 ` Stefan Agner 2016-09-06 4:02 ` [PATCH 3/4] drm/fsl-dcu: update all registers on flush Stefan Agner 2016-09-06 4:02 ` Stefan Agner 2016-09-07 8:46 ` Meng Yi 2016-09-06 4:02 ` Stefan Agner [this message] 2016-09-06 4:02 ` [PATCH 4/4] drm/fsl-dcu: do not update when modifying irq registers Stefan Agner 2016-09-07 8:43 ` [PATCH 0/4] drm/fsl-dcu: add overlay and cursor plane support Meng Yi 2016-09-07 8:43 ` Meng Yi 2016-09-21 18:13 ` Stefan Agner 2016-09-21 18:13 ` Stefan Agner
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=20160906040233.32471-5-stefan@agner.ch \ --to=stefan@agner.ch \ --cc=alison.wang@freescale.com \ --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: linkBe 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.