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-prev] [day] [month] [year] [list]
Message-ID: <1436349911.10819.64.camel@linux.intel.com>
Date:	Wed, 08 Jul 2015 13:05:11 +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
Subject: Re: [PATCH 0/2] x86: intel-mid-pci: fix to get eMMC detected

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@...ux.intel.com>
Intel Finland Oy
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