From: Andrew Lunn <andrew@lunn.ch>
To: Ong Boon Leong <boon.leong.ong@intel.com>
Cc: davem@davemloft.net, linux@armlinux.org.uk,
mcoquelin.stm32@gmail.com, joabreu@synopsys.com,
f.fainelli@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, peppe.cavallaro@st.com,
alexandre.torgue@st.com, weifeng.voon@intel.com
Subject: Re: [RFC net-next v2 3/5] net: phy: add private data to mdio_device
Date: Wed, 28 Aug 2019 20:06:47 +0200 [thread overview]
Message-ID: <20190828180647.GA17864@lunn.ch> (raw)
In-Reply-To: <20190828174722.6726-4-boon.leong.ong@intel.com>
On Thu, Aug 29, 2019 at 01:47:20AM +0800, Ong Boon Leong wrote:
> PHY converter device is represented as mdio_device and requires private
> data. So, we add pointer for private data to mdio_device struct.
Hi Ong
This was discussed recently with regard to the xilinx_gmii2rgmii.c
driver. You can use the usual dev_get_drvdata() to get private data
associated to the device. I did suggest adding wrappers, so you can
pass a phydev, or and mdiodev.
Andrew
next prev parent reply other threads:[~2019-08-28 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 17:47 [RFC net-next v2 0/5] PHY converter driver for DW xPCS IP Ong Boon Leong
2019-08-28 17:47 ` [RFC net-next v2 1/5] net: phy: make mdiobus_create_device() function callable from Eth driver Ong Boon Leong
2019-08-28 17:47 ` [RFC net-next v2 2/5] net: phy: introduce mdiobus_get_mdio_device Ong Boon Leong
2019-08-28 17:47 ` [RFC net-next v2 3/5] net: phy: add private data to mdio_device Ong Boon Leong
2019-08-28 18:06 ` Andrew Lunn [this message]
2019-08-28 17:47 ` [RFC net-next v2 4/5] net: phy: introducing support for DWC xPCS logics for EHL & TGL Ong Boon Leong
2019-09-06 13:28 ` Jose Abreu
2019-08-28 17:47 ` [RFC net-next v2 5/5] net: stmmac: add dwxpcs boardinfo for mdio_device registration Ong Boon Leong
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=20190828180647.GA17864@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexandre.torgue@st.com \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=joabreu@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=weifeng.voon@intel.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