mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Elson Serrao <elson.serrao@oss.qualcomm.com>
To: Peter Chen <peter.chen@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Souradeep Chowdhury <quic_schowdhu@quicinc.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/9] usb: misc: qcom_eud: add per-path High-Speed PHY control
Date: Tue, 14 Jul 2026 17:32:34 -0700	[thread overview]
Message-ID: <4ffd0645-dc50-4157-b63b-5e93fd7520a7@oss.qualcomm.com> (raw)
In-Reply-To: <aktKpIXVnJeydgCE@hu-petche-lv.qualcomm.com>



On 7/5/2026 11:26 PM, Peter Chen wrote:
> On 26-05-01 10:06:29, Elson Serrao wrote:
>> EUD hardware can support multiple High-Speed USB paths, each routed
>> through its own PHY. The active path is selected in hardware via the
>> EUD_PORT_SEL register. As a High-Speed hub, EUD requires access to
>> the High-Speed PHY associated with the active path. To support this
>> multi-path capability, the driver must manage PHY resources on a
>> per-path basis, ensuring that the PHY for the currently selected
>> path is properly initialized and powered.
>>
>> This patch restructures the driver to implement per-path PHY management.
>> The driver now powers the appropriate PHY based on the selected and
>> enabled UTMI path, ensuring correct operation when EUD is enabled.
>>
>> Historically, EUD appeared to work on single-path systems because the
>> USB controller kept the PHY initialized. However, EUD is designed to
>> operate independently of the USB controller and therefore requires
>> explicit PHY control for proper operation.

[...]

