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.8 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_PASS,URIBL_BLOCKED autolearn=ham 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 B112FC43387 for ; Fri, 18 Jan 2019 11:23:23 +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 6A6A52086D for ; Fri, 18 Jan 2019 11:23:23 +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="D9GmmFAg" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6A6A52086D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.91) (envelope-from ) id 1gkSF7-0002i5-Vk for kernelnewbies@archiver.kernel.org; Fri, 18 Jan 2019 06:23:21 -0500 Received: from mail-ua1-x931.google.com ([2607:f8b0:4864:20::931]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1gkSDD-0000UH-D8 for kernelnewbies@kernelnewbies.org; Fri, 18 Jan 2019 06:21:23 -0500 Received: by mail-ua1-x931.google.com with SMTP id c12so4554084uas.6 for ; Fri, 18 Jan 2019 03:21:22 -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=XqF0zZgFayTmTO/6SUH1t+WrRUcv72SweIyRMBjv87g=; b=D9GmmFAgjv+5fMxCXp5xCcl/ZSn3HHWyfLbIKnqEUoQGUzpEQtnK872HuAFMporWy8 FtB1I6hgNbsI6BGQyRFD66Jk28nEWyr1cJ54576q1P1tfwswQYlPZtG2LDSNwAGI5c2c vsmRxZ4VggCqcAce4ZGUjJzE0t3BtOo6o6NUmcmENogt0PgUndm2XUv92fNkLoN8XdiF eMhKQ5bgmb3zns4sBO+V0DVEjyLzAeeJ/i1ymIl+iLgWy3i+SBuuwKlGZezyWUgbN7ay NygDllUwwt1jhMga1NQiwO733GITXacZUEs+U3vjLk9yAcGaK99uJ+qO07OWCDuVJ+r7 ksnw== 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=XqF0zZgFayTmTO/6SUH1t+WrRUcv72SweIyRMBjv87g=; b=PeHE/2U6EQsGF9rwNByuWvpTG4WJHF3sNmJjW5JsS2gXOGtue4s2U3kfVrVujcgAdn WiLRrmMQDGZJDV7pMjKeAUPDBA8bLLr9L+ndS/OOkz9whxqUfWn5x5kgIgxEvBRZmPYI z0vx2BtG2XvSwGtNJDlRAj6hMf2mXDGrkPgwhnhNB6GYyY3tbi0Ncm9FpEcVbinTvjUI HkUQFDOixtKGG5ws/6Pctpa0YeIEu8mp5iZqQCB57q5BHRI06/6MlJ6tfI2G4iCpsSrN 2YCsBXCDHzXFop5cNNfm4BS5OXslrVaolR8/oIsqO4+FD+a+IXn5JHhIl6T8ZzAXoN4U Dakg== X-Gm-Message-State: AJcUukdsp+7s17/1n5EddP3TH+iw4TzaNCZFKy2yqZSP6sKNvJ0BP+y+ 4a/1YqmZQBAxbbo0PriYzGvIL2VSsgUQpplFcPs= X-Google-Smtp-Source: ALg8bN6mxLE2fuUGoFKjllqfM6KcxqbBeCmty7KewOuDUIEDxWLGW1kJw0dz41+rI27UPKQCj1yKvjE6TfH21SValXE= X-Received: by 2002:ab0:8d9:: with SMTP id o25mr7383232uaf.127.1547810421480; Fri, 18 Jan 2019 03:20:21 -0800 (PST) MIME-Version: 1.0 References: <57ff3437-47b5-fe92-d576-084ce26aa5d8@codeaurora.org> In-Reply-To: <57ff3437-47b5-fe92-d576-084ce26aa5d8@codeaurora.org> From: Pintu Agarwal Date: Fri, 18 Jan 2019 16:50:10 +0530 Message-ID: Subject: Re: Need help: how to locate failure from irq_chip subsystem To: Sai Prakash Ranjan Cc: linux-pm@vger.kernel.org, kernelnewbies@kernelnewbies.org, open list , Russell King - ARM Linux , linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org 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=archiver.kernel.org@kernelnewbies.org > >> Could you please tell which QCOM SoC this board is based on? > >> > > > > Snapdragon 845 with kernel 4.9.x > > I want to know from which subsystem it is triggered:drivers/soc/qcom/ > > > > Irqchip driver is "drivers/irqchip/irq-gic-v3.c". The kernel you are > using is msm-4.9 I suppose or some other kernel? > Yes, I am using customized version of msm-4.9 kernel based on Android. And yes the irqchip driver is: irq-gic-v3, which I can see from config. But, what I wanted to know is, how to find out which driver module (hopefully under: /drivers/soc/qcom/) that register with this irq_chip, is getting triggered at the time of crash ? So, that I can implement irq_hold function for it, which is the cause of crash. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies