From: Florian Fainelli <f.fainelli@gmail.com>
To: Jonathan Lemon <jonathan.lemon@gmail.com>,
bcm-kernel-feedback-list@broadcom.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk,
richardcochran@gmail.com
Cc: netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH net-next v1 2/4] net: phy: broadcom: Add Broadcom PTP hooks to bcm-phy-lib
Date: Sun, 24 Apr 2022 16:35:45 -0700 [thread overview]
Message-ID: <cf3bd081-25ed-8747-89d0-24ff5eab1870@gmail.com> (raw)
In-Reply-To: <20220424022356.587949-3-jonathan.lemon@gmail.com>
On 4/23/2022 7:23 PM, Jonathan Lemon wrote:
> Add the public bcm_ptp_probe() and bcm_ptp_config_init() functions
> to the bcm-phy library. The PTP functions are contained in a separate
> file for clarity, and also to simplify the PTP clock dependencies.
>
> Signed-off-by: Jonathan Lemon <jonathan.lemon@gmail.com>
> ---
> drivers/net/phy/bcm-phy-lib.c | 13 +++++++++++++
> drivers/net/phy/bcm-phy-lib.h | 3 +++
> 2 files changed, 16 insertions(+)
>
> diff --git a/drivers/net/phy/bcm-phy-lib.c b/drivers/net/phy/bcm-phy-lib.c
> index 287cccf8f7f4..b9d2d1d48402 100644
> --- a/drivers/net/phy/bcm-phy-lib.c
> +++ b/drivers/net/phy/bcm-phy-lib.c
> @@ -816,6 +816,19 @@ int bcm_phy_cable_test_get_status_rdb(struct phy_device *phydev,
> }
> EXPORT_SYMBOL_GPL(bcm_phy_cable_test_get_status_rdb);
>
> +#if !IS_ENABLED(CONFIG_BCM_NET_PHYPTP)
> +struct bcm_ptp_private *bcm_ptp_probe(struct phy_device *phydev)
> +{
> + return NULL;
> +}
> +EXPORT_SYMBOL_GPL(bcm_ptp_probe);
> +
> +void bcm_ptp_config_init(struct phy_device *phydev)
> +{
> +}
> +EXPORT_SYMBOL_GPL(bcm_ptp_config_init);
> +#endif
I would place those in bcm-phy-lib.h instead of in bcm-phy-lib.c and
have them be static inline stubs.
--
Florian
next prev parent reply other threads:[~2022-04-24 23:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 2:23 [PATCH net-next v1 0/4] Broadcom PTP PHY support Jonathan Lemon
2022-04-24 2:23 ` [PATCH net-next v1 1/4] net: phy: broadcom: Add PTP support for some Broadcom PHYs Jonathan Lemon
2022-04-24 23:27 ` Florian Fainelli
2022-04-25 23:53 ` Jonathan Lemon
2022-04-25 1:19 ` Richard Cochran
2022-04-25 23:30 ` Jonathan Lemon
2022-04-26 2:49 ` Richard Cochran
2022-04-26 3:02 ` Richard Cochran
2022-04-25 1:38 ` Richard Cochran
2022-04-25 23:55 ` Jonathan Lemon
2022-04-26 2:53 ` Richard Cochran
2022-04-26 18:02 ` Florian Fainelli
2022-04-25 3:12 ` Richard Cochran
2022-04-25 23:47 ` Jonathan Lemon
2022-04-27 14:40 ` Richard Cochran
2022-04-28 5:02 ` Jonathan Lemon
2022-04-24 2:23 ` [PATCH net-next v1 2/4] net: phy: broadcom: Add Broadcom PTP hooks to bcm-phy-lib Jonathan Lemon
2022-04-24 23:35 ` Florian Fainelli [this message]
2022-04-24 2:23 ` [PATCH net-next v1 3/4] net: phy: broadcom: Hook up the PTP PHY functions Jonathan Lemon
2022-04-24 23:29 ` Florian Fainelli
2022-04-24 2:23 ` [PATCH net-next v1 4/4] net: phy: Kconfig: Add broadcom PTP PHY library Jonathan Lemon
2022-04-24 23:29 ` Florian Fainelli
2022-04-25 1:01 ` [PATCH net-next v1 0/4] Broadcom PTP PHY support Richard Cochran
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=cf3bd081-25ed-8747-89d0-24ff5eab1870@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@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;
as well as URLs for NNTP newsgroup(s).