From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 3/3] ARM: nitrogen6: remove hard coded values
Date: Tue, 3 Mar 2020 18:46:16 +0100 [thread overview]
Message-ID: <20200303174616.4476-3-m.felsch@pengutronix.de> (raw)
In-Reply-To: <20200303174616.4476-1-m.felsch@pengutronix.de>
Since commit c3f5ce7308 ("net: phy: micrel: Add support for specifying pad
skew values") and commit 2720a02e8a ("net: phy: micrel: backport finding
PHY properties") the phy driver can handle this taking the DT specified
values into account. Those values are exactly the same as the ones
specified here.
Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
arch/arm/boards/boundarydevices-nitrogen6/board.c | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/arch/arm/boards/boundarydevices-nitrogen6/board.c b/arch/arm/boards/boundarydevices-nitrogen6/board.c
index d9514d9d48..8c565c74a0 100644
--- a/arch/arm/boards/boundarydevices-nitrogen6/board.c
+++ b/arch/arm/boards/boundarydevices-nitrogen6/board.c
@@ -43,16 +43,6 @@ static int ksz9021rn_phy_fixup(struct phy_device *dev)
{
phy_write(dev, 0x09, 0x0f00);
- /* do same as linux kernel */
- /* min rx data delay */
- phy_write(dev, 0x0b, 0x8105);
- phy_write(dev, 0x0c, 0x0000);
-
- /* max rx/tx clock delay, min rx/tx control delay */
- phy_write(dev, 0x0b, 0x8104);
- phy_write(dev, 0x0c, 0xf0f0);
- phy_write(dev, 0x0b, 0x104);
-
return 0;
}
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-03-03 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 17:46 [PATCH 1/3] ARM: nitrogen6x: add phy reset timings Marco Felsch
2020-03-03 17:46 ` [PATCH 2/3] net: phy: micrel: backport finding PHY properties Marco Felsch
2020-03-09 7:28 ` Sascha Hauer
2020-03-03 17:46 ` Marco Felsch [this message]
2020-03-06 16:06 ` [PATCH 3/3] ARM: nitrogen6: remove hard coded values Stefan Lengfeld
2020-03-09 6:32 ` Marco Felsch
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=20200303174616.4476-3-m.felsch@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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