netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Marek Vasut <marex@denx.de>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com
Subject: Re: [PATCH] net: phy: tja11xx: Add TJA11xx PHY driver
Date: Thu, 13 Dec 2018 09:38:12 +0100	[thread overview]
Message-ID: <20181213083812.GA1605@lunn.ch> (raw)
In-Reply-To: <20181213020150.17099-1-marex@denx.de>

> +static int tja11xx_config_aneg(struct phy_device *phydev)
> +{
> +	phydev->autoneg = 0;
> +	phydev->speed = SPEED_100;
> +	phydev->duplex = DUPLEX_FULL;
> +	phydev->pause = 0;
> +	phydev->asym_pause = 0;
> +
> +	return 0;
> +}

Hi Marek

That is, err, interesting. Are you saying the PHY cannot do auto-neg?

Does it happen to be a 100T1 device for automotive?

> +
> +static int tja11xx_config_init(struct phy_device *phydev)
> +{
> +	u32 features = SUPPORTED_TP | SUPPORTED_MII | SUPPORTED_100baseT_Full;
> +	int ret;
> +
> +	ret = tja11xx_enable_reg_write(phydev);
> +	if (ret)
> +		return ret;
> +
> +	phydev->supported &= features;
> +	phydev->advertising &= features;

What tree is this code based on? I doubt it is net-next. Please rebase
and fix up all the things that then break.

    Thanks
	Andrew

  parent reply	other threads:[~2018-12-13  8:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13  2:01 [PATCH] net: phy: tja11xx: Add TJA11xx PHY driver Marek Vasut
2018-12-13  3:49 ` Yunsheng Lin
2018-12-13  4:06   ` Marek Vasut
2018-12-13  8:38 ` Andrew Lunn [this message]
2018-12-13 13:27   ` Marek Vasut
2018-12-13 14:33     ` Andrew Lunn
2018-12-13 16:43       ` Marek Vasut
2018-12-14  8:23         ` Andrew Lunn
2018-12-14 15:44           ` Marek Vasut
2018-12-14 20:19             ` Andrew Lunn
2018-12-14 20:46               ` Marek Vasut
2018-12-13 18:53 ` Florian Fainelli
2018-12-14 15:26   ` Marek Vasut

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=20181213083812.GA1605@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=marex@denx.de \
    --cc=netdev@vger.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).