From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: jianxin.pan@amlogic.com, linux-amlogic@lists.infradead.org,
khilman@baylibre.com, ingrassia@epigenesys.com
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linus.luessing@c0d3.blue, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/1] Meson8b RGMII Ethernet pin cleanup
Date: Sat, 29 Dec 2018 01:08:28 +0100 [thread overview]
Message-ID: <20181229000829.16571-1-martin.blumenstingl@googlemail.com> (raw)
Hi Emiliano, Hi Linus, Hi Jianxin,
could you please test the patch from this series on your Odroid-C1?
I tested it on mine and Ethernet seems to be improve Ethernet transmit
speeds greatly (at the cost of a small drop in receive performance).
Jianxin, can you please give us the description for pin mux register 7
(PERIPHS_PIN_MUX_7) bits 22 and 23 on Meson8b (S805). The public
datasheet doesn't mention them so we're missing the name of the function
and the pin(s) which are controlled by each bit.
Changes since v1 at [0]:
- rebased so it applies on top of "ARM: dts: meson: meson8b: add the CPU
OPP tables" which will be part of v4.20-rc1 once the arm-soc tree is
merged into mainline
- updated patch description with more details
[0] http://lists.infradead.org/pipermail/linux-amlogic/2018-May/007274.html
Martin Blumenstingl (1):
ARM: dts: meson8b: drop eth_txd0_1 and eth_txd1_1 from eth_rgmii_pins
arch/arm/boot/dts/meson8b.dtsi | 2 --
1 file changed, 2 deletions(-)
--
2.20.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2018-12-29 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 0:08 Martin Blumenstingl [this message]
2018-12-29 0:08 ` [PATCH v2 1/1] ARM: dts: meson8b: drop eth_txd0_1 and eth_txd1_1 from eth_rgmii_pins Martin Blumenstingl
2018-12-29 5:18 ` [PATCH v2 0/1] Meson8b RGMII Ethernet pin cleanup Jianxin Pan
2018-12-29 12:25 ` Martin Blumenstingl
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=20181229000829.16571-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=ingrassia@epigenesys.com \
--cc=jianxin.pan@amlogic.com \
--cc=khilman@baylibre.com \
--cc=linus.luessing@c0d3.blue \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@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
all inboxes | Powered by JetHome®