From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,FROM_LOCAL_DIGITS, FROM_LOCAL_HEX,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A0FDCC43603 for ; Wed, 4 Dec 2019 19:25:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 711A22077B for ; Wed, 4 Dec 2019 19:25:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="tavjmU/Q" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729300AbfLDTZi (ORCPT ); Wed, 4 Dec 2019 14:25:38 -0500 Received: from mail-oi1-f172.google.com ([209.85.167.172]:42983 "EHLO mail-oi1-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728598AbfLDTZf (ORCPT ); Wed, 4 Dec 2019 14:25:35 -0500 Received: by mail-oi1-f172.google.com with SMTP id j22so307100oij.9; Wed, 04 Dec 2019 11:25:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pFUOvAm3fm348kgwrvmev1YNw19TgoAC7QPtF9q0W9g=; b=tavjmU/Q3DfvERF7bhd3q/fapLDjBaceWr0h20GkAqynBwFQMUwfUlK4JhVKg6DNba YcTrdtYwr9rzEBR4ioJALzSV7YV3HPPFYHcud6qn6L+QOAR5ZZWOyyXYIc+k/MqSde7Q KfnTP5KxI5P4mbTDuXUJp8Qyp6pBDieNXRGyaw6F2q4sBWmws/FiBMXMsX82JHHH7Ri2 zda5XYPi19vtq2GGB512vz3f72AXQfAZO7gQo89mrt/EjTshdpJ7t2GNV6x3qATQYnSo e5CFH7FHMs+hgaDF/YiW2ZIpHhfzssyZNkz+XapRCUModCWBJN82m2lpiTFd5a6Q+IoE wDRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pFUOvAm3fm348kgwrvmev1YNw19TgoAC7QPtF9q0W9g=; b=SJVX5HZYLhIkVgczuwf0obe7Fuc4Yzo2RlatqXA7mSkje2WmWP51Y/wDo/kD66nrYW UChWeqXmZQfQhKiENiYsyrSDLCi85zHRbSUVLLtLFITZ2xmSiNOcigAxuSoD4PKzgznk Y2xk7K8p2i0OSeGwzxS3Z1zRxZQPbH15Yew8SLnN0qAeF0JPceKnjdB64QBgyS0OFTQc xugaslIa6W7bISqPGcaJBNjORdDKjjVCLGFbJ+ikSr/WXoK/b8QiAC1V3hoXGBrvngm2 lBXAsC+E6Kirnk+FX1N6qVerzPODku4Bvdnit1CjEWtN55gvcmmiGgmmyDwcIywiE0pT SVOw== X-Gm-Message-State: APjAAAXUNojqU+Qtz7n3GpxOUsUdQ6hVQag7DJ728FlSwJlP6cv485gp QhqUm0nsQL3dvLGLPj43KaeIdCBku6+sVEirlWW4KkpL X-Google-Smtp-Source: APXvYqygeXnEPPwtKFRW0Y36WS+lxc9iXT3BUpe6OWDmYYx7OmzTFEQc+TYv16vi+70aFchYa1GmHEKib44SVaBMTL0= X-Received: by 2002:aca:c3c6:: with SMTP id t189mr4090470oif.98.1575487535056; Wed, 04 Dec 2019 11:25:35 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: anish singh Date: Wed, 4 Dec 2019 11:25:23 -0800 Message-ID: Subject: Re: interrupt handler not getting called after resume To: Pintu Agarwal Cc: Kernelnewbies , linux-pm@vger.kernel.org, open list , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 4, 2019 at 1:49 AM Pintu Agarwal wrote: > > On Wed, 4 Dec 2019 at 00:28, anish singh wrote: > > > > On Tue, Dec 3, 2019 at 6:12 AM Pintu Agarwal 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.2 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, FROM_LOCAL_DIGITS,FROM_LOCAL_HEX,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84560C43603 for ; Wed, 4 Dec 2019 19:25:48 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 570772077B for ; Wed, 4 Dec 2019 19:25:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="IPP9YPhW"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="tavjmU/Q" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 570772077B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=NbquXVYEa5SWh486MMTyQjZos+uoUZiOuc+HYPTAD2A=; b=IPP9YPhWU47u6r ckrLocI8y0munkHxywHv6tMXDAcQ7rZqkZ2lB32frtxeAmH6yYryjmqwQPsuEqJoNOdY396JCQvYB DzRjOQEejqTqWLuDMTz82QvzOfwRLIcPb2Tkiy/HFzk5sMdySrGLYxaGCmb3tcNj1aYmS+GS4ED7J Dh4imbbQD5QxkJVuRMMyllTjjDbiZUaa/awve/1qsul70+bYG8irZ9ofsgJ/4BrXwj/rwkJLV0WMf wDEs+Qou6XV7b/+Zvf/1SmW3GjCCby6cWd/GLny/exKp27x1BwItGeV9EL/PEGE7AxaSWmZ+2M/s+ UC8QhFFbqvo/bDlod8NA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1icaHS-00059i-Db; Wed, 04 Dec 2019 19:25:46 +0000 Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1icaHN-00058V-Hh for linux-arm-kernel@lists.infradead.org; Wed, 04 Dec 2019 19:25:43 +0000 Received: by mail-oi1-x231.google.com with SMTP id i1so315857oie.8 for ; Wed, 04 Dec 2019 11:25:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pFUOvAm3fm348kgwrvmev1YNw19TgoAC7QPtF9q0W9g=; b=tavjmU/Q3DfvERF7bhd3q/fapLDjBaceWr0h20GkAqynBwFQMUwfUlK4JhVKg6DNba YcTrdtYwr9rzEBR4ioJALzSV7YV3HPPFYHcud6qn6L+QOAR5ZZWOyyXYIc+k/MqSde7Q KfnTP5KxI5P4mbTDuXUJp8Qyp6pBDieNXRGyaw6F2q4sBWmws/FiBMXMsX82JHHH7Ri2 zda5XYPi19vtq2GGB512vz3f72AXQfAZO7gQo89mrt/EjTshdpJ7t2GNV6x3qATQYnSo e5CFH7FHMs+hgaDF/YiW2ZIpHhfzssyZNkz+XapRCUModCWBJN82m2lpiTFd5a6Q+IoE wDRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pFUOvAm3fm348kgwrvmev1YNw19TgoAC7QPtF9q0W9g=; b=GCrFxVgOlSH3JYDtdAB58AsPu5PifyljsB/sdfyWly0sbtbK3YupCOGqM4hUapsjIg S7ikrb4G0ijcqe6ouw/EuLZFk9ZPUq7BrKi/hxj7HOBJZaFuF6M/LwXTagkBwJPD+wZm H2sVk8kOOpxMdjg6pcO59JSi1+10WAs98AC+mB7rkJAKFQfRY9DUcIW7zLKq4s8I84Es lPeuKMC1kVmemBGO88XfD7+ivRsu5IWPDmrEmW9aPJ8nSxMeVdN7O9D0sKe14Ij8rHB9 DWMKeUUQ0DrI2ad2fjvcLvt4em9Z23FFw8VbJO1D/NGQpIIhoe/XIDCfvekGGyl+/Ok6 1u+w== X-Gm-Message-State: APjAAAWbon8M4BtaMTQuHIW3K2fubPyq4eOv174aAPr06P0j9uPob7a0 smuKgEEuL8avPOXhSdPphO5P1xTCMBINLhc1GUo= X-Google-Smtp-Source: APXvYqygeXnEPPwtKFRW0Y36WS+lxc9iXT3BUpe6OWDmYYx7OmzTFEQc+TYv16vi+70aFchYa1GmHEKib44SVaBMTL0= X-Received: by 2002:aca:c3c6:: with SMTP id t189mr4090470oif.98.1575487535056; Wed, 04 Dec 2019 11:25:35 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: anish singh Date: Wed, 4 Dec 2019 11:25:23 -0800 Message-ID: Subject: Re: interrupt handler not getting called after resume To: Pintu Agarwal X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191204_112541_588145_F6964814 X-CRM114-Status: GOOD ( 13.03 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-pm@vger.kernel.org, open list , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Kernelnewbies Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Dec 4, 2019 at 1:49 AM Pintu Agarwal wrote: > > On Wed, 4 Dec 2019 at 00:28, anish singh wrote: > > > > On Tue, Dec 3, 2019 at 6:12 AM Pintu Agarwal 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. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, FROM_LOCAL_DIGITS,FROM_LOCAL_HEX,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D2806C43603 for ; Wed, 4 Dec 2019 19:26:01 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 67F1720674 for ; Wed, 4 Dec 2019 19:26:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="tavjmU/Q" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 67F1720674 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92.3) (envelope-from ) id 1icaHL-0003qB-Ci; Wed, 04 Dec 2019 14:25:39 -0500 Received: from mail-oi1-x236.google.com ([2607:f8b0:4864:20::236]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1icaHJ-0003q5-Bv for kernelnewbies@kernelnewbies.org; Wed, 04 Dec 2019 14:25:37 -0500 Received: by mail-oi1-x236.google.com with SMTP id v140so367553oie.0 for ; Wed, 04 Dec 2019 11:25:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pFUOvAm3fm348kgwrvmev1YNw19TgoAC7QPtF9q0W9g=; b=tavjmU/Q3DfvERF7bhd3q/fapLDjBaceWr0h20GkAqynBwFQMUwfUlK4JhVKg6DNba YcTrdtYwr9rzEBR4ioJALzSV7YV3HPPFYHcud6qn6L+QOAR5ZZWOyyXYIc+k/MqSde7Q KfnTP5KxI5P4mbTDuXUJp8Qyp6pBDieNXRGyaw6F2q4sBWmws/FiBMXMsX82JHHH7Ri2 zda5XYPi19vtq2GGB512vz3f72AXQfAZO7gQo89mrt/EjTshdpJ7t2GNV6x3qATQYnSo e5CFH7FHMs+hgaDF/YiW2ZIpHhfzssyZNkz+XapRCUModCWBJN82m2lpiTFd5a6Q+IoE wDRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pFUOvAm3fm348kgwrvmev1YNw19TgoAC7QPtF9q0W9g=; b=XAwWPZnJy+e64a3kyAPU3PQ6DCDNhIcveiT5groBXnQ4Cz5vDYlNdmK9M8kYRB936v qdexu8c/2Z+oBD357MxajKa2cjDcoT3hIytsgXQsBya3ClKSaGL7Rs4NbRjpqz3PYabJ gA4d9MUxPJjriVdpppZJ2roBWRp7As1nEReqimmDV7ZMR8Vz0AvsKHnkC5tenB8SBf4T A5ftivsxkhrmoCkp9eAnDA52aIRHtHZteG9uPtVkTw3pKj2BVb8nNNo2XwNe+rfEgKNe VFhvZTmlsc/PJ2gBHLpGmXG3kjMuQ6fh8D5MpIDx20EaohBh+DPA/gfOAE50S1KIUiKY Iatw== X-Gm-Message-State: APjAAAWzMfAcjFVdE0lFMuniphJQr69+h5PZLkPcbkBlxLnXe8hmRI+O SiIqp8vSHO67wVZLjzwSyN8nqGEp/dMbww534S0= X-Google-Smtp-Source: APXvYqygeXnEPPwtKFRW0Y36WS+lxc9iXT3BUpe6OWDmYYx7OmzTFEQc+TYv16vi+70aFchYa1GmHEKib44SVaBMTL0= X-Received: by 2002:aca:c3c6:: with SMTP id t189mr4090470oif.98.1575487535056; Wed, 04 Dec 2019 11:25:35 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: anish singh Date: Wed, 4 Dec 2019 11:25:23 -0800 Message-ID: Subject: Re: interrupt handler not getting called after resume To: Pintu Agarwal Cc: linux-pm@vger.kernel.org, open list , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Wed, Dec 4, 2019 at 1:49 AM Pintu Agarwal wrote: > > On Wed, 4 Dec 2019 at 00:28, anish singh wrote: > > > > On Tue, Dec 3, 2019 at 6:12 AM Pintu Agarwal 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