On Tue, Oct 04, 2016 at 07:52:04AM +0200, Mike Looijmans wrote:
> Set bit 0 in register 1C.23 to enable the EDPD feature of the
> KSZ9031 PHY. This reduces power consumption when the link is
> down.
>
> Signed-off-by: Mike Looijmans
Reviewed-by: Andrew Lunn
Andrew
On Mon, Oct 03, 2016 at 03:20:57PM -0400, bdegr...@codeaurora.org wrote:
> Thinking about this, as the reader/writer code has no known "abuse"
> case, I'll remove it from the patchset, then provide a v2 patchset
> with a detailed explanation for the lockref problem using the commits
> you provided
* Andy Lutomirski wrote:
> > Running the task in user space, would have to ensure
> > "registers valid" is true, and make "memory valid"
> > false, because userspace could write to the registers.
> >
> > Doing a ptrace fpstate_read would make "memory valid"
> > true, but does not need to invalid
Marcelo Cerri writes:
> [ Unknown signature status ]
> On Wed, Sep 28, 2016 at 09:20:15PM +0800, Herbert Xu wrote:
>> On Wed, Sep 28, 2016 at 10:15:51AM -0300, Marcelo Cerri wrote:
>> > Hi Herbert,
>> >
>> > Any thoughts on this one?
>>
>> Can this patch wait until the next merge window? On the
On 4 October 2016 at 07:17, Sitsofe Wheeler wrote:
> While trying to do a discard inside an ESXi 6 VM to an LVM device atop
> an md RAID1 device composed of two SATA SSDs passed up as a raw disk
> mappings through a PVSCSI controller, this BUG followed by an Oops was
> hit:
>
> [ 86.902888]
On Fri, Sep 23, 2016 at 3:56 AM, wrote:
> From: Thor Thayer
>
> The tx-threshold parameter sets the TX FIFO low water threshold
> trigger for the Altera 16550-FIFO32 soft IP.
>
> Signed-off-by: Thor Thayer
> ---
> v2 Change from tx-loadsz to tx-threshold
> ---
> arch/nios2/boot/dts/10m50_dev
While trying to do a discard inside an ESXi 6 VM to an LVM device atop
an md RAID1 device composed of two SATA SSDs passed up as a raw disk
mappings through a PVSCSI controller, this BUG followed by an Oops was
hit:
[ 86.902888] [ cut here ]
[ 86.904600] kernel BUG at a
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
The new features and main improvements in this merge for v4.9
- Support for the UBSAN sanitizer
- Set HAVE_EFFICIENT_UNALIGNE
Hi Michael,
On Tue, Aug 30, 2016 at 10:32 AM, Anand Moon wrote:
> Hi All
>
> Adding Vivek Gautam.
Sorry for missing out this conversation. I am no longer part of Samsung.
>
> On 29 August 2016 at 16:35, Michael Niewöhner wrote:
>> Hi Mathias,
>> On Mo, 2016-08-29 at 13:59 +0300, Mathias Nyman
On Thu, Sep 22, 2016 at 12:10 PM, tip-bot for Gu Zheng wrote:
>
> x86/acpi: Introduce persistent storage for cpuid <-> apicid mapping
>
> The whole patch-set aims at making cpuid <-> nodeid mapping persistent. So
> that,
> when node online/offline happens, cache based on cpuid <-> nodeid mapping
Hi Shua,
your commit c6d2995da540 ("samples: move blackfin gptimers-example
from Documentation") has popped up in today's linux-next.
scripts/checkkconfigsymbols.py complained about two issues.
The refactoring from build rules to Kconfig preserved the 'CONFIG_'
prefix (i.e., depends on CONFIG_BLA
On Mon 03-10-16 15:05:57, Ross Zwisler wrote:
> > > @@ -623,22 +672,30 @@ static void *dax_insert_mapping_entry(struct
> > > address_space *mapping,
> > > error = radix_tree_preload(vmf->gfp_mask & ~__GFP_HIGHMEM);
> > > if (error)
> > > return ERR_PTR(error);
Set bit 0 in register 1C.23 to enable the EDPD feature of the
KSZ9031 PHY. This reduces power consumption when the link is
down.
Signed-off-by: Mike Looijmans
---
v2: Unconditionally enable EDPD mode
drivers/net/phy/micrel.c | 21 +
1 file changed, 21 insertions(+)
diff --g
Hi Linus,
a lot of movement in the EDAC tree this time around, coarse changelog
below.
Please pull,
thanks.
---
The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:
Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)
are available in the git repository at:
git://git.kernel.o
If NCR5380_poll_politely() is called under irq lock, the polling time
limit is clamped to avoid a spike in interrupt latency. When not under
irq lock, the same polling time limit acts as the worst case delay
between schedule() calls.
During PDMA (under irq lock) I've found that the 10 ms time limi
Re-order struct members so that hot data lies at the beginning of the
struct and cold data at the end. Improve the comments while we're here.
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.h | 40
1 file changed, 20 insertions(+), 20 deletions(-)
dif
Pass a NCR5380_hostdata struct pointer to the board-specific routines
instead of a Scsi_Host struct pointer. This reduces pointer chasing in
the PIO and PDMA fast paths. The old way was a mistake because it is
slow and the board-specific code is not concerned with the mid-layer.
Signed-off-by: Fin
The various 5380 drivers inconsistently store register pointers
either in the Scsi_Host struct "legacy crap" area or in special,
board-specific members of the NCR5380_hostdata struct. Uniform
use of the latter struct makes for simpler and faster code (see
the following patches) and helps to reduce
For timeout values adopt unsigned long, which is the type of jiffies etc.
For chip register values and bit masks pass u8, which is the return type
of readb, inb etc.
For device register offsets adopt unsigned int, as it is suitable for
adding to base addresses.
Pass the NCR5380_hostdata pointer
Apply prototypes to get consistent function signatures for the DMA
functions implemented in the board-specific drivers. To avoid using
macros to alter actual parameters, some of those functions are reworked
slightly.
This is a step toward the goal of passing the board-specific routines
to the core
Signed-off-by: Finn Thain
---
drivers/scsi/arm/cumana_1.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/scsi/arm/cumana_1.c b/drivers/scsi/arm/cumana_1.c
index 8e9cfe8..f616756 100644
--- a/drivers/scsi/arm/cumana_1.c
+++ b/drivers/scsi/arm/cumana_1.c
@@ -33,10 +33,6 @@
#inclu
This patch series has fixes for compatibility, reliability and
performance issues and some cleanup. It also includes a new version
of Ondrej Zary's patch that merges g_NCR5380_mmio into g_NCR5380.
I've tested this patch series on a Powerbook 180. If someone would
test some of the other platforms t
If a NCR5380 host instance ends up on a shared interrupt line then
this printk will be a problem. It is already a problem on some Mac
models: when testing mac_scsi on a PowerBook 180 I found that PDMA
transfers (but not PIO transfers) cause the message to be logged.
These spurious interrupts don't
Avoid the call to NCR5380_poll_politely2() when possible. The call is
easily short-circuited on the PIO fast path, using the inline wrapper.
This requires that the NCR5380_read macro be made available before
any #include "NCR5380.h" so a few declarations have to be moved too.
Signed-off-by: Finn T
This patch fixes an old bug: accesses to device registers from the
interrupt handler (after reselection, DMA completion etc.) could mess
up a device register access elsewhere, if the latter takes place outside
of an irq lock (during selection etc.).
Signed-off-by: Finn Thain
---
drivers/scsi/ata
From: Ondrej Zary
Merge the port-mapped IO and memory-mapped IO support (with the help of
ioport_map) into the g_NCR5380 module and delete g_NCR5380_mmio.
Signed-off-by: Ondrej Zary
Signed-off-by: Finn Thain
---
MAINTAINERS | 1 -
drivers/scsi/Kconfig | 32 +-
When polling a device register under irq lock the polling loop terminates
after a given number of jiffies. Make this timeout independent of the HZ
setting.
All 5380 drivers benefit from this patch, which optimizes the PIO fast
path, because they all use PIO transfers (for phases other than DATA IN
On Mon, Oct 03, 2016 at 03:48:36PM +0300, Jarkko Sakkinen wrote:
> On Mon, Oct 03, 2016 at 07:05:48AM +, Winkler, Tomas wrote:
> >
> > > On Sun, Oct 02, 2016 at 01:24:55PM +0300, Jarkko Sakkinen wrote:
> > > > On Sun, Oct 02, 2016 at 01:17:55PM +0300, Jarkko Sakkinen wrote:
> > > > > On Sun, O
Dearest Chosen One
With Due Respect And Humanity,I was compelled to write to you under a
humanitarian ground. My name is Mrs Amina Mohammed, My Husband was a director
in a trading company here in Cote D Ivoire.We were married for 36 years without
a child. He died after Cardiac Arteries operati
On Mon, 3 Oct 2016 11:07:36 +0200
Jiri Slaby wrote:
> Provided the architectures do not need any special handling (they seem
> not to support vga at all, actually), there is no need to have an
> empty vga.h. Let them refer to the generic one instead.
>
> Signed-off-by: Jiri Slaby
> Cc: David H
From: Long Li
hv_pci_devices_present is called in hv_pci_remove when we remove a PCI device
from host (e.g. by disabling SRIOV on a device). In hv_pci_remove, the bus is
already removed before the call, so we don't need to rescan the bus in the
workqueue scheduled from hv_pci_devices_present.
From: Long Li
A PCI_EJECT message can arrive at the same time we are calling
pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS message
or in create_root_hv_pci_bus(), in this case we could potentailly modify the
bus from multiple places. Properly lock the bus access.
Than
El 2016年10月03日 a las 20:18, Joe Perches escribió:
On Mon, 2016-10-03 at 20:12 +0200, Sergio Paracuellos wrote:
El 2016年10月03日 a las 18:16, Joe Perches escribió:
Perhaps better as hw->scanresults = kmemdup(inf, sizeof(*inf),
GFP_ATOMIC);
I agree. But because all the code is full of sizeo
Hello,
Cc Jens and block-dev,
I'll outline the commit message for Jens and blockdev people, may be
someone will have some thoughts/ideas/opinions:
> On (09/22/16 15:42), Minchan Kim wrote:
: zram supports stream-based parallel compression. IOW, it can support
: parallel compression on SMP system
From: Colin Cross
Rather than using explicit euid == 0 checks when trying to move
tasks into a cgroup, move permission checks into each specific
cgroup subsystem. If a subsystem does not specify a 'allow_attach'
handler, then we fall back to doing the checks the old way.
This patch adds a 'allow
From: Rom Lemarchand
If CONFIG_CGROUP_NICE_ATTACH is enabled, this implements an
allow_attach policy for Android, which allows any process with
CAP_SYS_NICE to move tasks across cpuset and cpuctrl cgroups.
This includes folded down fixes from:
Dmitry Shmidt
Riley Andrews
Amit Pundir
Cc
As a heads up, this is just a first RFC and not a submission.
I wanted to send this out again, as the last time I submitted this
(https://marc.info/?l=linux-kernel&m=143217972215192&w=2) the
discussion got out into the separate issue of how Android at one
time abused memcg (but I believe now memcg
Hello Stefan,
On 16-10-03 11:05:59, Stefan Agner wrote:
> On 2016-10-03 05:50, Sanchayan Maity wrote:
> > Enable DMA for DSPI on Vybrid.
>
> Hm, we have that in 4.4 already, is that meant for 4.1?
Sorry?! I send this out for mainline and the patch series is based
on top of shawn's for-next branc
CC Michal. It looks like a microblaze specific error. I'll blacklist
this old error on microblaze if there are no good solutions.
Sorry for the noise!
On Fri, Sep 23, 2016 at 05:11:32PM -0400, Nicolas Pitre wrote:
On Thu, 22 Sep 2016, kbuild test robot wrote:
Hi Nicolas,
FYI, the error/warni
Peter Zijlstra writes:
> On Mon, Oct 03, 2016 at 03:29:32PM +0200, Jiri Olsa wrote:
>> On Fri, Sep 23, 2016 at 06:37:47PM +0200, Peter Zijlstra wrote:
>> > On Wed, Sep 21, 2016 at 03:55:34PM +0200, Jiri Olsa wrote:
>> > > stack backtrace:
>> > > CPU: 9 PID: 2998 Comm: ls Tainted: GW
On Mon, Oct 3, 2016 at 7:47 PM, Maxime Ripard
wrote:
> Hi,
>
> On Mon, Oct 03, 2016 at 07:07:57PM +0800, Chen-Yu Tsai wrote:
>> The A31 has a similar codec to the A10/A20. The PCM parts are very
>> similar, with just different register offsets. The analog paths are
>> very different. There are mor
Hi all,
On Tue, 4 Oct 2016 14:56:49 +1100 Stephen Rothwell
wrote:
>
> There will be no linux-next release on Friday.
>
> Changes since 20161003:
I forgot to say: Please do *not* add any v4.10 material to your
linux-next included trees until v4.9-rc1 has been released i.e. the
On Mon, Oct 3, 2016 at 9:07 PM, Andrew Morton wrote:
>
> Well, it's a VM_BUG_ON and few people run with CONFIG_DEBUG_VM.
Ehh. If by "few people" you mean "pretty much everybody", you'd be
right, but your choice of wording would be somewhat misleading,
wouldn't you say?
Hint: here's a line from t
Unlike the temperature thresholds the temperature data is a 9-bit signed
value. This allows and additional 0.5 degrees of precision on the
reading but means we can't rely on sign-extension to handle negative
values.
Signed-off-by: Chris Packham
---
drivers/hwmon/adm9240.c | 19 +-
Jiri Olsa writes:
> The trinity syscall fuzzer triggered following WARN on powerpc:
> WARNING: CPU: 9 PID: 2998 at arch/powerpc/kernel/hw_breakpoint.c:278
> ...
> NIP [c093aedc] .hw_breakpoint_handler+0x28c/0x2b0
> LR [c093aed8] .hw_breakpoint_handler+0x288/0x2b0
> Call
On Mon, 3 Oct 2016 21:00:55 -0700 Linus Torvalds
wrote:
> In particular, I just got this
>
> kernel BUG at ./include/linux/swap.h:276
Well, it's a VM_BUG_ON and few people run with CONFIG_DEBUG_VM.
But a) something's clearly wrong and b) points taken.
As I stated before, I can't reproduce this.
Please check your toolchain. It apparently throws segmentation faults.
On Sun, 2 Oct 2016, kbuild test robot wrote:
> Hi Nicolas,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
I'm really sorry I applied that last series from Andrew just before
doing the 4.8 release, because they cause problems, and now it is in
4.8 (and that buggy crap is marked for stable too).
In particular, I just got this
kernel BUG at ./include/linux/swap.h:276
and the end result was a dead k
Hi all,
There will be no linux-next release on Friday.
Changes since 20161003:
Non-merge commits (relative to Linus' tree): 12964
9515 files changed, 516789 insertions(+), 294462 deletions(-)
I have created to
The following changes since commit c8d2bc9bc39ebea8437fd974fdbc21847bb897a3:
Linux 4.8 (2016-10-02 16:24:33 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
tags/regmap-v4.9
for you to fetch changes up to f785fb2ec0cbe73165333e
On 10/3/16, Jeffrey Merkey wrote:
> On 10/3/16, Joe Perches wrote:
>>
>> On Tue, 2016-10-04 at 13:29 +1100, Stephen Rothwell wrote:
>>> Hi Joe,
>>
>> Hi Stephen.
>>
>>> On Mon, 03 Oct 2016 18:47:04 -0700 Joe Perches wrote:
>>> >
>>> > On Mon, 2016-10-03 at 18:17 -0600, Jeffrey Merkey wrote:
>>>
Hi James,
Please see inline, thanks for the reply:
On Sat, 1 Oct 2016, James Chapman wrote:
> On 30/09/16 03:39, R. Parameswaran wrote:
> >
> >>> + /* Adjust MTU, factor overhead - underlay L3 hdr, overlay L2 hdr*/
> >>> + if (tunnel->sock->sk_family == AF_INET)
> >>> + overhead += (E
On Mon, Oct 3, 2016 at 7:47 PM, Rik van Riel wrote:
> On Mon, 2016-10-03 at 19:09 -0700, Andy Lutomirski wrote:
>
>> > Having two separate status booleans for "registers valid"
>> > and "memory valid" may make more sense.
>>
>> I have no problem with the concept of "owner_ctx", and I think it's a
On Oct 3, 2016 7:11 PM, "Rik van Riel" wrote:
>
> On Mon, 2016-10-03 at 14:36 -0700, Andy Lutomirski wrote:
> >
> > Anything else that tries to read task xstate from memory, i.e. MPX
> > and
> > PKRU. (Although if we switch to eager-switched PKRU, then PKRU stops
> > mattering for this purpose.)
On 10/3/16, Joe Perches wrote:
>
> On Tue, 2016-10-04 at 13:29 +1100, Stephen Rothwell wrote:
>> Hi Joe,
>
> Hi Stephen.
>
>> On Mon, 03 Oct 2016 18:47:04 -0700 Joe Perches wrote:
>> >
>> > On Mon, 2016-10-03 at 18:17 -0600, Jeffrey Merkey wrote:
>> > > The following changes since commit
>> > > c
On Mon, 2016-10-03 at 19:09 -0700, Andy Lutomirski wrote:
> > Having two separate status booleans for "registers valid"
> > and "memory valid" may make more sense.
>
> I have no problem with the concept of "owner_ctx", and I think it's a
> perfectly reasonable data structure. My problem with it
From: Andi Kleen
Implement the code to match CPU types to mapfile types for x86 based on
CPUID. This extends an existing similar function, but changes it to use
the x86 mapfile cpu description. This allows to resolve event lists
generated by jevents.
Signed-off-by: Andi Kleen
Signed-off-by: Su
On Sun, Oct 02, 2016 at 10:58:15PM +0200, Krzysztof Kozlowski wrote:
> Most of Maxim and Samsung PMIC/MUIC regulator drivers can be compile
> tested to increase build coverage.
All these drivers already just depend on the MFDs which don't have any
weird architecture dependencies - the main goal wi
On Tue, 2016-10-04 at 13:29 +1100, Stephen Rothwell wrote:
> Hi Joe,
Hi Stephen.
> On Mon, 03 Oct 2016 18:47:04 -0700 Joe Perches wrote:
> >
> > On Mon, 2016-10-03 at 18:17 -0600, Jeffrey Merkey wrote:
> > > The following changes since commit
> > > c8d2bc9bc39ebea8437fd974fdbc21847bb897a3:
>
From: Andi Kleen
Add support to group the output of perf list by the Topic field in the
JSON file.
Example output:
% perf list
...
Cache:
l1d.replacement
[L1D data line replacements]
l1d_pend_miss.pending
[L1D miss oustandings duration in cycles]
l1d_pend_miss.pending_cycles
From: Sukadev Bhattiprolu
At run time (when 'perf' is starting up), locate the specific table of
PMU events that corresponds to the current CPU. Using that table, create
aliases for the each of the PMU events in the CPU. The use these aliases
to parse the user specified perf event.
In short this
From: Andi Kleen
To work with existing mapfiles, assume that the first line in
'mapfile.csv' is a header line and skip over it.
Signed-off-by: Sukadev Bhattiprolu
Acked-by: Ingo Molnar
Acked-by: Jiri Olsa
Cc: Madhavan Srinivasan
Cc: Peter Zijlstra
Link:
http://lkml.kernel.org/r/1473978296-
From: Sukadev Bhattiprolu
Implement code that returns the generic CPU ID string for Powerpc. This
will be used to identify the specific table of PMU events to
parse/compare user specified events against.
Signed-off-by: Sukadev Bhattiprolu
Acked-by: Ingo Molnar
Acked-by: Jiri Olsa
Cc: Madhava
From: Andi Kleen
Add a PERF_CPUID variable to override the CPUID of the current CPU
(within the current architecture). This is useful for testing, so that
all event lists can be tested on a single system.
Signed-off-by: Andi Kleen
Signed-off-by: Sukadev Bhattiprolu
Acked-by: Ingo Molnar
Acked
From: Andi Kleen
The JSON event lists use a different encoding for fixed counters than
perf for instructions and cycles (ref-cycles is ok)
This lead to some common events like inst_retired.any or
cpu_clk_unhalted.thread not counting, when specified with their JSON
name.
Special case these event
From: Andi Kleen
This is a modified version of an earlier patch by Andi Kleen.
We expect architectures to create JSON files describing the performance
monitoring (PMU) events that each CPU model/family of the architecture
supports.
Following is an example of the JSON file entry for an x86 event
From: Andi Kleen
Add support to print alias descriptions in perf list, which are taken
from the generated event files.
The sorting code is changed to put the events with descriptions at the
end. The descriptions are printed as possibly multiple word wrapped
lines.
Example output:
% perf list
.
From: Andi Kleen
Make alias matching the events parser case-insensitive. This is useful
with the JSON events. perf uses lower case events, but the CPU manuals
generally use upper case event names. The JSON files use lower case by
default too. But if we search case insensitively then users can
cut
From: Sukadev Bhattiprolu
This avoids the JSON PMU events parser having to know whether its
aliases are for perf stat or perf record.
Signed-off-by: Andi Kleen
Signed-off-by: Sukadev Bhattiprolu
Acked-by: Ingo Molnar
Cc: Madhavan Srinivasan
Cc: Peter Zijlstra
Cc: linuxppc-...@lists.ozlabs.o
From: Sukadev Bhattiprolu
Previously we were dropping the useful longer descriptions that some
events have in the event list completely. This patch makes them appear with
perf list.
Old perf list:
baclears:
baclears.all
[Counts the number of baclears]
vs new:
perf list -v:
...
baclea
From: Andi Kleen
Automatically adapt the now wider and word wrapped perf list output to
wider terminals. This requires querying the terminal before the auto
pager takes over, and exporting this information from the pager
subsystem.
Signed-off-by: Andi Kleen
Signed-off-by: Sukadev Bhattiprolu
A
From: Jiri Olsa
It is used in the build process, so stop suppressing its build in tools
cross builds.
Signed-off-by: Jiri Olsa
Tested-by: Arnaldo Carvalho de Melo
Cc: Andi Kleen
Cc: Madhavan Srinivasan
Cc: Peter Zijlstra
Cc: Sukadev Bhattiprolu
Cc: linuxppc-...@lists.ozlabs.org
Link: http:
On Mon, Oct 3, 2016 at 6:21 PM, Maxime Ripard
wrote:
> Now that we can handle the generic pinctrl bindings, convert our DT to it.
>
> Signed-off-by: Maxime Ripard
Same comment as the last 2 patches.
ChenYu
From: Sukadev Bhattiprolu
Signed-off-by: Sukadev Bhattiprolu
Acked-by: Ingo Molnar
Acked-by: Jiri Olsa
Cc: Madhavan Srinivasan
Cc: Peter Zijlstra
Cc: linuxppc-...@lists.ozlabs.org
Link:
http://lkml.kernel.org/r/1473978296-20712-16-git-send-email-suka...@linux.vnet.ibm.com
Signed-off-by: Arn
into perf/core
(2016-09-29 19:09:58 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-20161003
for you to fetch changes up to b42c7369e3f451e22c2b0be5d193955498d37546:
perf pmu-events: Add Skylake frontend M
From: Colin Ian King
Static anaylsis with cppcheck[1] detected an incorrect comparison:
[tools/perf/util/probe-event.c:216]: (warning) Char literal compared
with pointer 'ptr2'. Did you intend to dereference it?
Dereference ptr2 for the comparison to fix this.
1: https://sourceforge.net/p/cppch
From: Arnaldo Carvalho de Melo
Experimenting a bit using cppcheck[1], a static checker brought to my
attention by Colin, reducing the scope of some variables, reducing the
line of source code lines in the process:
$ cppcheck --enable=style tools/perf/util/thread.c
Checking tools/perf/util/th
From: Andi Kleen
Add a --no-desc flag to 'perf list' to not print the event descriptions
that were earlier added for JSON events. This may be useful to get a
less crowded listing.
It's still default to print descriptions as that is the more useful
default for most users.
Signed-off-by: Andi Kle
From: Andi Kleen
I need a JSON parser. This adds the simplest JSON parser I could find --
Serge Zaitsev's jsmn `jasmine' -- to the perf library. I merely
converted it to (mostly) Linux style and added support for non 0
terminated input.
The parser is quite straight forward and does not copy any
From: Andi Kleen
Add support for the "frontend" extra MSR on Skylake in the JSON
conversion.
Signed-off-by: Andi Kleen
Acked-by: Ingo Molnar
Cc: Madhavan Srinivasan
Cc: Peter Zijlstra
Cc: linuxppc-...@lists.ozlabs.org
Link:
http://lkml.kernel.org/r/1473978296-20712-19-git-send-email-suka...
From: Jiri Olsa
In some cases, like for fixdep and shortly for jevents, we need to build a tool
to run on the host that will be used in building a tool, such as perf, that is
being cross compiled, so do like the kernel and provide HOSTCC, HOSTLD and
HOSTAR
to do that.
Signed-off-by: Jiri Olsa
From: Sukadev Bhattiprolu
Implement support in jevents to parse long descriptions for events that
may have them in the JSON files. A follow on patch will make this long
description available to user through the 'perf list' command.
Signed-off-by: Andi Kleen
Signed-off-by: Sukadev Bhattiprolu
A
On Mon, Oct 3, 2016 at 6:21 PM, Maxime Ripard
wrote:
> The allwinner,pull property set to NO_PULL was really considered our
> default (and wasn't even changing the default value in the code).
>
> Remove these properties to make it obvious that we do not set anything in
> such a case.
>
> Signed-of
On Mon, Oct 3, 2016 at 6:21 PM, Maxime Ripard
wrote:
> The allwinner,drive property set to 10mA was really considered as our
> default. Remove all those properties entirely to make that obvious.
>
> Signed-off-by: Maxime Ripard
Did you use sed or some other scripting tool to do this patch?
Inclu
On Mon, Oct 3, 2016 at 6:21 PM, Maxime Ripard
wrote:
> The generic pin configuration and multiplexing should be preferred now,
> even though we still support the old one.
>
> Signed-off-by: Maxime Ripard
> ---
> Documentation/devicetree/bindings/pinctrl/allwinner,sunxi-pinctrl.txt | 5
> +
>
On Mon, Oct 3, 2016 at 6:21 PM, Maxime Ripard
wrote:
> Our bindings are mostly irrelevant now that we have generic pinctrl
> bindings that cover exactly the same uses cases.
>
> Add support for the new ones, and obviously keep our old binding support in
> order to keep the ABI stable.
>
> Signed-o
Hi Joe,
On Mon, 03 Oct 2016 18:47:04 -0700 Joe Perches wrote:
>
> On Mon, 2016-10-03 at 18:17 -0600, Jeffrey Merkey wrote:
> > The following changes since commit c8d2bc9bc39ebea8437fd974fdbc21847bb897a3:
> >
> > Linux 4.8 (2016-10-02 16:24:33 -0700)
> >
> > are available in the git repository
On Mon, Oct 3, 2016 at 6:21 PM, Maxime Ripard
wrote:
> Even though the our binding had the assumption that the allwinner,pull and
> allwinner,drive properties were optional, the code never took that into
> account.
>
> Fix that.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/pinctrl/sunxi/pinc
On Mon, 3 Oct 2016 11:34:31 +0100
Colin King wrote:
> From: Colin Ian King
>
> Static anaylsis with cppcheck detected an incorrect comparison:
> [tools/perf/util/probe-event.c:216]: (warning) Char literal compared with
> pointer 'ptr2'. Did you intend to dereference it?
>
> Dereference ptr2 f
On Mon, Oct 3, 2016 at 6:21 PM, Maxime Ripard
wrote:
> So far, putting NO_PULL in allwinner,pull was ignored, behaving like if
> that property was not there at all.
>
> Obviously, this is not the right thing to do, and in that case, we really
> need to just disable the bias.
>
> Signed-off-by: Max
On Mon, 2016-10-03 at 14:36 -0700, Andy Lutomirski wrote:
>
> Anything else that tries to read task xstate from memory, i.e. MPX
> and
> PKRU. (Although if we switch to eager-switched PKRU, then PKRU stops
> mattering for this purpose.)
>
> Actually, I don't see any way your patches can be compa
On Mon, Oct 3, 2016 at 6:29 PM, Rik van Riel wrote:
> On Mon, 2016-10-03 at 14:36 -0700, Andy Lutomirski wrote:
>> On Mon, Oct 3, 2016 at 2:21 PM, Rik van Riel wrote:
>> >
>> > >
>> > > One of my objections to the current code structure is that I find
>> > > it
>> > > quite hard to keep track of
On Mon, Oct 3, 2016 at 6:21 PM, Maxime Ripard
wrote:
> Since we have some bindings header for our hardcoded flags, let's use them
> when we can.
"Use macros from bindings header file for DT parsing"
would make the subject clearer.
Otherwise,
Acked-by: Chen-Yu Tsai
>
> Signed-off-by: Maxime R
From: Christophe JAILLET
Date: Sun, 2 Oct 2016 09:04:16 +0200
> A call to 'ida_simple_remove()' is missing in the error handling path.
>
> This as been spotted with the following coccinelle script which tries to
> detect missing 'ida_simple_remove()' call in error handling paths.
...
> Signed-
Hi everyone,
This series fixes up generic pinconf support for the sunxi pinctrl driver
library. The driver was doing some bits wrong, like a) storing the pinconf
config value in its struct, and not actually reading the hardware to get
the current config, and b) not using the right arguments for th
The sunxi pinctrl driver only caches whatever pinconf setting was last
set on a given pingroup. This is not particularly helpful, nor is it
correct.
Fix this by actually reading the hardware registers and returning
the correct results or error codes. Also filter out unsupported
pinconf settings. S
From: Baoyou Xie
Date: Sat, 1 Oct 2016 16:15:26 +0800
> We get a few warnings when building kernel with W=1:
...
> In fact, these functions are only used in the file in which they are
> declared and don't need a declaration, but can be made static.
> So this patch marks these functions with 'st
The sunxi_pconf_reg helper introduced in the last patch gives us the
chance to rework sunxi_pconf_group_set to have it match the structure
of sunxi_pconf_(group_)get and make it easier to understand.
For each config to set, it:
1. checks if the parameter is supported.
2. checks if the arg
From: Miklos Szeredi
Date: Thu, 29 Sep 2016 14:09:14 +0200
> @@ -1550,6 +1550,17 @@ static int unix_attach_fds(struct scm_cookie *scm,
> struct sk_buff *skb)
> return max_level;
> }
>
> +static void unix_peek_fds(struct scm_cookie *scm, struct sk_buff *skb)
> +{
> + scm->fp = scm_fp
According to pinconf-generic.h, the argument for
PIN_CONFIG_BIAS_PULL_{DOWN,UP} is non-zero if the bias is enabled
with a pull up/down resistor, zero if it is directly connected
to VDD or ground.
Since Allwinner hardware uses a weak pull resistor internally,
the argument should be 1.
Signed-off-b
1 - 100 of 535 matches
Mail list logo