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
Subject: Re: [PATCH 0/2] x86: intel-mid-pci: fix to get eMMC detected
Date: Wed, 08 Jul 2015 13:05:11 +0300 [thread overview]
Message-ID: <1436349911.10819.64.camel@linux.intel.com> (raw)
In-Reply-To: <1434567830-237840-1-git-send-email-andriy.shevchenko@linux.intel.com>
On Wed, 2015-06-17 at 22:03 +0300, Andy Shevchenko wrote:
> On Intel Edison we have a nice 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.
Any comments on that?
>
> So, this series provides a workaround (patch 2) and small fix of
> error code
> (patch 1).
>
> I wonder if this can go to v4.2. What do you think?
>
> Andy Shevchenko (2):
> x86: intel_mid_pci: propagate actual return code
> x86: intel_mid_pci: work around for IRQ0 assignment
>
> arch/x86/pci/intel_mid_pci.c | 27 ++++++++++++++++++++++++---
> 1 file changed, 24 insertions(+), 3 deletions(-)
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2015-07-08 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 19:03 [PATCH 0/2] x86: intel-mid-pci: fix to get eMMC detected Andy Shevchenko
2015-06-17 19:03 ` [PATCH 1/2] x86: intel_mid_pci: propagate actual return code Andy Shevchenko
2015-06-17 19:03 ` [PATCH 2/2] x86: intel_mid_pci: work around for IRQ0 assignment Andy Shevchenko
2015-07-08 10:05 ` Andy Shevchenko [this message]
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=1436349911.10819.64.camel@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).