From: jingoohan1@gmail.com (Jingoo Han)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] PCI: dwc: Handle host_init failures
Date: Mon, 17 Jul 2017 15:28:13 -0400 [thread overview]
Message-ID: <000a01d2ff32$d5d59e00$8180da00$@gmail.com> (raw)
In-Reply-To: <73b9c442-38f6-cc5b-c6e0-4ce7187dc0a8@synopsys.com>
On Monday, July 17, 2017 7:18 AM, Joao Pinto wrote:
>
> Hi Bjorn Andersson,
>
> ?s 7:39 AM de 7/16/2017, Bjorn Andersson escreveu:
> > In several dwc based drivers host_init can fail, so make sure to
> > propagate and handle this to avoid continuing operation of a driver or
> > hardware in an invalid state.
> >
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > ---
> > drivers/pci/dwc/pci-dra7xx.c | 4 +++-
> > drivers/pci/dwc/pci-exynos.c | 4 +++-
> > drivers/pci/dwc/pci-imx6.c | 4 +++-
> > drivers/pci/dwc/pci-keystone.c | 4 +++-
> > drivers/pci/dwc/pci-layerscape.c | 14 ++++++++++----
> > drivers/pci/dwc/pcie-armada8k.c | 4 +++-
> > drivers/pci/dwc/pcie-artpec6.c | 4 +++-
> > drivers/pci/dwc/pcie-designware-host.c | 7 +++++--
> > drivers/pci/dwc/pcie-designware-plat.c | 4 +++-
> > drivers/pci/dwc/pcie-designware.h | 2 +-
> > drivers/pci/dwc/pcie-kirin.c | 4 +++-
> > drivers/pci/dwc/pcie-qcom.c | 6 ++++--
> > drivers/pci/dwc/pcie-spear13xx.c | 4 +++-
> > 13 files changed, 47 insertions(+), 18 deletions(-)
> >
[.....]
>
> A step in the right direction :). In the future we should add host init
> validation in the specific SoC drivers, like Layerscape and Qcom have, to
> assure
> that any problem is treated properly in the core driver.
I agree with your opinion.
>
> Acked-by: Joao Pinto <jpinto@synopsys.com>
Acked-by: Jingoo Han <jingoohan1@gmail.com>
Best regards,
Jingoo Han
next prev parent reply other threads:[~2017-07-17 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 6:39 [PATCH 1/3] PCI: dwc: Handle host_init failures Bjorn Andersson
2017-07-17 11:18 ` Joao Pinto
2017-07-17 19:28 ` Jingoo Han [this message]
2017-08-03 21:19 ` Bjorn Helgaas
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='000a01d2ff32$d5d59e00$8180da00$@gmail.com' \
--to=jingoohan1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).