[PATCH v8 0/3] Support for USB DRD PHY driver for NS2

[PATCH v8 0/3] Support for USB DRD PHY driver for NS2

[Raviteja Garimella]

Changes in v8:
=============
-Renamed phy shutdown routine
-Used devm_request_irq in stead of threaded irq
-Removed devm_unregister calls in probe routine

Changes in v7:
=============
Cleaned up unused variables in phy private data structure that's
missed out in v6.
Setting of phy mode to device/host is removed from phy power on.
routine.

Changes in v6:
=============
Removed spin locks which are not required as the references
to phy_ops in the same driver were removed in v5.

Removed host/device 'notify' routines which are registered
using 'extcon_register_notifier'. The irq handler is sufficient
to deal with the change in extcon events within the same driver.

Changes in v5:
=============
Removed references to phy_ops in the same driver by connect_work
event handler to change the phy modes.

To support dynamically changing the mode of the phy, it does
not require doing a phy reset/programming of PHY PLL. Changes
are made to the connect_work routine to just program the required
register bits to achieve this purpose.

Changes in v4:
=============
Remove references to edev->name in debug prints.

Changes in v3:
=============
Remove unnecessary checks for poweron as suggested in review.

Changes in v2:
=============
1. Initialize file operations .owner field with THIS_MODULE.
2. Remove unnecessary gpio example in DT bindings documentation.
   This is previously acked by Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

Introduction for PATCH v1:

This patch adds support for USB Dual Role Device Phy for Broadcom
Northstar2 SoC. Apart from the new phy driver, this patchset contains
changes to Kconfig, Makefile, and Device tree files.

This patchset is tested on Broadcom NS2 BCM958712K reference board.

Repo: https://github.com/Broadcom/arm64-linux.git
Branch: ns2_drdphy_v8

Raviteja Garimella (3):
  dt-bindings: phy: Add DT bindings documentation for NS2 USB DRD PHY
  phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2
  arm64: dts: NS2: Add USB DRD PHY device tree node

 .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt   |  30 ++
 arch/arm64/boot/dts/broadcom/ns2.dtsi              |  14 +
 drivers/phy/Kconfig                                |  13 +
 drivers/phy/Makefile                               |   1 +
 drivers/phy/phy-bcm-ns2-usbdrd.c                   | 437 +++++++++++++++++++++
 5 files changed, 495 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt
 create mode 100644 drivers/phy/phy-bcm-ns2-usbdrd.c

-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH v8 1/3] dt-bindings: phy: Add DT bindings documentation for NS2 USB DRD PHY

[Raviteja Garimella]

This patch adds DT bindings documentation for NS2 DRD PHY driver.

Signed-off-by: Raviteja Garimella <raviteja.garimella@broadcom.com>
Acked-by: Rob Herring <robh@kernel.org>
---
 .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt   | 30 ++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt

diff --git a/Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt b/Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt
new file mode 100644
index 0000000..04f063a
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt
@@ -0,0 +1,30 @@
+BROADCOM NORTHSTAR2 USB2 (DUAL ROLE DEVICE) PHY
+
+Required properties:
+ - compatible: brcm,ns2-drd-phy
+ - reg: offset and length of the NS2 PHY related registers.
+ - reg-names
+   The below registers must be provided.
+   icfg - for DRD ICFG configurations
+   rst-ctrl - for DRD IDM reset
+   crmu-ctrl - for CRMU core vdd, PHY and PHY PLL reset
+   usb2-strap - for port over current polarity reversal
+ - #phy-cells: Must be 0. No args required.
+ - vbus-gpios: vbus gpio binding
+ - id-gpios: id gpio binding
+
+Refer to phy/phy-bindings.txt for the generic PHY binding properties
+
+Example:
+	usbdrd_phy: phy@66000960 {
+			#phy-cells = <0>;
+			compatible = "brcm,ns2-drd-phy";
+			reg = <0x66000960 0x24>,
+			      <0x67012800 0x4>,
+			      <0x6501d148 0x4>,
+			      <0x664d0700 0x4>;
+			reg-names = "icfg", "rst-ctrl",
+				    "crmu-ctrl", "usb2-strap";
+			id-gpios = <&gpio_g 30 0>;
+			vbus-gpios = <&gpio_g 31 0>;
+	};
-- 
2.1.0

[PATCH v8 2/3] phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2

[Raviteja Garimella]

This is driver for USB DRD PHY used in Broadcom's Northstar2
SoC. The phy can be configured to be in Device mode or Host
mode based on the type of cable connected to the port. The
driver registers to  extcon framework to get appropriate
connect events for Host/Device cables connect/disconnect
states based on VBUS and ID interrupts.

Signed-off-by: Raviteja Garimella <raviteja.garimella@broadcom.com>
---
 drivers/phy/Kconfig              |  13 ++
 drivers/phy/Makefile             |   1 +
 drivers/phy/phy-bcm-ns2-usbdrd.c | 437 +++++++++++++++++++++++++++++++++++++++
 3 files changed, 451 insertions(+)
 create mode 100644 drivers/phy/phy-bcm-ns2-usbdrd.c

diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
index afaf7b6..8028da7 100644
--- a/drivers/phy/Kconfig
+++ b/drivers/phy/Kconfig
@@ -507,6 +507,19 @@ config PHY_CYGNUS_PCIE
 	  Enable this to support the Broadcom Cygnus PCIe PHY.
 	  If unsure, say N.
 
