On the some platforms of Freescale, sdhci controller can only
support 1.8V voltage, but the peripheral hardware circuit has
capability to support 3.3V voltage.
Signed-off-by: Chunhe Lan
---
drivers/mmc/host/sdhci.c |3 +++
include/linux/mmc/sdhci.h |4
2 files changed, 7 insertions
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Alex Williamson
> Sent: Tuesday, November 20, 2012 11:50 PM
> To: Alexey Kardashevskiy
> Cc: Benjamin Herrenschmidt; Paul Mackerras; linuxppc-
> d...@lists.ozlabs.or
Hi all,
I have a problem. This is on a MPC8536 based platform with 36-bit address space
and linux kernel 2.6.32 (32bit).
after X time we get coredumps from userspace applications(random):
one of the coredumps:
GNU gdb 6.8
Copyright (C) 2008 Fr
On Mon, Nov 19, 2012 at 01:20:05PM -0500, Bill Pemberton wrote:
> CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
> needed.
Erm, I don't understand. __devexit_p is defined also for modules not
only for CONFIG_HOTPLUG:
#if defined(MODULE) || defined(CONFIG_HOTPLUG)
#define __
On Thu, Nov 22, 2012 at 02:44:51PM +0100, Borislav Petkov wrote:
> On Mon, Nov 19, 2012 at 01:20:05PM -0500, Bill Pemberton wrote:
> > CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
> > needed.
>
> Erm, I don't understand. __devexit_p is defined also for modules not
> only f
On Tue, Nov 20, 2012 at 02:46:21PM +0100, Jean Delvare wrote:
> On Mon, 19 Nov 2012 13:20:14 -0500, Bill Pemberton wrote:
> > CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
> > needed.
>
> As mentioned on the lm-sensors list for hwmon patches already, I think
> it would be m
On 22/11/12 22:56, Sethi Varun-B16395 wrote:
-Original Message-
From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
ow...@vger.kernel.org] On Behalf Of Alex Williamson
Sent: Tuesday, November 20, 2012 11:50 PM
To: Alexey Kardashevskiy
Cc: Benjamin Herrenschmidt; Paul Mackerr
--- Begin Message ---
pseries msi: fixed crash on PCI devices without EEH capability
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/platforms/pseries/msi.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/platforms/pseries/msi.c
b/arch/powerpc/platfor
While hooking MSI interrupts, the corresponding device tree node
of the PE that the PCI device has been put into should be checked.
However, those PCI devices (e.g. VirtIO based PCI devices) that
don't have EEH capability shouldn't have the associated PE. So we
shouldn't try to get the PE's device
From: Gavin Shan
While hooking MSI interrupts, the corresponding device tree node
of the PE that the PCI device has been put into should be checked.
However, those PCI devices (e.g. VirtIO based PCI devices) that
don't have EEH capability shouldn't have the associated PE. So we
shouldn't try to g
Haren Myneni wrote:
> [PATCH 4/6] powerpc: Define ppr in thread_struct
>
> ppr in thread_struct is used to save PPR and restore it before process exits
> from kernel.
>
> This patch sets the default priority to 3 when tasks are created such
> that users can use 4 for higher priority tasks.
>
>
Haren Myneni wrote:
> [PATCH 5/6] powerpc: Macros for saving/restore PPR
>
> Several macros are defined for saving and restore user defined PPR value.
>
> Signed-off-by: Haren Myneni
> ---
> arch/powerpc/include/asm/exception-64s.h | 29 +
> arch/powerpc/include/
Heaven Myneni wrote:
> [PATCH 2/6] powerpc: Define CPU_FTR_HAS_PPR
>
> CPU_FTR_HAS_PPR is defined for POWER7.
>
> Signed-off-by: Haren Myneni
> ---
> arch/powerpc/include/asm/cputable.h |6 --
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/include/as
While the EEH does recovery on the specific PE that has PCI errors,
the PCI devices belonging to the PE will be removed and the PE will
be marked as invalid since we still need the information stored in
the PE. We only invalidate the PE when it doesn't have associated
EEH devices and valid child PE
14 matches
Mail list logo
