Hi,
I'm using TP-LINK PCIe NIC card on my PCIe Root Complex.
Probing looks fine by setting:
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
PCI: enabling device :00:00.0 (0140 -> 0143)
PCI: enabling device :01:00.0 (0140 -> 0143)
r8169 :01:00.0 eth0: RTL8168e/8111e at 0xf006a000,
c0:4
Guys, I don't really see why you get so worked up about this. There is
lots and lots of precedent of Linux allowing non-Posix (or non-standard
in general) arguments to system calls. Even ones that don't have
symbolic names defined for them (the magic 3 open argument for device
files).
Given that
On 04/03/2014 04:49 PM, Nishanth Menon wrote:
> On 04/03/2014 05:52 AM, Peter Ujfalusi wrote:
> [...]
>> .../devicetree/bindings/clock/clk-palmas.txt | 35 +++
>> drivers/clk/Kconfig| 7 +
>> drivers/clk/Makefile | 1 +
>> dr
In switch_hrtimer_base() we have created a local variable basenum which is set
to base->index initially. This variable is used at only one place. It makes code
more readable if we remove this variable and use base->index directly.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 3 +--
1 file
Currently we have a 'tab' here instead of 'space' after 'comma'. Replace it with
space.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index d55092c..a1120a0 100644
--- a/kernel/hrtimer.c
++
The comment was probably added when there were only two clock bases available
for hrtimers, now there are four.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index a1120a0..3c05140 100644
High Resolution feature can be enabled/disabled from bootargs if we have a
string 'highres=' followed by 'on' or 'off'. The default value of this variable
is '1'. When 'on' is passed as bootarg, we don't have to overwrite this
variable by '1'.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c |
As majority of this code came from existing kernel/timer.c, few comments still
had name of routines from timers framework. Fix them.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index 3c05
'for' loop in migrate_hrtimers() has only one line in its body and so doesn't
require {} as per coding guidelines. Remove it.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index c87e896..
retrigger_next_event() is defined within #ifdef CONFIG_HIGH_RES_TIMERS as we
already have pointer to base available. So it makes more sense to simple use
base->hres_active instead of doing this by calling hrtimer_hres_active():
__this_cpu_read(hrtimer_bases.hres_active)
Also the same reas
Breaking format fragments into multiple lines hits readability of code. Even if
it goes over 80 column width, its better to keep them together.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtim
Linux coding guidelines says:
The preferred form for passing a size of a struct is the following:
p = kmalloc(sizeof(*p), ...);
But __hrtimer_init() wasn't following that. Fix it.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
In hrtimers_init() we need to call init_hrtimers_cpu() for boot cpu. For this,
currently we are emulating a call to hotplug notifier. Probably this was done
initially to get rid of code redundancy. But this sequence always called a
single routine, i.e. init_hrtimers_cpu(), and so calling that routi
hrtimer_set_expires_range() and hrtimer_set_expires_range_ns() have almost same
implementations and so we can actually call hrtimer_set_expires_range() from
hrtimer_set_expires_range_ns() internally instead of duplicating code.
Signed-off-by: Viresh Kumar
---
include/linux/hrtimer.h | 3 +--
1 f
unlock_hrtimer_base() was handled specially at a separate place earlier as
lock_hrtimer_base() had separate definitions for SMP and non-SMP cases, but
unlock_hrtimer_base() had only a single definition. And so probably it was kept
at the end of this #ifdef/endif CONFIG_SMP. But this #ifdef ends rig
* Steven Rostedt wrote:
> On Thu, 03 Apr 2014 07:10:47 -0700
> "H. Peter Anvin" wrote:
>
> > Could you tell which of these modes work on your box:
Basically my thinking is that the patch should be reverted, if my fix
below does not work.
I distilled your test results into:
reboot=t
Complete bottom part of switch_hrtimer_base() is part of a 'if' block and so all
code present in that block has extra indentation level before it. Rewrite it to
remove this extra indentation level.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 51 ++--
This patch reorders code within __remove_hrtimer() routine to achieve this:
- no need to check if timer is the next timer to expire when high resolution
mode isn't configured in kernel. So, move this check within the #ifdef/endif
block.
- Validate 'reprogram' and hrtimer_hres_active() first as
Following code is repeated at many places:
ktime_sub(hrtimer_get_expires(timer), base->offset);
and so it makes sense to create a separate inlined routine for this.
Signed-off-by: Viresh Kumar
---
include/linux/hrtimer.h | 6 ++
kernel/hrtimer.c| 11 +--
2 files cha
__remove_hrtimer() is called from three locations: remove_hrtimer(),
__run_hrtimer() and migrate_hrtimer_list(). And all these guarantee that timer
was queued earlier. And so there is no need to check if the timer is queued or
not in __remove_hrtimer().
Signed-off-by: Viresh Kumar
---
kernel/hrt
This code was added long back by following commit:
commit 06027bdd278a32a84b273e41db68a5db8ffd2bb6
Author: Ingo Molnar
Date: Tue Feb 14 13:53:15 2006 -0800
[PATCH] hrtimer: round up relative start time on low-res arches
Don't know if it was a mistake or was
There are many places where we need to iterate over all the currently active
clock bases for a particular cpu_base. Create for_each_active_base() to simplify
code at those places.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/
There are various places where we are currently running a loop of
HRTIMER_MAX_CLOCK_BASES iterations. We just run 'continue;' if there are no
timers added to a clock base. Instead we can use the new for_each_active_base()
routine to iterate over only the bases which are currently active.
Signed-of
We are taking cpu_base->lock for every clock-base in hrtimer_run_queues() and
there is nothing in there which prevents us to take this lock only once. Modify
code to take lock only once for a cpu_base.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 4 ++--
1 file changed, 2 insertions(+), 2
clock 'base' can be obtained easily by doing timer->base and remove_timer()/
__remove_timer() never gets anything else than timer->base as its parameter.
Which means, these routines doesn't require this parameter. Remove it.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 26 +++--
clock 'base' can be obtained easily by doing timer->base and
switch_hrtimer_base() never gets anything else than timer->base as its
parameter. And so this routines doesn't require this parameter. Remove it.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 9 -
1 file changed, 4 inserti
enqueue_hrtimer() routine is called from three places and only one of them
effectively uses its return value. Also, by its name enqueue_hrtimer() isn't
supposed to return "if the queued timer is the leftmost". So it makes more sense
to separate this routine into two parts, first one enqueues a time
switch_hrtimer_base() always sets timer->base to the right base and so the
caller can obtain it easily. So, this routine doesn't need to return anything.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/kernel/h
clock 'base' can be obtained easily by doing timer->base and enqueue_hrtimer()
never gets anything else than timer->base as its parameter. And so this routines
doesn't require this parameter. Remove it.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 14 +++---
1 file changed, 7 inser
In init_timers() we need to call init_timers_cpu() for boot cpu. For this,
currently we are emulating a call to hotplug notifier. Probably this was done
initially to get rid of code redundancy. But this sequence always called a
single routine, i.e. init_timers_cpu(), and so calling that routine dir
The topology_##name() macro does not use its argument when CONFIG_SMP is not
set, as it ultimately calls the cpu_data() macro.
So we avoid maintaining a possibly unused `cpu' variable, to avoid the
following compilation warning:
drivers/base/topology.c: In function ‘show_physical_package_id’:
Currently we are returning notifier_from_errno() from CPU_UP_PREPARE notifier
when we detect there is an error while calling init_timers_cpu().
notifier_from_errno() already has enough checks within to do something similar.
And so we can call it directly without checking if there was an error or no
clock 'base' can be obtained easily by doing timer->base and hrtimer_reprogram()
& hrtimer_enqueue_reprogram() never gets anything else than timer->base as its
parameter. And so these routines doesn't require this parameter. Remove it.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 15 ++
lock_hrtimer_base() always returns after taking lock and so timer->base can't
change further. So, callers of this routine can simply do timer->base to get the
base and so we can make this routine return void.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 17 ++---
1 file changed
We had this code at two places to find if a clock base belongs to current CPU:
base->cpu_base == &__get_cpu_var(hrtimer_bases)
Better to get a inlined routine for that.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff
Complete bottom part of remove_hrtimer() is part of a 'if' block and so all code
present in that block has extra indentation level before it. Rewrite it to
remove this extra indentation level.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 46 ++
1
Timers are removed from the red-black trees from __remove_hrtimer() and after
removing timer from the tree, it calls hrtimer_force_reprogram() which might use
value of cpu_base->active_bases. If the timer being removed is the last one on
that clock base, then cpu_base->active_bases wouldn't give th
In switch_hrtimer_base() we are calling hrtimer_check_target() which guarantees
this:
/*
* With HIGHRES=y we do not migrate the timer when it is expiring
* before the next event on the target cpu because we cannot reprogram
* the target cpu hardware and we would cause it to fire late.
*
* Cal
We need to call hrtimer_get_softirq_time() only once for a cpu_base from
hrtimer_run_queues(). And it shouldn't be called if there are no timers queued
for that cpu_base.
Currently we are managing this with help of a variable: gettime. This part of
code can be simplified by using cpu_base->active_
Caller of hrtimer_switch_to_hres(), i.e. hrtimer_run_pending(), has already
verified this by calling hrtimer_hres_active() and so we don't need to do it
again in hrtimer_switch_to_hres().
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kerne
Hi Thomas,
I know you are not going to look at these before end of this merge window and
you wanted to have a look at V1 before me posting these. But I am reposting them
now due to these reasons:
- Need to resend my cpu isolation (cpuset.quiesce) patches which are based of
these
- Few patches ar
On Thursday 03 April 2014 12:51 PM, Dan Carpenter wrote:
> We are allocating the size of a pointer and not the size of the data.
> This will lead to memory corruption.
>
> There isn't actually a "cb_device" struct, btw. The code is only able
> to compile because GCC knows that all pointers are the
Hi Daniel,
Interesting idea.
The benefit of this patch is to reduce power.
Have you been able to measure a power reduction, via power meter, or
via built-in RAPL power meter?
(turbostat will show RAPL watts, or if you have constant quantity of
work, use turbostat -J)
thanks,
-Len
--
To unsubscri
Kirill A. Shutemov with faultaround patchset introduced
vm_ops->map_pages() for mapping easy accessible pages around
fault address in hope to reduce number of minor page faults.
This patchset creates infrastructure to move the FAULT_AROUND_ORDER
to arch/ using Kconfig. This will enable architectur
On Thu, Apr 3, 2014 at 6:21 PM, Jovi Zhangwei wrote:
> Hi Alexei,
>
> We talked a lot on ktap and ebpf integration in these days,
> Now I think we can put into deeply to thinking out some
> technical issues in there.
>
> Firstly, I want to make sure you are support this ktap and
> ebpf integration
Kirill A. Shutemov with faultaround patchset introduced
vm_ops->map_pages() for mapping easy accessible pages around
fault address in hope to reduce number of minor page faults.
This patch creates infrastructure to move the FAULT_AROUND_ORDER
to arch/ using Kconfig. This will enable architecture m
Performance data for different FAULT_AROUND_ORDER values from 4 socket
Power7 system (128 Threads and 128GB memory) is below. perf stat with
repeat of 5 is used to get the stddev values. This patch create
FAULT_AROUND_ORDER Kconfig parameter and defaults it to 3 based on the
performance data.
FAUL
* H. Peter Anvin wrote:
> Keep in mind we already tried CF9 in the default flow and it broke
> things. I'm willing to wait for reports about production machines,
> though, but I fully expect them.
Typically there's nothing particularly weird about preproduction Intel
hardware when it comes
On 04/03/2014 04:59 PM, Felipe Balbi wrote:
> On Thu, Apr 03, 2014 at 01:05:18PM +0530, Subbaraya Sundeep Bhatta wrote:
>> Add devicetree bindings for Xilinx axi udc driver.
>>
>> Signed-off-by: Subbaraya Sundeep Bhatta
>> ---
>> Changes for v2:
>> - replaced xlnx,include-dma with xlnx,has-bu
Hello Aneesh,
After integrating review comments from NeilBown, Christoph Hellwig,
and Mike Frysinger, here is draft 4 of a man page I've written for
name_to_handle_at(2) and open_by_handle_at(2). (The changes since
draft 3 are only minor.)
Would you be willing to review it please, and let me know
Hi Mark and Harini,
On 04/04/2014 05:01 AM, Harini Katakam wrote:
> Hi Mark,
>
> On Fri, Apr 4, 2014 at 2:31 AM, Mark Brown wrote:
>> On Thu, Apr 03, 2014 at 10:33:06PM +0530, Punnaiah Choudary Kalluri wrote:
>>
>>> +Optional properties:
>>> +- num-cs : Number of chip selects used.
>
From: "Lad, Prabhakar"
This patch upgrades the vpif display driver with
v4l helpers, this patch does the following,
1: initialize the vb2 queue and context at the time of probe
and removes context at remove() callback.
2: uses vb2_ioctl_*() helpers.
3: uses vb2_fop_*() helpers.
4: uses SIMPLE_DE
shiraz.has...@st.com email-id doesn't exist anymore as he has left the
company. Replace ST's id with shiraz.linux.ker...@gmail.com.
It also updates .mailmap file to fix address for 'git shortlog'.
Cc: Shiraz Hashim
Signed-off-by: Viresh Kumar
---
.mailmap | 1 +
MAINT
From: "Lad, Prabhakar"
This patch upgrades the vpif display driver with
v4l helpers, this patch does the following,
1: initialize the vb2 queue and context at the time of probe
and removes context at remove() callback.
2: uses vb2_ioctl_*() helpers.
3: uses vb2_fop_*() helpers.
4: uses SIMPLE_DE
From: "Lad, Prabhakar"
Hi All,
This patch series upgrades the vpif capture & display
driver with the all the helpers provided by v4l, this makes
the driver much simpler and cleaner. This also includes few
checkpatch issues.
Sending them as single patch one for capture and another for
display, s
On 04/03/2014 01:08 AM, Greg KH wrote:
> On Wed, Apr 02, 2014 at 08:52:18PM +, Insop Song wrote:
>> On Wed, April 02, 2014 1:04 PM, Greg KH wrote:
>>> On Wed, Apr 02, 2014 at 10:24:03AM +0200, Paul Bolle wrote:
On Tue, 2014-04-01 at 11:48 -0700, Greg KH wrote:
> Staging driver pull req
Commit-ID: 8df28b82ff0649dd293f0469b97792cfb9ed10ab
Gitweb: http://git.kernel.org/tip/8df28b82ff0649dd293f0469b97792cfb9ed10ab
Author: K. Y. Srinivasan
AuthorDate: Thu, 3 Apr 2014 18:16:33 -0700
Committer: H. Peter Anvin
CommitDate: Thu, 3 Apr 2014 22:00:13 -0700
x86, hyperv: When on H
Because of some driver base on DMA, changed the initcall order as
subsys_initcall.
Signed-off-by: Yuan Yao
---
drivers/dma/fsl-edma.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/fsl-edma.c b/drivers/dma/fsl-edma.c
index 381e793..b396a7f 100644
--
On Thu, 2014-04-03 at 19:39 -0400, KOSAKI Motohiro wrote:
> On Thu, Apr 3, 2014 at 3:50 PM, Davidlohr Bueso wrote:
> > On Thu, 2014-04-03 at 21:02 +0200, Manfred Spraul wrote:
> >> Hi Davidlohr,
> >>
> >> On 04/03/2014 02:20 AM, Davidlohr Bueso wrote:
> >> > The default size for shmmax is, and alw
Thanks Fengguang,
On 4 April 2014 08:49, Fengguang Wu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> git://git.linaro.org/people/vireshk/linux timer-cleanup-for-tglx
>
> commit 6378cb51af5f4743db0dcb3cbcf862eac5908754
> Author: Viresh Kumar
> AuthorDate: Thu Ma
Stefan Hajnoczi writes:
> On Tue, Apr 1, 2014 at 4:27 AM, Theodore Ts'o wrote:
>> On Mon, Mar 31, 2014 at 02:22:50PM +1030, Rusty Russell wrote:
>>>
>>> It's head of my virtio-next tree.
>>
>> Hey Rusty,
>>
>> While we have your attention --- what's your opinion about adding TRIM
>> support to vi
On 4 April 2014 08:45, Fengguang Wu wrote:
> [2.258025] BUG: unable to handle kernel NULL pointer dereference at
> 0010
> [2.258641] IP: [] hrtimer_force_reprogram+0x3d/0xb1
> [2.259151] *pde =
> [2.259412] Oops: [#1] DEBUG_PAGEALLOC
> [2.259786] CPU: 0 PID:
On Thursday, April 03, 2014 10:56 AM, Dan Carpenter wrote:
>
> Signed-off-by is like signing a legal document, to show you haven't violated
> copyright law or anything while the patch was in your hands.
> You should use Acked-by or Reviewed-by depending on what you mean.
>
Dan,
Thank you for p
Some developers want to output the pstore record trace flexible.
So add seq_ops into ramoops_zone in case users would make private output
format.
Signed-off-by: Zhang Yanmin
Signed-off-by: Liu ShuoX
---
fs/pstore/inode.c | 10 --
include/linux/pstore_ramoops.h | 1 +
2 fil
dump the records in runtime is useful sometime. We could check the
records and understand driver's and device's status.
Signed-off-by: Zhang Yanmin
Signed-off-by: Liu ShuoX
---
fs/pstore/inode.c | 39 +++
fs/pstore/internal.h | 3 ++-
fs/pstor
From: Zhang Yanmin
The patch restructure ramoops of pstore a little to support more user-defined
tracers through ramoops. Here is reason we enhance ramoops:
pstore ramoops is a very import debug feature for mobile development. At
present,
ramoops has supported kdump, console and ftrace tracer. S
Hi,
Here are the v3 of this series.
Changelog v3:
1) Fix compiling errors when CONFIG_PSTORE_RAM=m.
Changelog v2:
1) Fix compiling errors when CONFIG_PSTORE_RAM is disabled.
2) Add some protection in the code in case we disable CONFIG_PSTORE_RAM.
---
Liu ShuoX (2):
pstore: add seq_ops for
On 04/03/2014 11:23 PM, Boris Ostrovsky wrote:
Steven,
Looks like commit 198d208df (x86: Keep thread_info on thread stack in
x86_32) broke Xen's 32-bit PV guests.
I poked a little at it and it seems that at least the ifdef in
xen_cpu_up() needs to be adjusted to set up kernel_stack --- that
On Thu, Apr 03, 2014 at 12:39:42PM -0700, Linus Torvalds wrote:
> Btw, since I'm planning on getting to the filesystem pulls later today
> (or perhaps tomorrow), I wanted to check: are you ok with the ext4
> parts of the cross-rename patches from Miklos?
>
> They are currently at
>
> git://git.
Hi Mark
On Fri, Apr 4, 2014 at 3:13 AM, Mark Brown wrote:
> On Thu, Apr 03, 2014 at 04:40:30PM +0530, Harini Katakam wrote:
>> Add driver for Cadence SPI controller. This is used in Xilinx Zynq.
>
> I just reviewed a driver for "Zynq Quad SPI controller" from Punnaiah
> Choudary Kalluri (CCed) wh
Hi, Srivatsa
Thanks for your reply :)
On 04/03/2014 04:50 PM, Srivatsa S. Bhat wrote:
[snip]
>
> Now, the interesting thing to note here is that, if CPU0's node was already
> set as node0, *nothing* should go wrong, since its just a redundant update.
> However, if CPU0's original node mapping wa
KVM does not handle the reserved bits of x86 page tables correctly:
In PAE, bits 5:8 are reserved in the PDPTE.
In IA-32e, bit 8 is not reserved.
Signed-off-by: Nadav Amit
---
arch/x86/kvm/mmu.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arc
- Original Message -
> From: "Steven Rostedt"
> To: "Mathieu Desnoyers"
> Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" , "Frederic
> Weisbecker" ,
> "Andrew Morton" , "Frank Ch. Eigler"
> , "Johannes Berg"
>
> Sent: Thursday, April 3, 2014 2:54:41 PM
> Subject: Re: [PATCH v9 1/1] Tr
Hi Mark,
On Fri, Apr 4, 2014 at 2:59 AM, Mark Brown wrote:
> On Thu, Apr 03, 2014 at 10:33:07PM +0530, Punnaiah Choudary Kalluri wrote:
>
> Overall this looks fairly good, there are a few issues that need to be
> looked at but they're not too invasive. Please also check for coding
> style issues
From: Hongbo Zhang
Hi Vinod Koul,
Please have a look at the v2 patch set.
v1 -> v2 change:
The only one change is introducing a new patch[1/7] to remove the unnecessary
macro FSL_DMA_LD_DEBUG, thus the total patches number is 8 now (was 7)
Hongbo Zhang (8):
DMA: Freescale: remove the unnecess
From: Hongbo Zhang
There are several places where descriptors are freed using identical code.
This patch puts this code into a function to reduce code duplication.
Signed-off-by: Hongbo Zhang
Signed-off-by: Qiang Liu
---
drivers/dma/fsldma.c | 30 ++
1 file chang
From: Hongbo Zhang
The usage of spin_lock_irqsave() is a stronger locking mechanism than is
required throughout the driver. The minimum locking required should be used
instead. Interrupts will be turned off and context will be saved, it is
unnecessary to use irqsave.
This patch changes all insta
From: Hongbo Zhang
Fix the potential risk when enable config NET_DMA and ASYNC_TX. Async_tx is
lack of support in current release process of dma descriptor, all descriptors
will be released whatever is acked or no-acked by async_tx, so there is a
potential race condition when dma engine is uesd b
From: Hongbo Zhang
These functions will be modified in the next patch in the series. By moving the
function in a patch separate from the changes, it will make review easier.
Signed-off-by: Hongbo Zhang
Signed-off-by: Qiang Liu
---
drivers/dma/fsldma.c | 188 +-
From: Hongbo Zhang
This patch adds suspend resume functions for Freescale DMA driver.
.prepare callback is used to stop further descriptors from being added into the
pending queue, and also issue pending queues into execution if there is any.
.suspend callback makes sure all the pending jobs are
From: Hongbo Zhang
Delete attribute DMA_INTERRUPT because fsldma doesn't support this function,
exception will be thrown if talitos is used to offload xor at the same time.
Signed-off-by: Hongbo Zhang
Signed-off-by: Qiang Liu
---
drivers/dma/fsldma.c | 31 ---
1
From: Hongbo Zhang
Methods of accessing DMA contorller registers are inconsistent, some registers
are accessed by DMA_IN/OUT directly, while others are accessed by functions
get/set_* which are wrappers of DMA_IN/OUT, and even for the BCR register, it
is read by get_bcr but written by DMA_OUT.
Th
From: Hongbo Zhang
Some codes are calling chan_dbg with FSL_DMA_LD_DEBUG surrounded, it is really
unnecessary to use such a macro because chan_dbg is a wrapper of dev_dbg, we do
have corresponding DEBUG macro to switch on/off dev_dbg, and most of the other
codes are also calling chan_dbg directly
Add dma support for i2c. This function depend on DMA driver.
You can turn on it by write both the dmas and dma-name properties in dts node.
Signed-off-by: Yuan Yao
---
drivers/i2c/busses/i2c-imx.c | 372 +--
1 file changed, 319 insertions(+), 53 deletions(
Add i2c dts node properties for eDMA support, them depend on the eDMA driver.
Signed-off-by: Yuan Yao
---
Documentation/devicetree/bindings/i2c/i2c-imx.txt | 11 +++
1 file changed, 11 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-imx.txt
b/Documentation/devicetr
Changed in v4:
- cancelled "i2c_imx->use_dma".
- changed "Dma" to "DMA".
- add timeout handling for DMA transfer complete.
Changed in v3:
- fix a bug when request the DMA faild.
- some minor fixes for coding style.
- other minor fixes.
Changed in v2:
- remove has_dma_support property
- unify i2
Steven,
Looks like commit 198d208df (x86: Keep thread_info on thread stack in
x86_32) broke Xen's 32-bit PV guests.
I poked a little at it and it seems that at least the ifdef in
xen_cpu_up() needs to be adjusted to set up kernel_stack --- that allows
CPUs to get going. This is not enough th
So that in the very early booting place, we could call timekeeping
code, while it would not cause system panic, since clock is not
init yet.
And for system default clock is always jiffies, so that it shall be
safe to do so.
Signed-off-by: Lei Wen
---
include/linux/time.h | 1 +
init/main.
As people may want to align the kernel log with some other processor
running over the same machine but not the same copy of linux, we
need to keep their log aligned, so that it would not make debug
process hard and confused.
Signed-off-by: Lei Wen
---
kernel/printk/printk.c | 4 ++--
1 file chan
It is very common to have many processor to run over the same machine
but run different OS actually, so that timestamp alignment is key
to do the right debugging when find something wrong.
Linux adopt schedule clock stopped, so that printk timestamp would get
during suspend period which break such
Since sched_clock always get stopped during suspend period, it
would make it hard to use the kernel log to compare with other
procssor generated log which running over the same machine.
[Absolutely not running linux]
So we need a way to recover the printk timestamp that including
suspend time in t
(2014/04/03 3:08), Luiz Capitulino wrote:
> HugeTLB is limited to allocating hugepages whose size are less than
> MAX_ORDER order. This is so because HugeTLB allocates hugepages via
> the buddy allocator. Gigantic pages (that is, pages whose size is
> greater than MAX_ORDER order) have to be alloca
Hi Mark,
On Fri, Apr 4, 2014 at 2:31 AM, Mark Brown wrote:
> On Thu, Apr 03, 2014 at 10:33:06PM +0530, Punnaiah Choudary Kalluri wrote:
>
>> +Optional properties:
>> +- num-cs : Number of chip selects used.
>
> What does this translate into?
>
>> + num-cs = /bits/ 16 <1>;
Hi Mark,
On Fri, Apr 4, 2014 at 3:04 AM, Mark Brown wrote:
> On Thu, Apr 03, 2014 at 04:40:31PM +0530, Harini Katakam wrote:
>
>> +Optional properties:
>> +- num-cs : Number of chip selects used.
>
> How does this translate to the hardware?
This IP can drive 4 slaves.
The CS line to
On 04/03/2014 01:23 PM, Konrad Rzeszutek Wilk wrote:
On Wed, Apr 02, 2014 at 10:10:17PM -0400, Waiman Long wrote:
On 04/02/2014 04:35 PM, Waiman Long wrote:
On 04/02/2014 10:32 AM, Konrad Rzeszutek Wilk wrote:
On Wed, Apr 02, 2014 at 09:27:29AM -0400, Waiman Long wrote:
N.B. Sorry for the dup
(2014/04/03 18:51), Denys Vlasenko wrote:
> On Thu, Apr 3, 2014 at 9:02 AM, Hidetoshi Seto
> wrote:
[PROBLEM 2]: broken iowait accounting.
As historical nature, cpu's idle time was accounted as either
idle or iowait depending on the presence of tasks blocked by
I/O. No one
On 2014/4/4 10:16, Steven Rostedt wrote:
> On Fri, 04 Apr 2014 07:52:53 +0800
> "Li, Aubrey" wrote:
>
>> On 2014/4/4 7:40, Steven Rostedt wrote:
>>> On Fri, 04 Apr 2014 07:23:32 +0800
>>> "Li, Aubrey" wrote:
>>>
Can you please send the dmi table out?
>>>
>>> I already did as a gz attachment
On 04/03/2014 09:18 PM, Alex Elder wrote:
> This patch adds SMP support for BCM281XX and BCM21664 family SoCs.
>
> This feature is controlled with a distinct config option such that a
> SMP-enabled multi-v7 binary can be configured to run these SoCs in
> uniprocessor mode. Since this SMP function
The CPU_METHOD_OF_DECLARE() macro allows methods for assigning
SMP/hotplug operations to CPUS to be defined using device tree,
without the need for machine-dependent code.
And although it allows the *method* to be specified, it does *not*
allow any parameterization of that method. For example, th
Define nodes representing the two Cortex A9 CPUs in a bcm21644 SoC.
Signed-off-by: Alex Elder
---
arch/arm/boot/dts/bcm21664.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/boot/dts/bcm21664.dtsi b/arch/arm/boot/dts/bcm21664.dtsi
index 08a44d4..a37ded1 10
1 - 100 of 623 matches
Mail list logo
