Merge tag ‘omap-for-v5.0/fixes-rc7-signed’ of git:// into arm/fixes [Linux 5.0]

This Linux kernel change "Merge tag ‘omap-for-v5.0/fixes-rc7-signed’ of git:// into arm/fixes" is included in the Linux 5.0 release. This change is authored by Arnd Bergmann <arnd [at]> on Fri Feb 22 14:53:48 2019 +0100. The commit for this change in Linux stable tree is 3858bfc (patch). Other info about this change: Merge: 94d9b93 0661465

Merge tag 'omap-for-v5.0/fixes-rc7-signed' of git:// into arm/fixes

Two am335x ethernet phy mode fixes for v5.0-rc cycle

Recent changes with commit cd28d1d6e52e: ("net: phy: at803x: Disable phy
delay for RGMII mode") broke Ethernet on am335x-evmsk, and turns out some
device driver fixes are needed.

Even without the driver fixes, am335x needs to run in rgmii-id mode instead
rgmii-txid mode. Things have been working based on luck as the broken driver
has been configuring rgmii-id mode. Let's fix that as that way things work
as they're supposed to work from hardware wiring point of view.

* tag 'omap-for-v5.0/fixes-rc7-signed' of git://
  ARM: dts: am335x-evm: Fix PHY mode for ethernet
  ARM: dts: am335x-evmsk: Fix PHY mode for ethernet

Signed-off-by: Arnd Bergmann <[email protected]>

There is no are 0 lines of Linux source code added/deleted in this change. Code changes to Linux kernel are as follows.

 arch/arm/boot/dts/tegra124-nyan.dtsi | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/tegra124-nyan.dtsi b/arch/arm/boot/dts/tegra124-nyan.dtsi
index d5f11d6d..bc85b6a 100644
--- a/arch/arm/boot/dts/tegra124-nyan.dtsi
+++ b/arch/arm/boot/dts/tegra124-nyan.dtsi
@@ -13,10 +13,25 @@
        stdout-path = "serial0:115200n8";

-   [email protected] {
+   /*
+    * Note that recent version of the device tree compiler (starting with
+    * version 1.4.2) warn about this node containing a reg property, but
+    * missing a unit-address. However, the bootloader on these Chromebook
+    * devices relies on the full name of this node to be exactly /memory.
+    * Adding the unit-address causes the bootloader to create a /memory
+    * node and write the memory bank configuration to that node, which in
+    * turn leads the kernel to believe that the device has 2 GiB of
+    * memory instead of the amount detected by the bootloader.
+    *
+    * The name of this node is effectively ABI and must not be changed.
+    */
+   memory {
+       device_type = "memory";
        reg = <0x0 0x80000000 0x0 0x80000000>;

+   /delete-node/ [email protected];
    [email protected] {
        [email protected] {
            status = "okay";

Leave a Reply

Your email address will not be published. Required fields are marked *