Thierry Reding | 26 Aug 17:11 2014
Picon

[PATCH v3 0/6] PCI: tegra: Fixes and Tegra124 support

From: Thierry Reding <treding <at> nvidia.com>

This series implements various fixes and adds support for Tegra124 to the
Tegra PCIe controller driver.

Patches 1 and 2 were already sent out separately earlier on but haven't been
applied yet, so I'm including them here for convenience.

Patches 3 to 5 are various fixes that should make the driver more reliable,
though they don't (except maybe for patch 4) fix any known issues.

Patch 6 finally adds support for Tegra124.

Thierry

Eric Yuen (1):
  PCI: tegra: Make sure the PCIe PLL is really reset

Peter Daifuku (1):
  PCI: tegra: Fix extended configuration space mapping

Thierry Reding (4):
  resource: Add device-managed request/release_resource()
  PCI: tegra: Implement a proper resource hierarchy
  PCI: tegra: Clear CLKREQ# enable on port disable
  PCI: tegra: Add Tegra124 support

 .../bindings/pci/nvidia,tegra20-pcie.txt           |  25 +-
 Documentation/driver-model/devres.txt              |   2 +
 drivers/pci/host/pci-tegra.c                       | 257 ++++++++++++++++++---
(Continue reading)

Thierry Reding | 26 Aug 16:57 2014
Picon

[PATCH v2 0/6] PCI: tegra: Fixes and Tegra124 support

From: Thierry Reding <treding <at> nvidia.com>

This series implements various fixes and adds support for Tegra124 to the
Tegra PCIe controller driver.

Patches 1 and 2 were already sent out separately earlier on but haven't been
applied yet, so I'm including them here for convenience.

Patches 3 to 5 are various fixes that should make the driver more reliable,
though they don't (except maybe for patch 4) fix any known issues.

Patch 6 finally adds support for Tegra124.

Thierry

Eric Yuen (1):
  PCI: tegra: Make sure the PCIe PLL is really reset

Peter Daifuku (1):
  PCI: tegra: Fix extended configuration space mapping

Thierry Reding (4):
  resource: Add device-managed request/release_resource()
  PCI: tegra: Implement a proper resource hierarchy
  PCI: tegra: Clear CLKREQ# enable on port disable
  PCI: tegra: Add Tegra124 support

 .../bindings/pci/nvidia,tegra20-pcie.txt           |  25 +-
 Documentation/driver-model/devres.txt              |   2 +
 drivers/pci/host/pci-tegra.c                       | 257 ++++++++++++++++++---
(Continue reading)

Bjorn Helgaas | 26 Aug 06:10 2014
Picon

Re: [REGRESSION] pci: power off broken by commit 4fc9bbf98 / stable 2ab0ff9b

[+cc linux-kernel, linux-pci]

On Mon, Aug 25, 2014 at 04:43:50PM -0600, Khalid Aziz wrote:
> On 08/25/2014 03:23 PM, Knut Petersen wrote:
> >On 25.08.2014 18:36, Linus Torvalds wrote:
> >>On Mon, Aug 25, 2014 at 12:19 AM, Knut Petersen
> >><Knut_Petersen <at> t-online.de> wrote:
> >>>Testing some other kernels lurking around on the disk I realized that
> >>>after kernel 3.11.5 and before kernel 3.12.9 both the power button
> >>>and "shutdown -h now" lost the ability to power off the machine - the
> >>>system is halted instead and needs a reset / 4 second power button
> >>>pressing.
> >>Hmm. Does "shutdown -p" work?
> >No. Suspending works as expected, but a normal power-off hangs, no
> >matter if
> >triggered by the power button or shutdown -h or -p.
> >>But it might be interesting to see where the behavior changed.
> >>
> >>            Linus
> >
> >Ok, I bisected and found the offending commit. Some people that authored
> >/ acked / were interested in
> >the commit are added to the cc. No cc to lkml and the pci list as
> >t-online.de is still banned from vger.
> >
> >After a regression report discussed in
> >https://bugzilla.kernel.org/show_bug.cgi?id=63861
> >a fix that was tested on several machines was introduced to the kernel.
> >Unfortunately
> >that fix (linux git 4fc9bbf98, linux stable git 2ab0ff9b) breaks
(Continue reading)

Mathias Krause | 25 Aug 23:26 2014

[PATCH 0/5] x86/PCI: Minor size reduction by marking init code and data as such

Hi Bjorn,

this series is a collection of patches trying to mark initialization
code and data of the x86 specific PCI code as such. It also contains
__init annotation cleanups to move them to the spot they belong to
according to include/linux/init.h.