+config PHY_NS2_USB_DRD
+	tristate "Broadcom Northstar2 USB DRD PHY support"
+	depends on OF && (ARCH_BCM_IPROC || COMPILE_TEST)
+	select GENERIC_PHY
+	select EXTCON
+	default ARCH_BCM_IPROC
+	help
+	  Enable this to support the Broadcom Northstar2 USB DRD PHY.
+	  This driver initializes the PHY in either HOST or DEVICE mode.
+	  The host or device configuration is read from device tree.
+
+	  If unsure, say N.
+
 source "drivers/phy/tegra/Kconfig"
 
 config PHY_NS2_PCIE
diff --git a/drivers/phy/Makefile b/drivers/phy/Makefile
index f8047b4..e5fbb0e 100644
--- a/drivers/phy/Makefile
+++ b/drivers/phy/Makefile
@@ -61,6 +61,7 @@ obj-$(CONFIG_PHY_TUSB1210)		+= phy-tusb1210.o
 obj-$(CONFIG_PHY_BRCM_SATA)		+= phy-brcm-sata.o
 obj-$(CONFIG_PHY_PISTACHIO_USB)		+= phy-pistachio-usb.o
 obj-$(CONFIG_PHY_CYGNUS_PCIE)		+= phy-bcm-cygnus-pcie.o
+obj-$(CONFIG_PHY_NS2_USB_DRD)		+= phy-bcm-ns2-usbdrd.o
 obj-$(CONFIG_ARCH_TEGRA) += tegra/
 obj-$(CONFIG_PHY_NS2_PCIE)		+= phy-bcm-ns2-pcie.o
 obj-$(CONFIG_PHY_MESON8B_USB2)		+= phy-meson8b-usb2.o
