linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, johan@kernel.org,
	linux-usb@vger.kernel.org, alberto.vignani@fastwebnet.it
Subject: Re: [PATCH v2 1/2] PCI: Disable MSI for Pericom PCIe-USB adapter
Date: Mon, 16 Nov 2020 11:46:44 +0200	[thread overview]
Message-ID: <20201116094644.GP4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201113232138.GA1141907@bjorn-Precision-5520>

On Fri, Nov 13, 2020 at 05:21:38PM -0600, Bjorn Helgaas wrote:
> On Fri, Nov 06, 2020 at 12:05:25PM +0200, Andy Shevchenko wrote:
> > Pericom PCIe-USB adapter advertises MSI, but documentation says
> > "The MSI Function is not implemented on this device." in the chapters
> > 7.3.27, 7.3.29-7.3.31.
> > 
> > Fixes: 306c54d0edb6 ("usb: hcd: Try MSI interrupts on PCI devices")
> > Datasheet: https://www.diodes.com/assets/Datasheets/PI7C9X440SL.pdf
> > Reported-by: alberto.vignani@fastwebnet.it
> 
> Is there a URL to a problem report we can include here?

You mean URL to email archives or something else?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2020-11-16 10:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 10:05 [PATCH v2 1/2] PCI: Disable MSI for Pericom PCIe-USB adapter Andy Shevchenko
2020-11-06 10:05 ` [PATCH v2 2/2] PCI: Use predefined Pericom vendor ID Andy Shevchenko
2020-11-13 23:21 ` [PATCH v2 1/2] PCI: Disable MSI for Pericom PCIe-USB adapter Bjorn Helgaas
2020-11-16  9:46   ` Andy Shevchenko [this message]
2020-11-16 12:37     ` Bjorn Helgaas
2020-11-16 13:46       ` Andy Shevchenko
2020-11-16 16:24         ` Andy Shevchenko
2020-11-17 23:32 ` Bjorn Helgaas
2020-11-18 14:11   ` Andy Shevchenko

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=20201116094644.GP4077@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alberto.vignani@fastwebnet.it \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=johan@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@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).