All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jason Cooper <jason@lakedaemon.net>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/6] pci: mvebu: generate proper configuration access cycles
Date: Fri, 25 Sep 2015 00:40:34 +0200	[thread overview]
Message-ID: <20150924224034.GH20825@lunn.ch> (raw)
In-Reply-To: <20150924224305.GG21513@n2100.arm.linux.org.uk>

> > I tried
> > 
> > root@dir665:~# setpci -s 1:0.0 0xe8.l
> > 00102000
> > root@dir665:~# setpci -s 1:0.0 0xe8.w=0x2000
> > root@dir665:~# setpci -s 1:0.0 0xe8.l
> > 00102000
> > 
> > but that is not producing the FAIL you had.
> 
> The only bit you have set in your DevSta register is:
> 
> #define  PCI_EXP_DEVSTA_AUXPD   0x0010  /* AUX Power Detected */
> 
> which is not a RW1C bit.

So i cannot actually test this on my hardware :-(

I guess the best i can do is apply the patch, load the wifi driver,
and ensure i can still join a network.

    Andrew

WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] pci: mvebu: generate proper configuration access cycles
Date: Fri, 25 Sep 2015 00:40:34 +0200	[thread overview]
Message-ID: <20150924224034.GH20825@lunn.ch> (raw)
In-Reply-To: <20150924224305.GG21513@n2100.arm.linux.org.uk>

> > I tried
> > 
> > root at dir665:~# setpci -s 1:0.0 0xe8.l
> > 00102000
> > root at dir665:~# setpci -s 1:0.0 0xe8.w=0x2000
> > root at dir665:~# setpci -s 1:0.0 0xe8.l
> > 00102000
> > 
> > but that is not producing the FAIL you had.
> 
> The only bit you have set in your DevSta register is:
> 
> #define  PCI_EXP_DEVSTA_AUXPD   0x0010  /* AUX Power Detected */
> 
> which is not a RW1C bit.

So i cannot actually test this on my hardware :-(

I guess the best i can do is apply the patch, load the wifi driver,
and ensure i can still join a network.

    Andrew

  reply	other threads:[~2015-09-24 22:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 17:17 [PATCH 0/6] mvebu PCI fixes and cleanups Russell King - ARM Linux
2015-09-23 17:17 ` Russell King - ARM Linux
2015-09-23 17:17 ` [PATCH 1/6] pci: mvebu: provide a compliant PCI configuration space Russell King
2015-09-23 17:17   ` Russell King
2015-09-23 17:17 ` [PATCH 2/6] pci: mvebu: generate proper configuration access cycles Russell King
2015-09-23 17:17   ` Russell King
2015-09-24 14:30   ` Andrew Lunn
2015-09-24 14:30     ` Andrew Lunn
2015-09-24 22:23   ` Andrew Lunn
2015-09-24 22:23     ` Andrew Lunn
2015-09-24 22:43     ` Russell King - ARM Linux
2015-09-24 22:43       ` Russell King - ARM Linux
2015-09-24 22:40       ` Andrew Lunn [this message]
2015-09-24 22:40         ` Andrew Lunn
2015-09-23 17:17 ` [PATCH 3/6] pci: mvebu: use of_get_available_child_count() Russell King
2015-09-23 17:17   ` Russell King
2015-09-23 17:17 ` [PATCH 4/6] pci: mvebu: use for_each_available_child_of_node() to walk child nodes Russell King
2015-09-23 17:17   ` Russell King
2015-09-23 17:17 ` [PATCH 5/6] pci: mvebu: report full node name when reporting a DT error Russell King
2015-09-23 17:17   ` Russell King
2015-09-23 17:17 ` [PATCH 6/6] pci: mvebu: use port->name rather than "PCIe%d.%d" Russell King
2015-09-23 17:17   ` Russell King
2015-09-24 23:36 ` [PATCH 0/6] mvebu PCI fixes and cleanups Andrew Lunn
2015-09-24 23:36   ` Andrew Lunn
2015-09-25  7:38 ` Thomas Petazzoni
2015-09-25  7:38   ` Thomas Petazzoni
2015-09-25 12:51   ` Bjorn Helgaas
2015-09-25 12:51     ` Bjorn Helgaas
2015-10-08 16:26 ` Bjorn Helgaas
2015-10-08 16:26   ` 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=20150924224034.GH20825@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=bhelgaas@google.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=thomas.petazzoni@free-electrons.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.