From: Tero Kristo <t-kristo@ti.com>
To: Vladimir Oltean <olteanv@gmail.com>, David Miller <davem@davemloft.net>
Cc: Rob Herring <robh@kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
devicetree@vger.kernel.org, netdev <netdev@vger.kernel.org>,
nsekhar@ti.com, lkml <linux-kernel@vger.kernel.org>,
kishon@ti.com, peter.ujfalusi@ti.com,
Murali Karicheri <m-karicheri2@ti.com>,
Jakub Kicinski <kuba@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
rogerq@ti.com
Subject: Re: [PATCH net-next v6 00/11] net: ethernet: ti: add networking support for k3 am65x/j721e soc
Date: Mon, 30 Mar 2020 10:15:35 +0300 [thread overview]
Message-ID: <8f5e981a-193c-0c1e-1e0a-b0380b2e6a9c@ti.com> (raw)
In-Reply-To: <CA+h21hr8G24ddEgAbU_TfoNAe0fqUJ0_Uyp54Gxn5cvPrM6u9g@mail.gmail.com>
On 28/03/2020 03:53, Vladimir Oltean wrote:
> Hi David,
>
> On Fri, 27 Mar 2020 at 05:02, David Miller <davem@davemloft.net> wrote:
>>
>> From: Grygorii Strashko <grygorii.strashko@ti.com>
>> Date: Tue, 24 Mar 2020 00:52:43 +0200
>>
>>> This v6 series adds basic networking support support TI K3 AM654x/J721E SoC which
>>> have integrated Gigabit Ethernet MAC (Media Access Controller) into device MCU
>>> domain and named MCU_CPSW0 (CPSW2G NUSS).
>> ...
>>
>> Series applied, thank you.
>
> The build is now broken on net-next:
>
> arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi:303.23-309.6: ERROR
> (phandle_references):
> /interconnect@100000/interconnect@28380000/ethernet@46000000/ethernet-ports/port@1:
> Reference to non-existent node
> or label "mcu_conf"
>
> also defined at
> arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts:471.13-474.3
> arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi:303.23-309.6: ERROR
> (phandle_references):
> /interconnect@100000/interconnect@28380000/ethernet@46000000/ethernet-ports/port@1:
> Reference to non-existent node
> or label "phy_gmii_sel"
>
> also defined at
> arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts:471.13-474.3
>
> As Grygorii said:
>
> Patches 1-6 are intended for netdev, Patches 7-11 are intended for K3 Platform
> tree and provided here for testing purposes.
Yeah, I think you are missing a dependency that was applied via the K3
branch earlier. They are in linux-next now, but I am not so sure how
much that is going to help you.
You could just drop the DT patches from this merge and let me apply them
via the platform branch.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-30 7:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 22:52 [PATCH net-next v6 00/11] net: ethernet: ti: add networking support for k3 am65x/j721e soc Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 01/11] phy: ti: gmii-sel: simplify config dependencies between net drivers and gmii phy Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 02/11] net: ethernet: ti: ale: fix seeing unreg mcast packets with promisc and allmulti disabled Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 03/11] net: ethernet: ti: ale: add support for mac-only mode Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 04/11] net: ethernet: ti: ale: am65: add support for default thread cfg Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 05/11] dt-binding: ti: am65x: document mcu cpsw nuss Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 06/11] net: ethernet: ti: introduce am65x/j721e gigabit eth subsystem driver Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 07/11] arm64: dts: ti: k3-am65-mcu: add cpsw nuss node Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 08/11] arm64: dts: k3-am654-base-board: add mcu cpsw nuss pinmux and phy defs Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 09/11] arm64: dts: ti: k3-j721e-mcu: add mcu cpsw nuss node Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 10/11] arm64: dts: ti: k3-j721e-common-proc-board: add mcu cpsw nuss pinmux and phy defs Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 11/11] arm64: defconfig: ti: k3: enable dma and networking Grygorii Strashko
2020-03-27 3:01 ` [PATCH net-next v6 00/11] net: ethernet: ti: add networking support for k3 am65x/j721e soc David Miller
2020-03-28 1:53 ` Vladimir Oltean
2020-03-30 7:15 ` Tero Kristo [this message]
2020-03-30 7:36 ` Sekhar Nori
2020-03-30 8:28 ` Sekhar Nori
2020-03-30 18:14 ` Grygorii Strashko
2020-04-01 18:27 ` Vladimir Oltean
2020-04-01 18:36 ` David Miller
2020-04-01 22:35 ` Nick Desaulniers
2020-04-02 9:42 ` Will Deacon
2020-04-02 11:05 ` Grygorii Strashko
2020-04-02 17:27 ` Nick Desaulniers
2020-04-03 5:11 ` Sekhar Nori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f5e981a-193c-0c1e-1e0a-b0380b2e6a9c@ti.com \
--to=t-kristo@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=olteanv@gmail.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox