From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v2 0/3] x86/pci/intel-mid-pci: fix to get eMMC detected
Date: Wed, 8 Jul 2015 14:14:16 +0300 [thread overview]
Message-ID: <1436354059-130135-1-git-send-email-andriy.shevchenko@linux.intel.com> (raw)
On Intel Edison we have an interesting implementation of x86 platform without
legacy PIC and with specific PCI. There are devices which are not using
interrupt by some reasons, but have them as IRQ0 in the PCI configuration.
Suprisingly the first eMMC host controller is the actual user for IRQ0. Since
we have serial driver implemented that enumerates unused serial IP (one of
four) which has IRQ0 assigned we, in case it gets it first by
pci_enable_device(), lost a possibility to probe eMMC.
So, this series provides a quirk (patch 1), small fix of error code
(patch 2), and sparse warning fix (patch 3).
Changelog v2:
- rearrange patches 1 and 2 to provide fix first with Fixes: tag
- append patch 3
- rebase on top of recent linux-next
Andy Shevchenko (3):
x86/pci/intel_mid_pci: work around for IRQ0 assignment
x86/pci/intel_mid_pci: propagate actual return code
x86/pci/intel_mid_pci: fix a sparse warning
arch/x86/pci/intel_mid_pci.c | 27 ++++++++++++++++++++++++---
1 file changed, 24 insertions(+), 3 deletions(-)
--
2.1.4
next reply other threads:[~2015-07-08 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 11:14 Andy Shevchenko [this message]
2015-07-08 11:14 ` [PATCH v2 1/3] x86/pci/intel_mid_pci: work around for IRQ0 assignment Andy Shevchenko
2015-07-08 12:55 ` Thomas Gleixner
2015-07-08 11:14 ` [PATCH v2 2/3] x86/pci/intel_mid_pci: propagate actual return code Andy Shevchenko
2015-07-08 11:14 ` [PATCH v2 3/3] x86/pci/intel_mid_pci: fix a sparse warning 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=1436354059-130135-1-git-send-email-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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).