linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Frederick Lawler <fred@fredlawl.com>
Cc: bhelgaas@google.com, mike.marciniszyn@intel.com,
	dennis.dalessandro@intel.com, jgg@mellanox.com,
	linux-pci@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH v3 0/2] IB/hfi1: Cleanup PCIe link configuration
Date: Fri, 27 Apr 2018 14:18:27 -0400	[thread overview]
Message-ID: <1524853107.11756.70.camel@redhat.com> (raw)
In-Reply-To: <20180427175850.GC8199@bhelgaas-glaptop.roam.corp.google.com>

[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]

On Fri, 2018-04-27 at 12:58 -0500, Bjorn Helgaas wrote:
> On Mon, Apr 16, 2018 at 07:28:23PM -0500, Frederick Lawler wrote:
> > The IB/hfi1 driver uses custom macros to configure the target link speed. Some 
> > macros were previously replaced, but not fully. This patch series addresses the
> > configuration inconsistencies by adding PCI_EXP_LNKCTL2_TLS* macros to PCI,
> > and then use them in the following IB/hfi1 patch.
> > 
> > V3: 
> > 	* PCI: Add PCI_EXP_LNKCTL2_TLS_* macros
> > 	* Drop patch to use extract_speed() in do_pcie_gen3_transition()
> > V2:
> > 	* s/LINK/LNK
> > 
> > Frederick Lawler (2):
> >   PCI: Add PCI_EXP_LNKCTL2_TLS* macros
> >   IB/hfi1: Replace custom hfi1 macros with PCIe macros
> > 
> >  drivers/infiniband/hw/hfi1/pcie.c | 24 ++++++++----------------
> >  include/uapi/linux/pci_regs.h     |  5 +++++
> >  2 files changed, 13 insertions(+), 16 deletions(-)
> 
> I applied these, with Michael's reviewed-by on the second, to
> pci/misc for v4.18, thanks!
> 
> Ideally we could pull some of this link speed management code into the
> PCI core someday, but I think these patches are useful as-is.
> 
> Oh, I did s/PCI_EXP_LNKCTL2_TLS_2_5GB/PCI_EXP_LNKCTL2_TLS_2_5GT/
> because the link speeds are actually defined in terms of GT/s, not
> GB/s.

Thanks :-)

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-04-27 18:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17  0:28 [PATCH v3 0/2] IB/hfi1: Cleanup PCIe link configuration Frederick Lawler
2018-04-17  0:28 ` [PATCH v3 1/2] PCI: Add PCI_EXP_LNKCTL2_TLS* macros Frederick Lawler
2018-04-17  0:28 ` [PATCH v3 2/2] IB/hfi1: Replace custom hfi1 macros with PCIe macros Frederick Lawler
2018-04-20 18:21   ` Ruhl, Michael J
2018-04-17  6:53 ` [PATCH v3 0/2] IB/hfi1: Cleanup PCIe link configuration Christoph Hellwig
2018-04-17 14:32   ` Bjorn Helgaas
2018-04-18 21:53     ` Dennis Dalessandro
2018-04-17 15:56   ` Marciniszyn, Mike
2018-04-17 17:19     ` Bjorn Helgaas
2018-04-20 17:03       ` Dennis Dalessandro
2018-04-27 16:14 ` Doug Ledford
2018-04-27 17:58 ` Bjorn Helgaas
2018-04-27 18:18   ` Doug Ledford [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=1524853107.11756.70.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=dennis.dalessandro@intel.com \
    --cc=fred@fredlawl.com \
    --cc=helgaas@kernel.org \
    --cc=jgg@mellanox.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mike.marciniszyn@intel.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).