From: Andrew Murray <andrew.murray@arm.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 5/5] PCI: iproc: Properly handle optional PHYs
Date: Wed, 28 Aug 2019 22:26:55 +0100 [thread overview]
Message-ID: <20190828212655.GG14582@e119886-lin.cambridge.arm.com> (raw)
In-Reply-To: <20190828163636.12967-5-thierry.reding@gmail.com>
On Wed, Aug 28, 2019 at 06:36:36PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> devm_phy_get() can fail for a number of resides besides probe deferral.
> It can for example return -ENOMEM if it runs out of memory as it tries
> to allocate devres structures. Propagating only -EPROBE_DEFER is
> problematic because it results in these legitimately fatal errors being
> treated as "PHY not specified in DT".
>
> What we really want is to ignore the optional PHYs only if they have not
> been specified in DT. devm_phy_optional_get() is a function that exactly
> does what's required here, so use that instead.
>
> Cc: Ray Jui <rjui@broadcom.com>
> Cc: Scott Branden <sbranden@broadcom.com>
> Cc: bcm-kernel-feedback-list@broadcom.com
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> drivers/pci/controller/pcie-iproc-platform.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/pci/controller/pcie-iproc-platform.c b/drivers/pci/controller/pcie-iproc-platform.c
> index 5a3550b6bb29..9ee6200a66f4 100644
> --- a/drivers/pci/controller/pcie-iproc-platform.c
> +++ b/drivers/pci/controller/pcie-iproc-platform.c
> @@ -93,12 +93,9 @@ static int iproc_pcie_pltfm_probe(struct platform_device *pdev)
> pcie->need_ib_cfg = of_property_read_bool(np, "dma-ranges");
>
> /* PHY use is optional */
> - pcie->phy = devm_phy_get(dev, "pcie-phy");
> - if (IS_ERR(pcie->phy)) {
> - if (PTR_ERR(pcie->phy) == -EPROBE_DEFER)
> - return -EPROBE_DEFER;
> - pcie->phy = NULL;
> - }
> + pcie->phy = devm_phy_optional_get(dev, "pcie-phy");
> + if (IS_ERR(pcie->phy))
> + return PTR_ERR(pcie->phy);
Once you've applied Bjorn's feedback you can add:
Reviewed-by: Andrew Murray <andrew.murray@arm.com>
I initially thought that you forgot to check for -ENODEV - though I can see
that the implementation of devm_phy_optional_get very helpfully does this for
us and returns NULL instead of an error.
What is also confusing is that devm_regulator_get_optional, despite its
_optional suffix doesn't do this and returns an error. I wonder if
devm_phy_optional_get should be changed to return NULL instead of an error
instead of -ENODEV. I've copied Liam/Mark for feedback.
Thanks,
Andrew Murray
>
> ret = devm_of_pci_get_host_bridge_resources(dev, 0, 0xff, &resources,
> &iobase);
> --
> 2.22.0
>
next prev parent reply other threads:[~2019-08-28 21:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 16:36 [PATCH 1/5] PCI: exynos: Properly handle optional PHYs Thierry Reding
2019-08-28 16:36 ` [PATCH 2/5] PCI: imx6: Properly handle optional regulators Thierry Reding
2019-08-28 21:09 ` Andrew Murray
2019-08-28 16:36 ` [PATCH 3/5] PCI: armada8x: Properly handle optional PHYs Thierry Reding
2019-08-28 21:09 ` Andrew Murray
2019-08-28 16:36 ` [PATCH 4/5] PCI: histb: Properly handle optional regulators Thierry Reding
2019-08-28 21:09 ` Andrew Murray
2019-08-28 16:36 ` [PATCH 5/5] PCI: iproc: Properly handle optional PHYs Thierry Reding
2019-08-28 21:26 ` Andrew Murray [this message]
2019-08-28 21:49 ` Mark Brown
2019-08-29 10:09 ` Andrew Murray
2019-08-29 10:48 ` Thierry Reding
2019-08-29 12:13 ` Andrew Murray
2019-08-29 11:17 ` Mark Brown
2019-08-29 11:46 ` Thierry Reding
2019-08-29 12:08 ` Andrew Murray
2019-08-29 13:16 ` Mark Brown
2019-08-29 13:43 ` Andrew Murray
2019-08-29 15:25 ` Mark Brown
2019-08-29 13:03 ` Mark Brown
2019-08-29 14:58 ` Thierry Reding
2019-08-29 17:55 ` Mark Brown
2019-08-28 17:54 ` [PATCH 1/5] PCI: exynos: " Bjorn Helgaas
2019-08-28 21:08 ` Andrew Murray
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=20190828212655.GG14582@e119886-lin.cambridge.arm.com \
--to=andrew.murray@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=thierry.reding@gmail.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).