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_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,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 4DA41C432C0 for ; Tue, 3 Dec 2019 13:24:06 +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 DBEF82073B for ; Tue, 3 Dec 2019 13:24:05 +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="YtKJCANx" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DBEF82073B 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 1ic89X-0007nT-UR; Tue, 03 Dec 2019 08:23:43 -0500 Received: from mail-pl1-x633.google.com ([2607:f8b0:4864:20::633]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1ic89U-0007nM-N7 for kernelnewbies@kernelnewbies.org; Tue, 03 Dec 2019 08:23:41 -0500 Received: by mail-pl1-x633.google.com with SMTP id o8so1704370pls.5 for ; Tue, 03 Dec 2019 05:23:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=uw9v7L+LTUH3xdVHtzbGSUkvKE0WgT0tulgHPeRku6g=; b=YtKJCANxYNzaK3SU6fdL54J3MP+zjS9edJNMUqD7MyE6kSbiE8iQZWY5cb9VClBAgJ LErz1lIG9vJlzjj8xAECyLIqxiYwzdoqv3Y/Q3OYJ/I2Kzo08/p/iFTBDWJqODZL4heD JhOq8FoewgipmM5vuHA2ync6mQvPgpy14De4HGFEPlkJF208TAKdMPM1oJw0JASAgorW LNLdrAy5YMxI4ChL8sUAUtkUlka8nJD7G0OnWc29sQJ7bwroxMfc3qYozlpkuCeT8TYt pe6cV99rXi2htAqHmb8r0Bt4iOmHysYL6aGkoHusIIPYz4V1zfFeHOBNCSK4H4ZP99Hg Xc4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=uw9v7L+LTUH3xdVHtzbGSUkvKE0WgT0tulgHPeRku6g=; b=NHsOrE0Y7Ewrqu8OiMCXMbRipFtGZq3AdItC3VCa/dBMGs61/riMdpl4Z8aP9tcyak OIyoG53Ny0cv5VUAALvyl4tgw0c6P1Mr2axJ1gebx10ZRSRjLAQZZjwOXUnRkeu/vqgV G5IjIuo1/ztKO/fj4j03Z3L7aorxoE8mYXYl9mMyB36MXynzH/4+Ej2eTYyXCxjRTnXC zBt3ZK138hSudVr23Vp23VV4zvWcTMH4V3Oup0/UCO+CCnnPqnlT3HLSPWqn57UsxpJP vdczSnDe7GoxU1faG+IRDrdokzv56jGDmN+KJO+spyjdcMgtuYHVnDX9IeWPXXs7SIb6 EKoA== X-Gm-Message-State: APjAAAWOiR6L4RXthdSl48GJGuR/q2EZdXhHPWwX1Uk5yAWKebSS48dY 6UZavzX6RO6eTrFYAjBxqe6ZsVKiQkTkgsYrSe7PrlsL X-Google-Smtp-Source: APXvYqym8HC6dM5/+4wCaT6HSDyBfuU/vFvkAW91ZlvVbMc1p7rndJE+QMKNgtXf6N+/tdMXeDySDYkspPCDYew4vxg= X-Received: by 2002:a67:ea47:: with SMTP id r7mr2739857vso.106.1575379417107; Tue, 03 Dec 2019 05:23:37 -0800 (PST) MIME-Version: 1.0 From: Pintu Agarwal Date: Tue, 3 Dec 2019 18:53:26 +0530 Message-ID: Subject: interrupt handler not getting called after resume To: Kernelnewbies , open list , linux-pm@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 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: multipart/mixed; boundary="===============1959517495552419462==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============1959517495552419462== Content-Type: multipart/alternative; boundary="0000000000008b121c0598cc9aca" --0000000000008b121c0598cc9aca Content-Type: text/plain; charset="UTF-8" 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 --0000000000008b121c0598cc9aca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

I have one general query.

If an interrupt han= dler is NOT getting called (for one device) after the system resume (from s= napshot image), then what could be the issue?
Note:
* The suspend worked pe= rfectly fine.
* The runtime suspend/resume of the system is also working fi= ne.

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

Regards,
P= intu
--0000000000008b121c0598cc9aca-- --===============1959517495552419462== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============1959517495552419462==--