From: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
To: linux-kernel@vger.kernel.org
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
kernel@esmil.dk, atish.patra@wdc.com, alistair.francis@wdc.com,
anup@brainfault.org, yash.shah@sifive.com, aou@eecs.berkeley.edu,
palmer@dabbelt.com, paul.walmsley@sifive.com, robh+dt@kernel.org,
Sagar Shrikant Kadam <sagar.kadam@sifive.com>
Subject: [PATCH v2 2/3] dts: phy: add GPIO number and active state used for phy reset
Date: Tue, 10 Nov 2020 07:22:11 -0800 [thread overview]
Message-ID: <1605021732-268521-3-git-send-email-sagar.kadam@sifive.com> (raw)
In-Reply-To: <1605021732-268521-1-git-send-email-sagar.kadam@sifive.com>
The GEMGXL_RST line on HiFive Unleashed is pulled low and is
using GPIO number 12. Add these reset-gpio details to dt-node
using which the linux phylib can reset the phy.
Signed-off-by: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
---
arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts b/arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts
index 60846e8..24d75a1 100644
--- a/arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts
+++ b/arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts
@@ -90,6 +90,7 @@
phy0: ethernet-phy@0 {
compatible = "ethernet-phy-id0007.0771";
reg = <0>;
+ reset-gpios = <&gpio 12 GPIO_ACTIVE_LOW>;
};
};
--
2.7.4
next prev parent reply other threads:[~2020-11-10 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 15:22 [PATCH v2 0/3] fix macb phy probe failure if phy-reset is not handled Sagar Shrikant Kadam
2020-11-10 15:22 ` [PATCH v2 1/3] dts: phy: fix missing mdio device and probe failure of vsc8541-01 device Sagar Shrikant Kadam
2020-11-10 15:22 ` Sagar Shrikant Kadam [this message]
2020-11-10 15:22 ` [PATCH v2 3/3] riscv: defconfig: enable gpio support for HiFive Unleashed Sagar Shrikant Kadam
2021-01-14 5:01 ` [PATCH v2 0/3] fix macb phy probe failure if phy-reset is not handled Palmer Dabbelt
2021-02-04 10:16 ` Andreas Schwab
2021-02-05 3:41 ` Palmer Dabbelt
2021-02-06 10:27 ` David Abdurachmanov
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=1605021732-268521-3-git-send-email-sagar.kadam@sifive.com \
--to=sagar.kadam@sifive.com \
--cc=alistair.francis@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=yash.shah@sifive.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).