>> +};
>> +
>>  struct eud_chip {
>>  	struct device			*dev;
>>  	struct usb_role_switch		*role_sw;
>>  	void __iomem			*base;
>> +	struct eud_path			*paths[EUD_MAX_PORTS];
>>  	phys_addr_t			mode_mgr;
>>  	unsigned int			int_status;
>>  	int				irq;
>>  	bool				enabled;
>>  	bool				usb_attached;
>> +	bool				phy_enabled;
> 
> There is already a 'enabled' flag, could be leveraged or still need
> a new 'phy_enabled' flag?
> 
enabled reflects the user's sysfs intent, while phy_enabled tracks the
actual PHY power state. These need to stay independent because a later
patch in this series ("add host mode coordination") disables/re-enables
the PHY on host-mode role transitions without touching chip->enabled, so
as to preserve the user's original sysfs setting across the transition.

Thanks,
Elson

u8				port_idx;
>>  };
>>  
>> +static int eud_phy_enable(struct eud_chip *chip)
>> +{
>> +	struct phy *phy;
>> +	int ret;
>> +
>> +	if (chip->phy_enabled)
>> +		return 0;
>> +
>> +	phy = chip->paths[chip->port_idx]->phy;
>> +
>> +	ret = phy_init(phy);
>> +	if (ret) {
>> +		dev_err(chip->dev, "Failed to initialize USB2 PHY for port %u: %d\n",
>> +			chip->port_idx, ret);
>> +		return ret;
>> +	}
>> +
>> +	ret = phy_power_on(phy);
>> +	if (ret) {
>> +		dev_err(chip->dev, "Failed to power on USB2 PHY for port %u: %d\n",
>> +			chip->port_idx, ret);
>> +		phy_exit(phy);
>> +		return ret;
>> +	}
>> +
>> +	chip->phy_enabled = true;
>> +
>> +	return 0;
>> +}
>> +
>> +static void eud_phy_disable(struct eud_chip *chip)
>> +{
>> +	struct phy *phy;
>> +
>> +	if (!chip->phy_enabled)
>> +		return;
>> +
>> +	phy = chip->paths[chip->port_idx]->phy;
>> +
>> +	phy_power_off(phy);
>> +	phy_exit(phy);
>> +	chip->phy_enabled = false;
>> +}
>> +
>>  static int enable_eud(struct eud_chip *priv)
>>  {
>>  	int ret;
>>  
>> -	ret = qcom_scm_io_writel(priv->mode_mgr + EUD_REG_EUD_EN2, 1);
>> +	ret = eud_phy_enable(priv);
>>  	if (ret)
>>  		return ret;
>>  
>> +	ret = qcom_scm_io_writel(priv->mode_mgr + EUD_REG_EUD_EN2, 1);
>> +	if (ret) {
>> +		eud_phy_disable(priv);
>> +		return ret;
>> +	}
>> +
>>  	writel(EUD_ENABLE, priv->base + EUD_REG_CSR_EUD_EN);
>>  	writel(EUD_INT_VBUS | EUD_INT_SAFE_MODE,
>>  			priv->base + EUD_REG_INT1_EN_MASK);
>> @@ -75,6 +135,8 @@ static int disable_eud(struct eud_chip *priv)
>>  		return ret;
>>  
>>  	writel(0, priv->base + EUD_REG_CSR_EUD_EN);
>> +	eud_phy_disable(priv);
>> +
>>  	return 0;
>>  }
>>  
>> @@ -130,6 +192,12 @@ static ssize_t port_store(struct device *dev, struct device_attribute *attr,
>>  	if (port < 0)
>>  		return port;
>>  
>> +	/* Check if the corresponding path is available */
>> +	if (!chip->paths[port]) {
>> +		dev_err(chip->dev, "EUD not supported on selected port\n");
>> +		return -EOPNOTSUPP;
>> +	}
>> +
>>  	/* Port selection must be done before enabling EUD */
>>  	if (chip->enabled) {
>>  		dev_err(chip->dev, "Cannot change port while EUD is enabled\n");
>> @@ -229,8 +297,54 @@ static void eud_role_switch_release(void *data)
>>  	usb_role_switch_put(chip->role_sw);
>>  }
>>  
>> +static int eud_init_path(struct eud_chip *chip, struct device_node *np)
>> +{
>> +	struct device_node *controller_node;
>> +	struct eud_path *path;
>> +	u32 path_num;
>> +	int ret;
>> +
>> +	ret = of_property_read_u32(np, "reg", &path_num);
>> +	if (ret) {
>> +		/* Legacy DT uses 'ports' node without 'reg' property; treat as path 0 */
>> +		if (of_node_name_eq(np, "ports"))
>> +			path_num = 0;
>> +		else
>> +			return dev_err_probe(chip->dev, ret, "unexpected child node '%s'\n",
>> +					     np->name);
>> +	}
>> +
>> +	if (path_num >= EUD_MAX_PORTS)
>> +		return dev_err_probe(chip->dev, -EINVAL, "invalid path number: %u (max %d)\n",
>> +				     path_num, EUD_MAX_PORTS - 1);
>> +
>> +	path = devm_kzalloc(chip->dev, sizeof(*path), GFP_KERNEL);
>> +	if (!path)
>> +		return -ENOMEM;
>> +
>> +	path->chip = chip;
>> +	path->num = path_num;
>> +
>> +	controller_node = of_graph_get_remote_node(np, 0, -1);
>> +	if (!controller_node)
>> +		return dev_err_probe(chip->dev, -ENODEV,
>> +				     "failed to get controller node for path %u\n", path_num);
>> +
>> +	path->phy = devm_of_phy_get_by_index(chip->dev, controller_node, 0);
>> +	of_node_put(controller_node);
>> +
>> +	if (IS_ERR(path->phy))
>> +		return dev_err_probe(chip->dev, PTR_ERR(path->phy),
>> +				     "failed to get PHY for path %d\n", path_num);
>> +
>> +	chip->paths[path_num] = path;
>> +
>> +	return 0;
>> +}
>> +
>>  static int eud_probe(struct platform_device *pdev)
>>  {
>> +	struct device_node *np = pdev->dev.of_node;
>>  	struct eud_chip *chip;
>>  	struct resource *res;
>>  	int ret;
>> @@ -241,6 +355,16 @@ static int eud_probe(struct platform_device *pdev)
>>  
>>  	chip->dev = &pdev->dev;
>>  
>> +	for_each_child_of_node_scoped(np, child) {
>> +		ret = eud_init_path(chip, child);
>> +		if (ret)
>> +			return ret;
>> +	}
>> +
>> +	/* Primary path is mandatory. Secondary is optional */
>> +	if (!chip->paths[0])
>> +		return dev_err_probe(chip->dev, -ENODEV, "primary path not found\n");
>> +
>>  	chip->role_sw = usb_role_switch_get(&pdev->dev);
>>  	if (IS_ERR(chip->role_sw))
>>  		return dev_err_probe(chip->dev, PTR_ERR(chip->role_sw),
>> -- 
>> 2.34.1
>>
>>
> 

  reply	other threads:[~2026-07-15  0:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 17:06 [PATCH v4 0/9] Improve Qualcomm EUD driver and platform support Elson Serrao
2026-05-01 17:06 ` [PATCH v4 1/9] dt-bindings: soc: qcom: eud: Add per-path child nodes for UTMI routing Elson Serrao
2026-07-03  7:45   ` Krzysztof Kozlowski
2026-07-03  8:56     ` Konrad Dybcio
2026-07-04  0:01       ` Dmitry Baryshkov
2026-07-07 23:20         ` Elson Serrao
2026-07-07 23:43     ` Elson Serrao
2026-07-04  0:05   ` Dmitry Baryshkov
2026-07-06  9:27     ` Konrad Dybcio
2026-07-07 23:23       ` Elson Serrao
2026-07-08  6:14         ` Dmitry Baryshkov
2026-05-01 17:06 ` [PATCH v4 2/9] usb: misc: qcom_eud: add sysfs attribute for port selection Elson Serrao
2026-06-25 11:51   ` Konrad Dybcio
2026-07-06  5:06   ` Peter Chen
2026-05-01 17:06 ` [PATCH v4 3/9] usb: misc: qcom_eud: add per-path High-Speed PHY control Elson Serrao
2026-07-06  6:26   ` Peter Chen
2026-07-15  0:32     ` Elson Serrao [this message]
2026-07-15  5:33       ` Peter Chen
2026-05-01 17:06 ` [PATCH v4 4/9] usb: misc: qcom_eud: add per-path role switch support Elson Serrao
2026-07-06  3:32   ` Peter Chen
2026-07-07 23:48     ` Elson Serrao
2026-05-01 17:06 ` [PATCH v4 5/9] usb: misc: qcom_eud: improve enable_store API Elson Serrao
2026-07-06  6:28   ` Peter Chen
2026-05-01 17:06 ` [PATCH v4 6/9] usb: misc: qcom_eud: add host mode coordination Elson Serrao
2026-07-06  6:46   ` Peter Chen
2026-07-15  0:40     ` Elson Serrao
2026-05-01 17:06 ` [PATCH v4 7/9] usb: misc: qcom_eud: fix virtual attach/detach event handling Elson Serrao
2026-07-06  6:54   ` Peter Chen
2026-05-01 17:06 ` [PATCH v4 8/9] arm64: dts: qcom: kodiak: Describe EUD UTMI path using child node Elson Serrao
2026-05-01 17:06 ` [PATCH v4 9/9] arm64: dts: qcom: Map USB connector to EUD on Kodiak boards Elson Serrao
2026-06-29 14:48 ` [PATCH v4 0/9] Improve Qualcomm EUD driver and platform support Elson Serrao
2026-07-04  0:06   ` Dmitry Baryshkov
2026-07-06  9:29 ` Konrad Dybcio

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=4ffd0645-dc50-4157-b63b-5e93fd7520a7@oss.qualcomm.com \
    --to=elson.serrao@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@kernel.org \
    --cc=quic_schowdhu@quicinc.com \
    --cc=robh@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

all inboxes | Powered by JetHome®