On Wed, Apr 16, 2014 at 5:01 PM, Vinod Koul vinod.k...@intel.com wrote:
On Tue, Apr 01, 2014 at 05:57:04PM +0530, Srikanth Thokala wrote:
This is the driver for the AXI Direct Memory Access (AXI DMA)
core, which is a soft Xilinx IP core that provides high-
bandwidth direct memory access
Add tunable RX interrupt trigger I/F of FIFO buffers.
Serial devices are used as not only message communication devices but control
or sending communication devices. For the latter uses, normally small data
will be exchanged, so user applications want to receive data unit as soon as
possible for
On Wed, Apr 16, 2014 at 04:44:09PM +0200, Linus Walleij wrote:
This cleans up the STMPE driver a bit:
- Remove all static GPIO and IRQ number assignments as all platforms
with this hardware use device tree now.
- Add optional regulators.
- Add proper device tree probe path using
Hi, Jaso
Would you like to code review these 2 patches?
Thanks a lot.
Zhu Yanjun
On 04/17/2014 11:35 AM, zhuyj wrote:
Hi, all
In kernel 2.6.x, linux depends on nic vlan hardware acceleration to
insert/extract
vlan tag. In this scene, in kernel 2.6.x
_
Ok. I tried:
3.15-rc1 (16. April)
failed.
Bisecting turned out:
last working: 3.12.17
first failing: 3.13
Am 16.04.2014 16:22, schrieb Borislav Petkov:
On Wed, Apr 02, 2014 at 04:14:31PM +0200, Matthias Graf wrote:
I now tried booting with a different graphics card (on the same
machine),
Since max_nid value was minus three in previous commit:
'b63da15e8b475245026bdf2096853683f189706b', Our last three nids could not be
used ever, but 0/node nid/meta nid is still occupied.
And also our ra_meta_pages() could not readahead the last block of NAT.
Let's fix the wrong calculation of this
This add Freescale Periodic Interrupt Timer (PIT-RTI) devicetree
Documentation, The PIT-RTI binding has already been used on Vybrid,
so this add a binding document for it.
Signed-off-by: Xiubo Li li.xi...@freescale.com
Cc: Shawn Guo shawn@linaro.org
Cc: Jingchang Lu b35...@freescale.com
---
You are right !! It is not a right solution .
It is a speculation where the panic was.
[38261.652100] Call trace:
[38261.654616] [ffc000aa6fe0] mm_update_next_owner+0x190/0x238
[38261.660766] [ffc000aa728c] do_exit+0x204/0x924
[38261.665790] [ffc000aa7a1c] do_group_exit+0x40/0xcc
This patch tries to solve the device hot remove locking issues in a
different way from commit 5e33bc41, as kernfs already has a mechanism
to break active protection.
The problem here is the order of s_active, and series of hotplug related
lock.
This patch takes s_active out of the lock
On 04/17/2014 05:33 AM, Jisheng Zhang wrote:
On Wed, 16 Apr 2014 05:40:10 -0700
Antoine Ténart antoine.ten...@free-electrons.com wrote:
Add the SDHCI nodes for the Marvell Berlin BG2Q, using the berlin-sdhci
driver.
[...]
+sdhci0: sdhci@ab {
+compatible =
s/regmap/Regmap
It's consistently written regmap in all the documentation and so on :)
Furry muff; but the comments still stand for the acronyms.
addmap{0,1} doesn't quite sit right with me.
REVISIT: Ah, it's address-map, rather than add map. Okay, not as bad
as I first thought, but
Hi all,
Now I'm developing Freescale PCIe power management feature. The following is my
PCIe
suspend/resume code.
when I test system wake up from sleep(STANDBY), I got below calltrace. Looks
like e1000e
cannot transfer data, maybe watchdog has some issue. Or maybe some of the other
causes.
I
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from mm/shmem.c:61:0:
include/linux/swapops.h: In function 'is_swap_pte':
include/linux/swapops.h:57:2: error: implicit declaration of function
On 17/04/14 02:04, Linus Torvalds wrote:
On Wed, Apr 16, 2014 at 2:03 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
The drivers/video/Kconfig change in this pull request will conflict with the
fbdev reorder series, which is not yet in your tree. If that's an issue, I
can
resend this
The following changes since commit e240c1839d11152b0355442f8ac6d2d2d921be36:
raid5: get_active_stripe avoids device_lock (2014-04-09 14:42:42 +1000)
are available in the git repository at:
git://neil.brown.name/md tags/3.15-fixes
for you to fetch changes up to
Stephen Rothwell s...@canb.auug.org.au writes:
Hi Eric,
After merging the userns tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/namespace.c: In function 'new_mountpoint':
fs/namespace.c:725:9: error: implicit declaration of function 'hash'
Hi,
2014-04-17 (목), 14:27 +0800, Chao Yu:
Since max_nid value was minus three in previous commit:
'b63da15e8b475245026bdf2096853683f189706b', Our last three nids could not be
used ever, but 0/node nid/meta nid is still occupied.
And also our ra_meta_pages() could not readahead the last block
On Thu, 17 Apr 2014 10:05:02 +0800
Li Zefan lize...@huawei.com wrote:
Free cpudl-free_cpus allocated in cpudl_init().
Signed-off-by: Li Zefan lize...@huawei.com
Cc: sta...@vger.kernel.org # 3.14
---
kernel/sched/cpudeadline.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
These defconfigs contain the CONFIG_M25P80 symbol, which is now
dependent on the MTD_SPI_NOR symbol. Add CONFIG_MTD_SPI_NOR to the
relevant defconfigs.
At the same time, drop the now-nonexistent CONFIG_MTD_CHAR symbol.
Signed-off-by: Brian Norris computersforpe...@gmail.com
Cc: Steven Miao
These defconfigs contain the CONFIG_M25P80 symbol, which is now
dependent on the MTD_SPI_NOR symbol. Add CONFIG_MTD_SPI_NOR to the
relevant defconfigs.
At the same time, drop the now-nonexistent CONFIG_MTD_CHAR symbol.
Signed-off-by: Brian Norris computersforpe...@gmail.com
Cc: Benjamin
This defconfig contain the CONFIG_M25P80 symbol, which is now
dependent on the MTD_SPI_NOR symbol. Add CONFIG_MTD_SPI_NOR.
At the same time, drop the now-nonexistent CONFIG_MTD_CHAR symbol.
Signed-off-by: Brian Norris computersforpe...@gmail.com
Cc: linux...@vger.kernel.org
Cc:
These defconfigs contain the CONFIG_M25P80 symbol, which is now
dependent on the MTD_SPI_NOR symbol. Add CONFIG_MTD_SPI_NOR to the
relevant defconfigs.
At the same time, drop the now-nonexistent CONFIG_MTD_CHAR symbol.
Signed-off-by: Brian Norris computersforpe...@gmail.com
Cc: Ralf Baechle
These defconfigs contain the CONFIG_M25P80 symbol, which is now
dependent on the MTD_SPI_NOR symbol. Add CONFIG_MTD_SPI_NOR to the
relevant defconfigs.
At the same time, drop the now-nonexistent CONFIG_MTD_CHAR symbol.
Signed-off-by: Brian Norris computersforpe...@gmail.com
Cc: Russell King
Hi all,
We are introducing a new SPI-NOR library/framework for MTD, to support various
types of SPI-NOR flash controllers which require (or benefit from) intimate
knowledge of the flash interface, rather than just the relatively dumb SPI
interface. This library borrows much of the m25p80 driver
Hi all,
There will be no linux-next release until April 22 - have a nice break.
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140416:
Dropped tree: userns (complex conflicts)
The powerpc tree still had its build failure.
The sound-asoc tree lost its
poma wrote:
Sound whispers,
???
WARNING: CPU: 3 PID: 900 at lib/dma-debug.c:593
debug_dma_assert_idle+0x159/0x1d0()
snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped
cacheline [cln=0x03014000]
...
Mapped at:
[c074ec12] debug_dma_alloc_coherent+0x22/0x70
On Thu, Apr 17, 2014 at 02:18:58AM +0800, Chew Chiau Ee wrote:
From: Alan Cox a...@linux.intel.com
Not all systems enumerate the PWM devices via ACPI. They can also be exposed
via the PCI interface.
Signed-off-by: Alan Cox a...@linux.intel.com
Signed-off-by: Chew, Chiau Ee
Hi,
2014-04-16 (수), 18:11 -0700, Alexey Khoroshilov:
Hi,
But would not ability to trigger BUG_ON by mounting a crafted image
considered as an issue having security implications?
Sorry, I can't come up with you.
Could you please explain why this can be related to the security hole?
Did you
Hi,
On 04/16/2014 10:49 PM, Tejun Heo wrote:
Hello,
On Thu, Apr 10, 2014 at 01:24:28PM +0800, Kefeng Wang wrote:
From: Kefeng Wang kefeng.w...@linaro.org
The hip04 SoC of hisilicon has an AHCI compliant SATA controller,
and it is compliant with the ahci 1.3 and sata 3.0 specification.
+ ftm0: ftm@40038000 {
+ compatible = fsl,vf610-ftm-timer;
+ reg = 0x40038000 0x2000;
+ interrupts = 0 42 IRQ_TYPE_LEVEL_HIGH;
+ clock-names = ftm0, ftm1,
+
On Tue, 2014-04-15 at 23:34 -0500, Felipe Balbi wrote:
$ make drivers/usb/phy/phy-mv-u3d-usb.o
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL
When a filter is used for perf top, its hists-nr_non_filtered_entries
was not updated after applying the filter. But it needs to be updated
as new samples are captured.
Signed-off-by: Namhyung Kim namhy...@kernel.org
---
tools/perf/util/hist.c | 8 +++-
1 file changed, 7 insertions(+), 1
The nr_entries variable is increased inside the loop in the function
but it also counts when hists__filter_entries() returns NULL. Thus
the end result will have actual count + 1.
It'd become a problem especially there's no entry at all - it'd get a
segfault during referencing a NULL pointer.
Hi,
This is a small fixes for a bug in perf top I found during some tests.
It gets segfault if symbol filter found no entries - accessing NULL
pointer in that case.
The patches are also available at perf/percentage-v9 branch on my tree
for your convenience. I'm sorry for causing this bug..
The hist_browser__reset() is only called right after a filter is
applied so it needs to update browser-nr_entries properly. We cannot
use hists-nr_non_filtered_entries directly since it's possible that
such entries are also filtered out by minimum percentage.
In addition when a filter is used
On Wed, 16 Apr 2014, Greg KH wrote:
On Thu, Apr 17, 2014 at 01:00:53AM +0200, Thomas Gleixner wrote:
And cdevs is an array of struct cdev:
struct cdev {
struct kobject kobj;
Those are not real kobjects, and are never registered with the kobject
core.
I really need to go
On 16/04/2014 10:11, Michal Hocko wrote:
On Tue 15-04-14 09:38:10, Glyn Normington wrote:
On 14/04/2014 21:50, Johannes Weiner wrote:
On Mon, Apr 14, 2014 at 09:11:25AM +0100, Glyn Normington wrote:
Johannes/Michal
What are your thoughts on this matter? Do you see this as a valid
Hi,
-Original Message-
From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
Sent: Thursday, April 17, 2014 3:17 PM
To: Chao Yu
Cc: linux-f2fs-de...@lists.sourceforge.net; linux-fsde...@vger.kernel.org;
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix wrong
Hi Tomasz,
On 04/16/2014 11:28 PM, Tomasz Figa wrote:
Hi Chanwoo,
On 15.04.2014 03:59, Chanwoo Choi wrote:
This patch fix the offset of CPU boot address and don't operate smc call
of SMC_CMD_CPU1BOOT command for Exynos3250.
Signed-off-by: Chanwoo Choi cw00.c...@samsung.com
Acked-by:
Forgot to free uprobe_cpu_buffer percpu page in uprobe_buffer_disable.
Signed-off-by: zhangwei(Jovi) jovi.zhang...@huawei.com
---
kernel/trace/trace_uprobe.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
index e447336..071d3bb
* Jiri Olsa jo...@redhat.com wrote:
hi Ingo,
please consider pulling
thanks,
jirka
The following changes since commit fbdd17ec5ce2e5e4027356fcfde769b88d15702f:
Merge branch 'perf-core-for-mingo' into perf/urgent (2014-04-14 16:45:39
+0200)
are available in the git repository
The rtc-s5m driver does not support all of S2M and S5M chipsets
supported by main MFD sec-core driver. For such chipsets unsupported by
rtc-s5m, the MFD sec-core driver initialized regmap with default config.
This config in such cases wouldn't work at all.
The main MFD sec-core driver
Current kprobes in-kernel page fault handler doesn't
expect that its single-stepping can be interrupted by
an NMI handler which may cause a page fault(e.g. perf
with callback tracing).
In that case, the page-fault handled by kprobes and it
misunderstands the page-fault has been caused by the
There is no need to prohibit probing on the functions
used in preparation phase. Those are safely probed because
those are not invoked from breakpoint/fault/debug handlers,
there is no chance to cause recursive exceptions.
Following functions are now removed from the kprobes blacklist.
can_boost
Hi,
Here is the version 9 of NOKPROBE_SYMBOL series, including
bugfixes. This updates some issues pointed in Steven's review
against v8 (Thank you!)
Blacklist improvements
==
Currently, kprobes uses __kprobes annotation and internal symbol-
name based blacklist to prohibit
thunk/restore functions are also used for tracing irqoff etc.
and those are involved in kprobe's exception handling.
Prohibit probing on them to avoid kernel crash.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Reviewed-by: Steven Rostedt rost...@goodmis.org
Cc: Thomas Gleixner
Use NOKPROBE_SYMBOL macro to protect functions from
kprobes instead of __kprobes annotation in sched/core.c.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Reviewed-by: Steven Rostedt rost...@goodmis.org
Cc: Ingo Molnar mi...@redhat.com
Cc: Peter Zijlstra pet...@infradead.org
---
Allow kprobes on text_poke/hw_breakpoint because
those are not related to the critical int3-debug
recursive path of kprobes at this moment.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Reviewed-by: Steven Rostedt rost...@goodmis.org
Cc: Thomas Gleixner t...@linutronix.de
Cc:
Show blacklist entries (function names with the address
range) via /sys/kernel/debug/kprobes/blacklist.
Note that at this point the blacklist supports only
in vmlinux, not module. So the list is fixed and
not updated.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Ananth N
Use kprobe_blackpoint for blacklisting .entry.text and .kprobees.text
instead of arch_within_kprobe_blacklist. This also makes them visible
via (debugfs)/kprobes/blacklist.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc: Thomas Gleixner t...@linutronix.de
Cc: Ingo Molnar
Use NOKPROBE_SYMBOL macro to protect functions from
kprobes instead of __kprobes annotation in ftrace.
This applies nokprobe_inline annotation for some cases,
because NOKPROBE_SYMBOL() will inhibit inlining by
referring the symbol address.
Changes from v8:
- Fix a line-break style issue.
To blacklist the functions in a module (e.g. user-defined
kprobe handler and the functions invoked from it), expand
blacklist support for modules.
With this change, users can use NOKPROBE_SYMBOL() macro in
their own modules.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Cc:
Use NOKPROBE_SYMBOL macro for protecting functions
from kprobes instead of __kprobes annotation under
arch/x86.
This applies nokprobe_inline annotation for some cases,
because NOKPROBE_SYMBOL() will inhibit inlining by
referring the symbol address.
This just folds a bunch of previous
Since the kprobes itself owns a hash table to get a kprobe
data structure corresponding to the given ip address, there
is no need to test ftrace hash in ftrace side.
To achive better performance on ftrace-based kprobe,
FTRACE_OPS_FL_SELF_FILTER flag to ftrace_ops which means
that ftrace skips
Introduce kprobe cache to reduce cache misshits for
massive multiple kprobes.
For stress testing kprobes, we need to activate kprobes
as many as possible. This situation causes cache miss
hit storm on kprobe hash-list. kprobe hashlist is already
enlarged to 4k entries and this is still small for
Currently, since the kprobes expects to be used with less than
100 probe points, its hash table just has 64 entries. This is
too little to handle several thousands of probes.
Enlarge the size of kprobe_table to 512 entries which just
consumes 4KB (on 64bit arch) for better scalability.
Note that
Since the int3 itself disables the local_irq and kprobes
keeps it disabled while the single step has done, the
kernel preemption never happen while processing a kprobe.
This means that we don't need to disable/enable preemption.
Also, this changes kprobe_int3_handler to use goto-out style.
Hi Jiri,
On Wed, 16 Apr 2014 15:34:32 +0200, Jiri Olsa wrote:
On Wed, Apr 16, 2014 at 09:30:43AM +0900, Namhyung Kim wrote:
I think that after creating the workload, all error paths
need to release(wait) the child if there's any
Right. I'll resend v2.
Thanks,
Namhyung
--
To unsubscribe from
Use NOKPROBE_SYMBOL() to protect handlers from kprobes
in sample modules.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Ananth N Mavinakayanahalli ana...@in.ibm.com
---
samples/kprobes/jprobe_example.c|1 +
samples/kprobes/kprobe_example.c|3 +++
On Thu, Apr 17, 2014 at 07:49:31AM +, li.xi...@freescale.com wrote:
+ ftm0: ftm@40038000 {
+ compatible = fsl,vf610-ftm-timer;
+ reg = 0x40038000 0x2000;
+ interrupts = 0 42 IRQ_TYPE_LEVEL_HIGH;
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Intel BayTrail PCI mode LPSS devices inclusive of SPI do not rely
on common clock framework. Thus, this patch allows the PCI mode
SPI host to pass the supported clock rate info to the core layer
which eventually used for speed calculation.
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Hi,
BayTrail LPSS subsystem consists of one SPI host which can be PCI
enumerated. PXA2XX PCI layer used to support only CE4100's SPI. Thus,
we convert it into a generic PCI layer to add support for LPSS
SPI as well.
Since PCI mode LPSS SPI does not
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Similar to CE4100, BayTrail LPSS SPI can be PCI enumerated
as well. Thus, the functions are renamed from ce4100_xxx
to pxa2xx_spi_pci_xxx to clarify that this is a generic
PCI glue layer. Also, added required infrastructure to
support SPI hosts with
Use NOKPROBE_SYMBOL macro to protect functions from
kprobes instead of __kprobes annotation in notifier.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Reviewed-by: Steven Rostedt rost...@goodmis.org
Cc: Josh Triplett j...@joshtriplett.org
Cc: Paul E. McKenney
The device type was stored in sec_pmic state container twice:
- unsigned long type
- int device_type
Can you explain that one of them is in the main container and the
other is stored in pdata, which in turn is located in the main
container, as this implies that both of them are located in
Use NOKPROBE_SYMBOL macro to protect functions from
kprobes instead of __kprobes annotation.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Reviewed-by: Steven Rostedt rost...@goodmis.org
Cc: Ananth N Mavinakayanahalli ana...@in.ibm.com
Cc: David S. Miller da...@davemloft.net
---
Hi Sakari,
Thanks for the review.
On 04/16/2014 08:21 PM, Sakari Ailus wrote:
Hi Jacek,
Thanks for the update!
[...]
+static inline enum led_brightness v4l2_flash_intensity_to_led_brightness(
+ struct led_ctrl *config,
+
On 04/17/2014 04:25 PM, Jet Chen wrote:
Hi Alex
We noticed the below kernel BUG on
Thank a lot Jet!
https://github.com/alexshi/power-scheduling.git noload
commit 6b74b2031e15ae58470fd8dde7438df35e358c62
Author: Alex Shi alex@linaro.org
AuthorDate: Fri Apr 4 17:49:30 2014
There is no need to prohibit probing on the functions
used for preparation and uprobe only fetch functions.
Those are safely probed because those are not invoked
from kprobe's breakpoint/fault/debug handlers. So there
is no chance to cause recursive exceptions.
Following functions are now removed
There is no need to prohibit probing on the functions
used for preparation, registeration, optimization,
controll etc. Those are safely probed because those are
not invoked from breakpoint/fault/debug handlers,
there is no chance to cause recursive exceptions.
Following functions are now removed
Prohibit probing on native_set_debugreg and native_load_idt.
Since the kprobes uses do_debug for single stepping,
functions called from do_debug before notify_die must not
be probed.
And also native_load_idt is called from paranoid_exit when
returning int3, this also must not be probed.
Move exception_enter() call after kprobes handler
is done. Since the exception_enter() involves
many other functions (like printk), it can cause
recursive int3/break loop when kprobes probe such
functions.
Signed-off-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com
Reviewed-by: Steven Rostedt
Prohibit probing on debug_stack_reset and debug_stack_set_zero.
Since the both functions are called from TRACE_IRQS_ON/OFF_DEBUG
macros which run in int3 ist entry, probing it may cause a soft
lockup.
This happens when the kernel built with CONFIG_DYNAMIC_FTRACE=y
and CONFIG_TRACE_IRQFLAGS=y.
Introduce NOKPROBE_SYMBOL() macro which builds a kprobe
blacklist in build time. The usage of this macro is similar
to the EXPORT_SYMBOL, put the NOKPROBE_SYMBOL(function); just
after the function definition.
Since this macro will inhibit inlining of static/inline
functions, this patch also
To avoid a kernel crash by probing on lockdep code, call
kprobe_int3_handler() and kprobe_debug_handler()(which was
formerly called post_kprobe_handler()) directly from
do_int3 and do_debug.
Currently kprobes uses notify_die() to hook the int3/debug
exceptoins. Since there is a locking code in
Since the NMI handlers(e.g. perf) can interrupt in the
single stepping (or preparing the single stepping, do_debug
etc.), we should consider a kprobe is hit in the NMI
handler. Even in that case, the kprobe is allowed to be
reentered as same as the kprobes hit in kprobe handlers
(KPROBE_HIT_ACTIVE
.entry.text is a code area which is used for interrupt/syscall
entries, which includes many sensitive code.
Thus, it is better to prohibit probing on all of such code
instead of a part of that.
Since some symbols are already registered on kprobe blacklist,
this also removes them from the
Update the documentation for sec_pmic state container structure to
reflect current code.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
include/linux/mfd/samsung/core.h | 29 +
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git
Subject: Re: [RFC][PATCH 1/3] ARM: dts: vf610: Add Freescale FlexTimer Module
timer node.
On Thu, Apr 17, 2014 at 07:49:31AM +, li.xi...@freescale.com wrote:
+ ftm0: ftm@40038000 {
+ compatible = fsl,vf610-ftm-timer;
+
* Masami Hiramatsu masami.hiramatsu...@hitachi.com wrote:
Masami Hiramatsu (26):
[BUGFIX]kprobes/x86: Fix page-fault handling logic
kprobes/x86: Allow to handle reentered kprobe on singlestepping
kprobes: Prohibit probing on .entry.text code
kprobes: Introduce
The newly integrated dwapb gpio driver handles the Berlin SoCs GPIOs.
Add this driver to the multi_v7_defconfig.
Signed-off-by: Antoine Ténart antoine.ten...@free-electrons.com
---
This patch applies on top of Alexandre's one selecting
CONFIG_MACH_BERLIN_BG2Q:
Al Viro v...@zeniv.linux.org.uk writes:
On Thu, Apr 17, 2014 at 03:06:57PM +1000, Stephen Rothwell wrote:
Hi Eric,
Today's linux-next merge of the userns tree got a conflict in
fs/namespace.c between various commits from Linus' tree and various
commits from the userns tree.
I fixed it
The Berlin BG2CD has 32 GPIOs in SoC power domain and 16 in the SM one.
Signed-off-by: Antoine Ténart antoine.ten...@free-electrons.com
---
arch/arm/boot/dts/berlin2cd.dtsi | 102 +++
1 file changed, 102 insertions(+)
diff --git
After adding support for the Berlin BG2Q GPIOs, this series uses the
same GPIO dwapb driver to support the Berlin BG2 and BG2CD GPIOs.
Applies on top of Sebastian's for-next branch[1].
[1] https://github.com/shesselba/linux-berlin/commits/berlin/for-next
Antoine Ténart (2):
ARM: dts: berlin:
The Berlin BG2 has 32 GPIOs in SoC power domain and 16 in the SM one.
Only the first 8 SM GPIOs have interrupt support.
Signed-off-by: Antoine Ténart antoine.ten...@free-electrons.com
---
arch/arm/boot/dts/berlin2.dtsi | 105 +
1 file changed, 105
On 04/11/2014 05:25 PM, Vladimir Nikulichev wrote:
perf tools: Adjust symbols in VDSO
pert-report doesn't resolve function names in VDSO:
$ perf report --stdio -g flat,0.0,15,callee --sort pid
...
8.76%
0x7fff6b1fe861
__gettimeofday
Hi,
This patchset adds support for the DMA controller found in the
Allwinner A31 and A23 SoCs.
This has been tested using the newly introduced SPI driver on an A31
EVK. Support for DMA-driven SPI transfers will be the subject of
another patch serie.
Since this serie has been sent for the first
The Allwinner A31 has a 16 channels DMA controller that it shares with the
newer A23. Although sharing some similarities with the DMA controller of the
older Allwinner SoCs, it's significantly different, I don't expect it to be
possible to share the driver for these two.
The A31 Controller is
Now that we have a DMA driver, we can add the DMA bindings in the DTSI for the
controller and the devices supported that can use DMA.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/boot/dts/sun6i-a31.dtsi | 29 +
1 file changed, 29
Right now, AHB is an indirect child clock of the CPU clock. If that happens to
change, since the CPU clock has no other consumers declared in Linux, it would
be shut down, which is not really a good idea.
Prevent this by forcing it enabled.
Signed-off-by: Maxime Ripard
The DT are supposed to be ordered by physical address. Move the NMI node where
it belongs.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/boot/dts/sun6i-a31.dtsi | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
Callers of clk_put must disable the clock first. This also means that as long
as the clock is enabled the driver should hold a reference to that clock.
Hence, the call to clk_put here are bogus and should be removed.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
Acked-by: Mike
Prevent the SDRAM controller from being gated by force-enabling it in the
machine code.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/mach-sunxi/sun6i.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/mach-sunxi/sun6i.c b/arch/arm/mach-sunxi/sun6i.c
This will allow to add per-SoC hooks more easily.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/mach-sunxi/Makefile | 6 +-
arch/arm/mach-sunxi/restart.c | 104 +++
arch/arm/mach-sunxi/restart.h | 20 ++
arch/arm/mach-sunxi/sun4i.c |
Since we start to have a lot of clocks to protect, some of them in a few boards
only, it becomes difficult to handle the clock protection without having to add
per machine exceptions.
Move these where they belong, in the machine definition code.
Signed-off-by: Maxime Ripard
(2014/04/17 17:37), Ingo Molnar wrote:
* Masami Hiramatsu masami.hiramatsu...@hitachi.com wrote:
Masami Hiramatsu (26):
[BUGFIX]kprobes/x86: Fix page-fault handling logic
kprobes/x86: Allow to handle reentered kprobe on singlestepping
kprobes: Prohibit probing on
It is more idiomatic to process things relating to the regulator in its
driver. This patch moves both processing of device tree relating to the
regulator and checking if the regulator is external from arizona-core
into the regulator driver.
Signed-off-by: Charles Keepax
sparse complains as follows:
drivers/staging/vt6656/aes_ccmp.c:221:6: warning: symbol 'AESbGenCCMP'
was not declared. Should it be static?
In order to suppress the warning, we include the aes_ccmp.h header file
which contains an appropriate extern declaration.
Signed-off-by: huanqi chi
Using sp-role.level instead of @level since @level is not got from the
page table hierarchy
There is no issue in current code since the fast page fault currently only
fixes the fault caused by dirty-log that is always on the last level
(level = 1)
This patch makes the code more readable and
Now we can flush all the TLBs out of the mmu lock without TLB corruption when
write-proect the sptes, it is because:
- we have marked large sptes readonly instead of dropping them that means we
just change the spte from writable to readonly so that we only need to care
the case of changing
1 - 100 of 1430 matches
Mail list logo
