From: Arnd Bergmann <arnd@arndb.de>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: netdev@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
devicetree@vger.kernel.org,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] net: phy: micrel: Add KSZ8041FTL fiber mode support
Date: Thu, 14 Jul 2016 16:33:26 +0200 [thread overview]
Message-ID: <7346758.UKW3x0KYDY@wuerfel> (raw)
In-Reply-To: <1468506583-27299-1-git-send-email-p.zabel@pengutronix.de>
On Thursday, July 14, 2016 4:29:43 PM CEST Philipp Zabel wrote:
> +
> + - micrel,fiber-mode: If present the PHY is configured to operate in fiber mode
> +
> + Some PHYs, such as the KSZ8041FTL variant, support fiber mode, enabled
> + by the FXEN boot strapping pin. It can't be determined from the PHY
> + registers whether the PHY is in fiber mode, so this boolean device tree
> + property can be used to describe it.
> +
> + In fiber mode, auto-negotiation is disabled and the PHY can only work in
> + 100base-fx (full and half duplex) modes.
>
Could the generic "phy-mode" property used for this, to avoid the need for
definingn a custom property?
Arnd
next prev parent reply other threads:[~2016-07-14 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 14:29 [PATCH] net: phy: micrel: Add KSZ8041FTL fiber mode support Philipp Zabel
2016-07-14 14:33 ` Arnd Bergmann [this message]
2016-07-14 14:46 ` Philipp Zabel
2016-07-14 15:15 ` Andrew Lunn
2016-07-14 15:15 ` Arnd Bergmann
2016-07-15 18:53 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2016-07-14 10:18 Philipp Zabel
2016-07-14 11:35 ` Sergei Shtylyov
2016-07-14 13:16 ` Philipp Zabel
[not found] ` <1468491528-17515-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-07-14 13:37 ` Andrew Lunn
[not found] ` <20160714133706.GF6667-g2DYL2Zd6BY@public.gmane.org>
2016-07-14 13:51 ` Philipp Zabel
2016-07-14 14:32 ` Andrew Lunn
2016-07-14 15:13 ` Andrew Lunn
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=7346758.UKW3x0KYDY@wuerfel \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=geert@linux-m68k.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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