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, skhan@linuxfoundation.org Subject: [PATCH v4 22/25] PCI: Use PCI_ERROR_RESPONSE to specify hardware error Date: Thu, 18 Nov 2021 19:33:32 +0530 [thread overview] Message-ID: <866e2db544df45af70df7e64659bf02e03998ae3.1637243717.git.naveennaidu479@gmail.com> (raw) In-Reply-To: <cover.1637243717.git.naveennaidu479@gmail.com> Include PCI_ERROR_RESPONSE along with 0xFFFF and 0xFFFFFFFF in the comment to specify a hardware error. This makes MMIO read errors easier to find. Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com> --- drivers/pci/access.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/pci/access.c b/drivers/pci/access.c index a92637627845..a07b76761d74 100644 --- a/drivers/pci/access.c +++ b/drivers/pci/access.c @@ -413,8 +413,8 @@ int pcie_capability_read_word(struct pci_dev *dev, int pos, u16 *val) ret = pci_read_config_word(dev, pci_pcie_cap(dev) + pos, val); /* * Reset *val to 0 if pci_read_config_word() fails, it may - * have been written as 0xFFFF if hardware error happens - * during pci_read_config_word(). + * have been written as 0xFFFF (PCI_ERROR_RESPONSE) if hardware error + * happens during pci_read_config_word(). */ if (ret) *val = 0; @@ -448,8 +448,8 @@ int pcie_capability_read_dword(struct pci_dev *dev, int pos, u32 *val) ret = pci_read_config_dword(dev, pci_pcie_cap(dev) + pos, val); /* * Reset *val to 0 if pci_read_config_dword() fails, it may - * have been written as 0xFFFFFFFF if hardware error happens - * during pci_read_config_dword(). + * have been written as 0xFFFFFFFF (PCI_ERROR_RESPONSE) if hardware + * error happens during pci_read_config_dword(). */ if (ret) *val = 0; -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Naveen Naidu <naveennaidu479@gmail.com> To: bhelgaas@google.com Cc: linux-kernel-mentees@lists.linuxfoundation.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org Subject: [PATCH v4 22/25] PCI: Use PCI_ERROR_RESPONSE to specify hardware error Date: Thu, 18 Nov 2021 19:33:32 +0530 [thread overview] Message-ID: <866e2db544df45af70df7e64659bf02e03998ae3.1637243717.git.naveennaidu479@gmail.com> (raw) In-Reply-To: <cover.1637243717.git.naveennaidu479@gmail.com> Include PCI_ERROR_RESPONSE along with 0xFFFF and 0xFFFFFFFF in the comment to specify a hardware error. This makes MMIO read errors easier to find. Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com> --- drivers/pci/access.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/pci/access.c b/drivers/pci/access.c index a92637627845..a07b76761d74 100644 --- a/drivers/pci/access.c +++ b/drivers/pci/access.c @@ -413,8 +413,8 @@ int pcie_capability_read_word(struct pci_dev *dev, int pos, u16 *val) ret = pci_read_config_word(dev, pci_pcie_cap(dev) + pos, val); /* * Reset *val to 0 if pci_read_config_word() fails, it may - * have been written as 0xFFFF if hardware error happens - * during pci_read_config_word(). + * have been written as 0xFFFF (PCI_ERROR_RESPONSE) if hardware error + * happens during pci_read_config_word(). */ if (ret) *val = 0; @@ -448,8 +448,8 @@ int pcie_capability_read_dword(struct pci_dev *dev, int pos, u32 *val) ret = pci_read_config_dword(dev, pci_pcie_cap(dev) + pos, val); /* * Reset *val to 0 if pci_read_config_dword() fails, it may - * have been written as 0xFFFFFFFF if hardware error happens - * during pci_read_config_dword(). + * have been written as 0xFFFFFFFF (PCI_ERROR_RESPONSE) if hardware + * error happens during pci_read_config_dword(). */ if (ret) *val = 0; -- 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-11-18 14:09 UTC|newest] Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-18 14:03 [PATCH v4 00/25] Unify PCI error response checking Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 01/25] PCI: Add PCI_ERROR_RESPONSE and it's related definitions Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 02/25] PCI: Set error response in config access defines when ops->read() fails Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 03/25] PCI: Use PCI_SET_ERROR_RESPONSE() when device not found Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 04/25] PCI: Remove redundant error fabrication when device read fails Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 05/25] PCI: thunder: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 06/25] PCI: iproc: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 07/25] PCI: mediatek: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 08/25] PCI: exynos: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 09/25] PCI: histb: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 10/25] PCI: kirin: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 11/25] PCI: aardvark: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 12/25] PCI: mvebu: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 13/25] PCI: altera: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 14/25] PCI: rcar: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 15/25] PCI: rockchip: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 16/25] PCI/ERR: Use PCI_POSSIBLE_ERROR() to check read from hardware Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 17/25] PCI: vmd: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 18/25] PCI: pciehp: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 19/25] PCI/DPC: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 20/25] PCI/PME: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 21/25] PCI: cpqphp: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu [this message] 2021-11-18 14:03 ` [PATCH v4 22/25] PCI: Use PCI_ERROR_RESPONSE to specify hardware error Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 23/25] PCI: keystone: " Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 24/25] PCI: hv: Use PCI_ERROR_RESPONSE to specify hardware read error Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` [PATCH v4 25/25] PCI: xgene: Use PCI_ERROR_RESPONSE to specify hardware error Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 14:03 ` Naveen Naidu 2021-11-18 20:44 ` [PATCH v4 00/25] Unify PCI error response checking Bjorn Helgaas 2021-11-18 20:44 ` Bjorn Helgaas 2021-11-18 20:44 ` Bjorn Helgaas 2021-11-18 20:44 ` Bjorn Helgaas 2021-11-18 20:44 ` 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=866e2db544df45af70df7e64659bf02e03998ae3.1637243717.git.naveennaidu479@gmail.com \ --to=naveennaidu479@gmail.com \ --cc=bhelgaas@google.com \ --cc=linux-kernel-mentees@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=skhan@linuxfoundation.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.