All of lore.kernel.org
 help / color / mirror / Atom feed
From: kys@microsoft.com (KY Srinivasan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/3] PCI: Configure PCIe MPS settings
Date: Thu, 9 Feb 2017 00:32:10 +0000	[thread overview]
Message-ID: <DM5PR03MB249088D49C65C8E8FB3419FDA0450@DM5PR03MB2490.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20170208224632.14351.89895.stgit@bhelgaas-glaptop.roam.corp.google.com>



> -----Original Message-----
> From: Bjorn Helgaas [mailto:helgaas at kernel.org]
> Sent: Wednesday, February 8, 2017 2:49 PM
> To: linux-pci at vger.kernel.org
> Cc: Rob Herring <robh@kernel.org>; Haiyang Zhang
> <haiyangz@microsoft.com>; Michal Simek <michal.simek@xilinx.com>; Jon
> Mason <jon.mason@broadcom.com>; Ray Jui <ray.jui@broadcom.com>;
> S?ren Brinkmann <soren.brinkmann@xilinx.com>;
> devel at linuxdriverproject.org; KY Srinivasan <kys@microsoft.com>; linux-
> arm-kernel at lists.infradead.org; Tanmay Inamdar <tinamdar@apm.com>
> Subject: [PATCH v1 0/3] PCI: Configure PCIe MPS settings
> 
> [Some of you will get this twice because Gmail and I aren't getting along
> today; sorry]
> 
> The PCI core doesn't configure the PCIe MPS settings by itself.  Each
> host bridge driver has to call pcie_bus_configure_settings() to make
> this happen.
> 
> Jon fixed this already for pcie-iproc.c.  I propose these similar
> patches for other drivers.
> 
> HV guys, I included you because create_root_hv_pci_bus() is one place
> that calls pci_scan_child_bus() but does not call
> pcie_bus_configure_settings().  I know you probably don't strictly
> *need* to configure MPS settings in a paravirtual front-end, but the
> PCI core does other device configuration in this path:
> 
>   pci_scan_child_bus
>     pci_scan_slot
>       pci_scan_single_device
>         pci_device_add
>           pci_configure_device
>           pci_init_capabilities
> 
> and I would like to eventually migrate the MPS configuration into that
> same path.  Since we do this other configuration for HV devices
> already, I think pcie_bus_configure_settings() should also work (even
> if it ends up not doing anything to real devices).
> 
> It would make that eventual migration easier if all the
> pci_scan_child_bus() callers had the same pattern of calling
> pcie_bus_configure_settings().
> 
> So would it make sense to make a similar patch for HV?  It looks easy
> to add it to create_root_hv_pci_bus(), but I don't know exactly what
> to do about pci_devices_present_work().

Bjorn,

We will take a look.

K. Y
> 
> ---
> 
> Bjorn Helgaas (3):
>       PCI: xilinx: Configure PCIe MPS settings
>       PCI: versatile: Configure PCIe MPS settings
>       PCI: xgene: Configure PCIe MPS settings
> 
> 
>  drivers/pci/host/pci-versatile.c |    4 +++-
>  drivers/pci/host/pci-xgene.c     |    4 +++-
>  drivers/pci/host/pcie-xilinx.c   |    4 +++-
>  3 files changed, 9 insertions(+), 3 deletions(-)

  parent reply	other threads:[~2017-02-09  0:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 22:49 [PATCH v1 0/3] PCI: Configure PCIe MPS settings Bjorn Helgaas
2017-02-08 22:49 ` Bjorn Helgaas
2017-02-08 22:49 ` [PATCH v1 1/3] PCI: xilinx: " Bjorn Helgaas
2017-02-08 22:49   ` Bjorn Helgaas
2017-02-09  7:19   ` Christoph Hellwig
2017-02-09  7:19     ` Christoph Hellwig
2017-02-10 21:58     ` Bjorn Helgaas
2017-02-10 21:58       ` Bjorn Helgaas
2017-02-08 22:49 ` [PATCH v1 2/3] PCI: versatile: " Bjorn Helgaas
2017-02-08 22:49   ` Bjorn Helgaas
2017-02-08 22:49 ` [PATCH v1 3/3] PCI: xgene: " Bjorn Helgaas
2017-02-08 22:49   ` Bjorn Helgaas
2017-02-09  0:32 ` KY Srinivasan [this message]
2017-02-10 21:59 ` [PATCH v1 0/3] PCI: " Bjorn Helgaas
2017-02-10 21:59   ` Bjorn Helgaas
2017-02-24 11:16   ` Dexuan Cui
2017-02-24 11:16     ` Dexuan Cui
2017-02-24 14:32     ` Bjorn Helgaas
2017-02-24 14:32       ` Bjorn Helgaas
2017-02-24 15:10       ` Dexuan Cui
  -- strict thread matches above, loose matches on Subject: below --
2017-02-08 22:08 Bjorn Helgaas
2017-02-08 22:08 ` 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=DM5PR03MB249088D49C65C8E8FB3419FDA0450@DM5PR03MB2490.namprd03.prod.outlook.com \
    --to=kys@microsoft.com \
    --cc=linux-arm-kernel@lists.infradead.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: 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.