ef519a4371
When the pinmux mechanism was added in Kirkwood, the device driver core was not yet providing the possibility of attaching pinmux configurations to all devices, drivers had to do it explicitly, and not all drivers were doing this. Now that the driver core does that in a generic way, it makes sense to attach the pinmux configuration to their corresponding devices. This allows the pinctrl subsystem to show in debugfs to which device is related which pins, for example: pin 41 (PIN41): gpio-leds.1 mvebu-gpio:41 function gpio group mpp41 pin 42 (PIN42): gpio-leds.1 mvebu-gpio:42 function gpio group mpp42 pin 43 (PIN43): gpio-leds.1 mvebu-gpio:43 function gpio group mpp43 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: Jason Cooper <jason@lakedaemon.net>
53 lines
907 B
Plaintext
53 lines
907 B
Plaintext
/dts-v1/;
|
|
|
|
/include/ "kirkwood-ns2-common.dtsi"
|
|
|
|
/ {
|
|
/* This machine is embedded in the first LaCie CloudBox product. */
|
|
model = "LaCie Network Space Mini v2";
|
|
compatible = "lacie,netspace_mini_v2", "marvell,kirkwood-88f6192", "marvell,kirkwood";
|
|
|
|
memory {
|
|
device_type = "memory";
|
|
reg = <0x00000000 0x8000000>;
|
|
};
|
|
|
|
ocp@f1000000 {
|
|
sata@80000 {
|
|
pinctrl-0 = <&pmx_ns2_sata0>;
|
|
pinctrl-names = "default";
|
|
status = "okay";
|
|
nr-ports = <1>;
|
|
};
|
|
};
|
|
|
|
gpio_fan {
|
|
compatible = "gpio-fan";
|
|
gpios = <&gpio0 22 1
|
|
&gpio0 7 1
|
|
&gpio1 1 1
|
|
&gpio0 23 1>;
|
|
gpio-fan,speed-map =
|
|
< 0 0
|
|
3000 15
|
|
3180 14
|
|
4140 13
|
|
4570 12
|
|
6760 11
|
|
7140 10
|
|
7980 9
|
|
9200 8>;
|
|
alarm-gpios = <&gpio0 25 1>;
|
|
};
|
|
|
|
ns2-leds {
|
|
compatible = "lacie,ns2-leds";
|
|
|
|
blue-sata {
|
|
label = "ns2:blue:sata";
|
|
slow-gpio = <&gpio0 29 0>;
|
|
cmd-gpio = <&gpio0 30 0>;
|
|
};
|
|
};
|
|
};
|