public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Philip Oberfichtner <pro@denx.de>
To: u-boot@lists.denx.de
Cc: Stefano Babic <sbabic@denx.de>,
	Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	Peng Fan <peng.fan@nxp.com>, Fabio Estevam <festevam@denx.de>,
	Marek Vasut <marex@denx.de>, Philip Oberfichtner <pro@denx.de>,
	Andreas Geisreiter <ageisreiter@dh-electronics.de>,
	Tom Rini <trini@konsulko.com>,
	u-boot@dh-electronics.com
Subject: [PATCH v2 4/8] ARM: imx6: Remove CONFIG_FEC_MXC_PHYADDR from DH header
Date: Fri, 20 May 2022 10:46:22 +0200	[thread overview]
Message-ID: <20220520084626.656293-5-pro@denx.de> (raw)
In-Reply-To: <20220520084626.656293-1-pro@denx.de>

Use phy address from device tree instead of CONFIG_FEC_MXC_PHYADDR from
board header. This is required, because the DH picoITX and DRC02 boards
require different settings than PDK2. The corresponding 'phy-handle'
device tree properties are already there.

I tested this change on picoITX and DRC02, but on PDK2 it is untested.

Reviewed-by: Marek Vasut <marex@denx.de>
Signed-off-by: Philip Oberfichtner <pro@denx.de>
---

(no changes since v1)

 include/configs/dh_imx6.h | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/include/configs/dh_imx6.h b/include/configs/dh_imx6.h
index 2b14464dff..178f5a6e7d 100644
--- a/include/configs/dh_imx6.h
+++ b/include/configs/dh_imx6.h
@@ -30,9 +30,6 @@
 /* Bootcounter */
 #define CONFIG_SYS_BOOTCOUNT_BE
 
-/* FEC ethernet */
-#define CONFIG_FEC_MXC_PHYADDR		7
-
 /* MMC Configs */
 #define CONFIG_SYS_FSL_ESDHC_ADDR	0
 #define CONFIG_SYS_FSL_USDHC_NUM	3
-- 
2.34.1


  parent reply	other threads:[~2022-05-20  8:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  8:46 [PATCH v2 0/8] ARM: imx: Add support for iMX6QDL DHCOM DRC02 and DH picoITX Philip Oberfichtner
2022-05-20  8:46 ` [PATCH v2 1/8] ARM: imx6: Fix broken DT path in DH board file Philip Oberfichtner
2022-05-20 13:41   ` sbabic
2022-05-20  8:46 ` [PATCH v2 2/8] ARM: dts: imx: Migrate iMX6QDL DRC02 DTs from Linux Philip Oberfichtner
2022-05-20 13:44   ` sbabic
2022-05-20  8:46 ` [PATCH v2 3/8] ARM: dts: imx: Migrate iMX6QDL picoITX " Philip Oberfichtner
2022-05-20 13:43   ` sbabic
2022-05-20  8:46 ` Philip Oberfichtner [this message]
2022-05-20 13:40   ` [PATCH v2 4/8] ARM: imx6: Remove CONFIG_FEC_MXC_PHYADDR from DH header sbabic
2022-05-20  8:46 ` [PATCH v2 5/8] ARM: dts: imx: Simplify fec node for iMX6QDL DHCOM boards Philip Oberfichtner
2022-05-20 13:43   ` sbabic
2022-05-20  8:46 ` [PATCH v2 6/8] ARM: dts: imx: Configure FEC for iMX6QDL picoITX Philip Oberfichtner
2022-05-20 13:40   ` sbabic
2022-05-20  8:46 ` [PATCH v2 7/8] ARM: dts: imx: Configure FEC for iMX6QDL DRC02 Philip Oberfichtner
2022-05-20 13:42   ` sbabic
2022-05-20  8:46 ` [PATCH v2 8/8] ARM: imx6: Adapt device tree selection in DH board file Philip Oberfichtner
2022-05-20 10:57   ` Marek Vasut
2022-05-20 13:43   ` sbabic
2022-05-20 11:33 ` [PATCH v2 0/8] ARM: imx: Add support for iMX6QDL DHCOM DRC02 and DH picoITX Fabio Estevam

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=20220520084626.656293-5-pro@denx.de \
    --to=pro@denx.de \
    --cc=ageisreiter@dh-electronics.de \
    --cc=cniedermaier@dh-electronics.com \
    --cc=festevam@denx.de \
    --cc=marex@denx.de \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@dh-electronics.com \
    --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