[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d416f9b3-20d9-0339-a4d2-9a4ba0669633@linaro.org>
Date: Fri, 2 Dec 2016 11:51:26 +0000
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Joao Pinto <Joao.Pinto@...opsys.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org
Cc: Kishon Vijay Abraham I <kishon@...com>,
Jingoo Han <jingoohan1@...il.com>,
Kukjin Kim <kgene@...nel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Javier Martinez Canillas <javier@....samsung.com>,
Richard Zhu <Richard.Zhu@...escale.com>,
Lucas Stach <l.stach@...gutronix.de>,
Murali Karicheri <m-karicheri2@...com>,
Minghuan Lian <minghuan.Lian@...escale.com>,
Mingkai Hu <mingkai.hu@...escale.com>,
Roy Zang <tie-fei.zang@...escale.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Jose Abreu <Jose.Abreu@...opsys.com>,
Pratyush Anand <pratyush.anand@...il.com>,
Stanimir Varbanov <svarbanov@...sol.com>,
linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [RFC PATCH] PCI: designware: add host_init() error handling
On 02/12/16 10:32, Joao Pinto wrote:
>
> Hi Srinivas,
>
> Às 11:51 AM de 12/1/2016, Srinivas Kandagatla escreveu:
>> drivers/pci/host/pci-dra7xx.c | 4 +++-
>> drivers/pci/host/pci-exynos.c | 4 +++-
>> drivers/pci/host/pci-imx6.c | 4 +++-
>> drivers/pci/host/pci-keystone.c | 4 +++-
>> drivers/pci/host/pci-layerscape.c | 12 ++++++++----
>> drivers/pci/host/pcie-armada8k.c | 4 +++-
>> drivers/pci/host/pcie-designware-plat.c | 4 +++-
>> drivers/pci/host/pcie-designware.c | 4 +++-
>> drivers/pci/host/pcie-designware.h | 2 +-
>> drivers/pci/host/pcie-qcom.c | 6 ++++--
>> drivers/pci/host/pcie-spear13xx.c | 4 +++-
>> 11 files changed, 37 insertions(+), 15 deletions(-)
>>
>
> Thanks for the patch!
>
> In my opinion your idea is good but only qcom driver is able to detect failure
> in the specific host init routine, all others have a 'return 0' even if
> something not well init. I would recomend that we take this issue a bit further
> and add the error checking to all specific pci drivers in order to make them as
> robust as qcom'.
I totally agree with you, I can give this a go in next version.
Thanks,
srini
>
> Thanks,
> Joao
>
Powered by blists - more mailing lists