From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stanley Chang <stanley_chang@realtek.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
"Johan Hovold" <johan@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Jinjie Ruan" <ruanjinjie@huawei.com>,
"Rob Herring" <robh@kernel.org>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Flavio Suligoi" <f.suligoi@asem.it>,
"Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 RESEND 1/4] phy: core: add notify_connect and notify_disconnect callback
Date: Thu, 7 Dec 2023 11:02:43 +0100 [thread overview]
Message-ID: <2023120750-giggle-annotate-dc4f@gregkh> (raw)
In-Reply-To: <20231207074022.14116-1-stanley_chang@realtek.com>
On Thu, Dec 07, 2023 at 03:38:04PM +0800, Stanley Chang wrote:
> In Realtek SoC, the parameter of usb phy is designed to can dynamic
> tuning base on port status. Therefore, add a notify callback of phy
> driver when usb connection/disconnection change.
>
> Signed-off-by: Stanley Chang <stanley_chang@realtek.com>
> ---
> RESEND:
> Because there is no extcon device provided in the USB framework to
> notify connect and disconnect.
> Therefore, I added the notification connection/disconnection based
> on the generic phy. So I no use the EXTCON framework for notifying
> connect/disconnect.
> v2 to v3:
> No change
> v1 to v2:
> No change
> ---
> drivers/phy/phy-core.c | 47 +++++++++++++++++++++++++++++++++++++++++
> include/linux/phy/phy.h | 18 ++++++++++++++++
> 2 files changed, 65 insertions(+)
>
> diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
> index 96a0b1e111f3..a84ad4896b7f 100644
> --- a/drivers/phy/phy-core.c
> +++ b/drivers/phy/phy-core.c
> @@ -489,6 +489,53 @@ int phy_calibrate(struct phy *phy)
> }
> EXPORT_SYMBOL_GPL(phy_calibrate);
>
> +/**
> + * phy_notify_connect() - phy connect notify
> + * @phy: the phy returned by phy_get()
> + * @port: the port index for connect
> + *
> + * If phy need the get connection status, the callback can be used.
> + * Returns: %0 if successful, a negative error code otherwise
> + */
> +int phy_notify_connect(struct phy *phy, int port)
> +{
> + int ret;
> +
> + if (!phy || !phy->ops->connect)
> + return 0;
How can phy be null?
And it is not successful if connect is not valid, so why not return an
error there?
> +
> + mutex_lock(&phy->mutex);
> + ret = phy->ops->connect(phy, port);
> + mutex_unlock(&phy->mutex);
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(phy_notify_connect);
> +
> +/**
> + * phy_notify_disconnect() - phy disconnect notify
> + * @phy: the phy returned by phy_get()
> + * @port: the port index for disconnect
> + *
> + * If phy need the get disconnection status, the callback can be used.
> + *
> + * Returns: %0 if successful, a negative error code otherwise
> + */
> +int phy_notify_disconnect(struct phy *phy, int port)
> +{
> + int ret;
> +
> + if (!phy || !phy->ops->disconnect)
> + return 0;
Same as above.
> +
> + mutex_lock(&phy->mutex);
> + ret = phy->ops->disconnect(phy, port);
> + mutex_unlock(&phy->mutex);
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(phy_notify_disconnect);
> +
> /**
> * phy_configure() - Changes the phy parameters
> * @phy: the phy returned by phy_get()
> diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
> index f6d607ef0e80..cf98cb29ddaa 100644
> --- a/include/linux/phy/phy.h
> +++ b/include/linux/phy/phy.h
> @@ -122,6 +122,8 @@ struct phy_ops {
> union phy_configure_opts *opts);
> int (*reset)(struct phy *phy);
> int (*calibrate)(struct phy *phy);
> + int (*connect)(struct phy *phy, int port);
> + int (*disconnect)(struct phy *phy, int port);
You forgot to document these and would have a warning from the
documentation build if this was applied :(
> void (*release)(struct phy *phy);
> struct module *owner;
> };
> @@ -243,6 +245,8 @@ static inline enum phy_mode phy_get_mode(struct phy *phy)
> }
> int phy_reset(struct phy *phy);
> int phy_calibrate(struct phy *phy);
> +int phy_notify_connect(struct phy *phy, int port);
> +int phy_notify_disconnect(struct phy *phy, int port);
> static inline int phy_get_bus_width(struct phy *phy)
> {
> return phy->attrs.bus_width;
> @@ -396,6 +400,20 @@ static inline int phy_calibrate(struct phy *phy)
> return -ENOSYS;
> }
>
> +static inline int phy_notify_connect(struct phy *phy, int index)
> +{
> + if (!phy)
> + return 0;
Why check this?
> + return -ENOSYS;
> +}
> +
> +static inline int phy_notify_disconnect(struct phy *phy, int index)
> +{
> + if (!phy)
> + return 0;
Again, why check this?
thanks,
greg k-h
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2023-12-07 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231207074022.14116-1-stanley_chang@realtek.com>
2023-12-07 8:54 ` [PATCH v3 RESEND 1/4] phy: core: add notify_connect and notify_disconnect callback Sergei Shtylyov
2023-12-07 10:02 ` Greg Kroah-Hartman [this message]
[not found] ` <20231207074022.14116-4-stanley_chang@realtek.com>
2023-12-07 10:08 ` [PATCH v3 RESEND 4/4] usb: core: add phy notify connect and disconnect Greg Kroah-Hartman
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=2023120750-giggle-annotate-dc4f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=f.suligoi@asem.it \
--cc=geert+renesas@glider.be \
--cc=heikki.krogerus@linux.intel.com \
--cc=johan@kernel.org \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=ricardo.canuelo@collabora.com \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=stanley_chang@realtek.com \
--cc=stern@rowland.harvard.edu \
--cc=vkoul@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).