Re: [PATCH net-next 2/2] net: phy: dp83td510: Add support for the DP83TD510 Ethernet PHY

[Dan Murphy]

Heiner

On 10/8/20 11:51 AM, Heiner Kallweit wrote:
> On 08.10.2020 18:23, Dan Murphy wrote:
> > The DP83TD510E is an ultra-low power Ethernet physical layer transceiver
> > that supports 10M single pair cable.
> >
> > The device supports both 2.4-V p2p and 1-V p2p output voltage as defined
> > by IEEE 802.3cg 10Base-T1L specfications. These modes can be forced via
> > the device tree or the device is defaulted to auto negotiation to
> > determine the proper p2p voltage.
> >
> > Signed-off-by: Dan Murphy <dmurphy@xxxxxx>
> > ---
> >   drivers/net/phy/Kconfig     |   6 +

<snip>


> > +static struct phy_driver dp83td510_driver[] = {
> > +	{
> > +		PHY_ID_MATCH_MODEL(DP83TD510E_PHY_ID),
> > +		.name		= "TI DP83TD510E",
> > +		.probe          = dp83td510_probe,
> > +		.config_init	= dp83td510_config_init,
> > +		.soft_reset	= dp83td510_phy_reset,
> > +		.features	= PHY_BASIC_FEATURES,
> Per default phylib uses genphy_read_abilities() to auto-detect
> the features. Doesn't your PHY support the needed clause 22
> standard registers? Or are they incorrectly populated?
>
> Maybe better than setting PHY_BASIC_FEATURES and then removing
> unsuported features in dp83td510_config_init() would be to
> implement phy_driver callback get_features. Then you can set
> the supported fatures directly.
Thanks for the review.  I will have to look at this maybe the call back 
will be better.

I will probably post v2 after net-next opens for 5.10.

I wanted to get some reviews on this patch before net-next closes for 
the merge window.

Dan