From: "Leonidas P. Papadakos" <papadakospan@gmail.com>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Jose Abreu <jose.abreu@synopsys.com>,
devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: improve rk3328-roc-cc rgmii performance.
Date: Fri, 07 Jun 2019 15:58:15 +0300 [thread overview]
Message-ID: <1559912295.22520.0@gmail.com> (raw)
In-Reply-To: <20190607123731.8737-1-pgwipeout@gmail.com>
I'll test on my board, but if in the end it does end up being a change
to both tx and rxpbl then we can replce the 2 tx/rxpbl options with
one, as far as I know:
snps,pbl = <0x4>;
WARNING: multiple messages have this Message-ID (diff)
From: "Leonidas P. Papadakos" <papadakospan@gmail.com>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Jose Abreu <jose.abreu@synopsys.com>,
devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: improve rk3328-roc-cc rgmii performance.
Date: Fri, 07 Jun 2019 15:58:15 +0300 [thread overview]
Message-ID: <1559912295.22520.0@gmail.com> (raw)
In-Reply-To: <20190607123731.8737-1-pgwipeout@gmail.com>
I'll test on my board, but if in the end it does end up being a change
to both tx and rxpbl then we can replce the 2 tx/rxpbl options with
one, as far as I know:
snps,pbl = <0x4>;
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-07 12:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 12:37 [PATCH] arm64: dts: rockchip: improve rk3328-roc-cc rgmii performance Peter Geis
2019-06-07 12:37 ` Peter Geis
2019-06-07 12:58 ` Leonidas P. Papadakos [this message]
2019-06-07 12:58 ` Leonidas P. Papadakos
[not found] ` <1559912295.22520.0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-06-07 23:07 ` Peter Geis
2019-06-07 23:07 ` Peter Geis
[not found] ` <CAMdYzYorvWr1YhmFKaMQUCditjop5AZp4d1tO79XsVr7m7HrMw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-14 9:39 ` Heiko Stuebner
2019-06-14 9:39 ` Heiko Stuebner
2019-06-14 19:49 ` Leonidas P. Papadakos
2019-06-14 19:49 ` Leonidas P. Papadakos
2019-06-14 21:27 ` Leonidas P. Papadakos
2019-06-14 21:27 ` Leonidas P. Papadakos
2019-06-15 12:12 ` Peter Geis
2019-06-15 12:12 ` Peter Geis
2019-06-15 13:32 ` Jonas Karlman
2019-06-15 13:32 ` Jonas Karlman
-- strict thread matches above, loose matches on Subject: below --
2019-06-26 13:04 Peter Geis
2019-06-26 13:04 ` Peter Geis
[not found] ` <20190626130443.22025-1-pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-06-26 22:22 ` Heiko Stuebner
2019-06-26 22:22 ` Heiko Stuebner
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=1559912295.22520.0@gmail.com \
--to=papadakospan@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jose.abreu@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.