From: Jisheng Zhang <jszhang@marvell.com>
To: <jingoohan1@gmail.com>, <pratyush.anand@gmail.com>,
<bhelgaas@google.com>, <Joao.Pinto@synopsys.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] PCI: designware: let dw_pcie_link_up() beware of LTSSM training bit
Date: Wed, 10 Aug 2016 18:21:45 +0800 [thread overview]
Message-ID: <20160810182145.7a821b38@xhacker> (raw)
In-Reply-To: <1470823623-1360-1-git-send-email-jszhang@marvell.com>
On Wed, 10 Aug 2016 18:07:01 +0800 Jisheng Zhang wrote:
> patch1 is a trivial clean up: move the parameters for wait for link
> into the core pcie-designware.c
>
> Since link may be UP but still in link training, if so, we can't think
> the link is up and operating correctly. So patch2 teaches
> dw_pcie_link_up() beware of the PCIE_PHY_DEBUG_R1_LINK_IN_TRAINING bit.
hmm, there's one accident with my email system, the v2 series is sent twice
Sorry for inconvenience,
Jisheng
>
> Since v1:
> - add Joao's Ack
> - rebased on v4.8-rc1
>
> Jisheng Zhang (2):
> PCI: designware: mv parameters for wait for link into
> pcie-designware.c
> PCI: designware: let dw_pcie_link_up() beware of LTSSM training bit
>
> drivers/pci/host/pcie-designware.c | 11 +++++++++--
> drivers/pci/host/pcie-designware.h | 5 -----
> 2 files changed, 9 insertions(+), 7 deletions(-)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] PCI: designware: let dw_pcie_link_up() beware of LTSSM training bit
Date: Wed, 10 Aug 2016 18:21:45 +0800 [thread overview]
Message-ID: <20160810182145.7a821b38@xhacker> (raw)
In-Reply-To: <1470823623-1360-1-git-send-email-jszhang@marvell.com>
On Wed, 10 Aug 2016 18:07:01 +0800 Jisheng Zhang wrote:
> patch1 is a trivial clean up: move the parameters for wait for link
> into the core pcie-designware.c
>
> Since link may be UP but still in link training, if so, we can't think
> the link is up and operating correctly. So patch2 teaches
> dw_pcie_link_up() beware of the PCIE_PHY_DEBUG_R1_LINK_IN_TRAINING bit.
hmm, there's one accident with my email system, the v2 series is sent twice
Sorry for inconvenience,
Jisheng
>
> Since v1:
> - add Joao's Ack
> - rebased on v4.8-rc1
>
> Jisheng Zhang (2):
> PCI: designware: mv parameters for wait for link into
> pcie-designware.c
> PCI: designware: let dw_pcie_link_up() beware of LTSSM training bit
>
> drivers/pci/host/pcie-designware.c | 11 +++++++++--
> drivers/pci/host/pcie-designware.h | 5 -----
> 2 files changed, 9 insertions(+), 7 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@marvell.com>
To: <jingoohan1@gmail.com>, <pratyush.anand@gmail.com>,
<bhelgaas@google.com>, <Joao.Pinto@synopsys.com>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/2] PCI: designware: let dw_pcie_link_up() beware of LTSSM training bit
Date: Wed, 10 Aug 2016 18:21:45 +0800 [thread overview]
Message-ID: <20160810182145.7a821b38@xhacker> (raw)
In-Reply-To: <1470823623-1360-1-git-send-email-jszhang@marvell.com>
On Wed, 10 Aug 2016 18:07:01 +0800 Jisheng Zhang wrote:
> patch1 is a trivial clean up: move the parameters for wait for link
> into the core pcie-designware.c
>
> Since link may be UP but still in link training, if so, we can't think
> the link is up and operating correctly. So patch2 teaches
> dw_pcie_link_up() beware of the PCIE_PHY_DEBUG_R1_LINK_IN_TRAINING bit.
hmm, there's one accident with my email system, the v2 series is sent twice
Sorry for inconvenience,
Jisheng
>
> Since v1:
> - add Joao's Ack
> - rebased on v4.8-rc1
>
> Jisheng Zhang (2):
> PCI: designware: mv parameters for wait for link into
> pcie-designware.c
> PCI: designware: let dw_pcie_link_up() beware of LTSSM training bit
>
> drivers/pci/host/pcie-designware.c | 11 +++++++++--
> drivers/pci/host/pcie-designware.h | 5 -----
> 2 files changed, 9 insertions(+), 7 deletions(-)
>
next prev parent reply other threads:[~2016-08-10 10:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 10:07 [PATCH v2 0/2] PCI: designware: let dw_pcie_link_up() beware of LTSSM training bit Jisheng Zhang
2016-08-10 10:07 ` Jisheng Zhang
2016-08-10 10:07 ` Jisheng Zhang
2016-08-10 10:07 ` [PATCH v2 1/2] PCI: designware: mv parameters for wait for link into pcie-designware.c Jisheng Zhang
2016-08-10 10:07 ` Jisheng Zhang
2016-08-10 10:07 ` Jisheng Zhang
2016-08-10 10:07 ` [PATCH v2 2/2] PCI: designware: let dw_pcie_link_up() beware of LTSSM training bit Jisheng Zhang
2016-08-10 10:07 ` Jisheng Zhang
2016-08-10 10:07 ` Jisheng Zhang
2016-08-10 10:21 ` Jisheng Zhang [this message]
2016-08-10 10:21 ` [PATCH v2 0/2] " Jisheng Zhang
2016-08-10 10:21 ` Jisheng Zhang
2016-08-17 21:01 ` Bjorn Helgaas
2016-08-17 21:01 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2016-08-10 5:31 Jisheng Zhang
2016-08-10 5:31 ` Jisheng Zhang
2016-08-10 5:31 ` Jisheng Zhang
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=20160810182145.7a821b38@xhacker \
--to=jszhang@marvell.com \
--cc=Joao.Pinto@synopsys.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pratyush.anand@gmail.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 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.