From: Ayan Halder <ayan.halder@arm.com>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: airlied@linux.ie, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, malidp@foss.arm.com, nd@arm.com
Subject: Re: [PATCH v2 6/8] drm/arm/malidp: Enable/disable the scaling engine interrupts with memory writeback
Date: Tue, 24 Apr 2018 11:11:56 +0100 [thread overview]
Message-ID: <20180424101156.GA17307@arm.com> (raw)
In-Reply-To: <20180423153647.GF14661@e110455-lin.cambridge.arm.com>
Hi Liviu,
On Mon, Apr 23, 2018 at 04:36:47PM +0100, Liviu Dudau wrote:
> On Mon, Apr 23, 2018 at 03:50:49PM +0100, Ayan Kumar Halder wrote:
> > Scaling engine interrupts need to be enabled/disabled as and when memwrite
> > is enabled and disabled. The reason being scaling engine interrupts are
> > used only by the memory writeout layer.
> >
> > This patch depends on:
> > https://lkml.org/lkml/2017/5/15/695
> >
> > Signed-off-by: Ayan Kumar Halder <ayan.halder@arm.com>
> >
> > ---
> > Changes in v2:-
> > - Removed the change id and modified the commit message
> > ---
> > drivers/gpu/drm/arm/malidp_hw.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/arm/malidp_hw.c b/drivers/gpu/drm/arm/malidp_hw.c
> > index f5633bc..90d76e4 100644
> > --- a/drivers/gpu/drm/arm/malidp_hw.c
> > +++ b/drivers/gpu/drm/arm/malidp_hw.c
> > @@ -621,12 +621,14 @@ static int malidp550_enable_memwrite(struct malidp_hw_device *hwdev,
> > malidp_hw_setbits(hwdev, MALIDP550_SE_MEMWRITE_ONESHOT | MALIDP_SE_MEMWRITE_EN,
> > MALIDP550_SE_CONTROL);
> >
> > + malidp_se_irq_hw_init(hwdev);
> > return 0;
> > }
> >
> > static void malidp550_disable_memwrite(struct malidp_hw_device *hwdev)
> > {
> > u32 base = malidp_get_block_base(hwdev, MALIDP_DE_BLOCK);
> > + malidp_se_irq_fini(hwdev);
> > malidp_hw_clearbits(hwdev, MALIDP550_SE_MEMWRITE_ONESHOT | MALIDP_SE_MEMWRITE_EN,
> > MALIDP550_SE_CONTROL);
> > malidp_hw_clearbits(hwdev, MALIDP_SCALE_ENGINE_EN, base + MALIDP_DE_DISPLAY_FUNC);
>
> We now know that this patch is broken, because it disables interrupts
> for the writeback after a previous commit has enabled them but before
> the writeback engine has finished writing, so the better place for
> enabling and disabling the SE IRQs is in the malidp_pm_{suspend,resume}
> functions, not here.
>
Sorry, I missed this issue. I will send an updated v3 patch for this
only.
Thanks,
Ayan Kumar Halder
> Only for this patch: NACK.
>
> Best regards,
> Liviu
>
> > --
> > 2.7.4
> >
>
> --
> ====================
> | I would like to |
> | fix the world, |
> | but they're not |
> | giving me the |
> \ source code! /
> ---------------
> ??\_(???)_/??
_______________________________________________
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: Ayan Halder <ayan.halder@arm.com>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: brian.starkey@arm.com, malidp@foss.arm.com, airlied@linux.ie,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
nd@arm.com
Subject: Re: [PATCH v2 6/8] drm/arm/malidp: Enable/disable the scaling engine interrupts with memory writeback
Date: Tue, 24 Apr 2018 11:11:56 +0100 [thread overview]
Message-ID: <20180424101156.GA17307@arm.com> (raw)
In-Reply-To: <20180423153647.GF14661@e110455-lin.cambridge.arm.com>
Hi Liviu,
On Mon, Apr 23, 2018 at 04:36:47PM +0100, Liviu Dudau wrote:
> On Mon, Apr 23, 2018 at 03:50:49PM +0100, Ayan Kumar Halder wrote:
> > Scaling engine interrupts need to be enabled/disabled as and when memwrite
> > is enabled and disabled. The reason being scaling engine interrupts are
> > used only by the memory writeout layer.
> >
> > This patch depends on:
> > https://lkml.org/lkml/2017/5/15/695
> >
> > Signed-off-by: Ayan Kumar Halder <ayan.halder@arm.com>
> >
> > ---
> > Changes in v2:-
> > - Removed the change id and modified the commit message
> > ---
> > drivers/gpu/drm/arm/malidp_hw.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/arm/malidp_hw.c b/drivers/gpu/drm/arm/malidp_hw.c
> > index f5633bc..90d76e4 100644
> > --- a/drivers/gpu/drm/arm/malidp_hw.c
> > +++ b/drivers/gpu/drm/arm/malidp_hw.c
> > @@ -621,12 +621,14 @@ static int malidp550_enable_memwrite(struct malidp_hw_device *hwdev,
> > malidp_hw_setbits(hwdev, MALIDP550_SE_MEMWRITE_ONESHOT | MALIDP_SE_MEMWRITE_EN,
> > MALIDP550_SE_CONTROL);
> >
> > + malidp_se_irq_hw_init(hwdev);
> > return 0;
> > }
> >
> > static void malidp550_disable_memwrite(struct malidp_hw_device *hwdev)
> > {
> > u32 base = malidp_get_block_base(hwdev, MALIDP_DE_BLOCK);
> > + malidp_se_irq_fini(hwdev);
> > malidp_hw_clearbits(hwdev, MALIDP550_SE_MEMWRITE_ONESHOT | MALIDP_SE_MEMWRITE_EN,
> > MALIDP550_SE_CONTROL);
> > malidp_hw_clearbits(hwdev, MALIDP_SCALE_ENGINE_EN, base + MALIDP_DE_DISPLAY_FUNC);
>
> We now know that this patch is broken, because it disables interrupts
> for the writeback after a previous commit has enabled them but before
> the writeback engine has finished writing, so the better place for
> enabling and disabling the SE IRQs is in the malidp_pm_{suspend,resume}
> functions, not here.
>
Sorry, I missed this issue. I will send an updated v3 patch for this
only.
Thanks,
Ayan Kumar Halder
> Only for this patch: NACK.
>
> Best regards,
> Liviu
>
> > --
> > 2.7.4
> >
>
> --
> ====================
> | I would like to |
> | fix the world, |
> | but they're not |
> | giving me the |
> \ source code! /
> ---------------
> ??\_(???)_/??
next prev parent reply other threads:[~2018-04-24 10:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 14:50 [PATCH v2 0/8] drm/arm/malidp: Enhance support for system and runtime power management on malidp Ayan Kumar Halder
2018-04-23 14:50 ` Ayan Kumar Halder
2018-04-23 14:50 ` [PATCH v2 1/8] drm/arm/malidp: Modified the prototype of malidp_de_irq_fini Ayan Kumar Halder
2018-04-23 14:50 ` Ayan Kumar Halder
2018-04-23 14:50 ` [PATCH v2 2/8] drm/arm/malidp: Modified the prototype of malidp_se_irq_fini Ayan Kumar Halder
2018-04-23 14:50 ` Ayan Kumar Halder
2018-04-23 14:50 ` [PATCH v2 3/8] drm/arm/malidp: Split malidp_de_irq_init Ayan Kumar Halder
2018-04-23 14:50 ` Ayan Kumar Halder
2018-04-23 14:50 ` [PATCH v2 4/8] drm/arm/malidp: Split malidp_se_irq_init Ayan Kumar Halder
2018-04-23 14:50 ` [PATCH v2 5/8] drm/arm/malidp: Enable/disable interrupts in runtime pm Ayan Kumar Halder
2018-04-23 14:50 ` Ayan Kumar Halder
2018-04-23 14:50 ` [PATCH v2 6/8] drm/arm/malidp: Enable/disable the scaling engine interrupts with memory writeback Ayan Kumar Halder
2018-04-23 14:50 ` Ayan Kumar Halder
2018-04-23 15:36 ` Liviu Dudau
2018-04-24 10:11 ` Ayan Halder [this message]
2018-04-24 10:11 ` Ayan Halder
2018-04-23 14:50 ` [PATCH v2 7/8] drm/arm/malidp: Set the output_depth register in modeset Ayan Kumar Halder
2018-04-23 14:50 ` Ayan Kumar Halder
2018-04-23 14:50 ` [PATCH v2 8/8] drm/arm/malidp: Added the late system pm functions Ayan Kumar Halder
2018-04-23 14:50 ` Ayan Kumar Halder
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=20180424101156.GA17307@arm.com \
--to=ayan.halder@arm.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=malidp@foss.arm.com \
--cc=nd@arm.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 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.