From: Andrew Lunn <andrew@lunn.ch>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>, Dan Murphy <dmurphy@ti.com>,
kernel@pengutronix.de, David Jander <david@protonic.nl>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH net-next v1 1/1] net: phy: dp83td510: Add basic support for the DP83TD510 Ethernet PHY
Date: Mon, 26 Jul 2021 15:23:00 +0200 [thread overview]
Message-ID: <YP63NBaurhQ2Itse@lunn.ch> (raw)
In-Reply-To: <20210726121851.u3flif2opshwgz5e@pengutronix.de>
> With current driver ethtool with show this information:
> Settings for eth1:
> Supported ports: [ TP MII ]
> Supported link modes: Not reported
Interesting. The default function for getting the PHYs abilities is
doing better than i expected. I was guessing you would see 10BaseT
here.
Given that, what you have is O.K. for the moment.
> > I suspect you are talking about the PoE aspects. That is outside the
> > scope for phylib. PoE in general is not really supported in the Linux
> > kernel, and probably needs a subsystem of its own.
>
> No, no. I'm talking about data signals configuration (2.4Vpp/1Vpp), which
> depends on application and cable length. 1Vpp should not be used with
> cable over 200 meter
Should not be used, or is not expected to work very well?
> and 2.4Vpp should not be used on safety critical applications.
Please work with the other T1L driver writer to propose a suitable way
to configure this. We want all T1L drivers to use the same
configuration method, DT properties etc.
Andrew
next prev parent reply other threads:[~2021-07-26 13:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 10:42 [PATCH net-next v1 1/1] net: phy: dp83td510: Add basic support for the DP83TD510 Ethernet PHY Oleksij Rempel
2021-07-23 13:22 ` Andrew Lunn
2021-07-23 17:08 ` Oleksij Rempel
2021-07-23 18:12 ` Andrew Lunn
2021-07-26 12:18 ` Oleksij Rempel
2021-07-26 13:23 ` Andrew Lunn [this message]
2021-07-27 6:51 ` Oleksij Rempel
2021-07-24 0:56 ` kernel test robot
2021-07-24 0:56 ` kernel test robot
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=YP63NBaurhQ2Itse@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=david@protonic.nl \
--cc=dmurphy@ti.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.