From: "Heiko Stübner" <heiko@sntech.de>
To: Peter Geis <pgwipeout@gmail.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Marc Zyngier" <maz@kernel.org>, PCI <linux-pci@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Nicolas Frattaroli" <frattaroli.nicolas@gmail.com>
Subject: Re: [PATCH v9 2/5] PCI: rockchip-dwc: Reset core at driver probe
Date: Wed, 11 May 2022 17:23:28 +0200 [thread overview]
Message-ID: <1860493.taCxCBeP46@diego> (raw)
In-Reply-To: <YnvPdSPUm85Bg9zE@lpieralisi>
Am Mittwoch, 11. Mai 2022, 17:00:05 CEST schrieb Lorenzo Pieralisi:
> On Wed, May 11, 2022 at 10:26:20AM -0400, Peter Geis wrote:
> > On Wed, May 11, 2022 at 9:50 AM Lorenzo Pieralisi
> > <lorenzo.pieralisi@arm.com> wrote:
> > >
> > > On Fri, Apr 29, 2022 at 08:38:28AM -0400, Peter Geis wrote:
> > > > The PCIe controller is in an unknown state at driver probe. This can
> > > > lead to undesireable effects when the driver attempts to configure the
> > > > controller.
> > > >
> > > > Prevent issues in the future by resetting the core during probe.
> > > >
> > > > Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> > > > Tested-by: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
> > > > ---
> > > > drivers/pci/controller/dwc/pcie-dw-rockchip.c | 23 ++++++++-----------
> > > > 1 file changed, 10 insertions(+), 13 deletions(-)
> > >
> > > I fear that the controller reset behaviour is bootloader/firmware
> > > dependent.
> > >
> > > Are we sure we are not triggering any regressions by resetting the
> > > controller in the middle of probe (aka is the driver implicitly
> > > relying on existing behaviour on systems that are not the ones
> > > you are testing on) ?
> > >
> > > Just asking, the rockchip maintainers should be able to answer this
> > > question.
> >
> > This is a new driver with no current users, this series enables the
> > first user. It does not support ACPI nor any sort of handoff at this
> > time.
>
> Ok. I will take patches [1-3], dts changes will have to go via
> platform trees, I hope that's fine.
yep, that sounds great and I'll pick the dts patches then :-)
Thanks
Heiko
> > > > diff --git a/drivers/pci/controller/dwc/pcie-dw-rockchip.c b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > index c9b341e55cbb..faedbd6ebc20 100644
> > > > --- a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > +++ b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > @@ -152,6 +152,11 @@ static int rockchip_pcie_resource_get(struct platform_device *pdev,
> > > > if (IS_ERR(rockchip->rst_gpio))
> > > > return PTR_ERR(rockchip->rst_gpio);
> > > >
> > > > + rockchip->rst = devm_reset_control_array_get_exclusive(&pdev->dev);
> > > > + if (IS_ERR(rockchip->rst))
> > > > + return dev_err_probe(&pdev->dev, PTR_ERR(rockchip->rst),
> > > > + "failed to get reset lines\n");
> > > > +
> > > > return 0;
> > > > }
> > > >
> > > > @@ -182,18 +187,6 @@ static void rockchip_pcie_phy_deinit(struct rockchip_pcie *rockchip)
> > > > phy_power_off(rockchip->phy);
> > > > }
> > > >
> > > > -static int rockchip_pcie_reset_control_release(struct rockchip_pcie *rockchip)
> > > > -{
> > > > - struct device *dev = rockchip->pci.dev;
> > > > -
> > > > - rockchip->rst = devm_reset_control_array_get_exclusive(dev);
> > > > - if (IS_ERR(rockchip->rst))
> > > > - return dev_err_probe(dev, PTR_ERR(rockchip->rst),
> > > > - "failed to get reset lines\n");
> > > > -
> > > > - return reset_control_deassert(rockchip->rst);
> > > > -}
> > > > -
> > > > static const struct dw_pcie_ops dw_pcie_ops = {
> > > > .link_up = rockchip_pcie_link_up,
> > > > .start_link = rockchip_pcie_start_link,
> > > > @@ -222,6 +215,10 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
> > > > if (ret)
> > > > return ret;
> > > >
> > > > + ret = reset_control_assert(rockchip->rst);
> > > > + if (ret)
> > > > + return ret;
> > > > +
> > > > /* DON'T MOVE ME: must be enable before PHY init */
> > > > rockchip->vpcie3v3 = devm_regulator_get_optional(dev, "vpcie3v3");
> > > > if (IS_ERR(rockchip->vpcie3v3)) {
> > > > @@ -241,7 +238,7 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
> > > > if (ret)
> > > > goto disable_regulator;
> > > >
> > > > - ret = rockchip_pcie_reset_control_release(rockchip);
> > > > + ret = reset_control_deassert(rockchip->rst);
> > > > if (ret)
> > > > goto deinit_phy;
> > > >
> > > > --
> > > > 2.25.1
> > > >
>
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Peter Geis <pgwipeout@gmail.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Marc Zyngier" <maz@kernel.org>, PCI <linux-pci@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Nicolas Frattaroli" <frattaroli.nicolas@gmail.com>
Subject: Re: [PATCH v9 2/5] PCI: rockchip-dwc: Reset core at driver probe
Date: Wed, 11 May 2022 17:23:28 +0200 [thread overview]
Message-ID: <1860493.taCxCBeP46@diego> (raw)
In-Reply-To: <YnvPdSPUm85Bg9zE@lpieralisi>
Am Mittwoch, 11. Mai 2022, 17:00:05 CEST schrieb Lorenzo Pieralisi:
> On Wed, May 11, 2022 at 10:26:20AM -0400, Peter Geis wrote:
> > On Wed, May 11, 2022 at 9:50 AM Lorenzo Pieralisi
> > <lorenzo.pieralisi@arm.com> wrote:
> > >
> > > On Fri, Apr 29, 2022 at 08:38:28AM -0400, Peter Geis wrote:
> > > > The PCIe controller is in an unknown state at driver probe. This can
> > > > lead to undesireable effects when the driver attempts to configure the
> > > > controller.
> > > >
> > > > Prevent issues in the future by resetting the core during probe.
> > > >
> > > > Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> > > > Tested-by: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
> > > > ---
> > > > drivers/pci/controller/dwc/pcie-dw-rockchip.c | 23 ++++++++-----------
> > > > 1 file changed, 10 insertions(+), 13 deletions(-)
> > >
> > > I fear that the controller reset behaviour is bootloader/firmware
> > > dependent.
> > >
> > > Are we sure we are not triggering any regressions by resetting the
> > > controller in the middle of probe (aka is the driver implicitly
> > > relying on existing behaviour on systems that are not the ones
> > > you are testing on) ?
> > >
> > > Just asking, the rockchip maintainers should be able to answer this
> > > question.
> >
> > This is a new driver with no current users, this series enables the
> > first user. It does not support ACPI nor any sort of handoff at this
> > time.
>
> Ok. I will take patches [1-3], dts changes will have to go via
> platform trees, I hope that's fine.
yep, that sounds great and I'll pick the dts patches then :-)
Thanks
Heiko
> > > > diff --git a/drivers/pci/controller/dwc/pcie-dw-rockchip.c b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > index c9b341e55cbb..faedbd6ebc20 100644
> > > > --- a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > +++ b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > @@ -152,6 +152,11 @@ static int rockchip_pcie_resource_get(struct platform_device *pdev,
> > > > if (IS_ERR(rockchip->rst_gpio))
> > > > return PTR_ERR(rockchip->rst_gpio);
> > > >
> > > > + rockchip->rst = devm_reset_control_array_get_exclusive(&pdev->dev);
> > > > + if (IS_ERR(rockchip->rst))
> > > > + return dev_err_probe(&pdev->dev, PTR_ERR(rockchip->rst),
> > > > + "failed to get reset lines\n");
> > > > +
> > > > return 0;
> > > > }
> > > >
> > > > @@ -182,18 +187,6 @@ static void rockchip_pcie_phy_deinit(struct rockchip_pcie *rockchip)
> > > > phy_power_off(rockchip->phy);
> > > > }
> > > >
> > > > -static int rockchip_pcie_reset_control_release(struct rockchip_pcie *rockchip)
> > > > -{
> > > > - struct device *dev = rockchip->pci.dev;
> > > > -
> > > > - rockchip->rst = devm_reset_control_array_get_exclusive(dev);
> > > > - if (IS_ERR(rockchip->rst))
> > > > - return dev_err_probe(dev, PTR_ERR(rockchip->rst),
> > > > - "failed to get reset lines\n");
> > > > -
> > > > - return reset_control_deassert(rockchip->rst);
> > > > -}
> > > > -
> > > > static const struct dw_pcie_ops dw_pcie_ops = {
> > > > .link_up = rockchip_pcie_link_up,
> > > > .start_link = rockchip_pcie_start_link,
> > > > @@ -222,6 +215,10 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
> > > > if (ret)
> > > > return ret;
> > > >
> > > > + ret = reset_control_assert(rockchip->rst);
> > > > + if (ret)
> > > > + return ret;
> > > > +
> > > > /* DON'T MOVE ME: must be enable before PHY init */
> > > > rockchip->vpcie3v3 = devm_regulator_get_optional(dev, "vpcie3v3");
> > > > if (IS_ERR(rockchip->vpcie3v3)) {
> > > > @@ -241,7 +238,7 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
> > > > if (ret)
> > > > goto disable_regulator;
> > > >
> > > > - ret = rockchip_pcie_reset_control_release(rockchip);
> > > > + ret = reset_control_deassert(rockchip->rst);
> > > > if (ret)
> > > > goto deinit_phy;
> > > >
> > > > --
> > > > 2.25.1
> > > >
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Peter Geis <pgwipeout@gmail.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Marc Zyngier" <maz@kernel.org>, PCI <linux-pci@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Nicolas Frattaroli" <frattaroli.nicolas@gmail.com>
Subject: Re: [PATCH v9 2/5] PCI: rockchip-dwc: Reset core at driver probe
Date: Wed, 11 May 2022 17:23:28 +0200 [thread overview]
Message-ID: <1860493.taCxCBeP46@diego> (raw)
In-Reply-To: <YnvPdSPUm85Bg9zE@lpieralisi>
Am Mittwoch, 11. Mai 2022, 17:00:05 CEST schrieb Lorenzo Pieralisi:
> On Wed, May 11, 2022 at 10:26:20AM -0400, Peter Geis wrote:
> > On Wed, May 11, 2022 at 9:50 AM Lorenzo Pieralisi
> > <lorenzo.pieralisi@arm.com> wrote:
> > >
> > > On Fri, Apr 29, 2022 at 08:38:28AM -0400, Peter Geis wrote:
> > > > The PCIe controller is in an unknown state at driver probe. This can
> > > > lead to undesireable effects when the driver attempts to configure the
> > > > controller.
> > > >
> > > > Prevent issues in the future by resetting the core during probe.
> > > >
> > > > Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> > > > Tested-by: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
> > > > ---
> > > > drivers/pci/controller/dwc/pcie-dw-rockchip.c | 23 ++++++++-----------
> > > > 1 file changed, 10 insertions(+), 13 deletions(-)
> > >
> > > I fear that the controller reset behaviour is bootloader/firmware
> > > dependent.
> > >
> > > Are we sure we are not triggering any regressions by resetting the
> > > controller in the middle of probe (aka is the driver implicitly
> > > relying on existing behaviour on systems that are not the ones
> > > you are testing on) ?
> > >
> > > Just asking, the rockchip maintainers should be able to answer this
> > > question.
> >
> > This is a new driver with no current users, this series enables the
> > first user. It does not support ACPI nor any sort of handoff at this
> > time.
>
> Ok. I will take patches [1-3], dts changes will have to go via
> platform trees, I hope that's fine.
yep, that sounds great and I'll pick the dts patches then :-)
Thanks
Heiko
> > > > diff --git a/drivers/pci/controller/dwc/pcie-dw-rockchip.c b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > index c9b341e55cbb..faedbd6ebc20 100644
> > > > --- a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > +++ b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> > > > @@ -152,6 +152,11 @@ static int rockchip_pcie_resource_get(struct platform_device *pdev,
> > > > if (IS_ERR(rockchip->rst_gpio))
> > > > return PTR_ERR(rockchip->rst_gpio);
> > > >
> > > > + rockchip->rst = devm_reset_control_array_get_exclusive(&pdev->dev);
> > > > + if (IS_ERR(rockchip->rst))
> > > > + return dev_err_probe(&pdev->dev, PTR_ERR(rockchip->rst),
> > > > + "failed to get reset lines\n");
> > > > +
> > > > return 0;
> > > > }
> > > >
> > > > @@ -182,18 +187,6 @@ static void rockchip_pcie_phy_deinit(struct rockchip_pcie *rockchip)
> > > > phy_power_off(rockchip->phy);
> > > > }
> > > >
> > > > -static int rockchip_pcie_reset_control_release(struct rockchip_pcie *rockchip)
> > > > -{
> > > > - struct device *dev = rockchip->pci.dev;
> > > > -
> > > > - rockchip->rst = devm_reset_control_array_get_exclusive(dev);
> > > > - if (IS_ERR(rockchip->rst))
> > > > - return dev_err_probe(dev, PTR_ERR(rockchip->rst),
> > > > - "failed to get reset lines\n");
> > > > -
> > > > - return reset_control_deassert(rockchip->rst);
> > > > -}
> > > > -
> > > > static const struct dw_pcie_ops dw_pcie_ops = {
> > > > .link_up = rockchip_pcie_link_up,
> > > > .start_link = rockchip_pcie_start_link,
> > > > @@ -222,6 +215,10 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
> > > > if (ret)
> > > > return ret;
> > > >
> > > > + ret = reset_control_assert(rockchip->rst);
> > > > + if (ret)
> > > > + return ret;
> > > > +
> > > > /* DON'T MOVE ME: must be enable before PHY init */
> > > > rockchip->vpcie3v3 = devm_regulator_get_optional(dev, "vpcie3v3");
> > > > if (IS_ERR(rockchip->vpcie3v3)) {
> > > > @@ -241,7 +238,7 @@ static int rockchip_pcie_probe(struct platform_device *pdev)
> > > > if (ret)
> > > > goto disable_regulator;
> > > >
> > > > - ret = rockchip_pcie_reset_control_release(rockchip);
> > > > + ret = reset_control_deassert(rockchip->rst);
> > > > if (ret)
> > > > goto deinit_phy;
> > > >
> > > > --
> > > > 2.25.1
> > > >
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-11 15:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 12:38 [PATCH v9 0/5] Enable rk356x PCIe controller Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 12:38 ` [PATCH v9 1/5] dt-bindings: PCI: Remove fallback from Rockchip DesignWare binding Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 12:38 ` [PATCH v9 2/5] PCI: rockchip-dwc: Reset core at driver probe Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-05-11 13:50 ` Lorenzo Pieralisi
2022-05-11 13:50 ` Lorenzo Pieralisi
2022-05-11 13:50 ` Lorenzo Pieralisi
2022-05-11 14:26 ` Peter Geis
2022-05-11 14:26 ` Peter Geis
2022-05-11 14:26 ` Peter Geis
2022-05-11 15:00 ` Lorenzo Pieralisi
2022-05-11 15:00 ` Lorenzo Pieralisi
2022-05-11 15:00 ` Lorenzo Pieralisi
2022-05-11 15:23 ` Heiko Stübner [this message]
2022-05-11 15:23 ` Heiko Stübner
2022-05-11 15:23 ` Heiko Stübner
2022-04-29 12:38 ` [PATCH v9 3/5] PCI: rockchip-dwc: Add legacy interrupt support Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 18:07 ` Marc Zyngier
2022-04-29 18:07 ` Marc Zyngier
2022-04-29 18:07 ` Marc Zyngier
2022-04-29 12:38 ` [PATCH v9 4/5] arm64: dts: rockchip: Add rk3568 PCIe2x1 controller Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-05-15 19:17 ` Heiko Stübner
2022-05-15 19:17 ` Heiko Stübner
2022-05-15 19:17 ` Heiko Stübner
2022-04-29 12:38 ` [PATCH v9 5/5] arm64: dts: rockchip: Enable PCIe controller on quartz64-a Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-04-29 12:38 ` Peter Geis
2022-05-10 21:11 ` [PATCH v9 0/5] Enable rk356x PCIe controller Peter Geis
2022-05-10 21:11 ` Peter Geis
2022-05-10 21:11 ` Peter Geis
2022-05-10 21:15 ` Heiko Stübner
2022-05-10 21:15 ` Heiko Stübner
2022-05-10 21:15 ` Heiko Stübner
2022-05-11 15:15 ` (subset) " Lorenzo Pieralisi
2022-05-11 15:15 ` Lorenzo Pieralisi
2022-05-11 15:15 ` Lorenzo Pieralisi
2022-05-15 19:47 ` Heiko Stuebner
2022-05-15 19:47 ` Heiko Stuebner
2022-05-15 19:47 ` Heiko Stuebner
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=1860493.taCxCBeP46@diego \
--to=heiko@sntech.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frattaroli.nicolas@gmail.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pgwipeout@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.