diff --git a/drivers/phy/phy-bcm-ns2-usbdrd.c b/drivers/phy/phy-bcm-ns2-usbdrd.c
new file mode 100644
index 0000000..9ae59e2
--- /dev/null
+++ b/drivers/phy/phy-bcm-ns2-usbdrd.c
@@ -0,0 +1,437 @@
+/*
+ * Copyright (C) 2017 Broadcom
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation version 2.
+ *
+ * This program is distributed "as is" WITHOUT ANY WARRANTY of any
+ * kind, whether express or implied; without even the implied warranty
+ * of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ */
+
+#include <linux/delay.h>
+#include <linux/extcon.h>
+#include <linux/gpio.h>
+#include <linux/gpio/consumer.h>
+#include <linux/init.h>
+#include <linux/interrupt.h>
+#include <linux/io.h>
+#include <linux/irq.h>
+#include <linux/mfd/syscon.h>
+#include <linux/module.h>
+#include <linux/of.h>
+#include <linux/of_address.h>
+#include <linux/phy/phy.h>
+#include <linux/platform_device.h>
+#include <linux/regmap.h>
+#include <linux/slab.h>
+#include <linux/workqueue.h>
+
+#define ICFG_DRD_AFE		0x0
+#define ICFG_MISC_STAT		0x18
+#define ICFG_DRD_P0CTL		0x1C
+#define ICFG_STRAP_CTRL		0x20
+#define ICFG_FSM_CTRL		0x24
+
+#define ICFG_DEV_BIT		BIT(2)
+#define IDM_RST_BIT		BIT(0)
+#define AFE_CORERDY_VDDC	BIT(18)
+#define PHY_PLL_RESETB		BIT(15)
+#define PHY_RESETB		BIT(14)
+#define PHY_PLL_LOCK		BIT(0)
+
+#define DRD_DEV_MODE		BIT(20)
+#define OHCI_OVRCUR_POL		BIT(11)
+#define ICFG_OFF_MODE		BIT(6)
+#define PLL_LOCK_RETRY		1000
+
+#define EVT_DEVICE		0
+#define EVT_HOST		1
+
+#define DRD_HOST_MODE		(BIT(2) | BIT(3))
+#define DRD_DEVICE_MODE		(BIT(4) | BIT(5))
+#define DRD_HOST_VAL		0x803
+#define DRD_DEV_VAL		0x807
+#define GPIO_DELAY		20
+
+struct ns2_phy_data;
+struct ns2_phy_driver {
+	void __iomem *icfgdrd_regs;
+	void __iomem *idmdrd_rst_ctrl;
+	void __iomem *crmu_usb2_ctrl;
+	void __iomem *usb2h_strap_reg;
+	struct ns2_phy_data *data;
+	struct extcon_dev *edev;
+	struct gpio_desc *vbus_gpiod;
+	struct gpio_desc *id_gpiod;
+	int id_irq;
+	int vbus_irq;
+	unsigned long debounce_jiffies;
+	struct delayed_work wq_extcon;
+};
+
+struct ns2_phy_data {
+	struct ns2_phy_driver *driver;
+	struct phy *phy;
+	int new_state;
+};
+
+static const unsigned int usb_extcon_cable[] = {
+	EXTCON_USB,
+	EXTCON_USB_HOST,
+	EXTCON_NONE,
+};
+
+static inline int pll_lock_stat(u32 usb_reg, int reg_mask,
+				struct ns2_phy_driver *driver)
+{
+	int retry = PLL_LOCK_RETRY;
+	u32 val;
+
+	do {
+		udelay(1);
+		val = readl(driver->icfgdrd_regs + usb_reg);
+		if (val & reg_mask)
+			return 0;
+	} while (--retry > 0);
+
+	return -EBUSY;
+}
+
+static int ns2_drd_phy_init(struct phy *phy)
+{
+	struct ns2_phy_data *data = phy_get_drvdata(phy);
+	struct ns2_phy_driver *driver = data->driver;
+	u32 val;
+
+	val = readl(driver->icfgdrd_regs + ICFG_FSM_CTRL);
+
+	if (data->new_state == EVT_HOST) {
+		val &= ~DRD_DEVICE_MODE;
+		val |= DRD_HOST_MODE;
+	} else {
+		val &= ~DRD_HOST_MODE;
+		val |= DRD_DEVICE_MODE;
+	}
+	writel(val, driver->icfgdrd_regs + ICFG_FSM_CTRL);
+
+	return 0;
+}
+
+static int ns2_drd_phy_poweroff(struct phy *phy)
+{
+	struct ns2_phy_data *data = phy_get_drvdata(phy);
+	struct ns2_phy_driver *driver = data->driver;
+	u32 val;
+
+	val = readl(driver->crmu_usb2_ctrl);
+	val &= ~AFE_CORERDY_VDDC;
+	writel(val, driver->crmu_usb2_ctrl);
+
+	val = readl(driver->crmu_usb2_ctrl);
+	val &= ~DRD_DEV_MODE;
+	writel(val, driver->crmu_usb2_ctrl);
+
+	/* Disable Host and Device Mode */
+	val = readl(driver->icfgdrd_regs + ICFG_FSM_CTRL);
+	val &= ~(DRD_HOST_MODE | DRD_DEVICE_MODE | ICFG_OFF_MODE);
+	writel(val, driver->icfgdrd_regs + ICFG_FSM_CTRL);
+
+	return 0;
+}
+
+static int ns2_drd_phy_poweron(struct phy *phy)
+{
+	struct ns2_phy_data *data = phy_get_drvdata(phy);
+	struct ns2_phy_driver *driver = data->driver;
+	u32 extcon_event = data->new_state;
+	int ret;
+	u32 val;
+
+	if (extcon_event == EVT_DEVICE) {
+		writel(DRD_DEV_VAL, driver->icfgdrd_regs + ICFG_DRD_P0CTL);
+
+		val = readl(driver->idmdrd_rst_ctrl);
+		val &= ~IDM_RST_BIT;
+		writel(val, driver->idmdrd_rst_ctrl);
+
+		val = readl(driver->crmu_usb2_ctrl);
+		val |= (AFE_CORERDY_VDDC | DRD_DEV_MODE);
+		writel(val, driver->crmu_usb2_ctrl);
+
+		/* Bring PHY and PHY_PLL out of Reset */
+		val = readl(driver->crmu_usb2_ctrl);
+		val |= (PHY_PLL_RESETB | PHY_RESETB);
+		writel(val, driver->crmu_usb2_ctrl);
+
+		ret = pll_lock_stat(ICFG_MISC_STAT, PHY_PLL_LOCK, driver);
+		if (ret < 0) {
+			dev_err(&phy->dev, "Phy PLL lock failed\n");
+			return ret;
+		}
+	} else {
+		writel(DRD_HOST_VAL, driver->icfgdrd_regs + ICFG_DRD_P0CTL);
+
+		val = readl(driver->crmu_usb2_ctrl);
+		val |= AFE_CORERDY_VDDC;
+		writel(val, driver->crmu_usb2_ctrl);
+
+		ret = pll_lock_stat(ICFG_MISC_STAT, PHY_PLL_LOCK, driver);
+		if (ret < 0) {
+			dev_err(&phy->dev, "Phy PLL lock failed\n");
+			return ret;
+		}
+
+		val = readl(driver->idmdrd_rst_ctrl);
+		val &= ~IDM_RST_BIT;
+		writel(val, driver->idmdrd_rst_ctrl);
+
+		/* port over current Polarity */
+		val = readl(driver->usb2h_strap_reg);
+		val |= OHCI_OVRCUR_POL;
+		writel(val, driver->usb2h_strap_reg);
+	}
+
+	return 0;
+}
+
+static void connect_change(struct ns2_phy_driver *driver)
+{
+	u32 extcon_event;
+	u32 val;
+
+	extcon_event = driver->data->new_state;
+	val = readl(driver->icfgdrd_regs + ICFG_FSM_CTRL);
+
+	switch (extcon_event) {
+	case EVT_DEVICE:
+		val &= ~(DRD_HOST_MODE | DRD_DEVICE_MODE);
+		writel(val, driver->icfgdrd_regs + ICFG_FSM_CTRL);
+
+		val = (val & ~DRD_HOST_MODE) | DRD_DEVICE_MODE;
+		writel(val, driver->icfgdrd_regs + ICFG_FSM_CTRL);
+
+		val = readl(driver->icfgdrd_regs + ICFG_DRD_P0CTL);
+		val |= ICFG_DEV_BIT;
+		writel(val, driver->icfgdrd_regs + ICFG_DRD_P0CTL);
+		break;
+
+	case EVT_HOST:
+		val &= ~(DRD_HOST_MODE | DRD_DEVICE_MODE);
+		writel(val, driver->icfgdrd_regs + ICFG_FSM_CTRL);
+
+		val = (val & ~DRD_DEVICE_MODE) | DRD_HOST_MODE;
+		writel(val, driver->icfgdrd_regs + ICFG_FSM_CTRL);
+
+		val = readl(driver->usb2h_strap_reg);
+		val |= OHCI_OVRCUR_POL;
+		writel(val, driver->usb2h_strap_reg);
+
+		val = readl(driver->icfgdrd_regs + ICFG_DRD_P0CTL);
+		val &= ~ICFG_DEV_BIT;
+		writel(val, driver->icfgdrd_regs + ICFG_DRD_P0CTL);
+		break;
+
+	default:
+		pr_err("Invalid extcon event\n");
+		break;
+	}
+}
+
+static void extcon_work(struct work_struct *work)
+{
+	struct ns2_phy_driver *driver;
+	int vbus;
+	int id;
+
+	driver  = container_of(to_delayed_work(work),
+			       struct ns2_phy_driver, wq_extcon);
+
+	id = gpiod_get_value_cansleep(driver->id_gpiod);
+	vbus = gpiod_get_value_cansleep(driver->vbus_gpiod);
+
+	if (!id && vbus) { /* Host connected */
+		extcon_set_cable_state_(driver->edev, EXTCON_USB_HOST, true);
+		pr_debug("Host cable connected\n");
+		driver->data->new_state = EVT_HOST;
+		connect_change(driver);
+	} else if (id && !vbus) { /* Disconnected */
+		extcon_set_cable_state_(driver->edev, EXTCON_USB_HOST, false);
+		extcon_set_cable_state_(driver->edev, EXTCON_USB, false);
+		pr_debug("Cable disconnected\n");
+	} else if (id && vbus) { /* Device connected */
+		extcon_set_cable_state_(driver->edev, EXTCON_USB, true);
+		pr_debug("Device cable connected\n");
+		driver->data->new_state = EVT_DEVICE;
+		connect_change(driver);
+	}
+}
+
+static irqreturn_t gpio_irq_handler(int irq, void *dev_id)
+{
+	struct ns2_phy_driver *driver = dev_id;
+
+	queue_delayed_work(system_power_efficient_wq, &driver->wq_extcon,
+			   driver->debounce_jiffies);
+
+	return IRQ_HANDLED;
+}
+
+static struct phy_ops ops = {
+	.init		= ns2_drd_phy_init,
+	.power_on	= ns2_drd_phy_poweron,
+	.power_off	= ns2_drd_phy_poweroff,
+	.owner		= THIS_MODULE,
+};
+
+static const struct of_device_id ns2_drd_phy_dt_ids[] = {
+	{ .compatible = "brcm,ns2-drd-phy", },
+	{ }
+};
+MODULE_DEVICE_TABLE(of, ns2_drd_phy_dt_ids);
+
+static int ns2_drd_phy_probe(struct platform_device *pdev)
+{
+	struct phy_provider *phy_provider;
+	struct device *dev = &pdev->dev;
+	struct ns2_phy_driver *driver;
+	struct ns2_phy_data *data;
+	struct resource *res;
+	int ret;
+	u32 val;
+
+	driver = devm_kzalloc(dev, sizeof(struct ns2_phy_driver),
+			      GFP_KERNEL);
+	if (!driver)
+		return -ENOMEM;
+
+	driver->data = devm_kzalloc(dev, sizeof(struct ns2_phy_data),
+				  GFP_KERNEL);
+	if (!driver->data)
+		return -ENOMEM;
+
+	res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "icfg");
+	driver->icfgdrd_regs = devm_ioremap_resource(dev, res);
+	if (IS_ERR(driver->icfgdrd_regs))
+		return PTR_ERR(driver->icfgdrd_regs);
+
+	res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "rst-ctrl");
+	driver->idmdrd_rst_ctrl = devm_ioremap_resource(dev, res);
+	if (IS_ERR(driver->idmdrd_rst_ctrl))
+		return PTR_ERR(driver->idmdrd_rst_ctrl);
+
+	res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "crmu-ctrl");
+	driver->crmu_usb2_ctrl = devm_ioremap_resource(dev, res);
+	if (IS_ERR(driver->crmu_usb2_ctrl))
+		return PTR_ERR(driver->crmu_usb2_ctrl);
+
+	res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "usb2-strap");
+	driver->usb2h_strap_reg = devm_ioremap_resource(dev, res);
+	if (IS_ERR(driver->usb2h_strap_reg))
+		return PTR_ERR(driver->usb2h_strap_reg);
+
+	 /* create extcon */
+	driver->id_gpiod = devm_gpiod_get(&pdev->dev, "id", GPIOD_IN);
+	if (IS_ERR(driver->id_gpiod)) {
+		dev_err(dev, "failed to get ID GPIO\n");
+		return PTR_ERR(driver->id_gpiod);
+	}
+	driver->vbus_gpiod = devm_gpiod_get(&pdev->dev, "vbus", GPIOD_IN);
+	if (IS_ERR(driver->vbus_gpiod)) {
+		dev_err(dev, "failed to get VBUS GPIO\n");
+		return PTR_ERR(driver->vbus_gpiod);
+	}
+
+	driver->edev = devm_extcon_dev_allocate(dev, usb_extcon_cable);
+	if (IS_ERR(driver->edev)) {
+		dev_err(dev, "failed to allocate extcon device\n");
+		return -ENOMEM;
+	}
+
+	ret = devm_extcon_dev_register(dev, driver->edev);
+	if (ret < 0) {
+		dev_err(dev, "failed to register extcon device\n");
+		return ret;
+	}
+
+	ret = gpiod_set_debounce(driver->id_gpiod, GPIO_DELAY * 1000);
+	if (ret < 0)
+		driver->debounce_jiffies = msecs_to_jiffies(GPIO_DELAY);
+
+	INIT_DELAYED_WORK(&driver->wq_extcon, extcon_work);
+
+	driver->id_irq = gpiod_to_irq(driver->id_gpiod);
+	if (driver->id_irq < 0) {
+		dev_err(dev, "failed to get ID IRQ\n");
+		return driver->id_irq;
+	}
+
+	driver->vbus_irq = gpiod_to_irq(driver->vbus_gpiod);
+	if (driver->vbus_irq < 0) {
+		dev_err(dev, "failed to get ID IRQ\n");
+		return driver->vbus_irq;
+	}
+
+	ret = devm_request_irq(dev, driver->id_irq, gpio_irq_handler,
+			       IRQF_TRIGGER_RISING | IRQF_TRIGGER_FALLING,
+			       "usb_id", driver);
+	if (ret < 0) {
+		dev_err(dev, "failed to request handler for ID IRQ\n");
+		return ret;
+	}
+
+	ret = devm_request_irq(dev, driver->vbus_irq, gpio_irq_handler,
+			       IRQF_TRIGGER_RISING | IRQF_TRIGGER_FALLING,
+			       "usb_vbus", driver);
+	if (ret < 0) {
+		dev_err(dev, "failed to request handler for VBUS IRQ\n");
+		return ret;
+	}
+
+	dev_set_drvdata(dev, driver);
+
+	/* Shutdown all ports. They can be powered up as required */
+	val = readl(driver->crmu_usb2_ctrl);
+	val &= ~(AFE_CORERDY_VDDC | PHY_RESETB);
+	writel(val, driver->crmu_usb2_ctrl);
+
+	data = driver->data;
+	data->phy = devm_phy_create(dev, dev->of_node, &ops);
+	if (IS_ERR(data->phy)) {
+		dev_err(dev, "Failed to create usb drd phy\n");
+		return PTR_ERR(data->phy);
+	}
+
+	data->driver = driver;
+	phy_set_drvdata(data->phy, data);
+
+	phy_provider = devm_of_phy_provider_register(dev, of_phy_simple_xlate);
+	if (IS_ERR(phy_provider)) {
+		dev_err(dev, "Failed to register as phy provider\n");
+		return PTR_ERR(phy_provider);
+	}
+
+	platform_set_drvdata(pdev, driver);
+
+	dev_info(dev, "Registered NS2 DRD Phy device\n");
+	queue_delayed_work(system_power_efficient_wq, &driver->wq_extcon,
+			   driver->debounce_jiffies);
+
+	return 0;
+}
+
+static struct platform_driver ns2_drd_phy_driver = {
+	.probe = ns2_drd_phy_probe,
+	.driver = {
+		.name = "bcm-ns2-usbphy",
+		.of_match_table = of_match_ptr(ns2_drd_phy_dt_ids),
+	},
+};
+module_platform_driver(ns2_drd_phy_driver);
+
+MODULE_ALIAS("platform:bcm-ns2-drd-phy");
+MODULE_AUTHOR("Broadcom");
+MODULE_DESCRIPTION("Broadcom NS2 USB2 PHY driver");
+MODULE_LICENSE("GPL v2");
-- 
2.1.0

