All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
	Andrew Lunn <andrew@lunn.ch>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 3/3] arm64: dts: reset: add microchip sparx5 switch reset driver
Date: Mon, 8 Mar 2021 12:59:34 -0700	[thread overview]
Message-ID: <20210308195934.GA2855503@robh.at.kernel.org> (raw)
In-Reply-To: <20210303081158.684532-4-steen.hegelund@microchip.com>

On Wed, Mar 03, 2021 at 09:11:58AM +0100, Steen Hegelund wrote:
> This provides reset driver support for the Microchip Sparx5 PCB134 and
> PCB135 reference boards.

This still looks like an incompatible change with no explanation.

What happens on an old kernel that expects "microchip,sparx5-chip-reset" 
and doesn't understand "microchip,sparx5-switch-reset"?

> 
> Signed-off-by: Steen Hegelund <steen.hegelund@microchip.com>
> ---
>  arch/arm64/boot/dts/microchip/sparx5.dtsi | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/microchip/sparx5.dtsi b/arch/arm64/boot/dts/microchip/sparx5.dtsi
> index 380281f312d8..dc3ada5cf9fc 100644
> --- a/arch/arm64/boot/dts/microchip/sparx5.dtsi
> +++ b/arch/arm64/boot/dts/microchip/sparx5.dtsi
> @@ -132,9 +132,12 @@ mux: mux-controller {
>  			};
>  		};
>  
> -		reset@611010008 {
> -			compatible = "microchip,sparx5-chip-reset";
> +		reset: reset-controller@611010008 {
> +			compatible = "microchip,sparx5-switch-reset";
>  			reg = <0x6 0x11010008 0x4>;
> +			reg-names = "gcb";
> +			#reset-cells = <1>;
> +			cpu-syscon = <&cpu_ctrl>;
>  		};
>  
>  		uart0: serial@600100000 {
> -- 
> 2.30.1
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
	Andrew Lunn <andrew@lunn.ch>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 3/3] arm64: dts: reset: add microchip sparx5 switch reset driver
Date: Mon, 8 Mar 2021 12:59:34 -0700	[thread overview]
Message-ID: <20210308195934.GA2855503@robh.at.kernel.org> (raw)
In-Reply-To: <20210303081158.684532-4-steen.hegelund@microchip.com>

On Wed, Mar 03, 2021 at 09:11:58AM +0100, Steen Hegelund wrote:
> This provides reset driver support for the Microchip Sparx5 PCB134 and
> PCB135 reference boards.

This still looks like an incompatible change with no explanation.

What happens on an old kernel that expects "microchip,sparx5-chip-reset" 
and doesn't understand "microchip,sparx5-switch-reset"?

> 
> Signed-off-by: Steen Hegelund <steen.hegelund@microchip.com>
> ---
>  arch/arm64/boot/dts/microchip/sparx5.dtsi | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/microchip/sparx5.dtsi b/arch/arm64/boot/dts/microchip/sparx5.dtsi
> index 380281f312d8..dc3ada5cf9fc 100644
> --- a/arch/arm64/boot/dts/microchip/sparx5.dtsi
> +++ b/arch/arm64/boot/dts/microchip/sparx5.dtsi
> @@ -132,9 +132,12 @@ mux: mux-controller {
>  			};
>  		};
>  
> -		reset@611010008 {
> -			compatible = "microchip,sparx5-chip-reset";
> +		reset: reset-controller@611010008 {
> +			compatible = "microchip,sparx5-switch-reset";
>  			reg = <0x6 0x11010008 0x4>;
> +			reg-names = "gcb";
> +			#reset-cells = <1>;
> +			cpu-syscon = <&cpu_ctrl>;
>  		};
>  
>  		uart0: serial@600100000 {
> -- 
> 2.30.1
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-03-08 20:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  8:11 [PATCH v7 0/3] Adding the Sparx5 Switch Reset Driver Steen Hegelund
2021-03-03  8:11 ` Steen Hegelund
2021-03-03  8:11 ` [PATCH v7 1/3] dt-bindings: reset: microchip sparx5 reset driver bindings Steen Hegelund
2021-03-03  8:11   ` Steen Hegelund
2021-03-03  8:11 ` [PATCH v7 2/3] reset: mchp: sparx5: add switch reset driver Steen Hegelund
2021-03-03  8:11   ` Steen Hegelund
2021-03-03  8:55   ` Alexandre Belloni
2021-03-03  8:55     ` Alexandre Belloni
2021-03-03  8:11 ` [PATCH v7 3/3] arm64: dts: reset: add microchip sparx5 " Steen Hegelund
2021-03-03  8:11   ` Steen Hegelund
2021-03-03  8:56   ` Alexandre Belloni
2021-03-03  8:56     ` Alexandre Belloni
2021-03-08 19:59   ` Rob Herring [this message]
2021-03-08 19:59     ` Rob Herring
2021-03-16  8:36     ` Steen Hegelund
2021-03-16  8:36       ` Steen Hegelund

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=20210308195934.GA2855503@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=steen.hegelund@microchip.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.