linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Wang <sean.wang@kernel.org>
To: biao.huang@mediatek.com
Cc: davem@davemloft.net, robh+dt@kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org, nelson.chang@mediatek.com,
	andrew@lunn.ch, netdev@vger.kernel.org, liguo.zhang@mediatek.com,
	linux-kernel@vger.kernel.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	joabreu@synopsys.com, linux-mediatek@lists.infradead.org,
	honghui.zhang@mediatek.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [v3, PATCH 2/2] dt-binding: mediatek-dwmac: add binding document for MediaTek MT2712 DWMAC
Date: Fri, 16 Nov 2018 16:21:15 -0800	[thread overview]
Message-ID: <CAGp9LzrHm-ympV2zAKZKcEfA25aJp8BSS+=01B6G=sP_HiSSdA@mail.gmail.com> (raw)
In-Reply-To: <1542359926-28800-2-git-send-email-biao.huang@mediatek.com>

On Fri, Nov 16, 2018 at 1:19 AM Biao Huang <biao.huang@mediatek.com> wrote:
>
> The commit adds the device tree binding documentation for the MediaTek DWMAC
> found on MediaTek MT2712.
>
> Change-Id: I3728666bf65927164bd82fa8dddb90df8270bd44

Drop change-id

> Signed-off-by: Biao Huang <biao.huang@mediatek.com>
> ---
>  .../devicetree/bindings/net/mediatek-dwmac.txt     |   77 ++++++++++++++++++++
>  1 file changed, 77 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/net/mediatek-dwmac.txt
>
> diff --git a/Documentation/devicetree/bindings/net/mediatek-dwmac.txt b/Documentation/devicetree/bindings/net/mediatek-dwmac.txt
> new file mode 100644
> index 0000000..7fd56e0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/mediatek-dwmac.txt
> @@ -0,0 +1,77 @@
> +MediaTek DWMAC glue layer controller
> +
> +This file documents platform glue layer for stmmac.
> +Please see stmmac.txt for the other unchanged properties.
> +
> +The device node has following properties.
> +
> +Required properties:
> +- compatible:  Should be "mediatek,mt2712-gmac" for MT2712 SoC
> +- reg:  Address and length of the register set for the device
> +- interrupts:  Should contain the MAC interrupts
> +- interrupt-names: Should contain a list of interrupt names corresponding to
> +       the interrupts in the interrupts property, if available.
> +       Should be "macirq" for the main MAC IRQ
> +- clocks: Must contain a phandle for each entry in clock-names.
> +- clock-names: The name of the clock listed in the clocks property. These are
> +       "axi", "apb", "mac_ext", "mac_parent", "ptp_ref", "ptp_parent", "ptp_top"
> +       for MT2712 SoC

About not including these parent clocks to the controller, you can
refer to assigned-clocks, assigned-clock-parents, assigned-clock-rates
noted in Documentation/devicetree/bindings/clock/clock-bindings.txt to
determine what speed these MUXs should be run at and see [1] as the
example how applied in dts.

[1]
https://elixir.bootlin.com/linux/latest/source/arch/arm/boot/dts/mt7623.dtsi#L660

> +- mac-address: See ethernet.txt in the same directory
> +- phy-mode: See ethernet.txt in the same directory
> +
> +Optional properties:
> +- tx-delay: TX clock delay macro value. Range is 0~31. Default is 0.
> +       It should be defined for rgmii/rgmii-rxid/mii interface.
> +- rx-delay: RX clock delay macro value. Range is 0~31. Default is 0.
> +       It should be defined for rgmii/rgmii-txid/mii/rmii interface.
> +- fine-tune: This property will select coarse-tune delay or fine delay
> +       for rgmii interface.
what is the property's type?

> +       If fine-tune delay is enabled, tx-delay/rx-delay is 170+/-50ps
> +       per stage.
> +       Else coarse-tune delay is enabled, tx-delay/rx-delay is 0.55+/-0.2ns
> +       per stage.
> +       This property do not apply to non-rgmii PHYs.
> +       Only coarse-tune delay is supported for mii/rmii PHYs.
> +- rmii-rxc: Reference clock of rmii is from external PHYs,
what is the property's type?

> +       and it can be connected to TXC or RXC pin on MT2712 SoC.
> +       If ref_clk <--> TXC, disable it.
> +       Else ref_clk <--> RXC, enable it.
> +- txc-inverse: Inverse tx clock for mii/rgmii.
what is the property's type?

> +       Inverse tx clock inside MAC relative to reference clock for rmii,
> +       and it rarely happen.
> +- rxc-inverse: Inverse rx clock for mii/rgmii interfaces.
what is the property's type?

> +       Inverse reference clock for rmii.

If these optional properties look like generic enough, it would be
good that place them to stmmac.txt. Otherwise, they should be added
"mediatek," as the prefix string for these vendor-specific things.

> +
> +Example:
> +       eth: ethernet@1101c000 {
> +               compatible = "mediatek,mt2712-gmac";
> +               reg = <0 0x1101c000 0 0x1300>;
> +               interrupts = <GIC_SPI 237 IRQ_TYPE_LEVEL_LOW>;
> +               interrupt-names = "macirq";
> +               phy-mode ="rgmii-id";
> +               mac-address = [00 55 7b b5 7d f7];
> +               clock-names = "axi",
> +                             "apb",
> +                             "mac_ext",
> +                             "mac_parent",
> +                             "ptp_ref",
> +                             "ptp_parent",
> +                             "ptp_top";
> +               clocks = <&pericfg CLK_PERI_GMAC>,
> +                        <&pericfg CLK_PERI_GMAC_PCLK>,
> +                        <&topckgen CLK_TOP_ETHER_125M_SEL>,
> +                        <&topckgen CLK_TOP_ETHERPLL_125M>,
> +                        <&topckgen CLK_TOP_ETHER_50M_SEL>,
> +                        <&topckgen CLK_TOP_APLL1_D3>,
> +                        <&topckgen CLK_TOP_APLL1>;
> +               snps,txpbl = <32>;
> +               snps,rxpbl = <32>;
> +               snps,reset-gpio = <&pio 87 GPIO_ACTIVE_LOW>;
> +               snps,reset-active-low;
> +               tx-delay = <9>;
> +               rx-delay = <9>;
> +               fine-tune;
> +               rmii-rxc;
> +               txc-inverse;
> +               rxc-inverse;
> +       };
> --
> 1.7.9.5
>
>
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek

  reply	other threads:[~2018-11-17  0:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16  9:18 [v3, PATCH 1/2] net:stmmac: dwmac-mediatek: add support for mt2712 Biao Huang
2018-11-16  9:18 ` [v3, PATCH 2/2] dt-binding: mediatek-dwmac: add binding document for MediaTek MT2712 DWMAC Biao Huang
2018-11-17  0:21   ` Sean Wang [this message]
2018-11-19  2:12     ` biao huang
2018-11-17 14:56   ` Rob Herring
2018-11-19  2:51     ` biao huang
2018-11-17  1:03 ` [v3, PATCH 1/2] net:stmmac: dwmac-mediatek: add support for mt2712 Sean Wang
2018-11-19  2:38   ` biao huang

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='CAGp9LzrHm-ympV2zAKZKcEfA25aJp8BSS+=01B6G=sP_HiSSdA@mail.gmail.com' \
    --to=sean.wang@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=biao.huang@mediatek.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=honghui.zhang@mediatek.com \
    --cc=joabreu@synopsys.com \
    --cc=liguo.zhang@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=nelson.chang@mediatek.com \
    --cc=netdev@vger.kernel.org \
    --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).