devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jisheng Zhang <jszhang@marvell.com>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	linux@arm.linux.org.uk
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] arm: dts: berlin2q: remove duplicated interrupt-parent
Date: Thu, 19 Nov 2015 21:21:56 +0100	[thread overview]
Message-ID: <564E2F64.30709@gmail.com> (raw)
In-Reply-To: <1447670791-7874-1-git-send-email-jszhang@marvell.com>

On 16.11.2015 11:46, Jisheng Zhang wrote:
> The default interrupt-parent has been set in the upper layer, apb@e80000
> and apb@fc0000 for example. So if the interrupt-parent isn't changed, we
> don't need to set it again. This patch removes the dumplicated
> interrupt-parent settings.
> 
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>

Applied to berlin64/dt.

Thanks!

> ---
>  arch/arm/boot/dts/berlin2q.dtsi | 6 ------
>  1 file changed, 6 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/berlin2q.dtsi b/arch/arm/boot/dts/berlin2q.dtsi
> index 8ea177f..155430a 100644
> --- a/arch/arm/boot/dts/berlin2q.dtsi
> +++ b/arch/arm/boot/dts/berlin2q.dtsi
> @@ -309,7 +309,6 @@
>  				#address-cells = <1>;
>  				#size-cells = <0>;
>  				reg = <0x1400 0x100>;
> -				interrupt-parent = <&aic>;
>  				interrupts = <4>;
>  				clocks = <&chip_clk CLKID_CFG>;
>  				pinctrl-0 = <&twsi0_pmux>;
> @@ -322,7 +321,6 @@
>  				#address-cells = <1>;
>  				#size-cells = <0>;
>  				reg = <0x1800 0x100>;
> -				interrupt-parent = <&aic>;
>  				interrupts = <5>;
>  				clocks = <&chip_clk CLKID_CFG>;
>  				pinctrl-0 = <&twsi1_pmux>;
> @@ -528,7 +526,6 @@
>  				#address-cells = <1>;
>  				#size-cells = <0>;
>  				reg = <0x7000 0x100>;
> -				interrupt-parent = <&sic>;
>  				interrupts = <6>;
>  				clocks = <&refclk>;
>  				pinctrl-0 = <&twsi2_pmux>;
> @@ -541,7 +538,6 @@
>  				#address-cells = <1>;
>  				#size-cells = <0>;
>  				reg = <0x8000 0x100>;
> -				interrupt-parent = <&sic>;
>  				interrupts = <7>;
>  				clocks = <&refclk>;
>  				pinctrl-0 = <&twsi3_pmux>;
> @@ -552,7 +548,6 @@
>  			uart0: uart@9000 {
>  				compatible = "snps,dw-apb-uart";
>  				reg = <0x9000 0x100>;
> -				interrupt-parent = <&sic>;
>  				interrupts = <8>;
>  				clocks = <&refclk>;
>  				reg-shift = <2>;
> @@ -564,7 +559,6 @@
>  			uart1: uart@a000 {
>  				compatible = "snps,dw-apb-uart";
>  				reg = <0xa000 0x100>;
> -				interrupt-parent = <&sic>;
>  				interrupts = <9>;
>  				clocks = <&refclk>;
>  				reg-shift = <2>;
> 

      reply	other threads:[~2015-11-19 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 10:46 [PATCH RESEND] arm: dts: berlin2q: remove duplicated interrupt-parent Jisheng Zhang
2015-11-19 20:21 ` Sebastian Hesselbarth [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=564E2F64.30709@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).