public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kurt Miller <lists@intricatesoftware.com>
To: u-boot@lists.denx.de
Subject: [PATCH] pci: Make Rockchip PCIe voltage regulators optional
Date: Thu, 28 May 2020 14:43:05 -0400	[thread overview]
Message-ID: <1590691385.9708.28.camel@intricatesoftware.com> (raw)
In-Reply-To: <20200524203251.28260-1-kettenis@openbsd.org>

On Sun, 2020-05-24 at 22:32 +0200, Mark Kettenis wrote:
> The vpcie*-supply properties are optional and these are absent on
> boards like the ROCKPro64 and Firefly RK3399 where the voltage is
> supplied by always-on regulators that are already enabled upon
> boot.??Make these regulators optional and properly check their
> presence before attempting to enable them.
> 
> Makes PCIe work on un U-Boot on the boards mentioned above.
> 
> Signed-off-by: Mark Kettenis <kettenis@openbsd.org>

Tested by: Kurt Miller <kurt@intricatesoftware.com>

Model: Pine64 RockPro64 v2.1

=> pci
Scanning PCI devices on bus 0
BusDevFun??VendorId???DeviceId???Device Class???????Sub-Class
_____________________________________________________________
00.00.00???0x1d87?????0x0100?????Bridge device???????????0x04
=> pci 1
Scanning PCI devices on bus 1
BusDevFun??VendorId???DeviceId???Device Class???????Sub-Class
_____________________________________________________________
01.00.00???0x1b4b?????0x9128?????Mass storage controller 0x06

> ---
> ?drivers/pci/pcie_rockchip.c | 33 ++++++++++++++++++++-------------
> ?1 file changed, 20 insertions(+), 13 deletions(-)
> 
> diff --git a/drivers/pci/pcie_rockchip.c b/drivers/pci/pcie_rockchip.c
> index 82a8396e42..0edc2464a8 100644
> --- a/drivers/pci/pcie_rockchip.c
> +++ b/drivers/pci/pcie_rockchip.c
> @@ -322,7 +322,7 @@ static int rockchip_pcie_set_vpcie(struct udevice *dev)
> ?	struct rockchip_pcie *priv = dev_get_priv(dev);
> ?	int ret;
> ?
> -	if (!IS_ERR(priv->vpcie3v3)) {
> +	if (priv->vpcie3v3) {
> ?		ret = regulator_set_enable(priv->vpcie3v3, true);
> ?		if (ret) {
> ?			dev_err(dev, "failed to enable vpcie3v3 (ret=%d)\n",
> @@ -331,24 +331,31 @@ static int rockchip_pcie_set_vpcie(struct udevice *dev)
> ?		}
> ?	}
> ?
> -	ret = regulator_set_enable(priv->vpcie1v8, true);
> -	if (ret) {
> -		dev_err(dev, "failed to enable vpcie1v8 (ret=%d)\n", ret);
> -		goto err_disable_3v3;
> +	if (priv->vpcie1v8) {
> +		ret = regulator_set_enable(priv->vpcie1v8, true);
> +		if (ret) {
> +			dev_err(dev, "failed to enable vpcie1v8 (ret=%d)\n",
> +				ret);
> +			goto err_disable_3v3;
> +		}
> ?	}
> ?
> -	ret = regulator_set_enable(priv->vpcie0v9, true);
> -	if (ret) {
> -		dev_err(dev, "failed to enable vpcie0v9 (ret=%d)\n", ret);
> -		goto err_disable_1v8;
> +	if (priv->vpcie0v9) {
> +		ret = regulator_set_enable(priv->vpcie0v9, true);
> +		if (ret) {
> +			dev_err(dev, "failed to enable vpcie0v9 (ret=%d)\n",
> +				ret);
> +			goto err_disable_1v8;
> +		}
> ?	}
> ?
> ?	return 0;
> ?
> ?err_disable_1v8:
> -	regulator_set_enable(priv->vpcie1v8, false);
> +	if (priv->vpcie1v8)
> +		regulator_set_enable(priv->vpcie1v8, false);
> ?err_disable_3v3:
> -	if (!IS_ERR(priv->vpcie3v3))
> +	if (priv->vpcie3v3)
> ?		regulator_set_enable(priv->vpcie3v3, false);
> ?	return ret;
> ?}
> @@ -424,14 +431,14 @@ static int rockchip_pcie_parse_dt(struct udevice *dev)
> ?
> ?	ret = device_get_supply_regulator(dev, "vpcie1v8-supply",
> ?					??&priv->vpcie1v8);
> -	if (ret) {
> +	if (ret && ret != -ENOENT) {
> ?		dev_err(dev, "failed to get vpcie1v8 supply (ret=%d)\n", ret);
> ?		return ret;
> ?	}
> ?
> ?	ret = device_get_supply_regulator(dev, "vpcie0v9-supply",
> ?					??&priv->vpcie0v9);
> -	if (ret) {
> +	if (ret && ret != -ENOENT) {
> ?		dev_err(dev, "failed to get vpcie0v9 supply (ret=%d)\n", ret);
> ?		return ret;
> ?	}

      parent reply	other threads:[~2020-05-28 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 20:32 [PATCH] pci: Make Rockchip PCIe voltage regulators optional Mark Kettenis
2020-05-25  2:56 ` Kever Yang
2020-06-01  0:56   ` Kever Yang
2020-05-25  9:10 ` Marcin Juszkiewicz
2020-05-28 18:43 ` Kurt Miller [this message]

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=1590691385.9708.28.camel@intricatesoftware.com \
    --to=lists@intricatesoftware.com \
    --cc=u-boot@lists.denx.de \
    /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