[PATCH v8 3/3] arm64: dts: NS2: Add USB DRD PHY device tree node

[Raviteja Garimella]

This patch adds device tree node for USB Dual Role Device PHY for
Broadcom's Northstar2 SoC.

Signed-off-by: Raviteja Garimella <raviteja.garimella-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
---
 arch/arm64/boot/dts/broadcom/ns2.dtsi | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/arch/arm64/boot/dts/broadcom/ns2.dtsi b/arch/arm64/boot/dts/broadcom/ns2.dtsi
index 35a309a..35c8457 100644
--- a/arch/arm64/boot/dts/broadcom/ns2.dtsi
+++ b/arch/arm64/boot/dts/broadcom/ns2.dtsi
@@ -460,6 +460,20 @@
 			};
 		};
 
+		usbdrd_phy: phy@66000960 {
+			#phy-cells = <0>;
+			compatible = "brcm,ns2-drd-phy";
+			reg = <0x66000960 0x24>,
+			      <0x67012800 0x4>,
+			      <0x6501d148 0x4>,
+			      <0x664d0700 0x4>;
+			reg-names = "icfg", "rst-ctrl",
+				    "crmu-ctrl", "usb2-strap";
+			id-gpios = <&gpio_g 30 0>;
+			vbus-gpios = <&gpio_g 31 0>;
+			status = "disabled";
+		};
+
 		pwm: pwm@66010000 {
 			compatible = "brcm,iproc-pwm";
 			reg = <0x66010000 0x28>;
-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v8 3/3] arm64: dts: NS2: Add USB DRD PHY device tree node

