From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Paul Mackerras <paulus@samba.org>,
sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/2] powerpc/PCI: Use PCI_UNKNOWN for unknown power state
Date: Tue, 21 May 2013 09:42:01 +1000 [thread overview]
Message-ID: <1369093321.6387.24.camel@pasglop> (raw)
In-Reply-To: <20130520231909.32416.81752.stgit@bhelgaas-glaptop>
On Mon, 2013-05-20 at 17:19 -0600, Bjorn Helgaas wrote:
> Previously we initialized dev->current_state to 4 (PCI_D3cold), but I think
> we wanted PCI_UNKNOWN (5) here based on the comment and the fact that the
> generic version of this code, pci_setup_device(), uses PCI_UNKNOWN.
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
Ack. Do you send to Linus or should I ?
Thanks.
Cheers,
Ben.
> arch/powerpc/kernel/pci_of_scan.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/pci_of_scan.c b/arch/powerpc/kernel/pci_of_scan.c
> index 2a67e9b..d2d407d 100644
> --- a/arch/powerpc/kernel/pci_of_scan.c
> +++ b/arch/powerpc/kernel/pci_of_scan.c
> @@ -165,7 +165,7 @@ struct pci_dev *of_create_pci_dev(struct device_node *node,
> pr_debug(" class: 0x%x\n", dev->class);
> pr_debug(" revision: 0x%x\n", dev->revision);
>
> - dev->current_state = 4; /* unknown power state */
> + dev->current_state = PCI_UNKNOWN; /* unknown power state */
> dev->error_state = pci_channel_io_normal;
> dev->dma_mask = 0xffffffff;
>
next prev parent reply other threads:[~2013-05-20 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 23:19 [PATCH 1/2] powerpc/PCI: Use PCI_UNKNOWN for unknown power state Bjorn Helgaas
2013-05-20 23:19 ` [PATCH 2/2] sparc/PCI: " Bjorn Helgaas
2013-05-21 1:51 ` David Miller
2013-05-20 23:26 ` [PATCH 1/2] powerpc/PCI: " Bjorn Helgaas
2013-05-20 23:42 ` Benjamin Herrenschmidt [this message]
2013-05-20 23:45 ` 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=1369093321.6387.24.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=rjw@sisk.pl \
--cc=sparclinux@vger.kernel.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 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).