On Tue, Jun 23, 2015 at 06:23:53PM +0800, Shengjiu Wang wrote:
As the ssi is not the only cpu dai, there are esai, spdif, sai.
and imx_pcm_dma can be used by all of them. Especially ESAI need
a larger DMA buffer size. So Add dedicated DMA buffer for each cpu
dai.
Signed-off-by: Shengjiu
Hi Behn,
Need your help in understanding the historical context for having two
rtc interfaces in the kernel (CONFIG_GEN_RTC CONFIG_RTC_CLASS) and
which one should be enabled for pseries_defconfig. I have posted a patch
(http://patchwork.ozlabs.org/patch/478899/) to enable CONFIG_RTC_CLASS
in the
On Monday 22 June 2015 02:45 PM, Madhavan Srinivasan wrote:
On Tuesday 16 June 2015 11:58 AM, Preeti U Murthy wrote:
On 06/11/2015 10:47 AM, Madhavan Srinivasan wrote:
Adds cpumask attribute to be used by each nest pmu since nest
units are per-chip. Only one cpu (first online cpu) from each
On Mon 22-06-15 10:18:06, Eric B Munson wrote:
On Mon, 22 Jun 2015, Michal Hocko wrote:
On Fri 19-06-15 12:43:33, Eric B Munson wrote:
[...]
Are you objecting to the addition of the VMA flag VM_LOCKONFAULT, or the
new MAP_LOCKONFAULT flag (or both)?
I thought the MAP_FAULTPOPULATE
On some archs, the local clockevent device stops in deep cpuidle states.
The broadcast framework is used to wakeup cpus in these idle states, in
which either an external clockevent device is used to send wakeup ipis
or the hrtimer broadcast framework kicks in in the absence of such a
device. One
On Tue 23-06-15 14:45:17, Vlastimil Babka wrote:
On 06/22/2015 04:18 PM, Eric B Munson wrote:
On Mon, 22 Jun 2015, Michal Hocko wrote:
On Fri 19-06-15 12:43:33, Eric B Munson wrote:
[...]
My thought on detecting was that someone might want to know if they had
a VMA that was VM_LOCKED but
Nicolin Chen wrote:
As the ssi is not the only cpu dai, there are esai, spdif, sai.
and imx_pcm_dma can be used by all of them. Especially ESAI need
a larger DMA buffer size. So Add dedicated DMA buffer for each cpu
dai.
Signed-off-by: Shengjiu Wangshengjiu.w...@freescale.com
Acked-by: Nicolin
On 06/23/2015 11:01 PM, Bharata B Rao wrote:
So will it be correct to say that memory hotplug to memory-less node
isn't supported by PowerPC kernel ? Should I enforce the same in QEMU
for PowerKVM ?
I'm not sure if that is correct. It appears that we initialize all online
nodes, even those
On 24 June 2015 23:50:40 GMT+10:00, Rafael J. Wysocki r...@rjwysocki.net
wrote:
On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
On some archs, the local clockevent device stops in deep cpuidle
states.
The broadcast framework is used to wakeup cpus in these idle states,
in
On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
On some archs, the local clockevent device stops in deep cpuidle states.
The broadcast framework is used to wakeup cpus in these idle states, in
which either an external clockevent device is used to send wakeup ipis
or the hrtimer
On 06/24/15 00:07, Michael Ellerman wrote:
On Tue, 2015-06-23 at 09:48 -0400, David Long wrote:
On 06/22/15 23:32, Michael Ellerman wrote:
On Fri, 2015-06-19 at 10:12 -0400, David Long wrote:
On 06/19/15 00:19, Michael Ellerman wrote:
On Mon, 2015-06-15 at 12:42 -0400, David Long wrote:
On Thu, Jun 25, 2015 at 12:10 AM, Michael Ellerman
mich...@ellerman.id.au wrote:
On 24 June 2015 23:50:40 GMT+10:00, Rafael J. Wysocki r...@rjwysocki.net
wrote:
On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
On some archs, the local clockevent device stops in deep cpuidle
On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
4.2 material I suppose?
And stable. Without this, if you configure without TICK_ONESHOT, the
machine will hang.
OK, which -stable? All of them
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
4.2 material I suppose?
And stable. Without this, if you configure without TICK_ONESHOT, the
machine will hang.
Cheers,
Ben.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
On Tue, 2015-04-28 at 15:40 +0530, Vasant Hegde wrote:
+Device Tree binding for LEDs on IBM Power Systems
+-
+
+The 'led' node under '/ibm,opal' lists service indicators available in the
+system and their capabilities.
+
+led {
+
On Tue, 2015-04-28 at 15:39 +0530, Vasant Hegde wrote:
From: Anshuman Khandual khand...@linux.vnet.ibm.com
This patch registers the following two new OPAL interfaces calls
for the platform LED subsystem. With the help of these new OPAL calls,
the kernel will be able to get or set the state
On Tue, 2015-04-28 at 15:40 +0530, Vasant Hegde wrote:
This patch adds paltform devices for leds. Also export LED related
OPAL API's so that led driver can use these APIs.
Signed-off-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
Acked-by: Benjamin Herrenschmidt b...@kernel.crashing.org
On hotplug case, after a pdev is removed from the system, edev-mode will
set flag EEH_DEV_NO_HANDLER to mark the status. While this flag is not
cleared when we probe back those pdev. This will lead to miss the call of
driver-err_handler-slot_reset in eeh_report_reset().
This patch clear this flag
diff --git a/arch/powerpc/perf/core-book3s.c b/arch/powerpc/perf/core-book3s.c
index 7a03cce..892340e 100644
--- a/arch/powerpc/perf/core-book3s.c
+++ b/arch/powerpc/perf/core-book3s.c
@@ -930,7 +930,7 @@ static int power_check_constraints(struct cpu_hw_events
*cpuhw,
* added events.
On 06/25/2015 05:36 AM, Rafael J. Wysocki wrote:
On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
4.2 material I suppose?
And stable. Without this, if you configure without TICK_ONESHOT, the
- int bhrb_users;
+ unsigned intbhrb_users;
OK, so this is a good start.
A quick git grep for bhrb_users reveals this:
perf/core-book3s.c: WARN_ON_ONCE(cpuhw-bhrb_users 0);
That occurs in power_pmu_bhrb_disable, immediately
+static void insert_branch(struct cpu_hw_events *cpuhw,
+ int index, u64 from, u64 to, int mispred)
Given that your previous patch made mispred a bool, this could take a
bool too. It could probably be an inline function as well.
+{
+ cpuhw-bhrb_entries[index].from =
cpuhw-bhrb_entries[u_index].to = addr;
- cpuhw-bhrb_entries[u_index].mispred = pred;
- cpuhw-bhrb_entries[u_index].predicted = ~pred;
+ cpuhw-bhrb_entries[u_index].mispred =
From: Igal Liberman igal.liber...@freescale.com
Add Storage Profiles support.
The Storage Profiles contain parameters that are used by the FMan in
order to store frames being received on the Rx ports, or to
determine the parameters that affect writing the Internal Context
in the frame margin on
From: Igal Liberman igal.liber...@freescale.com
This patch adds the Ethernet MAC driver support.
Signed-off-by: Igal Liberman igal.liber...@freescale.com
Signed-off-by: Madalin Bucur madalin.bu...@freescale.com
---
drivers/net/ethernet/freescale/fman/inc/mac.h | 136
From: Igal Liberman igal.liber...@freescale.com
The FMan FLib provides the basic API used by the FMan drivers to
configure and control the FMan hardware.
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/net/ethernet/freescale/Kconfig |1 +
From: Igal Liberman igal.liber...@freescale.com
The Freescale Data Path Acceleration Architecture (DPAA) is a set of
hardware components on specific QorIQ multicore processors. This
architecture provides the infrastructure to support simplified sharing
of networking interfaces and accelerators
From: Igal Liberman igal.liber...@freescale.com
The FMan Port FLib provides basic API used by the drivers to
configure and control the FMan Port hardware.
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/net/ethernet/freescale/fman/Kconfig|1 +
From: Igal Liberman igal.liber...@freescale.com
Add Frame Manager Multi-User RAM support.
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/net/ethernet/freescale/fman/Kconfig|1 +
drivers/net/ethernet/freescale/fman/Makefile |6 +-
On 06/02/2015 10:48 AM, Kamalesh Babulal wrote:
We print the respective warning after parsing EPOW interrupts,
prompting user to take action depending upon the severity of the
event.
Some times same EPOW event warning, such as below could flood kernel
log, over a period of time. So Limit the
30 matches
Mail list logo
