Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
* interrupt handler not getting called after resume
@ 2019-12-03 14:10 Pintu Agarwal
  2019-12-03 18:58 ` anish singh
  0 siblings, 1 reply; 5+ messages in thread
From: Pintu Agarwal @ 2019-12-03 14:10 UTC (permalink / raw)
  To: Kernelnewbies, linux-pm, open list,
	moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE

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?
Note:
* The suspend worked perfectly fine.
* The runtime suspend/resume of the system is also working fine.

If anybody have experienced this situation and fixed it, please let us know.
It will be a great input for further debugging.

Regards,
Pintu

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: interrupt handler not getting called after resume
  2019-12-03 14:10 interrupt handler not getting called after resume Pintu Agarwal
@ 2019-12-03 18:58 ` anish singh
  2019-12-04  9:49   ` Pintu Agarwal
  0 siblings, 1 reply; 5+ messages in thread
From: anish singh @ 2019-12-03 18:58 UTC (permalink / raw)
  To: Pintu Agarwal
  Cc: linux-pm, open list,
	moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE,
	Kernelnewbies

On Tue, Dec 3, 2019 at 6:12 AM Pintu Agarwal <pintu.ping@gmail.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.

> Note:
> * The suspend worked perfectly fine.
> * The runtime suspend/resume of the system is also working fine.
>
> If anybody have experienced this situation and fixed it, please let us know.
> It will be a great input for further debugging.

Need more context.
>
> Regards,
> Pintu
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: interrupt handler not getting called after resume
  2019-12-03 18:58 ` anish singh
@ 2019-12-04  9:49   ` Pintu Agarwal
  2019-12-04 19:25     ` anish singh
  0 siblings, 1 reply; 5+ messages in thread
From: Pintu Agarwal @ 2019-12-04  9:49 UTC (permalink / raw)
  To: anish singh
  Cc: linux-pm, open list,
	moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE,
	Kernelnewbies

On Wed, 4 Dec 2019 at 00:28, anish singh <anish198519851985@gmail.com> wrote:
>
> On Tue, Dec 3, 2019 at 6:12 AM Pintu Agarwal <pintu.ping@gmail.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".
Apart from this I also tried calling enable_irq(irq) after resume, but
it did not help much.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: interrupt handler not getting called after resume
  2019-12-04  9:49   ` Pintu Agarwal
@ 2019-12-04 19:25     ` anish singh
  0 siblings, 0 replies; 5+ messages in thread
From: anish singh @ 2019-12-04 19:25 UTC (permalink / raw)
  To: Pintu Agarwal
  Cc: linux-pm, open list,
	moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE,
	Kernelnewbies

On Wed, Dec 4, 2019 at 1:49 AM Pintu Agarwal <pintu.ping@gmail.com> wrote:
>
> On Wed, 4 Dec 2019 at 00:28, anish singh <anish198519851985@gmail.com> wrote:
> >
> > On Tue, Dec 3, 2019 at 6:12 AM Pintu Agarwal <pintu.ping@gmail.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".

Is it something to do with MHL cable? Have you used scope
to find out if the interrupt was actually triggered?

> Apart from this I also tried calling enable_irq(irq) after resume, but
> it did not help much.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 5+ messages in thread

* interrupt handler not getting called after resume
@ 2019-12-03 13:23 Pintu Agarwal
  0 siblings, 0 replies; 5+ messages in thread
From: Pintu Agarwal @ 2019-12-03 13:23 UTC (permalink / raw)
  To: Kernelnewbies, open list, linux-pm,
	moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE

[-- Attachment #1.1: Type: text/plain, Size: 426 bytes --]

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?
Note:
* The suspend worked perfectly fine.
* The runtime suspend/resume of the system is also working fine.

If anybody have experienced this situation and fixed it, please let us know.
It will be a great input for further debugging.

Regards,
Pintu

[-- Attachment #1.2: Type: text/html, Size: 1459 bytes --]

<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Hi All,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I have one general query.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">If an interrupt handler is NOT getting called (for one device) after the system resume (from snapshot image), then what could be the issue?</div><div class="gmail_default" style="font-family:verdana,sans-serif">Note:</div><div class="gmail_default" style="font-family:verdana,sans-serif">* The suspend worked perfectly fine.</div><div class="gmail_default" style="font-family:verdana,sans-serif">* The runtime suspend/resume of the system is also working fine.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">If anybody have experienced this situation and fixed it, please let us know.</div><div class="gmail_default" style="font-family:verdana,sans-serif">It will be a great input for further debugging.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Regards,</div><div class="gmail_default" style="font-family:verdana,sans-serif">Pintu</div></div>

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, back to index

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-03 14:10 interrupt handler not getting called after resume Pintu Agarwal
2019-12-03 18:58 ` anish singh
2019-12-04  9:49   ` Pintu Agarwal
2019-12-04 19:25     ` anish singh
  -- strict thread matches above, loose matches on Subject: below --
2019-12-03 13:23 Pintu Agarwal

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git