linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>,
	Heiko Stuebner <heiko@sntech.de>, Olof Johansson <olof@lixom.net>,
	Arnd Bergmann <arnd@arndb.de>,
	ARM <linux-arm-kernel@lists.infradead.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Wu <david.wu@rock-chips.com>,
	Rocky Hao <rocky.hao@rock-chips.com>,
	Joseph Chen <chenjh@rock-chips.com>
Subject: Re: linux-next: manual merge of the net-next tree with the rockchip tree
Date: Mon, 4 Sep 2017 15:26:09 +1000	[thread overview]
Message-ID: <20170904152609.72aa1b9e@canb.auug.org.au> (raw)
In-Reply-To: <20170822112414.06f3b00f@canb.auug.org.au>

Hi all,

On Tue, 22 Aug 2017 11:24:14 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the net-next tree got a conflict in:
> 
>   arch/arm64/boot/dts/rockchip/rk3328-evb.dts
> 
> between commits:
> 
>   ab78718bda79 ("arm64: dts: rockchip: Enable tsadc module on RK3328 eavluation board")
>   1e28037ec88e ("arm64: dts: rockchip: add rk805 node for rk3328-evb")
> 
> from the rockchip tree and commit:
> 
>   4b05bc6157eb ("ARM64: dts: rockchip: Enable gmac2phy for rk3328-evb")
> 
> from the net-next tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc arch/arm64/boot/dts/rockchip/rk3328-evb.dts
> index 86605ae7b6f5,b9f36dad17e6..000000000000
> --- a/arch/arm64/boot/dts/rockchip/rk3328-evb.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3328-evb.dts
> @@@ -51,147 -51,24 +51,164 @@@
>   		stdout-path = "serial2:1500000n8";
>   	};
>   
>  +	dc_12v: dc-12v {
>  +		compatible = "regulator-fixed";
>  +		regulator-name = "dc_12v";
>  +		regulator-always-on;
>  +		regulator-boot-on;
>  +		regulator-min-microvolt = <12000000>;
>  +		regulator-max-microvolt = <12000000>;
>  +	};
>  +
> + 	vcc_phy: vcc-phy-regulator {
> + 		compatible = "regulator-fixed";
> + 		regulator-name = "vcc_phy";
> + 		regulator-always-on;
> + 		regulator-boot-on;
> + 	};
> ++
>  +	vcc_sys: vcc-sys {
>  +		compatible = "regulator-fixed";
>  +		regulator-name = "vcc_sys";
>  +		regulator-always-on;
>  +		regulator-boot-on;
>  +		regulator-min-microvolt = <5000000>;
>  +		regulator-max-microvolt = <5000000>;
>  +		vin-supply = <&dc_12v>;
>  +	};
>   };
>   
> + &gmac2phy {
> + 	phy-supply = <&vcc_phy>;
> + 	clock_in_out = "output";
> + 	assigned-clocks = <&cru SCLK_MAC2PHY_SRC>;
> + 	assigned-clock-rate = <50000000>;
> + 	assigned-clocks = <&cru SCLK_MAC2PHY>;
> + 	assigned-clock-parents = <&cru SCLK_MAC2PHY_SRC>;
> + 	status = "okay";
> + };
> + 
>  +&i2c1 {
>  +	status = "okay";
>  +
>  +	rk805: rk805@18 {
>  +		compatible = "rockchip,rk805";
>  +		reg = <0x18>;
>  +		interrupt-parent = <&gpio2>;
>  +		interrupts = <6 IRQ_TYPE_LEVEL_LOW>;
>  +		#clock-cells = <1>;
>  +		clock-output-names = "xin32k", "rk805-clkout2";
>  +		gpio-controller;
>  +		#gpio-cells = <2>;
>  +		pinctrl-names = "default";
>  +		pinctrl-0 = <&pmic_int_l>;
>  +		rockchip,system-power-controller;
>  +		wakeup-source;
>  +
>  +		vcc1-supply = <&vcc_sys>;
>  +		vcc2-supply = <&vcc_sys>;
>  +		vcc3-supply = <&vcc_sys>;
>  +		vcc4-supply = <&vcc_sys>;
>  +		vcc5-supply = <&vcc_io>;
>  +		vcc6-supply = <&vcc_io>;
>  +
>  +		regulators {
>  +			vdd_logic: DCDC_REG1 {
>  +				regulator-name = "vdd_logic";
>  +				regulator-min-microvolt = <712500>;
>  +				regulator-max-microvolt = <1450000>;
>  +				regulator-always-on;
>  +				regulator-boot-on;
>  +				regulator-state-mem {
>  +					regulator-on-in-suspend;
>  +					regulator-suspend-microvolt = <1000000>;
>  +				};
>  +			};
>  +
>  +			vdd_arm: DCDC_REG2 {
>  +				regulator-name = "vdd_arm";
>  +				regulator-min-microvolt = <712500>;
>  +				regulator-max-microvolt = <1450000>;
>  +				regulator-always-on;
>  +				regulator-boot-on;
>  +				regulator-state-mem {
>  +					regulator-on-in-suspend;
>  +					regulator-suspend-microvolt = <950000>;
>  +				};
>  +			};
>  +
>  +			vcc_ddr: DCDC_REG3 {
>  +				regulator-name = "vcc_ddr";
>  +				regulator-always-on;
>  +				regulator-boot-on;
>  +				regulator-state-mem {
>  +					regulator-on-in-suspend;
>  +				};
>  +			};
>  +
>  +			vcc_io: DCDC_REG4 {
>  +				regulator-name = "vcc_io";
>  +				regulator-min-microvolt = <3300000>;
>  +				regulator-max-microvolt = <3300000>;
>  +				regulator-always-on;
>  +				regulator-boot-on;
>  +				regulator-state-mem {
>  +					regulator-on-in-suspend;
>  +					regulator-suspend-microvolt = <3300000>;
>  +				};
>  +			};
>  +
>  +			vcc_18: LDO_REG1 {
>  +				regulator-name = "vcc_18";
>  +				regulator-min-microvolt = <1800000>;
>  +				regulator-max-microvolt = <1800000>;
>  +				regulator-always-on;
>  +				regulator-boot-on;
>  +				regulator-state-mem {
>  +					regulator-on-in-suspend;
>  +					regulator-suspend-microvolt = <1800000>;
>  +				};
>  +			};
>  +
>  +			vcc18_emmc: LDO_REG2 {
>  +				regulator-name = "vcc18_emmc";
>  +				regulator-min-microvolt = <1800000>;
>  +				regulator-max-microvolt = <1800000>;
>  +				regulator-always-on;
>  +				regulator-boot-on;
>  +				regulator-state-mem {
>  +					regulator-on-in-suspend;
>  +					regulator-suspend-microvolt = <1800000>;
>  +				};
>  +			};
>  +
>  +			vdd_10: LDO_REG3 {
>  +				regulator-name = "vdd_10";
>  +				regulator-min-microvolt = <1000000>;
>  +				regulator-max-microvolt = <1000000>;
>  +				regulator-always-on;
>  +				regulator-boot-on;
>  +				regulator-state-mem {
>  +					regulator-on-in-suspend;
>  +					regulator-suspend-microvolt = <1000000>;
>  +				};
>  +			};
>  +		};
>  +	};
>  +};
>  +
>  +&pinctrl {
>  +	pmic {
>  +		pmic_int_l: pmic-int-l {
>  +			rockchip,pins = <2 RK_PA6 RK_FUNC_GPIO &pcfg_pull_up>;
>  +		};
>  +	};
>  +};
>  +
>  +&tsadc {
>  +	status = "okay";
>  +};
>  +
>   &uart2 {
>   	status = "okay";
>   };

Just a reminder that these conflicts still exist.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-09-04  5:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22  1:24 linux-next: manual merge of the net-next tree with the rockchip tree Stephen Rothwell
2017-09-04  5:26 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-16  1:16 Stephen Rothwell
2017-08-28  1:33 Stephen Rothwell
2017-08-15  1:52 Stephen Rothwell

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=20170904152609.72aa1b9e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=chenjh@rock-chips.com \
    --cc=davem@davemloft.net \
    --cc=david.wu@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=rocky.hao@rock-chips.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 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).