linux-kernel - [PATCH 0/2] x86: intel-mid-pci: fix to get eMMC detected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Jun 2015 22:03:48 +0300
From:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:	linux-kernel@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
	linux-pci@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org
Cc:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: [PATCH 0/2] x86: intel-mid-pci: fix to get eMMC detected

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. 

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(-)

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/