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.4 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 AD3F4C2D0C2 for ; Mon, 30 Dec 2019 13:52:31 +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 41DB520663 for ; Mon, 30 Dec 2019 13:52:29 +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="CdmuDXJV" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 41DB520663 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 1ilvSX-0004A8-6o; Mon, 30 Dec 2019 08:51:49 -0500 Received: from mail-vk1-xa2a.google.com ([2607:f8b0:4864:20::a2a]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1ilvSU-00049q-RK for kernelnewbies@kernelnewbies.org; Mon, 30 Dec 2019 08:51:46 -0500 Received: by mail-vk1-xa2a.google.com with SMTP id u6so8269251vkn.13 for ; Mon, 30 Dec 2019 05:51:46 -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=XkMGH5DQxq4vpQ2V6RpbSRMhiMiNZc/V1Nq34hSwIJk=; b=CdmuDXJVWhggBHQW+pJHb6TNOzPvoOAZ7687gifPylrQZxVlozKmptWbBXg6ZvIkZu cSqCpWBasg60LSZFxQc68XKGx9tGCTYU/1glw3qAd+j+PnScVx8y7/q7mH8JpjHAT5W9 Z/9McLaAraQ3JOb8JHt6V0DPC6dpkL0tKD7GiqySLNj0KbpcRoSq8VLLF/YFzGp4277e yuOUGCFS3HHDim9Piq8i4Ve//zYDej7JIhFASN0gjkPfAca7mPla61VF7h1NhswQaTSP Bh/xohmtzFWp2TZ40Oq/berVwITGSAmsaECxo+5Kdz28ttDCRmv2KCr0fO77F+miqcHk Vwfw== 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=XkMGH5DQxq4vpQ2V6RpbSRMhiMiNZc/V1Nq34hSwIJk=; b=PGXhu/1zshwktKgHf1NaIOmbF0uVkjqlsvQaMPlEJcWmUM3wax5cSs3wBJrQ6ErTaV E2p6DMv+EflZ56dLs1sDX2GqBugSsMoKSDN76D7um34zCui7lILhCWGsojsY68bvaxVr ME3kT8LWNmi44vXjeNJVRBObYZOpBbazlaq/BhrF5D+hZ87WY1NjVIauvObd1fWhl2nK hqJVqJyFwps+BUsV++1rsp4djv7WkrVXTnpOqlgl/rWj2OfBByxlC9XOSDN4v5RoZGFB LLNjseE0TJYSOVk9C5B5aub6czCAIC+gehuUcBb4+V8If+u6iDp0gAYRn309VRIvjOke 0Biw== X-Gm-Message-State: APjAAAUTKSrDznS5AH+v0LcUFBrs3dwsGR9buAbu3NzXsprSSLeX84mC PQ/RaLA2BFP+zSsOlBQxwuiDxCgv9pcDZSuJQ6M= X-Google-Smtp-Source: APXvYqxLXFi9J20jdLU7H/ZiNuY8RrLKbXtPjBGXHbT9hV1C1voWZ2Ea3/nczoyLc4wggA/hUuYx3UiwGsQLQlVnEL0= X-Received: by 2002:a1f:7c0c:: with SMTP id x12mr38200964vkc.41.1577713845386; Mon, 30 Dec 2019 05:50:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Pintu Agarwal Date: Mon, 30 Dec 2019 19:20:34 +0530 Message-ID: Subject: Re: interrupt handler not getting called after resume To: anish singh 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 Dear Anish, On Thu, 5 Dec 2019 at 00:55, anish singh wrote: > > 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". 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 _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies