From: Pintu Agarwal <pintu.ping@gmail.com>
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: open list <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
Russell King - ARM Linux <linux@armlinux.org.uk>,
linux-mm@kvack.org, linux-pm@vger.kernel.org,
kernelnewbies@kernelnewbies.org
Subject: Re: Need help: how to locate failure from irq_chip subsystem
Date: Fri, 18 Jan 2019 16:50:10 +0530 [thread overview]
Message-ID: <CAOuPNLjjd67FnjaHbJj_auD-EWnbc+6sc+hcT_HE6fjeKhEQrw@mail.gmail.com> (raw)
Message-ID: <20190118112010._XUtl6ochgSJuztADmEnVnlr5sbl-F4jY5UCa-rmN2I@z> (raw)
In-Reply-To: <57ff3437-47b5-fe92-d576-084ce26aa5d8@codeaurora.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.
next prev parent reply other threads:[~2019-01-18 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 10:08 Pintu Agarwal
2019-01-18 10:24 ` Sai Prakash Ranjan
2019-01-18 10:48 ` Pintu Agarwal
2019-01-18 10:48 ` Pintu Agarwal
2019-01-18 11:03 ` Sai Prakash Ranjan
2019-01-18 11:20 ` Pintu Agarwal [this message]
2019-01-18 11:20 ` Pintu Agarwal
2019-01-18 11:53 ` Sai Prakash Ranjan
2019-01-21 12:35 ` Pintu Agarwal
2019-01-21 12:35 ` Pintu Agarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOuPNLjjd67FnjaHbJj_auD-EWnbc+6sc+hcT_HE6fjeKhEQrw@mail.gmail.com \
--to=pintu.ping@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=saiprakash.ranjan@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox