linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] net-next: stmmac: dwmac-sun8i: add support for V3s
Date: Tue, 20 Jun 2017 13:23:23 -0400 (EDT)	[thread overview]
Message-ID: <20170620.132323.46663908524667004.davem@davemloft.net> (raw)
In-Reply-To: <20170617140737.41951-1-icenowy@aosc.io>

From: Icenowy Zheng <icenowy@aosc.io>
Date: Sat, 17 Jun 2017 22:07:33 +0800

> Allwinner V3s features an EMAC like the on in H3, but without external MII
> interfaces, so being not able really to use RMII/RGMII.
> 
> And it has a different default value of syscon (0x38000 instead of 0x58000
> on H3), which shows a problem that the EMAC clock freq should be 24MHz.
> (Both H3 and V3s SoCs doesn't have extra xtal input for EPHY, and the
> main xtal is 24MHz. The default value of H3 is set to 24MHz, but the V3s
> default value is set to 25MHz).
> 
> First two patches are device tree binding patches, the third forces
> the frequency to 24MHz and the fourth really add the V3s support.

Series applied to net-next, thanks!

      parent reply	other threads:[~2017-06-20 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-17 14:07 [PATCH 0/4] net-next: stmmac: dwmac-sun8i: add support for V3s Icenowy Zheng
2017-06-17 14:07 ` [PATCH 1/4] dt-bindings: net-next: Add DT bindings documentation for Allwinner V3s EMAC Icenowy Zheng
2017-06-17 14:07 ` [PATCH 2/4] dt-bindings: syscon: Add DT bindings documentation for Allwinner V3s syscon Icenowy Zheng
2017-06-17 14:07 ` [PATCH 3/4] net-next: stmmac: dwmac-sun8i: force EPHY clock freq to 24MHz Icenowy Zheng
2017-06-17 14:07 ` [PATCH 4/4] net-next: stmmac: dwmac-sun8i: add support for V3s EMAC Icenowy Zheng
2017-06-20 17:23 ` David Miller [this message]

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=20170620.132323.46663908524667004.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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;
as well as URLs for NNTP newsgroup(s).