From: Simon Horman <simon.horman@corigine.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, linux@armlinux.org.uk,
jarkko.nikula@linux.intel.com, olteanv@gmail.com,
andriy.shevchenko@linux.intel.com, hkallweit1@gmail.com,
linux-i2c@vger.kernel.org, linux-gpio@vger.kernel.org,
mengyuanlou@net-swift.com
Subject: Re: [PATCH net-next v4 8/8] net: txgbe: Support phylink MAC layer
Date: Sun, 23 Apr 2023 21:57:41 +0200 [thread overview]
Message-ID: <ZEWNtepnhsZp/HwW@corigine.com> (raw)
In-Reply-To: <20230422045621.360918-9-jiawenwu@trustnetic.com>
On Sat, Apr 22, 2023 at 12:56:21PM +0800, Jiawen Wu wrote:
> Add phylink support to Wangxun 10Gb Ethernet controller for the 10GBASE-R
> interface.
>
> Signed-off-by: Jiawen Wu <jiawenwu@trustnetic.com>
...
> +static int txgbe_phylink_init(struct txgbe *txgbe)
> +{
> + struct phylink_config *config;
> + struct fwnode_handle *fwnode;
> + struct wx *wx = txgbe->wx;
> + phy_interface_t phy_mode;
> + struct phylink *phylink;
> +
> + config = devm_kzalloc(&wx->pdev->dev, sizeof(*config), GFP_KERNEL);
> + if (!config)
> + return -ENOMEM;
> +
> + config->dev = &wx->netdev->dev;
> + config->type = PHYLINK_NETDEV;
> + config->mac_capabilities = MAC_10000FD | MAC_1000FD | MAC_SYM_PAUSE | MAC_ASYM_PAUSE;
> + phy_mode = PHY_INTERFACE_MODE_10GBASER;
> + __set_bit(PHY_INTERFACE_MODE_10GBASER, config->supported_interfaces);
> + fwnode = software_node_fwnode(txgbe->nodes.group[SWNODE_PHYLINK]);
> + phylink = phylink_create(config, fwnode, phy_mode, &txgbe_mac_ops);
> + if (IS_ERR(phylink))
> + return PTR_ERR(phylink);
> +
> + txgbe->phylink = phylink;
> +
> + return 0;
> +}
Hi Jiawen,
txgbe_phylink_init() seems unused.
Perhaps it needs to be wired-up somewhere?
next prev parent reply other threads:[~2023-04-23 19:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 4:56 [PATCH net-next v4 0/8] TXGBE PHYLINK support Jiawen Wu
2023-04-22 4:56 ` [PATCH net-next v4 1/8] net: txgbe: Add software nodes to support phylink Jiawen Wu
2023-04-23 19:47 ` Simon Horman
2023-04-22 4:56 ` [PATCH net-next v4 2/8] i2c: designware: Add driver support for Wangxun 10Gb NIC Jiawen Wu
2023-04-22 16:25 ` Andy Shevchenko
2023-04-23 2:31 ` Jiawen Wu
2023-04-24 13:28 ` 'Andy Shevchenko'
2023-04-24 2:39 ` Jiawen Wu
2023-04-25 14:08 ` Andi Shyti
2023-05-01 18:28 ` Andy Shevchenko
2023-04-22 4:56 ` [PATCH net-next v4 3/8] net: txgbe: Register I2C platform device Jiawen Wu
2023-04-25 15:06 ` Andi Shyti
2023-04-25 15:16 ` Andi Shyti
2023-04-22 4:56 ` [PATCH net-next v4 4/8] net: txgbe: Add SFP module identify Jiawen Wu
2023-04-22 4:56 ` [PATCH net-next v4 5/8] net: txgbe: Support GPIO to SFP socket Jiawen Wu
2023-04-22 4:56 ` [PATCH net-next v4 6/8] net: pcs: Add 10GBASE-R mode for Synopsys Designware XPCS Jiawen Wu
2023-05-02 8:01 ` Russell King (Oracle)
2023-04-22 4:56 ` [PATCH net-next v4 7/8] net: txgbe: Implement phylink pcs Jiawen Wu
2023-04-22 4:56 ` [PATCH net-next v4 8/8] net: txgbe: Support phylink MAC layer Jiawen Wu
2023-04-23 19:57 ` Simon Horman [this message]
2023-04-24 1:49 ` Jiawen Wu
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=ZEWNtepnhsZp/HwW@corigine.com \
--to=simon.horman@corigine.com \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hkallweit1@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jiawenwu@trustnetic.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@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