From: Ravi Gunasekaran <r-gunasekaran@ti.com>
To: MD Danish Anwar <danishanwar@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>, <srk@ti.com>,
Roger Quadros <rogerq@kernel.org>
Subject: Re: [PATCH v3 0/3] Add AM64x ICSSG Ethernet support
Date: Fri, 2 Feb 2024 10:16:47 +0530 [thread overview]
Message-ID: <d40671cc-6e5d-461c-a1cf-3482a545042c@ti.com> (raw)
In-Reply-To: <20240122113045.1711818-1-danishanwar@ti.com>
On 1/22/2024 5:00 PM, MD Danish Anwar wrote:
> Hi All,
>
> This series adds support for ICSSG ethernet on AM64x.
> This series is based on the latest next-20231211 linux-next.
>
> AM64x EVM has three ethernet ports. One is dedicated to CPSW and one is
> dedicated to ICSSG1. The remaining port is muxed between CPSW and ICSSG1
> ICSSG1 ports. The ICSSG1 node is added in the k3-am642-evm.dts. By default
> the muxed port is used by CPSW so 2nd ICSSG1 port is disabled in the
> k3-am642-evm.dts. But overlay k3-am642-evm-icssg1-dualemac.dtso can be
> applied to use muxed port as ICSSG1.
>
> This is the v3 of the series [v1].
>
> Changes from v2 to v3:
> *) No functional changes.
> *) Rebased on latest linux-next (next-20240122) after 6.8-rc1.
>
> Changes from v1 to v2:
> *) Fixed aliases section in k3-am642-evm.dts
> *) Fixed firmware-names in k3-am642-evm.dts
> *) Changed icssg1_phy1 to ethernet-phy@f from ethernet-phy@0 as suggested
> by Andrew L.
> *) Changed makefile to handle overlays using CONFIG_OF_ALL_DTBS as
> suggested by Nishant and Andrew Davis.
> *) Fixed aliases section in k3-am642-evm-icssg1-dualemac.dtso
> *) Fixed pinctrl in k3-am642-evm-icssg1-dualemac.dtso
> *) Updated commit message of patch 3/3 of the series to warn about adding
> label name to 'mdio-mux-1' node.
>
> [v1] https://lore.kernel.org/all/20231207081917.340167-1-danishanwar@ti.com/
> [v2] https://lore.kernel.org/all/20231212165832.3933335-1-danishanwar@ti.com/
>
For the series,
Reviewed-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
prev parent reply other threads:[~2024-02-02 4:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 11:30 [PATCH v3 0/3] Add AM64x ICSSG Ethernet support MD Danish Anwar
2024-01-22 11:30 ` [PATCH v3 1/3] arm64: dts: ti: k3-am64-main: Add ICSSG IEP nodes MD Danish Anwar
2024-01-22 11:30 ` [PATCH v3 2/3] arm64: dts: ti: k3-am642-evm: add ICSSG1 Ethernet support MD Danish Anwar
2024-02-02 11:47 ` Roger Quadros
2024-02-02 16:43 ` Anwar, Md Danish
2024-01-22 11:30 ` [PATCH v3 3/3] arm64: dts: ti: k3-am642-evm: add overlay for icssg1 2nd port MD Danish Anwar
2024-02-02 12:26 ` Roger Quadros
2024-02-02 16:50 ` Anwar, Md Danish
2024-02-05 12:57 ` Roger Quadros
2024-02-06 5:15 ` MD Danish Anwar
2024-02-12 8:06 ` MD Danish Anwar
2024-02-02 4:46 ` Ravi Gunasekaran [this message]
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=d40671cc-6e5d-461c-a1cf-3482a545042c@ti.com \
--to=r-gunasekaran@ti.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@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;
as well as URLs for NNTP newsgroup(s).