···44 compiler and the textural representation of45 the tree that can be "compiled" by dtc.4647-48 November 21, 2005: Rev 0.549 - Additions/generalizations for 32-bit50 - Changed to reflect the new arch/powerpc···1303 device_type = "i2c";1304 compatible = "fsl-i2c";1305 dfsrr;000000000000000000000000000000000000000000000000000000000001306 };13071308
···44 compiler and the textural representation of45 the tree that can be "compiled" by dtc.46047 November 21, 2005: Rev 0.548 - Additions/generalizations for 32-bit49 - Changed to reflect the new arch/powerpc···1304 device_type = "i2c";1305 compatible = "fsl-i2c";1306 dfsrr;1307+ };1308+1309+1310+ f) Freescale SOC USB controllers1311+1312+ The device node for a USB controller that is part of a Freescale1313+ SOC is as described in the document "Open Firmware Recommended1314+ Practice : Universal Serial Bus" with the following modifications1315+ and additions : 1316+1317+ Required properties :1318+ - compatible : Should be "fsl-usb2-mph" for multi port host usb1319+ controllers, or "fsl-usb2-dr" for dual role usb controllers1320+ - phy_type : For multi port host usb controllers, should be one of1321+ "ulpi", or "serial". For dual role usb controllers, should be1322+ one of "ulpi", "utmi", "utmi_wide", or "serial".1323+ - reg : Offset and length of the register set for the device1324+ - port0 : boolean; if defined, indicates port0 is connected for1325+ fsl-usb2-mph compatible controllers. Either this property or1326+ "port1" (or both) must be defined for "fsl-usb2-mph" compatible 1327+ controllers.1328+ - port1 : boolean; if defined, indicates port1 is connected for1329+ fsl-usb2-mph compatible controllers. Either this property or1330+ "port0" (or both) must be defined for "fsl-usb2-mph" compatible 1331+ controllers.1332+1333+ Recommended properties :1334+ - interrupts : <a b> where a is the interrupt number and b is a1335+ field that represents an encoding of the sense and level1336+ information for the interrupt. This should be encoded based on1337+ the information in section 2) depending on the type of interrupt1338+ controller you have.1339+ - interrupt-parent : the phandle for the interrupt controller that1340+ services interrupts for this device.1341+1342+ Example multi port host usb controller device node : 1343+ usb@22000 {1344+ device_type = "usb";1345+ compatible = "fsl-usb2-mph";1346+ reg = <22000 1000>;1347+ #address-cells = <1>;1348+ #size-cells = <0>;1349+ interrupt-parent = <700>;1350+ interrupts = <27 1>;1351+ phy_type = "ulpi";1352+ port0;1353+ port1;1354+ };1355+1356+ Example dual role usb controller device node : 1357+ usb@23000 {1358+ device_type = "usb";1359+ compatible = "fsl-usb2-dr";1360+ reg = <23000 1000>;1361+ #address-cells = <1>;1362+ #size-cells = <0>;1363+ interrupt-parent = <700>;1364+ interrupts = <26 1>;1365+ phy = "ulpi";1366 };13671368
+6
arch/powerpc/Kconfig
···83 default y if PPC32 && SMP84 default n8500000086menu "Processor support"87choice88 prompt "Processor Type"
···83 default y if PPC32 && SMP84 default n8586+config DEFAULT_UIMAGE87+ bool88+ help89+ Used to allow a board to specify it wants a uImage built by default90+ default n91+92menu "Processor support"93choice94 prompt "Processor Type"
+1
arch/powerpc/Makefile
···142# Default to zImage, override when needed143defaultimage-y := zImage144defaultimage-$(CONFIG_PPC_ISERIES) := vmlinux0145KBUILD_IMAGE := $(defaultimage-y)146all: $(KBUILD_IMAGE)147
···142# Default to zImage, override when needed143defaultimage-y := zImage144defaultimage-$(CONFIG_PPC_ISERIES) := vmlinux145+defaultimage-$(CONFIG_DEFAULT_UIMAGE) := uImage146KBUILD_IMAGE := $(defaultimage-y)147all: $(KBUILD_IMAGE)148