On 02/20/2014 10:06 PM, Scott Wood wrote:
On Thu, 2014-02-20 at 21:53 +0100, Sebastian Andrzej Siewior wrote:
A MSI device may have multiple interrupts. That means that the
interrupts numbers should be continuos so that pdev-irq refers to the
first interrupt, pdev-irq + 1 to the second and so
A MSI device may have multiple interrupts. That means that the
interrupts numbers should be continuos so that pdev-irq refers to the
first interrupt, pdev-irq + 1 to the second and so on.
This patch adds support for continuous allocation of virqs for a range
of hwirqs. The function is based on
On Fri, Feb 21, 2014 at 06:31:28AM +, Alistair Popple wrote:
The IBM PPC476GTR SoC that is used on the Akebono board uses a
different ethernet PHY interface that has wake on lan (WOL) support
with the IBM emac. This patch adds support to the IBM emac driver for
this new PHY interface.
[Adding Tony Prisk to Cc]
On Fri, Feb 21, 2014 at 06:31:30AM +, Alistair Popple wrote:
Currently the ppc-of driver uses the compatibility string
usb-ehci. This means platforms that use device-tree and implement an
EHCI compatible interface have to either use the ppc-of driver or add
a
The PE state (for eeh_pe instance) EEH_PE_PHB_DEAD is duplicate to
EEH_PE_ISOLATED. Originally, those PHB (PHB PE) with EEH_PE_PHB_DEAD
would be removed from the system. However, it's safe to replace
that with EEH_PE_ISOLATED.
The patch also clear EEH_PE_RECOVERING after fenced PHB has been
According to Ben's suggestion, the patch makes the PHB diag-data
dump looks a bit short by printing multiple values in one line
and outputing - for zero fields.
After the patch applied, the PHB diag-data dump looks like:
PHB3 PHB#3 Diag-data (Version: 1)
brdgCtl: 0002
UtlSts: -
The PHB state PNV_EEH_STATE_REMOVED maintained in pnv_phb isn't
so useful any more and it's duplicated to EEH_PE_ISOLATED. The
patch replaces PNV_EEH_STATE_REMOVED with EEH_PE_ISOLATED.
Signed-off-by: Gavin Shan sha...@linux.vnet.ibm.com
---
arch/powerpc/platforms/powernv/eeh-ioda.c | 56
EEH core tries to recover from fenced PHB or frozen PE. Unfortunately,
the log isn't consistent with the site because enabling IO path for
the frozen PE before collecting log would ruin the site. The patch
solves the problem to cache the PHB diag-data in advance with the
help of additional flag
The flag PNV_EEH_STATE_ENABLED is put into pnv_phb::eeh_state, which
is protected by CONFIG_EEH. We needn't that. Instead, we can have
pnv_phb::flags and maintain all flags there, which is the purpose
of the patch.
Signed-off-by: Gavin Shan sha...@linux.vnet.ibm.com
---
On Friday 21 February 2014 17:31:27 Alistair Popple wrote:
+config MMC_SDHCI_OF_476GTR
+ tristate SDHCI OF support for the IBM PPC476GTR SoC
+ depends on MMC_SDHCI_PLTFM
+ depends on PPC_OF
+ help
+ This selects the Secure Digital Host Controller Interface (SDHCI)
On Friday 21 February 2014 11:48:03 Mark Rutland wrote:
+
+ np = of_find_compatible_node(NULL, NULL, ibm,usb-ohci-440epx);
+ if (np != NULL) {
+ /* claim we really affected by usb23 erratum */
+ if (!of_address_to_resource(np, 0, res))
+
On Friday 21 February 2014 17:31:29 Alistair Popple wrote:
+static const struct of_device_id ohci_of_match[] = {
+ { .compatible = usb-ohci, },
+ {},
+};
+
static const struct platform_device_id ohci_platform_table[] = {
{ ohci-platform, 0 },
{ }
@@ -198,6
On Friday 21 February 2014 17:31:33 Alistair Popple wrote:
+ HSTA0: hsta@31e {
+ compatible = ibm,476gtr-hsta-msi, ibm,hsta-msi;
+ reg = 0x310 0x000e 0x0 0xf0;
+ interrupt-parent = MPIC;
+
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE is required by the kdump kernel which is calling it to
retrieve the TCE set up by the panicing kernel.
On Fri, 21 Feb 2014, Alistair Popple wrote:
The IBM Akebono board uses the PPC476GTR SoC which has a OHCI
compliant USB host interface. This patch adds support for it to the
OHCI platform driver.
As we use device tree to pass platform specific data instead of
platform data we remove the
On Fri, 21 Feb 2014, Alistair Popple wrote:
Currently the ppc-of driver uses the compatibility string
usb-ehci. This means platforms that use device-tree and implement an
EHCI compatible interface have to either use the ppc-of driver or add
a compatible line to the ehci-platform driver. It
On 21.02.2014, at 16:31, Laurent Dufour lduf...@linux.vnet.ibm.com wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE is required by the kdump kernel
On Fri, 2014-02-21 at 16:31 +0100, Laurent Dufour wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE is required by the kdump kernel which is calling it
This patch is a modification of the patch originally proposed
by Xiaotian Feng xtf...@gmail.com: https://lkml.org/lkml/2012/11/5/413
This new version disables DMA channel interrupts and ensures that the tasklet
wil not be scheduled again before calling tasklet_kill().
Unfortunately the updated
On Fri, 21 Feb 2014, Alexandre Bounine wrote:
This patch is a modification of the patch originally proposed
by Xiaotian Feng xtf...@gmail.com: https://lkml.org/lkml/2012/11/5/413
This new version disables DMA channel interrupts and ensures that the tasklet
wil not be scheduled again before
On Fri, 2014-02-21 at 19:53 +0800, Gavin Shan wrote:
The flag PNV_EEH_STATE_ENABLED is put into pnv_phb::eeh_state, which
is protected by CONFIG_EEH. We needn't that. Instead, we can have
pnv_phb::flags and maintain all flags there, which is the purpose
of the patch.
Can you explain a bit
On Fri, 2014-02-21 at 19:53 +0800, Gavin Shan wrote:
EEH core tries to recover from fenced PHB or frozen PE. Unfortunately,
the log isn't consistent with the site because enabling IO path for
the frozen PE before collecting log would ruin the site. The patch
solves the problem to cache the PHB
On Fri, 2014-02-21 at 19:53 +0800, Gavin Shan wrote:
According to Ben's suggestion, the patch makes the PHB diag-data
dump looks a bit short by printing multiple values in one line
and outputing - for zero fields.
After the patch applied, the PHB diag-data dump looks like:
Actually, I
On Fri, 2014-02-21 at 15:33 +0100, Arnd Bergmann wrote:
@@ -242,8 +264,10 @@
ranges = 0x0200 0x 0x8000 0x0110
0x8000 0x0 0x8000
0x0100 0x00x00x0140
0x00x0 0x0001;
-
On Thu, 2014-02-20 at 12:56 -0600, Ruchika wrote:
linuxppc,
Is there another mailing list which is more appropriate ?
If so I'd be happy to get a recommendation.
If you're asking about U-Boot support, the list is u-b...@lists.denx.de
Be sure to mention what version of U-Boot you're using, and
On Friday 21 February 2014, Benjamin Herrenschmidt wrote:
On Fri, 2014-02-21 at 15:33 +0100, Arnd Bergmann wrote:
@@ -242,8 +264,10 @@
ranges = 0x0200 0x 0x8000 0x0110
0x8000 0x0 0x8000
0x0100 0x0
On Thu, 20 Feb 2014 10:28:47 -0800 Nishanth Aravamudan
n...@linux.vnet.ibm.com wrote:
On 20.02.2014 [10:05:39 -0600], Christoph Lameter wrote:
On Wed, 19 Feb 2014, Nishanth Aravamudan wrote:
We can call local_memory_node() before the zonelists are setup. In that
case,
I am out of the office until 25/02/2014.
Note: This is an automated response to your message Linuxppc-dev Digest,
Vol 114, Issue 105 sent on 21/02/2014 19:24:30.
This is the only notification you will receive while this person is away.
___
Hi,
On Thu, 2014-02-20 at 15:44 -0500, Tejun Heo wrote:
ps3_vuart wasn't overriding the work item with multiple work functions
but was using NULL for INIT_WORK() and then single PREPARE_WORK() to
set the work function. We can simply invoke INIT_WORK() with the work
function and remove the
On 21.02.2014 [14:42:03 -0800], Andrew Morton wrote:
On Thu, 20 Feb 2014 10:28:47 -0800 Nishanth Aravamudan
n...@linux.vnet.ibm.com wrote:
On 20.02.2014 [10:05:39 -0600], Christoph Lameter wrote:
On Wed, 19 Feb 2014, Nishanth Aravamudan wrote:
We can call local_memory_node()
/sys/devices/system/cpu/cpu*/smt-snooze-delay was converted into a NOP
in commit 3fa8cad82b94d0bed002571bd246f2299ffc876b, and now does
nothing. Add a pr_warn() to convince any users that they should stop
using it.
The commit message from the removing commit notes that this
functionality should
On 02/22/2014 06:23 AM, Benjamin Herrenschmidt wrote:
On Fri, 2014-02-21 at 16:31 +0100, Laurent Dufour wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE
On 02/22/2014 11:28 AM, Alexey Kardashevskiy wrote:
On 02/22/2014 06:23 AM, Benjamin Herrenschmidt wrote:
On Fri, 2014-02-21 at 16:31 +0100, Laurent Dufour wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture
On 22/02/14 00:48, Mark Rutland wrote:
[Adding Tony Prisk to Cc]
On Fri, Feb 21, 2014 at 06:31:30AM +, Alistair Popple wrote:
Currently the ppc-of driver uses the compatibility string
usb-ehci. This means platforms that use device-tree and implement an
EHCI compatible interface have to
34 matches
Mail list logo
