From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Serge Semin" <Sergey.Semin@baikalelectronics.ru>,
linux-pci@vger.kernel.org
Subject: Re: Re: [PATCH 1/1] PCI: dwc: reduce log severity level if no link came up
Date: Tue, 01 Nov 2022 09:55:03 +0100 [thread overview]
Message-ID: <5874911.lOV4Wx5bFT@steina-w> (raw)
In-Reply-To: <41c536dd-99c4-9fa5-39cc-2aea5b5e015b@nvidia.com>
Hi Vidya,
Am Dienstag, 1. November 2022, 09:27:50 CET schrieb Vidya Sagar:
> Hi Alexander,
> Thanks for the patch, but, we already have a patch for it here
>
> https://patchwork.kernel.org/project/linux-pci/patch/20220913101237.4337-1-v
> idyas@nvidia.com/
>
> and discussion is going on there.
Ah, I wasn't aware of that. Thanks for the link and sorry for the noise.
Thanks,
Alexander
> Thanks,
> Vidya Sagar
>
> On 11/1/2022 1:48 PM, Alexander Stein wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > Commit 14c4ad125cf9 ("PCI: dwc: Log link speed and width if it comes up")
> > changed the severity from info to error. If no device is attached this
> > error always is recorded which is not an error in this case.
> >
> > Fixes: 14c4ad125cf9 ("PCI: dwc: Log link speed and width if it comes up")
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.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
> > 9e4d96e5a3f5a..432aead68d1fd 100644
> > --- a/drivers/pci/controller/dwc/pcie-designware.c
> > +++ b/drivers/pci/controller/dwc/pcie-designware.c
> > @@ -448,7 +448,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.34.1
prev parent reply other threads:[~2022-11-01 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 8:18 [PATCH 1/1] PCI: dwc: reduce log severity level if no link came up Alexander Stein
2022-11-01 8:27 ` Vidya Sagar
2022-11-01 8:55 ` Alexander Stein [this message]
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=5874911.lOV4Wx5bFT@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--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