linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Prarit Bhargava <prarit@redhat.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Linux PCI <linux-pci@vger.kernel.org>,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH 0/2] ACPI: return error in acpi_pci_irq_enable when there is no irq
Date: Mon, 16 Sep 2013 10:40:00 +0300	[thread overview]
Message-ID: <20130916074000.GA24222@xps8300> (raw)
In-Reply-To: <CAErSpo4r=oQ+J0=cM9gp3-i5-+5JYpYZQfzi3HFa6spxOO9OJg@mail.gmail.com>

On Fri, Sep 13, 2013 at 05:55:40PM -0600, Bjorn Helgaas wrote:
> On Fri, Sep 13, 2013 at 5:43 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Friday, September 13, 2013 08:52:18 AM Prarit Bhargava wrote:
> >>
> >> Rafael, is this in your queue?
> >
> > No, it is not, because Bjorn wanted to debug this issue deeper as far as I
> > could understand.
> >
> > Bjorn?
> 
> Yes.  Yinghai pointed out a possible issue ("some USB3 host controller
> does not have intx configured, but still work with MSI?").  I can't
> explain to you right now what that means, but I did look at it enough
> to think that there indeed might be a problem there.
> 
> So I asked [1] for a bugzilla with more info (dmesg, acpidump) so
> somebody could look at it.  Actually, I was hoping Heikki or Prarit
> would look into it and address Yinghai's concern.  Maybe there's no
> problem there, but we should at least look and explain *why* it's not
> a problem.  And I would really like a kernel.org bugzilla with the
> info, in case this change turns out to have unintended consequences
> and we have to debug it again later.

I'll ask Sarah (xHCI maintaner) for help in case she knows something
and create a bug for this if needed.

I don't understand much about PCI, I need to study it a bit. Why would
it be a problem to get the xHCI working with only MSI?

Thanks,

-- 
heikki

  reply	other threads:[~2013-09-16  7:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1375965314-24232-1-git-send-email-heikki.krogerus@linux.intel.com>
     [not found] ` <1375965314-24232-2-git-send-email-heikki.krogerus@linux.intel.com>
2013-08-08 13:57   ` [PATCH 1/2] ACPI / PCI: don't allow PCI devices without irq to be enabled Rafael J. Wysocki
2013-08-12 21:14     ` Bjorn Helgaas
2013-08-12 21:32       ` Yinghai Lu
2013-08-12 22:32         ` Bjorn Helgaas
2013-08-23 17:00           ` Bjorn Helgaas
2013-10-03 23:58           ` Prarit Bhargava
     [not found] ` <1375965314-24232-3-git-send-email-heikki.krogerus@linux.intel.com>
2013-08-08 13:58   ` [PATCH 2/2] ACPI / PCI: remove an extra check from acpi_pci_irq_enable() Rafael J. Wysocki
2013-08-12 21:15     ` Bjorn Helgaas
     [not found] ` <52330A82.7050607@redhat.com>
2013-09-13 23:43   ` [PATCH 0/2] ACPI: return error in acpi_pci_irq_enable when there is no irq Rafael J. Wysocki
2013-09-13 23:55     ` Bjorn Helgaas
2013-09-16  7:40       ` Heikki Krogerus [this message]
2013-09-16 10:28         ` Heikki Krogerus

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=20130916074000.GA24222@xps8300 \
    --to=heikki.krogerus@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=yinghai@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).