netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: philippe.schenker@toradex.com
Cc: andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
	linux@armlinux.org.uk, netdev@vger.kernel.org,
	robh+dt@kernel.org, devicetree@vger.kernel.org,
	shawnguo@kernel.org, mark.rutland@arm.com,
	linux-kernel@vger.kernel.org, silvan.murer@gmail.com,
	a.fatoum@pengutronix.de, s.hauer@pengutronix.de,
	o.rempel@pengutronix.de
Subject: Re: [PATCH net-next v2 1/2] net: phy: micrel.c: add rgmii interface delay possibility to ksz9131
Date: Sun, 29 Mar 2020 21:44:36 -0700 (PDT)	[thread overview]
Message-ID: <20200329.214436.1632842454034665578.davem@davemloft.net> (raw)
In-Reply-To: <20200325173425.306802-1-philippe.schenker@toradex.com>

From: Philippe Schenker <philippe.schenker@toradex.com>
Date: Wed, 25 Mar 2020 18:34:24 +0100

> The KSZ9131 provides DLL controlled delays on RXC and TXC lines. This
> patch makes use of those delays. The information which delays should
> be enabled or disabled comes from the interface names, documented in
> ethernet-controller.yaml:
> 
> rgmii:      Disable RXC and TXC delays
> rgmii-id:   Enable RXC and TXC delays
> rgmii-txid: Enable only TXC delay, disable RXC delay
> rgmii-rxid: Enable onlx RXC delay, disable TXC delay
> 
> Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>

Applied.

      parent reply	other threads:[~2020-03-30  4:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 17:34 [PATCH net-next v2 1/2] net: phy: micrel.c: add rgmii interface delay possibility to ksz9131 Philippe Schenker
2020-03-25 17:34 ` [PATCH net-next v2 2/2] ARM: dts: apalis-imx6qdl: use rgmii-id instead of rgmii Philippe Schenker
2020-03-30  4:44   ` David Miller
2020-03-30  4:44 ` 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=20200329.214436.1632842454034665578.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=a.fatoum@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=philippe.schenker@toradex.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=silvan.murer@gmail.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 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).