From: Matthias Brugger <mbrugger@suse.com>
To: Stuart Yoder <stuart.yoder@nxp.com>,
"German.Rivera@freescale.com" <German.Rivera@freescale.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Scott Wood <scott.wood@nxp.com>, "agraf@suse.de" <agraf@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH] staging: fsl-mc: bus: Drop warning
Date: Fri, 15 Apr 2016 12:43:31 +0200 [thread overview]
Message-ID: <5710C5D3.1040700@suse.com> (raw)
In-Reply-To: <HE1PR04MB16417F7234DB62E73DF9EA168D970@HE1PR04MB1641.eurprd04.prod.outlook.com>
On 15/04/16 00:57, Stuart Yoder wrote:
>
>
>> -----Original Message-----
>> From: Matthias Brugger [mailto:mbrugger@suse.com]
>> Sent: Thursday, April 14, 2016 4:24 PM
>> To: German.Rivera@freescale.com; gregkh@linuxfoundation.org
>> Cc: Stuart Yoder <stuart.yoder@nxp.com>; Scott Wood <scott.wood@nxp.com>; agraf@suse.de; linux-
>> kernel@vger.kernel.org; devel@driverdev.osuosl.org; mbrugger@suse.com
>> Subject: [PATCH] staging: fsl-mc: bus: Drop warning
>>
>> When updating the irq_chip and msi_domain_ops, the code checkes for
>> already present functions.
>> When more then one ITS controller are present in the system,
>> irq_chip and msi_domain_ops got already set and a warning is invoked.
>
> How can this situation happen? And what do you mean by
> multiple ITS controllers? ...multiple instances of the GIC ITS
> on an SoC?
>
Yes, there are two arm,gic-v3-its defined in the FDT.
~ # ll /proc/device-tree/interrupt-controller@8010\,00000000/
total 0
-r--r--r-- 1 root root 4 Apr 15 12:31 #address-cells
-r--r--r-- 1 root root 11 Apr 15 12:31 compatible
drwxr-xr-x 2 root root 0 Apr 15 12:31 gic-its@8010,00020000
drwxr-xr-x 2 root root 0 Apr 15 12:31 gic-its@9010,00020000
-r--r--r-- 1 root root 4 Apr 15 12:31 #interrupt-cells
-r--r--r-- 1 root root 0 Apr 15 12:31 interrupt-controller
-r--r--r-- 1 root root 12 Apr 15 12:31 interrupts
-r--r--r-- 1 root root 4 Apr 15 12:31 linux,phandle
-r--r--r-- 1 root root 21 Apr 15 12:31 name
-r--r--r-- 1 root root 4 Apr 15 12:31 phandle
-r--r--r-- 1 root root 0 Apr 15 12:31 ranges
-r--r--r-- 1 root root 4 Apr 15 12:31 #redistributor-regions
-r--r--r-- 1 root root 48 Apr 15 12:31 reg
-r--r--r-- 1 root root 4 Apr 15 12:31 #size-cells
Regards,
Matthias
prev parent reply other threads:[~2016-04-15 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 21:24 [PATCH] staging: fsl-mc: bus: Drop warning Matthias Brugger
2016-04-14 22:57 ` Stuart Yoder
2016-04-15 10:43 ` Matthias Brugger [this message]
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=5710C5D3.1040700@suse.com \
--to=mbrugger@suse.com \
--cc=German.Rivera@freescale.com \
--cc=agraf@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.wood@nxp.com \
--cc=stuart.yoder@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.