From: Kishon Vijay Abraham I <kishon@ti.com>
To: Vivek Gautam <vivek.gautam@codeaurora.org>,
jejb@linux.vnet.ibm.com, vinholikatti@gmail.com,
martin.petersen@oracle.com, linux-kernel@vger.kernel.org
Cc: subhashj@codeaurora.org, linux-scsi@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 04/10] phy: qcom-ufs-qmp-xx: Discard remove callback for drivers.
Date: Thu, 27 Oct 2016 01:50:46 +0530 [thread overview]
Message-ID: <35ce06b5-8d80-57b4-1c27-4be57be1ecbc@ti.com> (raw)
In-Reply-To: <1476800897-19898-5-git-send-email-vivek.gautam@codeaurora.org>
On Tuesday 18 October 2016 07:58 PM, Vivek Gautam wrote:
> remove() callback does a phy_exit() only and nothing else now.
remove callback calls a phy_power_off() ;-)
-Kishon
> The phy_exit() over the generic phy is called from the phy
> consumer, and phy provider driver should not explicitly need to
> call any phy_exit().
> So discard the remove callback for qcom-ufs phy platform drivers.
>
> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
> Reviewed-by: Subhash Jadavani <subhashj@codeaurora.org>
> ---
>
> No change since v1.
>
> drivers/phy/phy-qcom-ufs-qmp-14nm.c | 16 ----------------
> drivers/phy/phy-qcom-ufs-qmp-20nm.c | 16 ----------------
> drivers/phy/phy-qcom-ufs.c | 9 ---------
> 3 files changed, 41 deletions(-)
>
> diff --git a/drivers/phy/phy-qcom-ufs-qmp-14nm.c b/drivers/phy/phy-qcom-ufs-qmp-14nm.c
> index 6ee5149..a305016 100644
> --- a/drivers/phy/phy-qcom-ufs-qmp-14nm.c
> +++ b/drivers/phy/phy-qcom-ufs-qmp-14nm.c
> @@ -163,21 +163,6 @@ out:
> return err;
> }
>
> -static int ufs_qcom_phy_qmp_14nm_remove(struct platform_device *pdev)
> -{
> - struct device *dev = &pdev->dev;
> - struct phy *generic_phy = to_phy(dev);
> - struct ufs_qcom_phy *ufs_qcom_phy = get_ufs_qcom_phy(generic_phy);
> - int err = 0;
> -
> - err = ufs_qcom_phy_remove(generic_phy, ufs_qcom_phy);
> - if (err)
> - dev_err(dev, "%s: ufs_qcom_phy_remove failed = %d\n",
> - __func__, err);
> -
> - return err;
> -}
> -
> static const struct of_device_id ufs_qcom_phy_qmp_14nm_of_match[] = {
> {.compatible = "qcom,ufs-phy-qmp-14nm"},
> {},
> @@ -186,7 +171,6 @@ MODULE_DEVICE_TABLE(of, ufs_qcom_phy_qmp_14nm_of_match);
>
> static struct platform_driver ufs_qcom_phy_qmp_14nm_driver = {
> .probe = ufs_qcom_phy_qmp_14nm_probe,
> - .remove = ufs_qcom_phy_qmp_14nm_remove,
> .driver = {
> .of_match_table = ufs_qcom_phy_qmp_14nm_of_match,
> .name = "ufs_qcom_phy_qmp_14nm",
> diff --git a/drivers/phy/phy-qcom-ufs-qmp-20nm.c b/drivers/phy/phy-qcom-ufs-qmp-20nm.c
> index 770087a..2db1fbb 100644
> --- a/drivers/phy/phy-qcom-ufs-qmp-20nm.c
> +++ b/drivers/phy/phy-qcom-ufs-qmp-20nm.c
> @@ -219,21 +219,6 @@ out:
> return err;
> }
>
> -static int ufs_qcom_phy_qmp_20nm_remove(struct platform_device *pdev)
> -{
> - struct device *dev = &pdev->dev;
> - struct phy *generic_phy = to_phy(dev);
> - struct ufs_qcom_phy *ufs_qcom_phy = get_ufs_qcom_phy(generic_phy);
> - int err = 0;
> -
> - err = ufs_qcom_phy_remove(generic_phy, ufs_qcom_phy);
> - if (err)
> - dev_err(dev, "%s: ufs_qcom_phy_remove failed = %d\n",
> - __func__, err);
> -
> - return err;
> -}
> -
> static const struct of_device_id ufs_qcom_phy_qmp_20nm_of_match[] = {
> {.compatible = "qcom,ufs-phy-qmp-20nm"},
> {},
> @@ -242,7 +227,6 @@ MODULE_DEVICE_TABLE(of, ufs_qcom_phy_qmp_20nm_of_match);
>
> static struct platform_driver ufs_qcom_phy_qmp_20nm_driver = {
> .probe = ufs_qcom_phy_qmp_20nm_probe,
> - .remove = ufs_qcom_phy_qmp_20nm_remove,
> .driver = {
> .of_match_table = ufs_qcom_phy_qmp_20nm_of_match,
> .name = "ufs_qcom_phy_qmp_20nm",
> diff --git a/drivers/phy/phy-qcom-ufs.c b/drivers/phy/phy-qcom-ufs.c
> index f639a7c..b8f9286 100644
> --- a/drivers/phy/phy-qcom-ufs.c
> +++ b/drivers/phy/phy-qcom-ufs.c
> @@ -645,15 +645,6 @@ int ufs_qcom_phy_calibrate_phy(struct phy *generic_phy, bool is_rate_B)
> }
> EXPORT_SYMBOL_GPL(ufs_qcom_phy_calibrate_phy);
>
> -int ufs_qcom_phy_remove(struct phy *generic_phy,
> - struct ufs_qcom_phy *ufs_qcom_phy)
> -{
> - phy_power_off(generic_phy);
> -
> - return 0;
> -}
> -EXPORT_SYMBOL_GPL(ufs_qcom_phy_remove);
> -
> int ufs_qcom_phy_exit(struct phy *generic_phy)
> {
> struct ufs_qcom_phy *ufs_qcom_phy = get_ufs_qcom_phy(generic_phy);
>
next prev parent reply other threads:[~2016-10-26 20:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 14:28 [PATCH v2 00/10] ufs-qcom: phy/hcd: Clean up qcom-ufs phy and ufs-qcom hcd Vivek Gautam
2016-10-18 14:28 ` [PATCH v2 01/10] phy: qcom-ufs: remove failure when rx/tx_iface_clk are absent Vivek Gautam
2016-10-18 18:38 ` Subhash Jadavani
2016-10-18 21:18 ` Stephen Boyd
2016-10-19 17:20 ` Vivek Gautam
2016-10-29 20:21 ` Vivek Gautam
2016-10-18 14:28 ` [PATCH v2 02/10] phy: qcom-ufs: Remove unnecessary BUG_ON Vivek Gautam
2016-10-18 14:28 ` [PATCH v2 03/10] phy: qcom-ufs: Use devm sibling of kstrdup for regulator names Vivek Gautam
2016-10-18 14:28 ` [PATCH v2 04/10] phy: qcom-ufs-qmp-xx: Discard remove callback for drivers Vivek Gautam
2016-10-26 20:20 ` Kishon Vijay Abraham I [this message]
2016-10-29 20:16 ` Vivek Gautam
2016-10-18 14:28 ` [PATCH v2 05/10] phy: qcom-ufs: Cleanup clock and regulator initialization Vivek Gautam
2016-10-18 14:28 ` [PATCH v2 06/10] phy: qcom-ufs: Remove unnecessary function declarations Vivek Gautam
2016-10-18 18:41 ` Subhash Jadavani
2016-10-18 14:28 ` [PATCH v2 07/10] phy: qcom-ufs-qmp-xx: Move clock and regulator init out of phy init Vivek Gautam
2016-10-18 14:28 ` [PATCH 08/10] ufs-qcom: phy/hcd: Refactoring phy clock handling Vivek Gautam
2016-10-18 20:13 ` Subhash Jadavani
2016-10-19 17:45 ` Vivek Gautam
2016-10-19 19:18 ` Subhash Jadavani
2016-10-20 3:44 ` Vivek Gautam
2016-10-18 14:28 ` [PATCH v2 09/10] scsi/ufs: qcom: Add phy_exit call in hcd exit path Vivek Gautam
2016-10-18 20:19 ` Subhash Jadavani
2016-10-18 14:28 ` [PATCH v2 10/10] phy: qcom-ufs: Remove common layer phy exit callback Vivek Gautam
2016-10-19 0:07 ` Subhash Jadavani
2016-10-25 0:40 ` [PATCH v2 00/10] ufs-qcom: phy/hcd: Clean up qcom-ufs phy and ufs-qcom hcd Martin K. Petersen
2016-10-25 6:00 ` Vivek Gautam
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=35ce06b5-8d80-57b4-1c27-4be57be1ecbc@ti.com \
--to=kishon@ti.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=vivek.gautam@codeaurora.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).