From: Tom Rini <trini@konsulko.com>
To: Amjad Ouled-Ameur <aouledameur@baylibre.com>
Cc: u-boot@lists.denx.de, Roger Quadros <rogerq@ti.com>,
Heiko Schocher <hs@denx.de>,
Igor Opaniuk <igor.opaniuk@foundries.io>,
Kory Maincent <kory.maincent@bootlin.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Priyanka Jain <priyanka.jain@nxp.com>,
Rick Chen <rick@andestech.com>, Sean Anderson <seanga2@gmail.com>,
Simon Glass <sjg@chromium.org>,
khilman@baylibre.com
Subject: Re: [PATCH] board: ti: am335x: Choose CPSW or PRUSS configuration based on jumper setting
Date: Mon, 17 Jan 2022 13:36:07 -0500 [thread overview]
Message-ID: <20220117183607.GS2631111@bill-the-cat> (raw)
In-Reply-To: <20211029140817.85307-1-aouledameur@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
On Fri, Oct 29, 2021 at 04:08:17PM +0200, Amjad Ouled-Ameur wrote:
> The am335x-ice-v2 board's Ethernet ports can be configured
> in 'MII' or 'RMII' mode to be connected to 'PRUSS' or 'CPSW'
> Ethernet subsystems.
>
> This patch sets the environment variable 'ice_mii' to
> 'mii' or 'rmii' accordingly. Based on that we choose the
> appropriate board devicetree i.e. 'am335x-ice-v2.dtb' or
> 'am335x-ice-v2-prueth.dtb'.
>
> Since there are 2 Ethernet ports with 2 modes, there can be 4
> configurations but for now we consider both ports in different modes
> to be an invalid configuration and prevent boot in that case.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> [Amjad: use overlay instead of using new am335x-ice-v2-prueth.dtb]
> Signed-off-by: Amjad Ouled-Ameur <aouledameur@baylibre.com>
> Reviewed-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-01-17 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 14:08 [PATCH] board: ti: am335x: Choose CPSW or PRUSS configuration based on jumper setting Amjad Ouled-Ameur
2021-10-29 17:28 ` Tom Rini
2022-01-17 18:36 ` Tom Rini [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=20220117183607.GS2631111@bill-the-cat \
--to=trini@konsulko.com \
--cc=aouledameur@baylibre.com \
--cc=hs@denx.de \
--cc=igor.opaniuk@foundries.io \
--cc=khilman@baylibre.com \
--cc=kory.maincent@bootlin.com \
--cc=lokeshvutla@ti.com \
--cc=priyanka.jain@nxp.com \
--cc=rick@andestech.com \
--cc=rogerq@ti.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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