netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: netdev@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
	kernel@pengutronix.de, Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH net-next] Revert "riscv: dts: allwinner: d1: Add CAN controller nodes"
Date: Mon, 07 Aug 2023 09:48:42 +0200	[thread overview]
Message-ID: <2690985.mvXUDI8C0e@jernej-laptop> (raw)
In-Reply-To: <20230807074222.1576119-2-mkl@pengutronix.de>

Dne ponedeljek, 07. avgust 2023 ob 09:42:22 CEST je Marc Kleine-Budde 
napisal(a):
> It turned out the dtsi changes were not quite ready, revert them for
> now.
> 
> This reverts commit 6ea1ad888f5900953a21853e709fa499fdfcb317.
> 
> Link: https://lore.kernel.org/all/2690764.mvXUDI8C0e@jernej-laptop
> Suggested-by: Jernej Škrabec <jernej.skrabec@gmail.com>
> Link:
> https://lore.kernel.org/all/20230807-riscv-allwinner-d1-revert-can-controll
> er-nodes-v1-1-eb3f70b435d9@pengutronix.de Signed-off-by: Marc Kleine-Budde
> <mkl@pengutronix.de>

Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>

Best regards,
Jernej

> ---
>  .../boot/dts/allwinner/sunxi-d1s-t113.dtsi    | 30 -------------------
>  1 file changed, 30 deletions(-)
> 
> diff --git a/arch/riscv/boot/dts/allwinner/sunxi-d1s-t113.dtsi
> b/arch/riscv/boot/dts/allwinner/sunxi-d1s-t113.dtsi index
> 4086c0cc0f9d..1bb1e5cae602 100644
> --- a/arch/riscv/boot/dts/allwinner/sunxi-d1s-t113.dtsi
> +++ b/arch/riscv/boot/dts/allwinner/sunxi-d1s-t113.dtsi
> @@ -131,18 +131,6 @@ uart3_pb_pins: uart3-pb-pins {
>  				pins = "PB6", "PB7";
>  				function = "uart3";
>  			};
> -
> -			/omit-if-no-ref/
> -			can0_pins: can0-pins {
> -				pins = "PB2", "PB3";
> -				function = "can0";
> -			};
> -
> -			/omit-if-no-ref/
> -			can1_pins: can1-pins {
> -				pins = "PB4", "PB5";
> -				function = "can1";
> -			};
>  		};
> 
>  		ccu: clock-controller@2001000 {
> @@ -891,23 +879,5 @@ rtc: rtc@7090000 {
>  			clock-names = "bus", "hosc", "ahb";
>  			#clock-cells = <1>;
>  		};
> -
> -		can0: can@2504000 {
> -			compatible = "allwinner,sun20i-d1-can";
> -			reg = <0x02504000 0x400>;
> -			interrupts = <SOC_PERIPHERAL_IRQ(21) 
IRQ_TYPE_LEVEL_HIGH>;
> -			clocks = <&ccu CLK_BUS_CAN0>;
> -			resets = <&ccu RST_BUS_CAN0>;
> -			status = "disabled";
> -		};
> -
> -		can1: can@2504400 {
> -			compatible = "allwinner,sun20i-d1-can";
> -			reg = <0x02504400 0x400>;
> -			interrupts = <SOC_PERIPHERAL_IRQ(22) 
IRQ_TYPE_LEVEL_HIGH>;
> -			clocks = <&ccu CLK_BUS_CAN1>;
> -			resets = <&ccu RST_BUS_CAN1>;
> -			status = "disabled";
> -		};
>  	};
>  };
> 
> base-commit: c35e927cbe09d38b2d72183bb215901183927c68





  reply	other threads:[~2023-08-07  7:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  7:42 [PATCH net-next 0/1] pull-request: can-next 2023-08-07 Marc Kleine-Budde
2023-08-07  7:42 ` [PATCH net-next] Revert "riscv: dts: allwinner: d1: Add CAN controller nodes" Marc Kleine-Budde
2023-08-07  7:48   ` Jernej Škrabec [this message]
2023-08-07 19:30   ` patchwork-bot+netdevbpf

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=2690985.mvXUDI8C0e@jernej-laptop \
    --to=jernej.skrabec@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.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).