linux_dsm_epyc7002/arch/arm/boot/dts/bcm47094.dtsi

/*
 * Copyright (C) 2016 Rafał Miłecki <rafal@milecki.pl>
 *
 * Licensed under the ISC license.
 */

#include "bcm4708.dtsi"

/ {
};

&usb3_phy {
	compatible = "brcm,ns-bx-usb3-phy";
};

&uart0 {
	clock-frequency = <125000000>;
	status = "okay";
};
ARM: BCM5301X: Add separated DTS include file for BCM47094 Use it to store BCM47094 specific properties/values and avoid repeating them in device DTS files. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> 2016-09-22 03:58:32 +07:00			`/*`
			`* Copyright (C) 2016 Rafał Miłecki <rafal@milecki.pl>`
			`*`
			`* Licensed under the ISC license.`
			`*/`

			`#include "bcm4708.dtsi"`

ARM: BCM5301X: Specify USB 3.0 PHY in DT Driver for Northstar USB 3.0 PHY has been recently added under the name phy-bcm-ns-usb3. Add binding for it into the DT files. The only slightly tricky part is BCM47094 which uses different PHY version and requires different compatible value. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> 2016-09-22 03:58:34 +07:00			`/ {`
ARM: dts: BCM5301X: Make USB 3.0 PHY use MDIO PHY driver Currently, the USB 3.0 PHY in bcm5301x.dtsi uses platform driver which requires register range "ccb-mii" <0x18003000 0x1000>. This range overlaps with MDIO cmd and param registers (<0x18003000 0x8>). Essentially, the platform driver partly acts like a MDIO bus driver, hence to use of this register range. In some Northstar devices like Linksys EA9500, secondary switch is connected via external MDIO. The only way to access and configure the external switch is via MDIO bus. When we enable the MDIO bus in it's current state, the MDIO bus and any child buses fail to register because of the register range overlap. On Northstar, the USB 3.0 PHY is connected at address 0x10 on the internal MDIO bus. This change moves the usb3_phy node and makes it a child node of internal MDIO bus. Thanks to Rafał Miłecki's commit af850e14a7ae ("phy: bcm-ns-usb3: add MDIO driver using proper bus layer") the same USB 3.0 platform driver can now act as USB 3.0 PHY MDIO driver. Tested on Linksys Panamera (EA9500) Signed-off-by: Vivek Unune <npcomplete13@gmail.com> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> 2018-04-10 05:31:53 +07:00			`};`

			`&usb3_phy {`
			`compatible = "brcm,ns-bx-usb3-phy";`
ARM: BCM5301X: Specify USB 3.0 PHY in DT Driver for Northstar USB 3.0 PHY has been recently added under the name phy-bcm-ns-usb3. Add binding for it into the DT files. The only slightly tricky part is BCM47094 which uses different PHY version and requires different compatible value. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> 2016-09-22 03:58:34 +07:00			`};`

ARM: BCM5301X: Add separated DTS include file for BCM47094 Use it to store BCM47094 specific properties/values and avoid repeating them in device DTS files. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> 2016-09-22 03:58:32 +07:00			`&uart0 {`
			`clock-frequency = <125000000>;`
ARM: dts: BCM5301X: Enable UART by default for BCM4708(1), BCM4709(4) & BCM53012 Every device tested so far got UART0 (at 0x18000300) working as serial console. It's most likely part of reference design and all vendors use it that way. It seems to be easier to enable it by default and just disable it if we ever see a device with different hardware design. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Acked-by: Jon Mason <jon.mason@broadcom.com> Acked-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> 2016-12-02 00:40:51 +07:00			`status = "okay";`
ARM: BCM5301X: Add separated DTS include file for BCM47094 Use it to store BCM47094 specific properties/values and avoid repeating them in device DTS files. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> 2016-09-22 03:58:32 +07:00			`};`