From patchwork Sat Mar 11 21:18:42 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Ron Eggler X-Patchwork-Id: 20820 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id A8F56C6FD1C for ; Sat, 11 Mar 2023 21:18:48 +0000 (UTC) Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by mx.groups.io with SMTP id smtpd.web10.54169.1678569524441103504 for ; Sat, 11 Mar 2023 13:18:44 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@mistywest-com.20210112.gappssmtp.com header.s=20210112 header.b=OIKT/QIP; spf=pass (domain: mistywest.com, ip: 209.85.216.44, mailfrom: ron.eggler@mistywest.com) Received: by mail-pj1-f44.google.com with SMTP id mg1so394335pjb.0 for ; Sat, 11 Mar 2023 13:18:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mistywest-com.20210112.gappssmtp.com; s=20210112; t=1678569523; h=subject:from:content-language:to:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=hpNV/bxJj5A8bOSxGfk1jI7DS3VFnXU5ZpFstzsgYgo=; b=OIKT/QIPS6C3iY6k6K62fZnFWNtaomo8WITxMD+QtmVAfa9q97ttiphKeLIQHPl7Fz 05jvHctXaAcbyJAJv57DbXcdMZtmcfn5k5aHGQYCxgfLYB8VnPZBdhGxz0zGMgG2HJFs mc5AaCWt3Re6KrwqRYxrOkOxYcB9GfiS7nxCFitDhzIYnAG7jd6qskjWphwtn6bS85qz NQosC9pLcFS4MKY8xC3yLOX6FD+1sYyKws+E4I5xR/FZC8zxJYnPdbOLJEttpTncxhD9 xCvbMRV5lVe9LZPTb24EZjlt1bmNJ2g0zBZm/QADFkI34EUZnl3qTy+6YE98HTxqgevQ ygGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678569523; h=subject:from:content-language:to:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hpNV/bxJj5A8bOSxGfk1jI7DS3VFnXU5ZpFstzsgYgo=; b=JZLtAew6/fUlzeGpkkBG5S5qJ1kUoOMdGL/2Kx9K+Q0leTbt0ssX9EyYwk55HDKXtY c3BzsL9QVwsg+EAM830zy8RahbWUsqrjq7BL44uAcihoKCThqs3tZuoj0tJ7zr4GvcC+ jQLG+MWj1fKqrWyXDerbl+QL2+mcDPPGrFnBlsfmVsLVDn3hP8GFXX9HKfJbncRTDrCY iewFTu+SEONQkpFNHxR4OwM5v/azNRN58LOGT7mIolvvhal7ELVAzafCC5f20h0/Bfyf abRJvklfuB3PvAvmM2byPWttnv09c3floZmfo1Jwwq9z4LyULx+bh2/U9o8URfM07qgt xO6Q== X-Gm-Message-State: AO0yUKWb3gq3Ad/WPx9evQjm7YALlfUiFMK15TIRIoQ3wneM2smJY0lI z/LrZAQUs1ciueEnU1FpHTEQ6M92eYZURknMjOHkIQ== X-Google-Smtp-Source: AK7set83z9RgRY7cRBNSOJl8I1k330P1OdTPkoUpMaJ0AmcO7ywUQA4QKFf5liDsg9nib4aCopwkAQ== X-Received: by 2002:a17:902:ea11:b0:194:cc66:66f7 with SMTP id s17-20020a170902ea1100b00194cc6666f7mr36263965plg.19.1678569522930; Sat, 11 Mar 2023 13:18:42 -0800 (PST) Received: from [192.168.100.190] ([209.52.149.8]) by smtp.gmail.com with ESMTPSA id ld13-20020a170902facd00b0019f3c61201esm93160plb.227.2023.03.11.13.18.42 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 11 Mar 2023 13:18:42 -0800 (PST) Message-ID: <3f9d9623-ca06-c198-439b-a8762f856779@mistywest.com> Date: Sat, 11 Mar 2023 13:18:42 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 To: yocto@lists.yoctoproject.org Content-Language: en-US From: Ron Eggler Subject: eth devices not visible after applictaion of phy patch List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Sat, 11 Mar 2023 21:18:48 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/yocto/message/59401 Hi list, I want to apply a patch to the ethernet devices for the phy, where the patch looks like: cat ../meta-mistysom/recipes-kernel/linux/smarc-rzg2l/0001-add-vsc8531-userspace-dts.patch + One question I have is, if the ampersand (&) should apply to the top eth node (as seen above) or the inner phy nodes, instead?, I only want to modify the phy settings. When I boot the system with the kernel & device tree, on bootup I see the following messages: [    6.721177] ravb 11c30000.ethernet eth1: failed to connect PHY [    6.869282] ravb 11c20000.ethernet eth0: failed to connect PHY and when I log in and check contents in /proc/device-tree/ I don't see any network interfaces. diff --git a/r9a07g044l2-smarc.dts.orig b/r9a07g044l2-smarc.dts index bc2af6c..82ba67e 100644 --- a/arch/arm64/boot/dts/renesas/r9a07g044l2-smarc.dts +++ b/arch/arm64/boot/dts/renesas/r9a07g044l2-smarc.dts @@ -11,8 +11,32 @@  #include "rzg2l-smarc-pinfunction.dtsi"  #include "rz-smarc-common.dtsi"  #include "rzg2l-smarc.dtsi" +#include  / {         model = "Renesas SMARC EVK based on r9a07g044l2";         compatible = "renesas,smarc-evk", "renesas,r9a07g044l2", "renesas,r9a07g044";  }; + +ð0 { +        phy0: ethernet-phy@7 { +                compatible = "ethernet-phy-ieee802.3-c45"; +                reg = <0>; +                vsc8531,vddmac          = <1800>; +                vsc8531,edge-slowdown   = <0>; +                vsc8531,led-0-mode      = ; +                vsc8531,led-1-mode      = ; +       }; +}; + +ð1 { +        phy1: ethernet-phy@7 { +                compatible = "ethernet-phy-ieee802.3-c45"; +                reg = <0>; +                vsc8531,vddmac          = <1800>; +                vsc8531,edge-slowdown   = <0>; +                vsc8531,led-0-mode      = ; +                vsc8531,led-1-mode      = ; +        }; +};