From: Naveen Naidu <naveennaidu479@gmail.com> To: bhelgaas@google.com Cc: "Naveen Naidu" <naveennaidu479@gmail.com>, linux-kernel-mentees@lists.linuxfoundation.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>, "Rob Herring" <robh@kernel.org>, "Krzysztof Wilczyński" <kw@linux.com>, "Jingoo Han" <jingoohan1@gmail.com>, "Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>, "Marc Zyngier" <maz@kernel.org> Subject: [PATCH 20/22] PCI: keystone: Use PCI_ERROR_RESPONSE to specify hardware error Date: Mon, 11 Oct 2021 23:41:52 +0530 [thread overview] Message-ID: <01c86d23327e28ee6d09daa01538f1a12f9e4d11.1633972263.git.naveennaidu479@gmail.com> (raw) In-Reply-To: <cover.1633972263.git.naveennaidu479@gmail.com> Include PCI_ERROR_RESPONSE along with 0xffffffff in the comment to specify a hardware error. This helps finding where MMIO read error occurs easier to find. Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com> --- drivers/pci/controller/dwc/pci-keystone.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/pci/controller/dwc/pci-keystone.c b/drivers/pci/controller/dwc/pci-keystone.c index 865258d8c53c..25b11610b500 100644 --- a/drivers/pci/controller/dwc/pci-keystone.c +++ b/drivers/pci/controller/dwc/pci-keystone.c @@ -748,8 +748,8 @@ static int ks_pcie_config_legacy_irq(struct keystone_pcie *ks_pcie) #ifdef CONFIG_ARM /* * When a PCI device does not exist during config cycles, keystone host gets a - * bus error instead of returning 0xffffffff. This handler always returns 0 - * for this kind of faults. + * bus error instead of returning 0xffffffff (PCI_ERROR_RESPONSE). + * This handler always returns 0 for this kind of faults. */ static int ks_pcie_fault(unsigned long addr, unsigned int fsr, struct pt_regs *regs) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Naveen Naidu <naveennaidu479@gmail.com> To: bhelgaas@google.com Cc: "Rob Herring" <robh@kernel.org>, "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>, "Marc Zyngier" <maz@kernel.org>, "Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>, "Krzysztof Wilczyński" <kw@linux.com>, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, "Jingoo Han" <jingoohan1@gmail.com>, linux-kernel-mentees@lists.linuxfoundation.org Subject: [PATCH 20/22] PCI: keystone: Use PCI_ERROR_RESPONSE to specify hardware error Date: Mon, 11 Oct 2021 23:41:52 +0530 [thread overview] Message-ID: <01c86d23327e28ee6d09daa01538f1a12f9e4d11.1633972263.git.naveennaidu479@gmail.com> (raw) In-Reply-To: <cover.1633972263.git.naveennaidu479@gmail.com> Include PCI_ERROR_RESPONSE along with 0xffffffff in the comment to specify a hardware error. This helps finding where MMIO read error occurs easier to find. Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com> --- drivers/pci/controller/dwc/pci-keystone.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/pci/controller/dwc/pci-keystone.c b/drivers/pci/controller/dwc/pci-keystone.c index 865258d8c53c..25b11610b500 100644 --- a/drivers/pci/controller/dwc/pci-keystone.c +++ b/drivers/pci/controller/dwc/pci-keystone.c @@ -748,8 +748,8 @@ static int ks_pcie_config_legacy_irq(struct keystone_pcie *ks_pcie) #ifdef CONFIG_ARM /* * When a PCI device does not exist during config cycles, keystone host gets a - * bus error instead of returning 0xffffffff. This handler always returns 0 - * for this kind of faults. + * bus error instead of returning 0xffffffff (PCI_ERROR_RESPONSE). + * This handler always returns 0 for this kind of faults. */ static int ks_pcie_fault(unsigned long addr, unsigned int fsr, struct pt_regs *regs) -- 2.25.1 _______________________________________________ Linux-kernel-mentees mailing list Linux-kernel-mentees@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2021-10-11 18:12 UTC|newest] Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-11 17:35 [PATCH 00/22] PCI: Unify PCI error response checking Naveen Naidu 2021-10-11 17:35 ` Naveen Naidu 2021-10-11 17:35 ` Naveen Naidu 2021-10-11 17:35 ` Naveen Naidu 2021-10-11 17:35 ` Naveen Naidu 2021-10-11 17:35 ` Naveen Naidu 2021-10-11 17:37 ` [PATCH 01/22] PCI: Add PCI_ERROR_RESPONSE and it's related defintions Naveen Naidu 2021-10-11 17:37 ` Naveen Naidu 2021-10-11 17:37 ` Naveen Naidu 2021-10-11 17:37 ` Naveen Naidu 2021-10-11 17:37 ` Naveen Naidu 2021-10-11 17:37 ` Naveen Naidu 2021-10-11 17:38 ` [PATCH 02/22] PCI: Unify PCI error response checking Naveen Naidu 2021-10-11 17:38 ` Naveen Naidu 2021-10-11 22:05 ` Rob Herring 2021-10-11 22:05 ` Rob Herring 2021-10-12 16:21 ` Naveen Naidu 2021-10-12 16:21 ` Naveen Naidu 2021-10-12 18:02 ` Rob Herring 2021-10-12 18:02 ` Rob Herring 2021-10-12 22:52 ` Pali Rohár 2021-10-12 22:52 ` Pali Rohár 2021-10-13 2:43 ` Bjorn Helgaas 2021-10-13 2:43 ` Bjorn Helgaas 2021-10-13 13:06 ` Rob Herring 2021-10-13 13:06 ` Rob Herring 2021-10-13 17:16 ` Naveen Naidu 2021-10-13 17:16 ` Naveen Naidu 2021-10-13 17:54 ` Pali Rohár 2021-10-13 17:54 ` Pali Rohár 2021-10-13 18:48 ` Bjorn Helgaas 2021-10-13 18:48 ` Bjorn Helgaas 2021-10-13 21:47 ` Rob Herring 2021-10-13 21:47 ` Rob Herring 2021-10-13 22:03 ` Pali Rohár 2021-10-13 22:03 ` Pali Rohár 2021-10-13 22:12 ` Bjorn Helgaas 2021-10-13 22:12 ` Bjorn Helgaas 2021-10-11 17:45 ` [PATCH 03/22] PCI: thunder: Use SET_PCI_ERROR_RESPONSE() when device not found Naveen Naidu 2021-10-11 17:45 ` Naveen Naidu 2021-10-11 17:45 ` Naveen Naidu 2021-10-11 17:46 ` [PATCH 04/22] PCI: iproc: " Naveen Naidu 2021-10-11 17:46 ` Naveen Naidu 2021-10-11 17:46 ` Naveen Naidu 2021-10-11 17:51 ` [PATCH 05/22] PCI: mediatek: " Naveen Naidu 2021-10-11 17:51 ` Naveen Naidu 2021-10-11 17:51 ` Naveen Naidu 2021-10-11 17:51 ` Naveen Naidu 2021-10-11 17:52 ` [PATCH 06/22] PCI: exynos: " Naveen Naidu 2021-10-11 17:52 ` Naveen Naidu 2021-10-11 17:52 ` Naveen Naidu 2021-10-11 17:53 ` [PATCH 07/22] PCI: histb: " Naveen Naidu 2021-10-11 17:53 ` Naveen Naidu 2021-10-11 17:55 ` [PATCH 08/22] PCI: kirin: " Naveen Naidu 2021-10-11 17:55 ` Naveen Naidu 2021-10-11 17:56 ` [PATCH 09/22] PCI: aardvark: " Naveen Naidu 2021-10-11 17:56 ` Naveen Naidu 2021-10-11 17:56 ` Naveen Naidu 2021-10-11 18:08 ` Pali Rohár 2021-10-11 18:08 ` Pali Rohár 2021-10-11 18:08 ` Pali Rohár 2021-10-11 18:28 ` Naveen Naidu 2021-10-11 18:28 ` Naveen Naidu 2021-10-11 18:28 ` Naveen Naidu [not found] ` <20211011182526.kboaxqofdpd2jjrl@theprophet> 2021-10-11 18:41 ` Pali Rohár 2021-10-11 18:41 ` Pali Rohár 2021-10-11 18:41 ` Pali Rohár 2021-10-12 15:59 ` Naveen Naidu 2021-10-12 15:59 ` Naveen Naidu 2021-10-12 15:59 ` Naveen Naidu 2021-10-13 2:13 ` Bjorn Helgaas 2021-10-13 2:13 ` Bjorn Helgaas 2021-10-13 2:13 ` Bjorn Helgaas 2021-10-13 17:59 ` Pali Rohár 2021-10-13 17:59 ` Pali Rohár 2021-10-13 17:59 ` Pali Rohár 2021-10-11 18:00 ` [PATCH 10/22] PCI: mvebu: " Naveen Naidu 2021-10-11 18:00 ` Naveen Naidu 2021-10-11 18:00 ` Naveen Naidu 2021-10-11 18:00 ` [PATCH 11/22] PCI: altera: " Naveen Naidu 2021-10-11 18:00 ` Naveen Naidu 2021-10-11 18:02 ` [PATCH 12/22] PCI: rcar: " Naveen Naidu 2021-10-11 18:02 ` Naveen Naidu 2021-10-11 18:02 ` [PATCH 13/22] PCI: rockchip: " Naveen Naidu 2021-10-11 18:02 ` Naveen Naidu 2021-10-11 18:02 ` Naveen Naidu 2021-10-11 18:02 ` Naveen Naidu 2021-10-11 18:04 ` [PATCH 14/22] PCI/ERR: Use RESPONSE_IS_PCI_ERROR() to check read from hardware Naveen Naidu 2021-10-11 18:04 ` Naveen Naidu 2021-10-11 18:06 ` [PATCH 15/22] PCI: vmd: " Naveen Naidu 2021-10-11 18:06 ` Naveen Naidu 2021-10-14 18:04 ` Jonathan Derrick 2021-10-14 18:04 ` Jonathan Derrick 2021-10-11 18:07 ` [PATCH 16/22] PCI: pciehp: " Naveen Naidu 2021-10-11 18:07 ` Naveen Naidu 2021-10-11 19:47 ` Lukas Wunner 2021-10-11 19:47 ` Lukas Wunner 2021-10-12 16:05 ` Naveen Naidu 2021-10-12 16:05 ` Naveen Naidu 2021-10-12 23:12 ` Pali Rohár 2021-10-12 23:12 ` Pali Rohár 2021-10-13 12:20 ` Lukas Wunner 2021-10-13 12:20 ` Lukas Wunner 2021-10-11 18:08 ` [PATCH 17/22] PCI/DPC: " Naveen Naidu 2021-10-11 18:08 ` Naveen Naidu 2021-10-11 18:08 ` Naveen Naidu 2021-10-11 18:10 ` [PATCH 18/22] PCI/PME: " Naveen Naidu 2021-10-11 18:10 ` Naveen Naidu 2021-10-11 18:11 ` [PATCH 19/22] PCI: cpqphp: " Naveen Naidu 2021-10-11 18:11 ` Naveen Naidu 2021-10-11 18:11 ` Naveen Naidu [this message] 2021-10-11 18:11 ` [PATCH 20/22] PCI: keystone: Use PCI_ERROR_RESPONSE to specify hardware error Naveen Naidu 2021-10-11 18:12 ` [PATCH 21/22] PCI: hv: Use PCI_ERROR_RESPONSE to specify hardware read error Naveen Naidu 2021-10-11 18:12 ` Naveen Naidu 2021-10-11 18:13 ` [PATCH 22/22] PCI: xgene: Use PCI_ERROR_RESPONSE to specify hardware error Naveen Naidu 2021-10-11 18:13 ` Naveen Naidu 2021-10-11 18:13 ` Naveen Naidu
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=01c86d23327e28ee6d09daa01538f1a12f9e4d11.1633972263.git.naveennaidu479@gmail.com \ --to=naveennaidu479@gmail.com \ --cc=bhelgaas@google.com \ --cc=hayashi.kunihiko@socionext.com \ --cc=jingoohan1@gmail.com \ --cc=kw@linux.com \ --cc=linux-kernel-mentees@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=maz@kernel.org \ --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: linkBe 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.