The annotation leads to a nice reduction of run-time memory size. At
least two additional pages can be released after initialization which
are otherwise occupied by code and data no longer needed.

Please apply!

Thanks,

Mathias Krause (5):
  x86/PCI: Mark DMI tables as initialization data
  x86/PCI: Move __init annotation were it belongs to
  x86/PCI: Mark constants of pci_mmcfg_nvidia_mcp55() as __initconst
  x86/PCI: Constify pci_mmcfg_probes[] array
  x86/PCI: Mark PCI BIOS initialization code as such

 arch/x86/pci/common.c          |   20 ++++++++--------
 arch/x86/pci/mmconfig-shared.c |   40 ++++++++++++++++++--------------
 arch/x86/pci/pcbios.c          |    8 +++----
 3 files changed, 36 insertions(+), 32 deletions(-)

--

-- 
1.7.10.4

(Continue reading)

Scott Wood | 25 Aug 20:47 2014

Re: PCIe driver not working properly after upgrading to linux 3.8.13

On Sun, 2014-08-24 at 18:41 +0530, Gokul C G wrote:
> HI all,
> 
> Thank you very much for your information .I solved my problem !!!
> 
> Here is my findings 
> =====================
>  I found out that support for the PCIe serial extension for
> ( XR17V35x) has been added to the standard Linux serial driver. If I
> just need to transmit/receive data, then this driver will work
> perfectly fine. The deficiencies is that you can not use any of the
> enhanced features in the XR17V35x such as the larger FIFOs, automatic
> hardware/software flow control, auto RS-485 half-duplex control, etc.
> 
> Now I have 2 options:
> 1. Remove support for the XR17V35x IDs and re-compile the kernel, then
> use the module driver.
> 2. Use an external EEPROM to use different Vendor and/or Device IDs so
> that you can use the module driver.

3. Remove the generic PCI serial driver from your config.
4. Dynamically unbind the device using sysfs, and either defer module
loading until after this, or rebind it to the already-loaded specialized
driver using sysfs.
5. Add these features to the standard PCI serial driver. :-)

-Scott

Abdul Nasser Sokariah | 23 Aug 16:08 2014
Picon

Urgent Assistance from Syria

--

-- 
Good Day From Syria,

My name is Abdul Nasser Sokariah and I am writing you from Syria, I
choose to contact you directly as I need a reliable person to trust
who can help me make claims to my huge deposit with a vault company in
AFRICA, and based on my present situation in Syria, I need you
urgently to take  possession of everything and further
modalities/directives will follow.

Contact me  only on my private Email:nabdul247 <at> gmail.com for
clarifications,I await your response.

Yours truly, Abdul Nasser Sokariah
Contact Email:nabdul247 <at> gmail.com
Yinghai Lu | 23 Aug 03:15 2014

[PATCH] PCI: add back missing MEM_64 mask check for hotplug path

We missed that in
|  commit 5b28541552ef5eeffc41d6936105f38c2508e566
|    PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources
for pci hotplug path.

We have MEM_64 in type_mask from pci_assign_unassigned_root_bus_resources()
for boot path.

Signed-off-by: Yinghai Lu <yinghai <at> kernel.org>

---
 drivers/pci/setup-bus.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6/drivers/pci/setup-bus.c
===================================================================
--- linux-2.6.orig/drivers/pci/setup-bus.c
+++ linux-2.6/drivers/pci/setup-bus.c
 <at>  <at>  -1652,7 +1652,7  <at>  <at>  void pci_assign_unassigned_bridge_resour
 	struct pci_dev_resource *fail_res;
 	int retval;
 	unsigned long type_mask = IORESOURCE_IO | IORESOURCE_MEM |
-				  IORESOURCE_PREFETCH;
+				  IORESOURCE_PREFETCH | IORESOURCE_MEM_64;

 again:
 	__pci_bus_size_bridges(parent, &add_list);
Yijing Wang | 22 Aug 10:07 2014

[PATCH v2 0/5] Some cleanup for MSI code

This is collection of two cleanup patchset,
http://marc.info/?l=linux-pci&m=140807095026813&w=2 and
http://marc.info/?l=linux-pci&m=140633779729162&w=2

I rebased it on 3.17-rc1, and dropped a incorrect patch.

