aboutsummaryrefslogtreecommitdiff
path: root/arch/arm/dts/imx6q-bx50v3-uboot.dtsi
blob: 0253d2fa6f5bf5572a48f4daaa702cb645c706e8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
// SPDX-License-Identifier: GPL-2.0+ OR X11
/*
 * Copyright 2019 Collabora Ltd
 * Copyright 2019 General Electric Company
 */

/ {
	bootcount {
		compatible = "u-boot,bootcount-i2c-eeprom";
		i2c-eeprom = <&bootcount>;
	};

	wdt-reboot {
		compatible = "wdt-reboot";
		wdt = <&wdog1>;
	};

	panel-lvds0 {
		compatible = "simple-panel";
	};
};

&eeprom {
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		vpd@0 {
			reg = <0 800>;
		};

		bootcount: bootcount {
			reg = <1022 2>;
		};
	};
};

/*
 * This is not done in imx6q-ba16.dtsi, since that file is shared
 * with the kernel and the kernel should not reset the PHY, since
 * it lacks support for configuring the reserved registeres to
 * avoid a board specific voltage peak issue.
 */
&fec {
	phy-reset-gpios = <&gpio1 28 GPIO_ACTIVE_LOW>;
	phy-reset-duration = <1>;
	phy-reset-post-delay = <0>;
};

/*
 * PCIe reset is not done in the file shared with the kernel, since
 * this GPIO also resets other peripherals (i.e. not just PCIe).
 * These peripherals are being initialized by U-Boot and should not
 * be reset by the kernel, so it may not reset PCIe via this GPIO.
 */
&pcie {
	reset-gpio = <&gpio7 12 GPIO_ACTIVE_LOW>;
};