From: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
To: Andrew Andrianov <andrew-g16cbSVCqPUdnm+yROfE0A@public.gmane.org>
Cc: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
Gregory Clement
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 0/1] ARM: mvebu: dts: Add dts file for DLink DNS-327L
Date: Sun, 3 May 2015 22:50:43 +0200 [thread overview]
Message-ID: <20150503205043.GA23342@lunn.ch> (raw)
In-Reply-To: <1430663256-22714-1-git-send-email-andrew-g16cbSVCqPUdnm+yROfE0A@public.gmane.org>
Hi Andrew
> DNS-327L is a 2-bay NAS with the following specs:
> - 512MiB RAM
> - 128MiB NAND Flash
> - 1 GbE interface (Marvell PHY)
...
> /* Set RGMII voltage to 1.8v, according to public docs. Nice! */
> mw.l 0xd00184e0 0xa8a;
> /* Some weird magic that goes into phy registers, no public docs */
> phyWrite 0 16 2;
> phyWrite 0 19 77;
> phyWrite 0 18 5747;
Take a look at the marvell,reg-init property. Might do what you need.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-03 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 14:27 [PATCH v3 0/1] ARM: mvebu: dts: Add dts file for DLink DNS-327L Andrew Andrianov
[not found] ` <1430663256-22714-1-git-send-email-andrew-g16cbSVCqPUdnm+yROfE0A@public.gmane.org>
2015-05-03 14:27 ` [PATCH v3 1/1] " Andrew Andrianov
2015-05-03 20:50 ` Andrew Lunn [this message]
[not found] ` <20150503205043.GA23342-g2DYL2Zd6BY@public.gmane.org>
2015-05-03 22:05 ` [PATCH v3 0/1] " Andrew
[not found] ` <ad0fbb28b4b74de4c6685a5ddd21010c-IcawJbj+vY1vZ+LtbKW8tg@public.gmane.org>
2015-05-06 14:05 ` Andrew Lunn
[not found] ` <20150506140534.GC10890-g2DYL2Zd6BY@public.gmane.org>
2015-05-19 21:10 ` [PATCH v4 " Andrew Andrianov
2015-05-19 21:10 ` [PATCH v4 1/1] " Andrew Andrianov
[not found] ` <1432069858-10958-2-git-send-email-andrew-g16cbSVCqPUdnm+yROfE0A@public.gmane.org>
2015-05-20 9:05 ` Sebastian Hesselbarth
2015-05-20 10:20 ` Andrew
[not found] ` <699cee8678f6e671bd1457aa06180ccf-IcawJbj+vY1vZ+LtbKW8tg@public.gmane.org>
2015-05-20 11:00 ` Sebastian Hesselbarth
2015-05-25 11:17 ` Gregory CLEMENT
2015-05-26 15:51 ` [PATCH v5 0/1] " Andrew Andrianov
2015-05-26 15:51 ` [PATCH v5 1/1] " Andrew Andrianov
[not found] ` <1432655471-16212-2-git-send-email-andrew-g16cbSVCqPUdnm+yROfE0A@public.gmane.org>
2015-05-26 15:50 ` Andrew Lunn
2015-05-27 10:01 ` Gregory CLEMENT
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=20150503205043.GA23342@lunn.ch \
--to=andrew-g2dyl2zd6by@public.gmane.org \
--cc=andrew-g16cbSVCqPUdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).