[Florian Fainelli]

On 06/08/2017 03:35 AM, Raviteja Garimella wrote:
> This patch adds device tree node for USB Dual Role Device PHY for
> Broadcom's Northstar2 SoC.
> 
> Signed-off-by: Raviteja Garimella <raviteja.garimella-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>

Since Rob acked the binding, applied to devicetree-arm64/next, thanks
-- 
-- 
Florian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v8 0/3] Support for USB DRD PHY driver for NS2

[Kishon Vijay Abraham I]

Hi,

On Thursday 08 June 2017 04:05 PM, Raviteja Garimella wrote:
> Changes in v8:
> =============
> -Renamed phy shutdown routine
> -Used devm_request_irq in stead of threaded irq

That's not what I intended. Continue to use threaded irq but remove delayed work.

Thanks
Kishon
> -Removed devm_unregister calls in probe routine
> 
> Changes in v7:
> =============
> Cleaned up unused variables in phy private data structure that's
> missed out in v6.
> Setting of phy mode to device/host is removed from phy power on.
> routine.
> 
> Changes in v6:
> =============
> Removed spin locks which are not required as the references
> to phy_ops in the same driver were removed in v5.
> 
> Removed host/device 'notify' routines which are registered
> using 'extcon_register_notifier'. The irq handler is sufficient
> to deal with the change in extcon events within the same driver.
> 
> Changes in v5:
> =============
> Removed references to phy_ops in the same driver by connect_work
> event handler to change the phy modes.
> 
> To support dynamically changing the mode of the phy, it does
> not require doing a phy reset/programming of PHY PLL. Changes
> are made to the connect_work routine to just program the required
> register bits to achieve this purpose.
> 
> Changes in v4:
> =============
> Remove references to edev->name in debug prints.
> 
> Changes in v3:
> =============
> Remove unnecessary checks for poweron as suggested in review.
> 
> Changes in v2:
> =============
> 1. Initialize file operations .owner field with THIS_MODULE.
> 2. Remove unnecessary gpio example in DT bindings documentation.
>    This is previously acked by Rob Herring <robh@kernel.org>
> 
> Introduction for PATCH v1:
> 
> This patch adds support for USB Dual Role Device Phy for Broadcom
> Northstar2 SoC. Apart from the new phy driver, this patchset contains
> changes to Kconfig, Makefile, and Device tree files.
> 
> This patchset is tested on Broadcom NS2 BCM958712K reference board.
> 
> Repo: https://github.com/Broadcom/arm64-linux.git
> Branch: ns2_drdphy_v8
> 
> Raviteja Garimella (3):
>   dt-bindings: phy: Add DT bindings documentation for NS2 USB DRD PHY
>   phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2
>   arm64: dts: NS2: Add USB DRD PHY device tree node
> 
>  .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt   |  30 ++
>  arch/arm64/boot/dts/broadcom/ns2.dtsi              |  14 +
>  drivers/phy/Kconfig                                |  13 +
>  drivers/phy/Makefile                               |   1 +
>  drivers/phy/phy-bcm-ns2-usbdrd.c                   | 437 +++++++++++++++++++++
>  5 files changed, 495 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt
>  create mode 100644 drivers/phy/phy-bcm-ns2-usbdrd.c
> 

