linux-kernel - Re: interrupt handler not getting called after resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAOuPNLicwavzWQZAqzyLdc12Rb=yo49QxrRM3Zr0KOGrhCtJpg@mail.gmail.com>
Date:   Mon, 30 Dec 2019 19:20:34 +0530
From:   Pintu Agarwal <pintu.ping@...il.com>
To:     anish singh <anish198519851985@...il.com>
Cc:     Kernelnewbies <kernelnewbies@...nelnewbies.org>,
        linux-pm@...r.kernel.org, open list <linux-kernel@...r.kernel.org>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: interrupt handler not getting called after resume

Dear Anish,

On Thu, 5 Dec 2019 at 00:55, anish singh <anish198519851985@...il.com> wrote:
>
> On Wed, Dec 4, 2019 at 1:49 AM Pintu Agarwal <pintu.ping@...il.com> wrote:
> >
> > On Wed, 4 Dec 2019 at 00:28, anish singh <anish198519851985@...il.com> wrote:
> > >
> > > On Tue, Dec 3, 2019 at 6:12 AM Pintu Agarwal <pintu.ping@...il.com> wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I have one general query.
> > > >
> > > > If an interrupt handler is NOT getting called (for one device) after
> > > > the system resume (from snapshot image), then what could be the issue?
> > >
> > > Most likely during resume the interrupt was not enabled. So check
> > > irq status registers to see in the working and non working case.
> > >
> > Oh sorry, I forgot to mention one thing.
> > After resume, I can see that the interrupts are visible under /proc/interrupts.
> > # cat /proc/interrupts
> >            CPU0       CPU1
> > [...]
> > 416:          1          0       IPU  (null)
> > 417:          0          0       IPU  (null)
> > 418:          0          0       IPU  imx_drm  ===> HDMI
> > 419:       2242       2       IPU  imx_drm   ===> LCD
> > [...]
> >
> > The interrupts are coming only for LCD display and thus its irq
> > handler is getting called.
> > But the interrupts are not coming for HDMI case, thus HDMI gives
> > "vblank timeout issue".

Just wanted to update you that I have resolved the "vblank timeout
issue" for HDMI (by restoring clock data during resume path).
Now the ipu-v3 interrupts are coming even for HDMI crtc.

But HDMI display is still not working. May be this is another issue.

Anyways, thank you so much for your support :)


Regards,
Pintu