linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: jingoohan1@gmail.com, gustavo.pimentel@synopsys.com,
	lpieralisi@kernel.org, robh@kernel.org, kw@linux.com,
	bhelgaas@google.com, treding@nvidia.com, jonathanh@nvidia.com,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	kthota@nvidia.com, mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V1] PCI: dwc: Use dev_info for PCIe link down event logging
Date: Tue, 13 Sep 2022 22:21:59 +0530	[thread overview]
Message-ID: <20220913165159.GH25849@workstation> (raw)
In-Reply-To: <20220913101237.4337-1-vidyas@nvidia.com>

On Tue, Sep 13, 2022 at 03:42:37PM +0530, Vidya Sagar wrote:
> Some of the platforms (like Tegra194 and Tegra234) have open slots and
> not having an endpoint connected to the slot is not an error.
> So, changing the macro from dev_err to dev_info to log the event.
> 

But the link up not happening is an actual error and -ETIMEDOUT is being
returned. So I don't think the log severity should be changed.

Thanks,
Mani

> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
> ---
>  drivers/pci/controller/dwc/pcie-designware.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/pci/controller/dwc/pcie-designware.c b/drivers/pci/controller/dwc/pcie-designware.c
> index 650a7f22f9d0..25154555aa7a 100644
> --- a/drivers/pci/controller/dwc/pcie-designware.c
> +++ b/drivers/pci/controller/dwc/pcie-designware.c
> @@ -456,7 +456,7 @@ int dw_pcie_wait_for_link(struct dw_pcie *pci)
>  	}
>  
>  	if (retries >= LINK_WAIT_MAX_RETRIES) {
> -		dev_err(pci->dev, "Phy link never came up\n");
> +		dev_info(pci->dev, "Phy link never came up\n");
>  		return -ETIMEDOUT;
>  	}
>  
> -- 
> 2.17.1
> 

  reply	other threads:[~2022-09-13 17:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 10:12 [PATCH V1] PCI: dwc: Use dev_info for PCIe link down event logging Vidya Sagar
2022-09-13 16:51 ` Manivannan Sadhasivam [this message]
2022-09-13 17:00   ` Jon Hunter
2022-09-13 20:07     ` Bjorn Helgaas
2022-09-14  6:24       ` Manivannan Sadhasivam
2022-09-14 11:02         ` Vidya Sagar
2022-09-14 11:18           ` Manivannan Sadhasivam
2022-09-14 11:25             ` Jon Hunter
2022-09-14 11:43               ` Manivannan Sadhasivam
2022-09-14 11:52                 ` Jon Hunter
2022-09-14 12:44                 ` Krzysztof Wilczyński
2022-09-14 13:45                   ` Manivannan Sadhasivam
2022-09-14 14:52                     ` Krzysztof Wilczyński
2022-09-14 15:11                       ` Jon Hunter
2022-09-15 14:16         ` Rob Herring
2022-09-15 14:52           ` Manivannan Sadhasivam
2022-09-26 10:29             ` Vidya Sagar
2022-10-03 11:25               ` Vidya Sagar
2022-10-04 12:53             ` Rob Herring
2022-10-10  6:02               ` Vidya Sagar
2022-10-26 18:06                 ` Rob Herring
2022-10-27  9:39           ` Lorenzo Pieralisi
2022-10-27 11:03             ` Manivannan Sadhasivam
2022-09-14  6:12     ` Manivannan Sadhasivam
2022-09-15 10:44 ` Manivannan Sadhasivam
2022-10-18  6:21 ` Jon Hunter
2022-10-18 16:43   ` Bjorn Helgaas
2022-10-26 11:39     ` Jon Hunter
2022-10-26 12:33       ` Lorenzo Pieralisi
2022-10-27  9:55       ` Ben Dooks
2022-10-27 11:05         ` Manivannan Sadhasivam
2022-11-10 15:40 ` Lorenzo Pieralisi

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=20220913165159.GH25849@workstation \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=kthota@nvidia.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mmaddireddy@nvidia.com \
    --cc=robh@kernel.org \
    --cc=sagar.tv@gmail.com \
    --cc=treding@nvidia.com \
    --cc=vidyas@nvidia.com \
    /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).