Re: [PATCH v8 0/3] Support for USB DRD PHY driver for NS2

[Raviteja Garimella]

Hi,

On Fri, Jun 9, 2017 at 2:25 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
> Hi,
>
> On Thursday 08 June 2017 04:05 PM, Raviteja Garimella wrote:
>> Changes in v8:
>> =============
>> -Renamed phy shutdown routine
>> -Used devm_request_irq in stead of threaded irq
>
> That's not what I intended. Continue to use threaded irq but remove delayed work.
>

Yes I get that. We see intermittent connection issues without delayed
work. Debounce delay matters there.

Thanks,
Ravi

> Thanks
> Kishon
>> -Removed devm_unregister calls in probe routine
>>
>> Changes in v7:
>> =============
>> Cleaned up unused variables in phy private data structure that's
>> missed out in v6.
>> Setting of phy mode to device/host is removed from phy power on.
>> routine.
>>
>> Changes in v6:
>> =============
>> Removed spin locks which are not required as the references
>> to phy_ops in the same driver were removed in v5.
>>
>> Removed host/device 'notify' routines which are registered
>> using 'extcon_register_notifier'. The irq handler is sufficient
>> to deal with the change in extcon events within the same driver.
>>
>> Changes in v5:
>> =============
>> Removed references to phy_ops in the same driver by connect_work
>> event handler to change the phy modes.
>>
>> To support dynamically changing the mode of the phy, it does
>> not require doing a phy reset/programming of PHY PLL. Changes
>> are made to the connect_work routine to just program the required
>> register bits to achieve this purpose.
>>
>> Changes in v4:
>> =============
>> Remove references to edev->name in debug prints.
>>
>> Changes in v3:
>> =============
>> Remove unnecessary checks for poweron as suggested in review.
>>
>> Changes in v2:
>> =============
>> 1. Initialize file operations .owner field with THIS_MODULE.
>> 2. Remove unnecessary gpio example in DT bindings documentation.
>>    This is previously acked by Rob Herring <robh@kernel.org>
>>
>> Introduction for PATCH v1:
>>
>> This patch adds support for USB Dual Role Device Phy for Broadcom
>> Northstar2 SoC. Apart from the new phy driver, this patchset contains
>> changes to Kconfig, Makefile, and Device tree files.
>>
>> This patchset is tested on Broadcom NS2 BCM958712K reference board.
>>
>> Repo: https://github.com/Broadcom/arm64-linux.git
>> Branch: ns2_drdphy_v8
>>
>> Raviteja Garimella (3):
>>   dt-bindings: phy: Add DT bindings documentation for NS2 USB DRD PHY
>>   phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2
>>   arm64: dts: NS2: Add USB DRD PHY device tree node
>>
>>  .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt   |  30 ++
>>  arch/arm64/boot/dts/broadcom/ns2.dtsi              |  14 +
>>  drivers/phy/Kconfig                                |  13 +
>>  drivers/phy/Makefile                               |   1 +
>>  drivers/phy/phy-bcm-ns2-usbdrd.c                   | 437 +++++++++++++++++++++
>>  5 files changed, 495 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt
>>  create mode 100644 drivers/phy/phy-bcm-ns2-usbdrd.c
>>

