From: Jason Cooper <jason@lakedaemon.net>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Stefan Agner <stefan@agner.ch>,
tglx@linutronix.de, mark.rutland@arm.com, marc.zyngier@arm.com,
u.kleine-koenig@pengutronix.de, kernel@pengutronix.de,
arnd@arndb.de, robh+dt@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
pebolle@tiscali.nl, linux@arm.linux.org.uk,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 3/3] ARM: dts: vf610: add Miscellaneous System Control Module (MSCM)
Date: Wed, 11 Mar 2015 04:05:39 +0000 [thread overview]
Message-ID: <20150311040539.GD21998@io.lakedaemon.net> (raw)
In-Reply-To: <20150311004812.GU20455@dragon>
On Wed, Mar 11, 2015 at 08:48:15AM +0800, Shawn Guo wrote:
> On Sun, Mar 01, 2015 at 11:41:29PM +0100, Stefan Agner wrote:
> > Add the Miscellaneous System Control Module (MSCM) to the base
> > device tree for Vybrid SoC's. This module contains registers
> > to get information of the individual and current (accessing)
> > CPU. In a second block, there is an interrupt router, which
> > handles the routing of the interrupts between the two CPU cores
> > on VF6xx variants of the SoC. However, also on single core
> > variants the interrupt router needs to be configured in order
> > to receive interrupts on the CPU's interrupt controller. Almost
> > all peripheral interrupts are routed through the router, hence
> > the MSCM module is the default interrupt parent for this SoC.
> >
> > In a earlier commit the interrupt nodes were moved out of the
> > peripheral nodes and specified in the CPU specific vf500.dtsi
> > device tree. This allowed to use the base device tree vfxxx.dtsi
> > also for a Cortex-M4 specific device tree, which uses different
> > interrupt nodes due to the NVIC interrupt controller. However,
> > since the interrupt parent for peripherals is the MSCM module
> > independently which CPU the device tree is used for, we can move
> > the interrupt nodes into the base device tree vfxxx.dtsi again.
> > Depending on which CPU this base device tree will be used with,
> > the correct parent interrupt controller has to be assigned to
> > the MSCM-IR node (GIC or NVIC). The driver takes care of the
> > parent interrupt controller specific needs (interrupt-cells).
> >
> > Acked-by: Marc Zyngier <marc.zyngier@arm.com>
> > Signed-off-by: Stefan Agner <stefan@agner.ch>
>
> Stefan,
>
> I guess this patch has a run-time dependency on the first two in the
> series, right? Or put it another way, if I apply this single patch on
> my branch, the dtb and kernel built from the same branch do not work
> together, right? If so, we will need to either wait for the first two
> hit mainline or pull Jason's irqchip/vybrid branch into my tree as
> prerequisite (irqchip/vybrid needs to be stable).
No problem, I'll only add patches on top of this if needed. no rebasing.
thx,
Jason.
WARNING: multiple messages have this Message-ID (diff)
From: Jason Cooper <jason@lakedaemon.net>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
pebolle@tiscali.nl, linux@arm.linux.org.uk, pawel.moll@arm.com,
arnd@arndb.de, ijc+devicetree@hellion.org.uk,
marc.zyngier@arm.com, galak@codeaurora.org,
linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>,
robh+dt@kernel.org, kernel@pengutronix.de,
u.kleine-koenig@pengutronix.de, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 3/3] ARM: dts: vf610: add Miscellaneous System Control Module (MSCM)
Date: Wed, 11 Mar 2015 04:05:39 +0000 [thread overview]
Message-ID: <20150311040539.GD21998@io.lakedaemon.net> (raw)
In-Reply-To: <20150311004812.GU20455@dragon>
On Wed, Mar 11, 2015 at 08:48:15AM +0800, Shawn Guo wrote:
> On Sun, Mar 01, 2015 at 11:41:29PM +0100, Stefan Agner wrote:
> > Add the Miscellaneous System Control Module (MSCM) to the base
> > device tree for Vybrid SoC's. This module contains registers
> > to get information of the individual and current (accessing)
> > CPU. In a second block, there is an interrupt router, which
> > handles the routing of the interrupts between the two CPU cores
> > on VF6xx variants of the SoC. However, also on single core
> > variants the interrupt router needs to be configured in order
> > to receive interrupts on the CPU's interrupt controller. Almost
> > all peripheral interrupts are routed through the router, hence
> > the MSCM module is the default interrupt parent for this SoC.
> >
> > In a earlier commit the interrupt nodes were moved out of the
> > peripheral nodes and specified in the CPU specific vf500.dtsi
> > device tree. This allowed to use the base device tree vfxxx.dtsi
> > also for a Cortex-M4 specific device tree, which uses different
> > interrupt nodes due to the NVIC interrupt controller. However,
> > since the interrupt parent for peripherals is the MSCM module
> > independently which CPU the device tree is used for, we can move
> > the interrupt nodes into the base device tree vfxxx.dtsi again.
> > Depending on which CPU this base device tree will be used with,
> > the correct parent interrupt controller has to be assigned to
> > the MSCM-IR node (GIC or NVIC). The driver takes care of the
> > parent interrupt controller specific needs (interrupt-cells).
> >
> > Acked-by: Marc Zyngier <marc.zyngier@arm.com>
> > Signed-off-by: Stefan Agner <stefan@agner.ch>
>
> Stefan,
>
> I guess this patch has a run-time dependency on the first two in the
> series, right? Or put it another way, if I apply this single patch on
> my branch, the dtb and kernel built from the same branch do not work
> together, right? If so, we will need to either wait for the first two
> hit mainline or pull Jason's irqchip/vybrid branch into my tree as
> prerequisite (irqchip/vybrid needs to be stable).
No problem, I'll only add patches on top of this if needed. no rebasing.
thx,
Jason.
WARNING: multiple messages have this Message-ID (diff)
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/3] ARM: dts: vf610: add Miscellaneous System Control Module (MSCM)
Date: Wed, 11 Mar 2015 04:05:39 +0000 [thread overview]
Message-ID: <20150311040539.GD21998@io.lakedaemon.net> (raw)
In-Reply-To: <20150311004812.GU20455@dragon>
On Wed, Mar 11, 2015 at 08:48:15AM +0800, Shawn Guo wrote:
> On Sun, Mar 01, 2015 at 11:41:29PM +0100, Stefan Agner wrote:
> > Add the Miscellaneous System Control Module (MSCM) to the base
> > device tree for Vybrid SoC's. This module contains registers
> > to get information of the individual and current (accessing)
> > CPU. In a second block, there is an interrupt router, which
> > handles the routing of the interrupts between the two CPU cores
> > on VF6xx variants of the SoC. However, also on single core
> > variants the interrupt router needs to be configured in order
> > to receive interrupts on the CPU's interrupt controller. Almost
> > all peripheral interrupts are routed through the router, hence
> > the MSCM module is the default interrupt parent for this SoC.
> >
> > In a earlier commit the interrupt nodes were moved out of the
> > peripheral nodes and specified in the CPU specific vf500.dtsi
> > device tree. This allowed to use the base device tree vfxxx.dtsi
> > also for a Cortex-M4 specific device tree, which uses different
> > interrupt nodes due to the NVIC interrupt controller. However,
> > since the interrupt parent for peripherals is the MSCM module
> > independently which CPU the device tree is used for, we can move
> > the interrupt nodes into the base device tree vfxxx.dtsi again.
> > Depending on which CPU this base device tree will be used with,
> > the correct parent interrupt controller has to be assigned to
> > the MSCM-IR node (GIC or NVIC). The driver takes care of the
> > parent interrupt controller specific needs (interrupt-cells).
> >
> > Acked-by: Marc Zyngier <marc.zyngier@arm.com>
> > Signed-off-by: Stefan Agner <stefan@agner.ch>
>
> Stefan,
>
> I guess this patch has a run-time dependency on the first two in the
> series, right? Or put it another way, if I apply this single patch on
> my branch, the dtb and kernel built from the same branch do not work
> together, right? If so, we will need to either wait for the first two
> hit mainline or pull Jason's irqchip/vybrid branch into my tree as
> prerequisite (irqchip/vybrid needs to be stable).
No problem, I'll only add patches on top of this if needed. no rebasing.
thx,
Jason.
next prev parent reply other threads:[~2015-03-11 5:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 22:41 [PATCH v6 0/3] irqchip: vf610-mscm: add MSCM interrupt router driver Stefan Agner
2015-03-01 22:41 ` Stefan Agner
2015-03-01 22:41 ` [PATCH v6 1/3] irqchip: vf610-mscm-ir: add support for MSCM interrupt router Stefan Agner
2015-03-01 22:41 ` Stefan Agner
2015-03-01 22:41 ` Stefan Agner
2015-03-01 22:41 ` [PATCH v6 2/3] irqchip: vf610-mscm: dt-bindings: add MSCM bindings Stefan Agner
2015-03-01 22:41 ` Stefan Agner
2015-03-01 22:41 ` [PATCH v6 3/3] ARM: dts: vf610: add Miscellaneous System Control Module (MSCM) Stefan Agner
2015-03-01 22:41 ` Stefan Agner
2015-03-01 22:41 ` Stefan Agner
2015-03-11 0:48 ` Shawn Guo
2015-03-11 0:48 ` Shawn Guo
2015-03-11 4:05 ` Jason Cooper [this message]
2015-03-11 4:05 ` Jason Cooper
2015-03-11 4:05 ` Jason Cooper
2015-03-12 9:03 ` Stefan Agner
2015-03-12 9:03 ` Stefan Agner
2015-03-13 4:48 ` Shawn Guo
2015-03-13 4:48 ` Shawn Guo
2015-03-13 4:48 ` Shawn Guo
2015-03-13 9:42 ` Stefan Agner
2015-03-13 9:42 ` Stefan Agner
2015-03-08 5:31 ` [PATCH v6 0/3] irqchip: vf610-mscm: add MSCM interrupt router driver Jason Cooper
2015-03-08 5:31 ` Jason Cooper
2015-03-08 5:31 ` Jason Cooper
2015-03-08 23:43 ` Stefan Agner
2015-03-08 23:43 ` Stefan Agner
2015-03-09 1:22 ` Jason Cooper
2015-03-09 1:22 ` Jason Cooper
2015-03-09 1:22 ` Jason Cooper
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=20150311040539.GD21998@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=pebolle@tiscali.nl \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stefan@agner.ch \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@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.