Yijing Wang (5):
  PCI/MSI: Clean up the kobject in struct msi_desc
  PCI/MSI: Remove msi_attrib->pos in struct msi_desc
  PCI/MSI: Change msi_bus attribute to support enable/disable MSI for
    EP
  MSI: Use __get_cached_msi_msg() instead of get_cached_msi_msg()
  MSI: Use __read_msi_msg() instead of read_msi_msg()

 arch/ia64/kernel/msi_ia64.c          |    2 +-
 arch/ia64/sn/kernel/msi_sn.c         |    4 ++--
 arch/mips/pci/msi-octeon.c           |    6 +++---
 arch/powerpc/platforms/pseries/msi.c |    2 +-
 arch/x86/kernel/apic/io_apic.c       |    2 +-
 arch/x86/pci/xen.c                   |    2 +-
 drivers/pci/host/pcie-designware.c   |    2 +-
 drivers/pci/msi.c                    |   31 ++-----------------------------
 drivers/pci/pci-sysfs.c              |   12 ++++++------
 include/linux/msi.h                  |    9 ++-------
 10 files changed, 20 insertions(+), 52 deletions(-)

Linus Torvalds | 21 Aug 02:17 2014

Annoying and insane pci kernel messages..

[ Oops, my mail client ended up picking an old address for Bjorn, so
resending with the correct one ]

So I don't know when this started happening, and it may well be an
age-old issue, possibly made worse by configurations copied from
distro makers that enable various random PCI hotplug logic, but my
laptop dmesg is full of these annoying and worthless messages after
suspend/resume:

  ...
  pci 0000:00:00.0: no hotplug settings from platform
  pci 0000:00:00.0: using default PCI settings
  i915 0000:00:02.0: no hotplug settings from platform
  i915 0000:00:02.0: using default PCI settings
  ...

basically repeating mindlessly for each PCI device. It's insane. It
adds zero value. Why do we print out those inane messages?

The reason _seems_ to be that some ACPI hotplug logic basically ends
up doing "pci_configure_slot()" on every PCI slot, whether something
is hotpluggable or not. Trust me, those things aren't. Printing
pointless hotplug information for them is just crazy, and takes up
kernel message space and hides _real_ messages for no good reason.

Lookie here:

  [torvalds <at> vaio linux]$ dmesg | grep "no hotplug settings" | wc
     1006    8658   71574

(Continue reading)

Linus Torvalds | 21 Aug 02:15 2014

Annoying and insane pci kernel messages..

So I don't know when this started happening, and it may well be an
age-old issue, possibly made worse by configurations copied from
distro makers that enable various random PCI hotplug logic, but my
laptop dmesg is full of these annoying and worthless messages after
suspend/resume:

  ...
  pci 0000:00:00.0: no hotplug settings from platform
  pci 0000:00:00.0: using default PCI settings
  i915 0000:00:02.0: no hotplug settings from platform
  i915 0000:00:02.0: using default PCI settings
  ...

basically repeating mindlessly for each PCI device. It's insane. It
adds zero value. Why do we print out those inane messages?

The reason _seems_ to be that some ACPI hotplug logic basically ends
up doing "pci_configure_slot()" on every PCI slot, whether something
is hotpluggable or not. Trust me, those things aren't. Printing
pointless hotplug information for them is just crazy, and takes up
kernel message space and hides _real_ messages for no good reason.

Lookie here:

  [torvalds <at> vaio linux]$ dmesg | grep "no hotplug settings" | wc
     1006    8658   71574

yeah, that's a thousand lines of crap. There's another 568 lines of
the "using default PCI settings". In fact, there's *more* of this, but
there's been so much of it that it's scrolled off the kernel message
(Continue reading)

Anton Blanchard | 21 Aug 01:26 2014
Picon

[PATCH] PCI: Increase BAR size quirk for IBM ipr SAS Crocodile adapters

From: Douglas Lehr <dllehr <at> us.ibm.com>

The Crocodile chip occasionally comes up with 4k and 8k BAR sizes.
Due to an errata, setting the SR-IOV page size causes the physical
function BARs to expand to the system page size.  Since ppc64 uses
64k pages, when Linux tries to assign the smaller resource sizes
to the now 64k BARs the address will be truncated and the BARs will
overlap.

This quirk will force Linux to allocate the resource as a full page,
which will avoid the overlap.

Cc: <stable <at> vger.kernel.org> 
Signed-off-by: Douglas Lehr <dllehr <at> us.ibm.com>
Signed-off-by: Anton Blanchard <anton <at> samba.org>
Acked-by: Milton Miller <miltonm <at> us.ibm.com>
---
 drivers/pci/quirks.c |   19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 80c2d01..45b946d 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
 <at>  <at>  -24,6 +24,7  <at>  <at> 
 #include <linux/ioport.h>
 #include <linux/sched.h>
 #include <linux/ktime.h>
+#include <linux/mm.h>
 #include <asm/dma.h>	/* isa_dma_bridge_buggy */
(Continue reading)


Gmane