Re: [PATCH v8 0/3] Support for USB DRD PHY driver for NS2

[Kishon Vijay Abraham I]

Hi,

On Friday 09 June 2017 02:30 PM, Raviteja Garimella wrote:
> Hi,
> 
> On Fri, Jun 9, 2017 at 2:25 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>> Hi,
>>
>> On Thursday 08 June 2017 04:05 PM, Raviteja Garimella wrote:
>>> Changes in v8:
>>> =============
>>> -Renamed phy shutdown routine
>>> -Used devm_request_irq in stead of threaded irq
>>
>> That's not what I intended. Continue to use threaded irq but remove delayed work.
>>
> 
> Yes I get that. We see intermittent connection issues without delayed
> work. Debounce delay matters there.

All right!

I'm unable to apply the series. Please rebase to linux-phy next (directory
structure has changed)

Thanks
Kishon
> 
> Thanks,
> Ravi
> 
>> Thanks
>> Kishon
>>> -Removed devm_unregister calls in probe routine
>>>
>>> Changes in v7:
>>> =============
>>> Cleaned up unused variables in phy private data structure that's
>>> missed out in v6.
>>> Setting of phy mode to device/host is removed from phy power on.
>>> routine.
>>>
>>> Changes in v6:
>>> =============
>>> Removed spin locks which are not required as the references
>>> to phy_ops in the same driver were removed in v5.
>>>
>>> Removed host/device 'notify' routines which are registered
>>> using 'extcon_register_notifier'. The irq handler is sufficient
>>> to deal with the change in extcon events within the same driver.
>>>
>>> Changes in v5:
>>> =============
>>> Removed references to phy_ops in the same driver by connect_work
>>> event handler to change the phy modes.
>>>
>>> To support dynamically changing the mode of the phy, it does
>>> not require doing a phy reset/programming of PHY PLL. Changes
>>> are made to the connect_work routine to just program the required
>>> register bits to achieve this purpose.
>>>
>>> Changes in v4:
>>> =============
>>> Remove references to edev->name in debug prints.
>>>
>>> Changes in v3:
>>> =============
>>> Remove unnecessary checks for poweron as suggested in review.
>>>
>>> Changes in v2:
>>> =============
>>> 1. Initialize file operations .owner field with THIS_MODULE.
>>> 2. Remove unnecessary gpio example in DT bindings documentation.
>>>    This is previously acked by Rob Herring <robh@kernel.org>
>>>
>>> Introduction for PATCH v1:
>>>
>>> This patch adds support for USB Dual Role Device Phy for Broadcom
>>> Northstar2 SoC. Apart from the new phy driver, this patchset contains
>>> changes to Kconfig, Makefile, and Device tree files.
>>>
>>> This patchset is tested on Broadcom NS2 BCM958712K reference board.
>>>
>>> Repo: https://github.com/Broadcom/arm64-linux.git
>>> Branch: ns2_drdphy_v8
>>>
>>> Raviteja Garimella (3):
>>>   dt-bindings: phy: Add DT bindings documentation for NS2 USB DRD PHY
>>>   phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2
>>>   arm64: dts: NS2: Add USB DRD PHY device tree node
>>>
>>>  .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt   |  30 ++
>>>  arch/arm64/boot/dts/broadcom/ns2.dtsi              |  14 +
>>>  drivers/phy/Kconfig                                |  13 +
>>>  drivers/phy/Makefile                               |   1 +
>>>  drivers/phy/phy-bcm-ns2-usbdrd.c                   | 437 +++++++++++++++++++++
>>>  5 files changed, 495 insertions(+)
>>>  create mode 100644 Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt
>>>  create mode 100644 drivers/phy/phy-bcm-ns2-usbdrd.c
>>>

Re: [PATCH v8 0/3] Support for USB DRD PHY driver for NS2

[Raviteja Garimella]

Hi Kishon,

On Fri, Jun 9, 2017 at 2:36 PM, Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org> wrote:
> Hi,
>
> On Friday 09 June 2017 02:30 PM, Raviteja Garimella wrote:
>> Hi,
>>
>> On Fri, Jun 9, 2017 at 2:25 PM, Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org> wrote:
>>> Hi,
>>>
>>> On Thursday 08 June 2017 04:05 PM, Raviteja Garimella wrote:
>>>> Changes in v8:
>>>> =============
>>>> -Renamed phy shutdown routine
>>>> -Used devm_request_irq in stead of threaded irq
>>>
>>> That's not what I intended. Continue to use threaded irq but remove delayed work.
>>>
>>
>> Yes I get that. We see intermittent connection issues without delayed
>> work. Debounce delay matters there.
>
> All right!
>
> I'm unable to apply the series. Please rebase to linux-phy next (directory
> structure has changed)
>

Ok. They got applied to linux-phy next for me without issues.
I will resend the patchset anyways after rebasing to linux-phy next.

Thanks,
Ravi

