From: Alim Akhtar <alim.akhtar@gmail.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Martin K Petersen <martin.petersen@oracle.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
Janek Kotas <jank@cadence.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, nsekhar@ti.com
Subject: Re: [PATCH v2 2/2] scsi: ufs: Add driver for TI wrapper for Cadence UFS IP
Date: Tue, 15 Oct 2019 07:04:55 +0530 [thread overview]
Message-ID: <CAGOxZ51-ds99wNomK3xbws3G9nZgmhyox9k=fKrLmnJL68N2Vw@mail.gmail.com> (raw)
In-Reply-To: <20191010083357.28982-3-vigneshr@ti.com>
Hi Vignesh
On Thu, Oct 10, 2019 at 2:05 PM Vignesh Raghavendra <vigneshr@ti.com> wrote:
>
> TI's J721e SoC has a Cadence UFS IP with a TI specific wrapper. This is
> a minimal driver to configure the wrapper. It releases the UFS slave
> device out of reset and sets up registers to indicate PHY reference
> clock input frequency before probing child Cadence UFS driver.
>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> ---
>
> v2: No change
>
> drivers/scsi/ufs/Kconfig | 10 ++++
> drivers/scsi/ufs/Makefile | 1 +
> drivers/scsi/ufs/ti-j721e-ufs.c | 90 +++++++++++++++++++++++++++++++++
> 3 files changed, 101 insertions(+)
> create mode 100644 drivers/scsi/ufs/ti-j721e-ufs.c
>
> diff --git a/drivers/scsi/ufs/Kconfig b/drivers/scsi/ufs/Kconfig
> index 0b845ab7c3bf..d14c2243e02a 100644
> --- a/drivers/scsi/ufs/Kconfig
> +++ b/drivers/scsi/ufs/Kconfig
> @@ -132,6 +132,16 @@ config SCSI_UFS_HISI
> Select this if you have UFS controller on Hisilicon chipset.
> If unsure, say N.
>
> +config SCSI_UFS_TI_J721E
> + tristate "TI glue layer for Cadence UFS Controller"
> + depends on OF && HAS_IOMEM && (ARCH_K3 || COMPILE_TEST)
> + help
> + This selects driver for TI glue layer for Cadence UFS Host
> + Controller IP.
> +
> + Selects this if you have TI platform with UFS controller.
> + If unsure, say N.
> +
> config SCSI_UFS_BSG
> bool "Universal Flash Storage BSG device node"
> depends on SCSI_UFSHCD
> diff --git a/drivers/scsi/ufs/Makefile b/drivers/scsi/ufs/Makefile
> index 2a9097939bcb..94c6c5d7334b 100644
> --- a/drivers/scsi/ufs/Makefile
> +++ b/drivers/scsi/ufs/Makefile
> @@ -11,3 +11,4 @@ obj-$(CONFIG_SCSI_UFSHCD_PCI) += ufshcd-pci.o
> obj-$(CONFIG_SCSI_UFSHCD_PLATFORM) += ufshcd-pltfrm.o
> obj-$(CONFIG_SCSI_UFS_HISI) += ufs-hisi.o
> obj-$(CONFIG_SCSI_UFS_MEDIATEK) += ufs-mediatek.o
> +obj-$(CONFIG_SCSI_UFS_TI_J721E) += ti-j721e-ufs.o
> diff --git a/drivers/scsi/ufs/ti-j721e-ufs.c b/drivers/scsi/ufs/ti-j721e-ufs.c
> new file mode 100644
> index 000000000000..a653bf1902f3
> --- /dev/null
> +++ b/drivers/scsi/ufs/ti-j721e-ufs.c
> @@ -0,0 +1,90 @@
> +// SPDX-License-Identifier: GPL-2.0
> +//
> +// Copyright (C) 2019 Texas Instruments Incorporated - http://www.ti.com/
> +//
> +
> +#include <linux/clk.h>
> +#include <linux/io.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/of_platform.h>
> +#include <linux/platform_device.h>
> +#include <linux/pm_runtime.h>
> +
> +#define UFS_SS_CTRL 0x4
> +#define UFS_SS_RST_N_PCS BIT(0)
> +#define UFS_SS_CLK_26MHZ BIT(4)
> +
These looks like vendor specific defines, if so, please add TI_* suffix.
> +static int ti_j721e_ufs_probe(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + unsigned long clk_rate;
> + void __iomem *regbase;
> + struct clk *clk;
> + u32 reg = 0;
> + int ret;
> +
> + regbase = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(regbase))
> + return PTR_ERR(regbase);
> +
> + /* Select MPHY refclk frequency */
> + clk = devm_clk_get(dev, NULL);
> + if (IS_ERR(clk)) {
> + dev_err(dev, "Cannot claim MPHY clock.\n");
> + return PTR_ERR(clk);
> + }
No need to enable MPHY clock? Moreover this clock belongs to MPHY and
should be handled using generic PHY framework to do that.
> + clk_rate = clk_get_rate(clk);
> + if (clk_rate == 26000000)
> + reg |= UFS_SS_CLK_26MHZ;
> + devm_clk_put(dev, clk);
> +
Is this only needed to select one bit in UFS_SS_CLK_26MHz? if so, just
have a DT property and get this selection from there.
> + pm_runtime_enable(dev);
> + ret = pm_runtime_get_sync(dev);
> + if (ret < 0) {
> + pm_runtime_put_noidle(dev);
> + return ret;
> + }
> +
> + /* Take UFS slave device out of reset */
> + reg |= UFS_SS_RST_N_PCS;
What is the default value of UFS_SS_CLK_26MHZ bit above? Incase 26MHZ
is not set, then what is default?
> + writel(reg, regbase + UFS_SS_CTRL);
> +
> + ret = of_platform_populate(pdev->dev.of_node, NULL, NULL,
> + dev);
> + if (ret) {
> + dev_err(dev, "failed to populate child nodes %d\n", ret);
> + pm_runtime_put_sync(dev);
> + }
> +
> + return ret;
> +}
> +
> +static int ti_j721e_ufs_remove(struct platform_device *pdev)
> +{
> + of_platform_depopulate(&pdev->dev);
> + pm_runtime_put_sync(&pdev->dev);
> +
> + return 0;
> +}
> +
> +static const struct of_device_id ti_j721e_ufs_of_match[] = {
> + {
> + .compatible = "ti,j721e-ufs",
> + },
> + { },
> +};
> +
> +static struct platform_driver ti_j721e_ufs_driver = {
> + .probe = ti_j721e_ufs_probe,
> + .remove = ti_j721e_ufs_remove,
> + .driver = {
> + .name = "ti-j721e-ufs",
> + .of_match_table = ti_j721e_ufs_of_match,
> + },
> +};
> +module_platform_driver(ti_j721e_ufs_driver);
> +
> +MODULE_AUTHOR("Vignesh Raghavendra <vigneshr@ti.com>");
> +MODULE_DESCRIPTION("TI UFS host controller glue driver");
> +MODULE_LICENSE("GPL v2");
> --
> 2.23.0
>
--
Regards,
Alim
next prev parent reply other threads:[~2019-10-15 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 8:33 [PATCH v2 0/2] scsi: ufs: Add driver for TI wrapper for Cadence UFS IP Vignesh Raghavendra
2019-10-10 8:33 ` [PATCH v2 1/2] dt-bindings: ufs: ti,j721e-ufs.yaml: Add binding for TI UFS wrapper Vignesh Raghavendra
2019-10-14 18:09 ` Rob Herring
2019-10-10 8:33 ` [PATCH v2 2/2] scsi: ufs: Add driver for TI wrapper for Cadence UFS IP Vignesh Raghavendra
2019-10-15 1:34 ` Alim Akhtar [this message]
2019-10-15 4:50 ` Vignesh Raghavendra
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='CAGOxZ51-ds99wNomK3xbws3G9nZgmhyox9k=fKrLmnJL68N2Vw@mail.gmail.com' \
--to=alim.akhtar@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=jank@cadence.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.petersen@oracle.com \
--cc=nsekhar@ti.com \
--cc=pedrom.sousa@synopsys.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).