From: Shawn Guo <shawnguo@kernel.org>
To: Jacky Bai <ping.bai@nxp.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>
Subject: Re: [PATCH v2 1/3] arm64: dts: imx: Add i.mx8mm dtsi support
Date: Fri, 22 Mar 2019 10:13:32 +0800 [thread overview]
Message-ID: <20190322021331.GX12513@dragon> (raw)
In-Reply-To: <VI1PR0402MB351954C0C30D3AD28C77A77187430@VI1PR0402MB3519.eurprd04.prod.outlook.com>
On Fri, Mar 22, 2019 at 01:55:45AM +0000, Jacky Bai wrote:
> > > + gpc: gpc@303a0000 {
> >
> > interrupt-controller for node name?
> >
>
> For the i.MX8MM and future i.MX8M serious, it is not very necessary to use GPC as a interrupt controller
> in linux kernel side. For system suspend, ATF can config the GPC IMRs based on IRQ enable status in GICv3.
> For cpuidle support, GICv3 has per-CPU core wakeup signals connected to the GPC logic, so GICv3 has the ability
> to wake up the corresponding CPU core if the IRQ is routed to that CPU core. Additionally, I am thinking to
> config the GPC as a secure resource in the future.
>
> Maybe, we can remove the GPC node for now. If necessary, we can add it back again?
Sounds good to me.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Jacky Bai <ping.bai@nxp.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>
Subject: Re: [PATCH v2 1/3] arm64: dts: imx: Add i.mx8mm dtsi support
Date: Fri, 22 Mar 2019 10:13:32 +0800 [thread overview]
Message-ID: <20190322021331.GX12513@dragon> (raw)
In-Reply-To: <VI1PR0402MB351954C0C30D3AD28C77A77187430@VI1PR0402MB3519.eurprd04.prod.outlook.com>
On Fri, Mar 22, 2019 at 01:55:45AM +0000, Jacky Bai wrote:
> > > + gpc: gpc@303a0000 {
> >
> > interrupt-controller for node name?
> >
>
> For the i.MX8MM and future i.MX8M serious, it is not very necessary to use GPC as a interrupt controller
> in linux kernel side. For system suspend, ATF can config the GPC IMRs based on IRQ enable status in GICv3.
> For cpuidle support, GICv3 has per-CPU core wakeup signals connected to the GPC logic, so GICv3 has the ability
> to wake up the corresponding CPU core if the IRQ is routed to that CPU core. Additionally, I am thinking to
> config the GPC as a secure resource in the future.
>
> Maybe, we can remove the GPC node for now. If necessary, we can add it back again?
Sounds good to me.
Shawn
next prev parent reply other threads:[~2019-03-22 2:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 5:44 [PATCH v2 1/3] arm64: dts: imx: Add i.mx8mm dtsi support Jacky Bai
2019-03-12 5:44 ` Jacky Bai
2019-03-12 5:44 ` [PATCH v2 2/3] dt-bindings: arm: imx: Add the soc binding for imx8mm Jacky Bai
2019-03-12 5:44 ` Jacky Bai
2019-03-12 12:06 ` Rob Herring
2019-03-12 12:06 ` Rob Herring
2019-03-12 5:45 ` [PATCH v2 3/3] arm64: dts: imx: Add i.mx8mm evk basic dts support Jacky Bai
2019-03-12 5:45 ` Jacky Bai
2019-03-21 8:44 ` Shawn Guo
2019-03-21 8:44 ` Shawn Guo
2019-03-22 2:10 ` Jacky Bai
2019-03-22 2:10 ` Jacky Bai
2019-03-22 5:53 ` Jacky Bai
2019-03-22 5:53 ` Jacky Bai
2019-03-22 7:49 ` Shawn Guo
2019-03-22 7:49 ` Shawn Guo
2019-03-21 8:22 ` [PATCH v2 1/3] arm64: dts: imx: Add i.mx8mm dtsi support Shawn Guo
2019-03-21 8:22 ` Shawn Guo
2019-03-22 1:55 ` Jacky Bai
2019-03-22 1:55 ` Jacky Bai
2019-03-22 2:13 ` Shawn Guo [this message]
2019-03-22 2:13 ` Shawn Guo
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=20190322021331.GX12513@dragon \
--to=shawnguo@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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.