> Thanks
> Kishon
>>
>> Thanks,
>> Ravi
>>
>>> Thanks
>>> Kishon
>>>> -Removed devm_unregister calls in probe routine
>>>>
>>>> Changes in v7:
>>>> =============
>>>> Cleaned up unused variables in phy private data structure that's
>>>> missed out in v6.
>>>> Setting of phy mode to device/host is removed from phy power on.
>>>> routine.
>>>>
>>>> Changes in v6:
>>>> =============
>>>> Removed spin locks which are not required as the references
>>>> to phy_ops in the same driver were removed in v5.
>>>>
>>>> Removed host/device 'notify' routines which are registered
>>>> using 'extcon_register_notifier'. The irq handler is sufficient
>>>> to deal with the change in extcon events within the same driver.
>>>>
>>>> Changes in v5:
>>>> =============
>>>> Removed references to phy_ops in the same driver by connect_work
>>>> event handler to change the phy modes.
>>>>
>>>> To support dynamically changing the mode of the phy, it does
>>>> not require doing a phy reset/programming of PHY PLL. Changes
>>>> are made to the connect_work routine to just program the required
>>>> register bits to achieve this purpose.
>>>>
>>>> Changes in v4:
>>>> =============
>>>> Remove references to edev->name in debug prints.
>>>>
>>>> Changes in v3:
>>>> =============
>>>> Remove unnecessary checks for poweron as suggested in review.
>>>>
>>>> Changes in v2:
>>>> =============
>>>> 1. Initialize file operations .owner field with THIS_MODULE.
>>>> 2. Remove unnecessary gpio example in DT bindings documentation.
>>>>    This is previously acked by Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>>>>
>>>> Introduction for PATCH v1:
>>>>
>>>> This patch adds support for USB Dual Role Device Phy for Broadcom
>>>> Northstar2 SoC. Apart from the new phy driver, this patchset contains
>>>> changes to Kconfig, Makefile, and Device tree files.
>>>>
>>>> This patchset is tested on Broadcom NS2 BCM958712K reference board.
>>>>
>>>> Repo: https://github.com/Broadcom/arm64-linux.git
>>>> Branch: ns2_drdphy_v8
>>>>
>>>> Raviteja Garimella (3):
>>>>   dt-bindings: phy: Add DT bindings documentation for NS2 USB DRD PHY
>>>>   phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2
>>>>   arm64: dts: NS2: Add USB DRD PHY device tree node
>>>>
>>>>  .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt   |  30 ++
>>>>  arch/arm64/boot/dts/broadcom/ns2.dtsi              |  14 +
>>>>  drivers/phy/Kconfig                                |  13 +
>>>>  drivers/phy/Makefile                               |   1 +
>>>>  drivers/phy/phy-bcm-ns2-usbdrd.c                   | 437 +++++++++++++++++++++
>>>>  5 files changed, 495 insertions(+)
>>>>  create mode 100644 Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt
>>>>  create mode 100644 drivers/phy/phy-bcm-ns2-usbdrd.c
>>>>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v8 0/3] Support for USB DRD PHY driver for NS2

[Kishon Vijay Abraham I]

On Friday 09 June 2017 04:23 PM, Raviteja Garimella wrote:
> Hi Kishon,
> 
> On Fri, Jun 9, 2017 at 2:36 PM, Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org> wrote:
>> Hi,
>>
>> On Friday 09 June 2017 02:30 PM, Raviteja Garimella wrote:
>>> Hi,
>>>
>>> On Fri, Jun 9, 2017 at 2:25 PM, Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org> wrote:
>>>> Hi,
>>>>
>>>> On Thursday 08 June 2017 04:05 PM, Raviteja Garimella wrote:
>>>>> Changes in v8:
>>>>> =============
>>>>> -Renamed phy shutdown routine
>>>>> -Used devm_request_irq in stead of threaded irq
>>>>
>>>> That's not what I intended. Continue to use threaded irq but remove delayed work.
>>>>
>>>
>>> Yes I get that. We see intermittent connection issues without delayed
>>> work. Debounce delay matters there.
>>
>> All right!
>>
>> I'm unable to apply the series. Please rebase to linux-phy next (directory
>> structure has changed)
>>
> 
> Ok. They got applied to linux-phy next for me without issues.
> I will resend the patchset anyways after rebasing to linux-phy next.

the patch you sent is not rebased to the latest linux-phy next.

-Kishon
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v8 0/3] Support for USB DRD PHY driver for NS2

[Raviteja Garimella]

Hi,

On Fri, Jun 9, 2017 at 4:46 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>
>
> On Friday 09 June 2017 04:23 PM, Raviteja Garimella wrote:
>> Hi Kishon,
>>
>> On Fri, Jun 9, 2017 at 2:36 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>>> Hi,
>>>
>>> On Friday 09 June 2017 02:30 PM, Raviteja Garimella wrote:
>>>> Hi,
>>>>
>>>> On Fri, Jun 9, 2017 at 2:25 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>>>>> Hi,
>>>>>
>>>>> On Thursday 08 June 2017 04:05 PM, Raviteja Garimella wrote:
>>>>>> Changes in v8:
>>>>>> =============
>>>>>> -Renamed phy shutdown routine
>>>>>> -Used devm_request_irq in stead of threaded irq
>>>>>
>>>>> That's not what I intended. Continue to use threaded irq but remove delayed work.
>>>>>
>>>>
>>>> Yes I get that. We see intermittent connection issues without delayed
>>>> work. Debounce delay matters there.
>>>
>>> All right!
>>>
>>> I'm unable to apply the series. Please rebase to linux-phy next (directory
>>> structure has changed)
>>>
>>
>> Ok. They got applied to linux-phy next for me without issues.
>> I will resend the patchset anyways after rebasing to linux-phy next.
>
> the patch you sent is not rebased to the latest linux-phy next.
>

Sorry.. That's correct, I am sending v9. Thanks.

> -Kishon