From: Anand Moon <linux.amoon@gmail.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Cc: Neil Armstrong <narmstrong@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Kevin Hilman <khilman@baylibre.com>,
Anand Moon <linux.amoon@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Jerome Brunet <jbrunet@baylibre.com>
Subject: [PATCH v2 0/3] Add missing ethernet reset ID for Amlogic SoC
Date: Fri, 31 Jul 2020 08:20:40 +0000 [thread overview]
Message-ID: <20200731082043.1682-1-linux.amoon@gmail.com> (raw)
Add reset id for Ethernet to reset Ethernet IP.
Re-based on linux-next-20200730.
Could not test as their is build failed on linux-next-20200730.
My observation:
- Sometime the device on upgrade of the kernel
don't show up in the network.
- My observation that Ethernet interface come up successfully
but no packet get forwarded.
- This happens some times on my network.
-Anand
Anand Moon (3):
arm64: dts: amlogic: meson-gx: add missing ethernet reset ID
arm64: dts: amlogic: meson-axg: add missing ethernet reset ID
arm64: dts: amlogic: meson-g12: add missing ethernet reset ID
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 2 ++
arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 2 ++
arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 3 +++
3 files changed, 7 insertions(+)
--
2.28.0
:
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-07-31 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 8:20 Anand Moon [this message]
2020-07-31 8:20 ` [PATCH v2 1/3] arm64: dts: amlogic: meson-gx: add missing ethernet reset ID Anand Moon
2020-07-31 8:20 ` [PATCH v2 2/3] arm64: dts: amlogic: meson-axg: " Anand Moon
2020-07-31 8:20 ` [PATCH v2 3/3] arm64: dts: amlogic: meson-g12: " Anand Moon
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=20200731082043.1682-1-linux.amoon@gmail.com \
--to=linux.amoon@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).