Add support for Cortina CS4315/CS4340 10G PHY.
(Tested with CS4315 on T2080RDB and CS4340 on T4240RDB).
Signed-off-by: YongHua Cao b43...@freescale.com
Signed-off-by: Shengzhou Liu shengzhou@freescale.com
---
drivers/net/phy/Kconfig | 5 +++
drivers/net/phy/Makefile | 1 +
On Mar 5, 2014, at 2:16 AM, Shengzhou Liu shengzhou@freescale.com wrote:
Add support for Cortina CS4315/CS4340 10G PHY.
(Tested with CS4315 on T2080RDB and CS4340 on T4240RDB).
Signed-off-by: YongHua Cao b43...@freescale.com
Signed-off-by: Shengzhou Liu shengzhou@freescale.com
---
Sure, will too post to netdev list.
Regards,
Shengzhou
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Wednesday, March 05, 2014 5:30 PM
To: Liu Shengzhou-B36685
Cc: linuxppc-dev@lists.ozlabs.org; Wood Scott-B07421; Cao Yong Hua-B43619
Subject: Re:
On Wed, Mar 05, 2014 at 09:48 +0800, Shawn Guo wrote:
On Mon, Mar 03, 2014 at 10:22:31AM +0100, Gerhard Sittig wrote:
On Mon, Feb 24, 2014 at 11:25 +0100, Gerhard Sittig wrote:
a recent FEC binding document update that was motivated by i.MX
development revealed that ARM and PowerPC
Abandon this patch, in Kernel gen10g_driver can support Cortina PHY, we need
specific PHY driver just in u-boot.
-Shengzhou
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
On Tue, Mar 04, 2014 at 02:07:31PM -0700, Bjorn Helgaas wrote:
This is just cleanup of a couple unused interfaces and (for sparc64) a
supporting variable.
Thanks!
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
On Mar 5, 2014, at 1:21 AM, Zhao Qiang b45...@freescale.com wrote:
There is QE on platform T104x, add support.
Call funcs qe_ic_init and qe_init if CONFIG_QUICC_ENGINE is defined.
Signed-off-by: Zhao Qiang b45...@freescale.com
---
Changes for v2:
- use mpc85xx_qe_init() instead
RTAS manipulates its input and output arguments in big endian order.
I have looked at factoring some lines with rtas_call() but it is not really
worth it because of the variable arguments.
Signed-off-by: Greg Kurz gk...@linux.vnet.ibm.com
---
arch/powerpc/kernel/rtas.c | 15 +--
1
On Wed, 2014-03-05 at 05:09 -0600, Liu Shengzhou-B36685 wrote:
Abandon this patch, in Kernel gen10g_driver can support Cortina PHY, we need
specific PHY driver just in u-boot.
Why shouldn't U-Boot have a generic driver too?
-Scott
___
Each arch that supports audit requires syscall_get_arch() to able to log
and identify architecture-dependent syscall numbers. The information is used
in at least two different subsystems, so standardize it in the same call across
all arches.
Use the standardized syscall_get_arch() locally to add
The AUDIT_SECCOMP record looks something like this:
type=SECCOMP msg=audit(1373478171.953:32775): auid=4325 uid=4325 gid=4325 ses=1
subj=unconfined_u:unconfined_r:unconfined_t:s0 pid=12381 comm=test sig=31
syscall=231 compat=0 ip=0x39ea8bca89 code=0x0
In order to determine what syscall 231
Each arch that supports audit requires syscall_get_arch() to able to log and
identify architecture-dependent syscall numbers. The information is used in at
least two different subsystems, so standardize it in the same call across all
arches.
Signed-off-by: Richard Guy Briggs r...@redhat.com
---
Since all the callers of syscall_get_arch() presently pass current and none
of the arch-specific syscall_get_arch() implementations use the regs parameter,
ignore the passed in arch parameter to __audit_syscall_entry() and call
syscall_get_arch() directly.
Change the audit header file from the
Make audit_syscall_entry() ignore the arch parameter passed to it and call
syscall_get_arch() locally.
Remove arch from the audit_syscall_entry() parameter list.
Signed-off-by: Richard Guy Briggs r...@redhat.com
---
arch/arm/kernel/ptrace.c|2 +-
arch/ia64/kernel/ptrace.c |
Since arch is found locally in __audit_syscall_entry(), there is no need to
pass it in as a parameter. Delete it from the parameter list.
x86* was the only arch to call __audit_syscall_entry() directly and did so from
assembly code.
Signed-off-by: Richard Guy Briggs r...@redhat.com
---
Can I
Since all callers of syscall_get_arch() call with task current and none of
the arch-dependent functions use the regs parameter (which could just as
easily be found with task_pt_regs()), delete both parameters.
Signed-off-by: Richard Guy Briggs r...@redhat.com
---
arch/arm/include/asm/syscall.h
Add PMU_FORMAT_RANGE() and PMU_FORMAT_RANGE_RESERVED() (for reserved
areas) which generate functions to extract the relevent bits from
event-attr.config{,1,2} for use by sw-like pmus where the
'config{,1,2}' values don't map directly to hardware registers.
Signed-off-by: Cody P Schafer
These patches add basic pmus for 2 powerpc hypervisor interfaces to obtain
performance counters: gpci (get performance counter info) and 24x7.
The counters supplied by these interfaces are continually counting and never
need to be (and cannot be) disabled or enabled. They additionally do not
Rather an having every pmu that needs a function that just returns 0 for
.event_idx define their own copy, reuse the one in kernel/events/core.c.
Rename from perf_swevent_event_idx() because we're no longer using it
for just software events. Naming is based on the perf_pmu_nop_*()
functions.
Signed-off-by: Cody P Schafer c...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/hvcall.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/include/asm/hvcall.h
b/arch/powerpc/include/asm/hvcall.h
index d8b600b..5dbbb29 100644
--- a/arch/powerpc/include/asm/hvcall.h
+++
bin_attributes created/updated in create_files() (such as those listed
via (struct device).attribute_groups) were not placed under the
specified group, and instead appeared in the base kobj directory.
Fix this by making bin_attributes use creating code similar to normal
attributes.
A quick grep
H_GetPerformanceCounterInfo (refered to as hv_gpci or just gpci from
here on) is an interface to retrieve specific performance counters and
other data from the hypervisor. All outputs have a fixed format. This
header only describes the portions of the interface that we plan on
using in linux at
24x7 (also called hv_24x7 or H_24X7) is an interface to obtain
performance counters from the hypervisor. These counters do not have a
fixed format/possition and are instead documented in a 24x7 Catalog,
which is provided by the hypervisor (that interface is also documented
paritialy in the
This exposes a simple way to grab the firmware provided
collect_priveliged, ga, expanded, and lab capability bits. All of these
bits come in from the same gpci request, so we've exposed all of them.
Only the collect_priveliged bit is really used by the hv-gpci/hv-24x7
code, the other bits are
This provides a basic link between perf and hv_gpci. Notably, it does
not yet support transactions and does not list any events (they can
still be manually composed).
Example usage via perf tool:
perf stat -e
This provides a basic interface between hv_24x7 and perf. Similar to
the one provided for gpci, it lacks transaction support and does not
list any events.
Example usage via perf tool:
perf stat -e
'hv_24x7/domain=2,offset=8,starting_index=0,lpar=0x/' -r 0 -C 0 -x ' '
sleep 0.1
Signed-off-by: Cody P Schafer c...@linux.vnet.ibm.com
---
arch/powerpc/perf/Makefile | 2 ++
arch/powerpc/platforms/pseries/Kconfig | 12
2 files changed, 14 insertions(+)
diff --git a/arch/powerpc/perf/Makefile b/arch/powerpc/perf/Makefile
index 60d71ee..f9c083a 100644
gpci and 24x7 expose some device specific attributes. Add some
documentation for them.
Signed-off-by: Cody P Schafer c...@linux.vnet.ibm.com
---
.../testing/sysfs-bus-event_source-devices-hv_24x7 | 23
.../testing/sysfs-bus-event_source-devices-hv_gpci | 43 ++
2
On 03/04/2014 12:09 AM, Cody P Schafer wrote:
On 03/03/2014 09:19 PM, Michael Ellerman wrote:
On Thu, 2014-27-02 at 21:04:55 UTC, Cody P Schafer wrote:
Add PMU_FORMAT_RANGE() and PMU_FORMAT_RANGE_RESERVED() (for reserved
areas) which generate functions to extract the relevent bits from
Add documentation for the event, event.scale, and event.unit
files in sysfs.
event.scale and event.unit were undocumented.
event was previously documented only for specific powerpc pmu events.
I've added a restriction that event names cannot contain '.' characters
so we can avoid breaking the
Listing specific events doesn't actually help us at all here because:
- these events actually vary between different ppc processors, they
aren't garunteed to be present.
- the documentation of the file contents is now duplicated by the
docs for arbitrary event file contents.
Documents pmu/event/event{,.scale,.units} and then removes the redundant
POWER docs.
Slightly restricts event names to avoid API funkyness when we add new
event.? files ('.' forbidden in event names).
The contact is currently lkml, it would be very useful to have a perf
development list to
New QE doesn't have par_io, it doesn't need to init par_io
for new QE.
Split function mpc85xx_qe_init() into mpc85xx_qe_init()
and mpc85xx_qe_par_io_init().
Call mpc85xx_qe_init() for both new and old while
mpc85xx_qe_par_io_init() after mpc85xx_qe_init() for old.
Signed-off-by: Zhao Qiang
There is QE on platform T104x, add support.
Call funcs qe_ic_init and qe_init if CONFIG_QUICC_ENGINE is defined.
Signed-off-by: Zhao Qiang b45...@freescale.com
---
Changes for v2:
- use mpc85xx_qe_init() instead
Changes for v3:
- remove #ifdef which aren't really needed
From: Gavin Shan sha...@linux.vnet.ibm.com
Date: Tue, 4 Mar 2014 15:35:20 +0800
In kexec scenario, we failed to load the mlx4 driver in the
second kernel because the ownership bit was hold by the first
kernel without release correctly.
The patch adds shutdown() interface so that the
On 03/05/2014 02:37 AM, Bjorn Helgaas wrote:
Remove mc_capable() and smt_capable(). Neither is used.
Both were added by 5c45bf279d37 (sched: mc/smt power savings sched
policy). Uses of both were removed by 8e7fbcbc22c1 (sched: Remove stale
power aware scheduling remnants and dysfunctional
The IBM Akebono board is a development board for the new PPC476GTR
system on chip (SoC).
This version of the series updates the device tree and drops the USB
patches as the equivalent functionality is already in linux-next. It
also addresses feedback from the previous submission.
Alistair Popple
This patch adds a generic platform driver registration to the exiting SDHCI
platform driver using the devicetree compatibility string generic-sdhci.
Signed-off-by: Alistair Popple alist...@popple.id.au
---
.../devicetree/bindings/mmc/sdhci-pltfm.txt| 16 +
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.
At this stage the wake on lan functionality has not been implemented.
The IBM Akebono code uses the same initialisation functions as the
earlier Currituck board. Rather than create a copy of this code for
Akebono we will instead integrate support for it into the same file as
the Currituck code.
This patch just renames the board support file and updates the
This patch adds support for the IBM Akebono board.
Signed-off-by: Alistair Popple alist...@popple.id.au
---
.../devicetree/bindings/powerpc/4xx/akebono.txt| 54 +++
arch/powerpc/boot/Makefile | 3 +
arch/powerpc/boot/dcr.h| 4 +
The PPC476GTR SoC supports message signalled interrupts (MSI) by writing
to special addresses within the High Speed Transfer Assist (HSTA) module.
This patch adds support for PCI MSI with a new system device. The DMA
window is also updated to allow access to the entire 42-bit address range
to
When requested, have the kernel save the user stack in each perf sample
so 'perf report' can use libunwind and produce better backtraces.
The downside of course is that the kernel has to copy the user-stack
on each sample which has both performance and file-size implications
(of the perf.data
When we try to create backtraces (call-graphs) with the perf tool
perf record -g /tmp/sprintft
we get backtraces with duplicate arcs for sprintft[1]:
14.61% sprintft libc-2.18.so [.] __random
|
--- __random
When checking whether a bit representing a register is set in
sample_regs, a 64-bit mask, use 64-bit value (1LL).
Signed-off-by: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
---
tools/perf/util/unwind.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Add ability to link with libunwind on Power.
This is based on similar changes in x86 and arm. Basically, implement
accessor functions that libunwind can call into while building the
backtrace from the user stack (which the kernel saved in a perf sample
- in previous commit).
Tested on Fedora-20
I noticed this when testing setarch. No, we don't magically
support a big endian userspace on a little endian kernel.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@vger.kernel.org # v3.10+
---
diff --git a/arch/powerpc/include/asm/compat.h
b/arch/powerpc/include/asm/compat.h
index
On Wed, 2014-03-05 at 18:20 +0100, Greg Kurz wrote:
RTAS manipulates its input and output arguments in big endian order.
I have looked at factoring some lines with rtas_call() but it is not really
worth it because of the variable arguments.
I'm not sure about that one ...
So this assumes
Although we already block EBB events which request sampling using
sample_period, technically it's possible for an event to set sample_type
but not sample_period.
Nothing terrible will happen if an EBB event does specify sample_type,
but it signals a major confusion on the part of userspace, and
Rather than using PERF_EVENT_CONFIG_EBB_SHIFT everywhere, add an
EVENT_EBB_SHIFT like every other event and use that.
Signed-off-by: Michael Ellerman m...@ellerman.id.au
---
arch/powerpc/perf/power8-pmu.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
We only need to mask the EBB bit out of the event for the check of the
special PMC 5 6 events. So use a local to do it just for that code,
rather than changing the event value for the life of the function.
While we're there move the set of mask and value after all the checks.
Signed-off-by:
We want a way for users of EBB (Event Based Branches) to also access the
BHRB (Branch History Rolling Buffer). EBB does not interoperate with our
existing BHRB support, which is wired into the generic Linux branch
stack sampling support.
To support EBB BHRB we add three new bits to the event
The previous commit added constraint and register handling to allow
processes using EBB (Event Based Branches) to request access to the BHRB
(Branch History Rolling Buffer).
With that in place we can allow processes using EBB to access the BHRB.
This is achieved by setting BHRBA in MMCR0 when we
53 matches
Mail list logo
