On 02/17/2014 11:31 PM, Peter Zijlstra wrote:
>>
>> This is starting to look good, so I have pulled it into
>> tip:x86/spinlocks to start give it some testing mileage.
>
> It very much needs paravirt muck before we can even consider it.
>
Ah yes. Joy ... I so love PV.
-hpa
--
To
Hi Lee,
On 02/17/2014 06:57 PM, Lee Jones wrote:
+static const struct resource lm3633_effect_resources[] = {
+ {
+ .name = LM3633_EFFECT_BL0_RAMPUP,
+ .flags = IORESOURCE_REG,
+ .start = LM3633_EFFECT_REGISTER(BL0_RAMPUP),
+ },
+ {
+
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
One example is Compulab's mini-desktop, the Intense-PC2.
The bug can be
On Mon, Feb 17, 2014 at 03:41:22PM -0500, Waiman Long wrote:
> +void queue_spin_lock_slowpath(struct qspinlock *lock, int qsval)
> +{
> + unsigned int cpu_nr, qn_idx;
> + struct qnode *node, *next;
> + u32 prev_qcode, my_qcode;
> +
> +#ifdef queue_spin_trylock_quick
> + /*
> +
Hi Geert,
On Mon, Feb 17, 2014 at 07:02:09PM +0100, Geert Uytterhoeven wrote:
> On Mon, Feb 17, 2014 at 6:20 PM, Maxime Ripard
> wrote:
> > When the generic implementation of the transfer_one_message callback was
> > called
> > by the spi_pump_messages function, if that transfer was to fail,
On Mon, Feb 17, 2014 at 02:47:03PM -0800, H. Peter Anvin wrote:
> This is starting to look good, so I have pulled it into
> tip:x86/spinlocks to start give it some testing mileage.
Its still atrociously ugly code please drop it.
--
To unsubscribe from this list: send the line "unsubscribe
On Mon, Feb 17, 2014 at 03:41:22PM -0500, Waiman Long wrote:
> +#define _QCODE(lock)(atomic_read(&(lock)->qlcode) >> _QCODE_OFFSET)
> +#define _QLOCK(lock)(atomic_read(&(lock)->qlcode) &
> _QSPINLOCK_LOCKED)
> +#define GET_QN_IDX(code) (((code) >> _QCODE_VAL_OFFSET) & 3)
>
On Mon, Feb 17, 2014 at 02:47:03PM -0800, H. Peter Anvin wrote:
> On 02/17/2014 12:41 PM, Waiman Long wrote:
> > v3->v4:
> > - Remove debugging code and fix a configuration error
> > - Simplify the qspinlock structure and streamline the code to make it
> >perform a bit better
> > - Add an
On Mon, Feb 17, 2014 at 03:41:22PM -0500, Waiman Long wrote:
> +/*
> + * The queue node structure
> + *
> + * This structure is essentially the same as the mcs_spinlock structure
> + * in mcs_spinlock.h file. This structure is retained for future extension
> + * where new fields may be added.
> +
Hi,
I'm sorry to bother you!
Does it need to implement irq_set_type method in the
ioapic_chip(arch/x86/kernel/apic/io_apic.c) structure?
Recently, I developed a device driver based on x86. The device uses a
falling edge interrupt trigger mode, so I have to set the trigger mode
in the
Currently max_sane_readahead() returns zero on the cpu having no local memory
node
which leads to readahead failure. Fix the readahead failure by returning
minimum of (requested pages, 512). Users running application on a memory-less
cpu
which needs readahead such as streaming application see
Hi Courtney,
On 18 February 2014 06:22, Courtney Cavin wrote:
> On Sat, Feb 15, 2014 at 07:25:27PM +0100, Jassi Brar wrote:
>> +request_token_t ipc_send_message(void *channel, void *mssg)
>> +{
>> + struct ipc_chan *chan = (struct ipc_chan *)channel;
>> + request_token_t t;
>> +
>>
Hi Grant,
On Mon, Feb 17, 2014 at 06:14:51PM +, Grant Likely wrote:
> On Tue, 11 Feb 2014 07:56:33 -0600, Rob Herring wrote:
> > On Tue, Feb 11, 2014 at 5:45 AM, Philipp Zabel
> > wrote:
> > > From: Philipp Zabel
> > >
> > > This patch moves the parsing helpers used to parse connected
Hi Lucas,
> Commit bfacbb9 (Bluetooth: Use devname:vhci module alias for virtual HCI
> driver) added the module alias to hci_vhci module so it's possible to
> create the /dev/vhci node. However creating an alias without
> specifying the minor doesn't allow us to create the node ahead,
>
microblaze:allmodconfig complains for some configurations that 'heartbeat'
is redefined as different kind of symbol. This is seen in test compiles
of watchdog drivers, which often use 'heartbeat' as ststic variable.
Since 'heartbeat' is an unfortunate name for a global function,
rename it to
This patch for hwdrv_apci035.c changes a printk() call to a dev_err() call
since this is generally preferred. It also removes a newline from the start
of the error message.
Signed-off-by: Chase Southwood
---
2: Removed leading newline, per Ian's request.
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +
> +#include
> +
> +
> +/*
> + * Return the domain number for this bus
> + */
> +int pci_domain_nr(struct pci_bus *bus)
> +{
> + struct pci_host_bridge *bridge = to_pci_host_bridge(bus->bridge);
On 02/18/2014 02:03 PM, Alex Shi wrote:
[snip]
>>
>
> I reviewed my patch again. Also didn't find suspicious line for the
> following rcu stall. Will wait for your report. :)
Posted, it will be triggered in pure tip/master, your patch set was
innocent ;-)
Regards,
Michael Wang
>>
>
--
To
The index of lbr_sel_map is bit value of perf branch_sample_type.
PERF_SAMPLE_BRANCH_MAX is 1024 at present, so each lbr_sel_map uses
4096 bytes. By using bit shift as index, we can reduce lbr_sel_map
size to 40 bytes.
Signed-off-by: Yan, Zheng
---
arch/x86/kernel/cpu/perf_event.h |
Enable the pmu context switch callback when LBR is used. Use the
callback to flush LBR stack when task is scheduled in. This allows
us to move code that flushes LBR stack from perf core to perf x86.
Signed-off-by: Yan, Zheng
---
arch/x86/kernel/cpu/perf_event.c | 7 ---
Introduce a new field to 'struct pmu' to specify the size of PMU
specific data. Allocate memory for PMU specific data when allocating
perf task context. The PMU specific data are initialized to zeros.
Later patches will use PMU specific data to save LBR stack.
Signed-off-by: Yan, Zheng
---
The callback is invoked when process is scheduled in or out. It
provides mechanism for later patches to save/store the LBR stack.
It can also replace the flush branch stack callback.
To avoid unnecessary overhead, the callback is enabled dynamically
Signed-off-by: Yan, Zheng
---
When the LBR call stack is enabled, it is necessary to save/restore
the LBR stack on context switch. We can use pmu specific data to
store LBR stack when task is scheduled out. This patch adds code
that allocates the pmu specific data.
Signed-off-by: Yan, Zheng
---
If two tasks were both forked from the same parent task, Events in
their perf task contexts can be the same. Perf core optimizes context
switch out in this case.
Previous patch inroduces pmu specific data. The data is task specific,
so we should switch the data even when context switch is
Haswell has a new feature that utilizes the existing LBR facility to
record call chains. To enable this feature, bits (JCC, NEAR_IND_JMP,
NEAR_REL_JMP, FAR_BRANCH, EN_CALLSTACK) in LBR_SELECT must be set to 1,
bits (NEAR_REL_CALL, NEAR-IND_CALL, NEAR_RET) must be cleared. Due to
a hardware bug of
When the LBR call stack is enabled, it is necessary to save/restore
the LBR stack on context switch. The solution is saving/restoring
the LBR stack to/from task's perf event context.
The LBR stack is saved/restored only when there are events that use
the LBR call stack. If no event uses LBR call
Try enabling the LBR callstack facility if user requests recording
user callchain. Also adds a cpu pmu attribute to enable/disable this
feature. This feature is disabled by default because it may contend
for the LBR with other events that explicitly require branch stack.
Note: this feature only
event->attr.branch_sample_type is non-zero no matter branch stack
is enabled explicitly or is enabled implicitly. So we can use it
to replace intel_pmu_needs_lbr_smpl(). This avoids duplicating
code that implicitly enables the LBR.
Signed-off-by: Yan, Zheng
---
Haswell has a new feature that utilizes the existing Last Branch Record
facility to record call chains. When the feature is enabled, function
call will be collected as normal, but as return instructions are executed
the last captured branch record is popped from the on-chip LBR registers.
The LBR
Haswell has a new feature that utilizes the existing Last Branch Record
facility to record call chains. When the feature is enabled, function
call will be collected as normal, but as return instructions are executed
the last captured branch record is popped from the on-chip LBR registers.
The LBR
For many profiling tasks we need the callgraph. For example we often
need to see the caller of a lock or the caller of a memcpy or other
library function to actually tune the program. Frame pointer unwinding
is efficient and works well. But frame pointers are off by default on
64bit code (and on
"Zero length call" uses the attribute of the call instruction to push
the immediate instruction pointer on to the stack and then pops off
that address into a register. This is accomplished without any matching
return instruction. It confuses the hardware and make the recorded call
stack incorrect.
When enabling/disabling an event, check if the event uses the LBR
callstack feature, adjust the LBR callstack usage count accordingly.
Later patch will use the usage count to decide if the LBR stack
should be saved/restored.
Signed-off-by: Yan, Zheng
---
On 02/18/2014 12:52 PM, Michael wang wrote:
> On 02/17/2014 09:55 AM, Alex Shi wrote:
>> The cpu_load decays on time according past cpu load of rq. The sched_avg
>> also decays tasks' load on time. Now we has 2 kind decay for cpu_load. That
>> is a kind of redundancy. And increase the system
Hello Sergey,
On Thu, Feb 13, 2014 at 08:43:18PM +0300, Sergey Senozhatsky wrote:
> This patchset introduces zcomp compression backend abstraction
> adding ability to support compression algorithms other than LZO;
> support for multi compression streams, making parallel compressions
> possible.
>
Some system's ACPI video backlight control interface is broken and the
native backlight control interface should be used by default. This patch
sets the use_native_backlight parameter to true for those systems so
that video backlight control interface will not be created. For detailed
models that
On Sat, 2014-02-15 at 02:06 -0800, David Rientjes wrote:
> On Fri, 14 Feb 2014, Luiz Capitulino wrote:
>
> > > Again, I think this syntax is horrendous and doesn't couple well with the
> > > other hugepage-related kernel command line options. We already have
> > > hugepages= and hugepagesz=
For an established association, if user has updated the HB.interval
parameter by setsockopt(), this new heartbeat interval will not
take effect until:
- the expiry of the heartbeat timer and new hearbeat is sent.
- DATA chunk has been sent and the transport resets the timer.
This could not
From: Lucas De Marchi
Signed-off-by: Lucas De Marchi
---
Documentation/devices.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devices.txt b/Documentation/devices.txt
index 04356f5..0ea1cc2 100644
--- a/Documentation/devices.txt
+++ b/Documentation/devices.txt
@@
From: Lucas De Marchi
Signed-off-by: Lucas De Marchi
---
include/linux/miscdevice.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/include/linux/miscdevice.h b/include/linux/miscdevice.h
index 7bb6148..51e26f3 100644
--- a/include/linux/miscdevice.h
+++
From: Lucas De Marchi
These patches are not intended for merging as is... clearly we have at least
one problem: fram's minor is clashing with logibm's. I don't know what to do
here.
The first patch also adds comments on those minors that are defined but not
used. Is that ok?
Lucas De Marchi
On Mon, Feb 17, 2014 at 07:42:42PM -0800, Linus Torvalds wrote:
> On Mon, Feb 17, 2014 at 7:24 PM, Linus Torvalds
> wrote:
> >
> > As far as I can tell, the intent is that you can't do value
> > speculation (except perhaps for the "relaxed", which quite frankly
> > sounds largely useless).
>
>
From: Lucas De Marchi
Commit bfacbb9 (Bluetooth: Use devname:vhci module alias for virtual HCI
driver) added the module alias to hci_vhci module so it's possible to
create the /dev/vhci node. However creating an alias without
specifying the minor doesn't allow us to create the node ahead,
On Thu, Feb 13, 2014 at 08:43:19PM +0300, Sergey Senozhatsky wrote:
> ZRAM performs direct LZO compression algorithm calls, making it the one and
> only option. Introduce compressing backend abstraction zcomp in order to
> support multiple compression algorithms with the following set of
(more than usual) the powerpc allyesconfig build.
Changes since 20140217:
New tree: keystone
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The net-next tree gained conflicts against the net tree.
The tip t
On Mon, Feb 17, 2014 at 07:24:56PM -0800, Linus Torvalds wrote:
> On Mon, Feb 17, 2014 at 7:00 PM, Paul E. McKenney
> wrote:
> >
> > One example that I learned about last week uses the branch-prediction
> > hardware to validate value speculation. And no, I am not at all a fan
> > of value
On Mon, Feb 17, 2014 at 07:29:55PM -0800, Josh Triplett wrote:
> On Mon, Feb 17, 2014 at 05:21:37PM -0800, Paul E. McKenney wrote:
> > On Mon, Feb 17, 2014 at 04:45:11PM -0800, Josh Triplett wrote:
> > > On Mon, Feb 17, 2014 at 04:17:40PM -0800, Paul E. McKenney wrote:
> > > > On Mon, Feb 17, 2014
Quoting Andrey Vagin (ava...@openvz.org):
> When we restore a task we need to restore its exe link from userspace to
> the values the task had at checkpoint time.
>
> Currently this operations required the global CAP_SYS_RESOURCE, which is
> always absent in a non-root user namespace.
>
> So
On 02/17/2014 09:55 AM, Alex Shi wrote:
> The cpu_load decays on time according past cpu load of rq. The sched_avg also
> decays tasks' load on time. Now we has 2 kind decay for cpu_load. That is a
> kind of redundancy. And increase the system load by decay calculation. This
> patch try to
Hi Alan,
Thank you for your reply.
(2014/02/18 0:12), One Thousand Gnomes wrote:
According to HW specification of serial UART devices, RX interrupt trigger
can be changed, but the trigger is hard-coded. For example, RX interrupt trigger
in 16550A can be set to 1, 4, 8, or 14 bytes for HW, but
On Tue, Feb 18, 2014 at 10:17:11AM +0800, Jingchang Lu wrote:
> Signed-off-by: Jingchang Lu
> Acked-by: Arnd Bergmann
Applied, thanks.
Shawn
> ---
> no changes in v10 ~ v11.
>
> changes in v9:
> remove include/dt-bindings/dma/vf610-edma.h, the request source ID
> is the same as SoC's
On Mon, Feb 17, 2014 at 7:24 PM, Linus Torvalds
wrote:
>
> As far as I can tell, the intent is that you can't do value
> speculation (except perhaps for the "relaxed", which quite frankly
> sounds largely useless).
Hmm. The language I see for "consume" is not obvious:
"Consume operation: no
On Mon, Feb 17, 2014 at 05:43:57PM -0800, Paul E. McKenney wrote:
> On Mon, Feb 17, 2014 at 05:23:18PM -0800, Josh Triplett wrote:
> > On Mon, Feb 17, 2014 at 04:58:02PM -0800, Paul E. McKenney wrote:
> > > On Mon, Feb 17, 2014 at 04:26:06PM -0800, Josh Triplett wrote:
> > > > On Mon, Feb 17, 2014
On Mon, Feb 17, 2014 at 05:21:37PM -0800, Paul E. McKenney wrote:
> On Mon, Feb 17, 2014 at 04:45:11PM -0800, Josh Triplett wrote:
> > On Mon, Feb 17, 2014 at 04:17:40PM -0800, Paul E. McKenney wrote:
> > > On Mon, Feb 17, 2014 at 04:02:47PM -0800, Josh Triplett wrote:
> > > > On Mon, Feb 17, 2014
Update driver to use SIMPLE_DEV_PM_OPS macro for power
management suspend and resume operations.
Signed-off-by: Manish Badarkhe
---
:100644 100644 a1d74dd... 0c0ba92... M drivers/video/da8xx-fb.c
drivers/video/da8xx-fb.c | 22 ++
1 file changed, 10 insertions(+), 12
On Mon, Feb 17, 2014 at 7:00 PM, Paul E. McKenney
wrote:
>
> One example that I learned about last week uses the branch-prediction
> hardware to validate value speculation. And no, I am not at all a fan
> of value speculation, in case you were curious.
Heh. See the example I used in my reply to
This series add Freescale eDMA engine support.
Jingchang Lu (2):
ARM: dts: vf610: Add eDMA node
dma: Add Freescale eDMA engine driver support
Documentation/devicetree/bindings/dma/fsl-edma.txt | 76 ++
arch/arm/boot/dts/vf610.dtsi | 30 +
drivers/dma/Kconfig
Signed-off-by: Jingchang Lu
Acked-by: Arnd Bergmann
---
no changes in v10 ~ v11.
changes in v9:
remove include/dt-bindings/dma/vf610-edma.h, the request source ID
is the same as SoC's reference manual.
changes in v8:
describe dmamux info in edma node to avoid confusion.
change eDMA requst
Add Freescale enhanced direct memory(eDMA) controller support.
This module can be found on Vybrid and LS-1 SoCs.
Signed-off-by: Alison Wang
Signed-off-by: Jingchang Lu
Acked-by: Arnd Bergmann
---
changes in v11:
Add dma device_slave_caps definition.
changes in v10:
define fsl_edma_mutex in
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/avr32/include/asm/Kbuild between commit d7668f9d448a ("avr32: add
generic vga.h to Kbuild") from the tree and commit b119fa61d440
("locking/mcs: Order the header files in Kbuild of each architecture in
alphabetical order")
Howdy all,
Meet following warning and call trace:
[307001.720980] [ cut here ]
[307001.720994] WARNING: CPU: 0 PID: 0 at lib/dma-debug.c:491
add_dma_entry+0x127/0x130()
[307001.720996] DMA-API: exceeded 7 overlapping mappings of pfn 1932f8
[307001.720998] Modules linked
On Mon, Feb 17, 2014 at 12:18:21PM -0800, Linus Torvalds wrote:
> On Mon, Feb 17, 2014 at 11:55 AM, Torvald Riegel wrote:
> >
> > Which example do you have in mind here? Haven't we resolved all the
> > debated examples, or did I miss any?
>
> Well, Paul seems to still think that the standard
Hi Thomas,
With regard to the patch: "tick: Clear broadcast pending bit when
switching to oneshot"
isn't BROADCAST_EXIT called atleast after initializing the high
resolution timers while
handling the broadcast IPI and before re-entering idle? This should
clear the cpu bit
in the pending mask
On 02/17/2014 07:24 PM, Peter Zijlstra wrote:
[snip]
>> Since idle_balance() won't happen in the loop, may be we could use:
>>
>> if p && p->sched_class == class
>> return p
>>
>> in here, let it fall down into the loop if p is idle, since that means
>> we got RT/DL and will do
... since __initcall is now deprecated.
Signed-off-by: Davidlohr Bueso
---
ipc/ipc_sysctl.c | 2 +-
ipc/mqueue.c | 2 +-
ipc/util.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/ipc/ipc_sysctl.c b/ipc/ipc_sysctl.c
index 1702864..998d31b 100644
---
This macro appears to have been introduced back in the 2.5 era for
semtimedop32 backward compatibility on ia32:
https://lkml.org/lkml/2003/4/28/78
Nowadays, this syscall in compat just defaults back to the code found in
sem.c, so it is no longer used and can thus be removed:
long
In analogy with commits 5af84b82701a and 97df8c12995, using
asynchronous threads can improve the overall suspend_late
time significantly.
This patch is for suspend_late phase.
Signed-off-by: Chuansheng Liu
---
drivers/base/power/main.c | 66 ++-
1
In analogy with commits 5af84b82701a and 97df8c12995, using
asynchronous threads can improve the overall resume_early
time significantly.
This patch is for resume_early phase.
Signed-off-by: Chuansheng Liu
---
drivers/base/power/main.c | 55 +--
1
In analogy with commits 5af84b82701a and 97df8c12995, using
asynchronous threads can improve the overall suspend_noirq
time significantly.
This patch is for suspend_noirq phase.
Signed-off-by: Chuansheng Liu
---
drivers/base/power/main.c | 68 +++
1
The patch is a helper adding two new flags for implementing
async threads for suspend_noirq and suspend_late.
Signed-off-by: Chuansheng Liu
---
drivers/base/power/main.c | 24 ++--
include/linux/pm.h| 2 ++
2 files changed, 24 insertions(+), 2 deletions(-)
diff
In analogy with commits 5af84b82701a and 97df8c12995, using
asynchronous threads can improve the overall resume_noirq time
significantly.
One typical case is:
In resume_noirq phase and for the PCI devices, the function
pci_pm_resume_noirq() will be called, and there is one d3_delay
(10ms) at
Hello,
This patch series are for enabling the asynchronous threads for the phases
resume_noirq, resume_early, suspend_noirq and suspend_late.
Just like commit 5af84b82701a and 97df8c12995, with async threads it will
reduce the system suspending and resuming time significantly.
With these
On 02/17/2014 09:55 AM, Alex Shi wrote:
> The cpu_load decays on time according past cpu load of rq. The sched_avg also
> decays tasks' load on time. Now we has 2 kind decay for cpu_load. That is a
> kind of redundancy. And increase the system load by decay calculation. This
> patch try to
> I'm not convinced it needs to be a PERF_RECORD_SAMPLE; but some
> PERF_RECORD_* type for sure.
Adding a header shouldn't be a problem, it's merely wasting 4K.
> Also it must allow interleaving with other > events.
But can you describe a concrete use case where interleaving is better?
I'm
On Mon, Feb 17, 2014 at 02:33:29PM +0530, Sachin Kamat wrote:
> Add of_node_put to decrement the ref count.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Feb 17, 2014 at 02:33:34PM +0530, Sachin Kamat wrote:
> Add of_node_put to decrement the ref count.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Feb 17, 2014 at 02:33:35PM +0530, Sachin Kamat wrote:
> Add of_node_put to decrement the ref count.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Feb 17, 2014 at 02:33:36PM +0530, Sachin Kamat wrote:
> Add of_node_put to decrement the ref count.
Applied, thanks.
signature.asc
Description: Digital signature
On 02/17/2014 08:43 PM, Ben Hutchings wrote:
On Sat, 2014-02-15 at 14:38 -0500, Peter Hurley wrote:
Since commit a2c1c57be8d9fd5b716113c8991d3d702eeacf77,
workqueue: consider work function when searching for busy work items
work items whose work functions are re-assigned are no longer
On 02/18/2014 05:07 AM, Sasha Levin wrote:
[snip]
>
> I *think* it works. There seems to be another sched issue that causes
> lockups,
> so I can't say for certain that this one doesn't occur anymore.
>
> I'm still working on collecting data for the other issue, I'll mail
> about it soon.
On 02/17/2014 05:20 PM, Peter Zijlstra wrote:
[snip]
>> static void switched_to_fair(struct rq *rq, struct task_struct *p)
>> {
>> -if (!p->se.on_rq)
>> +struct sched_entity *se = >se;
>> +#ifdef CONFIG_FAIR_GROUP_SCHED
>> +se->depth = se->parent ? se->parent->depth + 1 : 0;
>>
On 18 February 2014 03:30, Rafael J. Wysocki wrote:
> On Monday, February 17, 2014 02:25:34 PM Srivatsa S. Bhat wrote:
>> Why go to no_policy when we can actually set things right?
>>
>> Anyway, I am not arguing against this strongly. I just wanted to share my
>> thoughts, since this is the
From: Magnus Damm
Select BOUNCE in case of HIGHMEM to enable bounce buffers in
the block layer. Without this patch the DMABOUNCE code will
error out due to lack of HIGHMEM support, and without DMABOUNCE
there will be silent errors.
Signed-off-by: Magnus Damm
---
drivers/pci/host/Kconfig |
From: Magnus Damm
Convert the code to allow per-device probe() like other device
drivers. This also delays driver registration due to change from
subsys_initcall() to regular module_platform_driver().
Signed-off-by: Magnus Damm
---
Changes since V2:
- Remove __init tags from
From: Magnus Damm
Update the R-Car Generation 2 PCI driver Kconfig dependencies
to follow same style as other drivers - no SoC dependencies.
Also, update the COMPILE_TEST bits to depend on ARM. This since
the DMA bounce buffer and dma_ops handling code is ARM specific.
Signed-off-by: Magnus
From: Magnus Damm
Break out the hard coded window size code to allow
dynamic setup. The window size is still left at 1GiB
but with this patch changing window size is easy for
testing.
Signed-off-by: Magnus Damm
---
Changes since V1:
- Updated to fit on top of patches from Ben Dooks
From: Magnus Damm
Add DMABOUNCE support together with a local memory area for
all PCI devices hanging off this bridge. 4MiB of memory is
set aside for coherent allocations which is shared between
the on-chip OHCI and EHCI devices that are hanging off the
PCI bridge. With this patch the driver
From: Ben Dooks
The current code does not check the return from platform_get_irq()
so add an error check and return if this call does fail.
Signed-off-by: Ben Dooks
Signed-off-by: Magnus Damm
---
drivers/pci/host/pci-rcar-gen2.c |5 +
1 file changed, 5 insertions(+)
---
since V1 of this series:
- Updated [4/8] from v2 to v3 to fix init section issues, thanks Bjorn!
Written against renesas.git tag renesas-devel-v3.14-rc3-20140217
drivers/pci/host/Kconfig |5
drivers/pci/host/pci-rcar-gen2.c | 449 --
2 files
From: Ben Dooks
Add option to enable interrupts to report any errors from
the AHB-PCI bridge to help find any issues with the bridge
when in use.
Signed-off-by: Ben Dooks
Signed-off-by: Magnus Damm
---
v2:
- removed kconfig entry and use CONFIG_PCI_DEBUG
- check for irq > 0
From: Ben Dooks
The bridge logic at slot 0 only supports reads up to 0x40 and the
rest of the PCI configuration space for this slot is marked as
reserved in the manual.
Trying a read from offset 0x100 is producing an error from the
bridge. With error interrupts enabled, the following is
cc'ing stable for getting this in 3.12 and 3.13 as well..
On 17 February 2014 16:18, Srivatsa S. Bhat
wrote:
> The powernow-k8 driver maintains a per-cpu data-structure called powernow_data
> that is used to perform the frequency transitions. It initializes this data-
> structure only for the
On Mon, Feb 17, 2014 at 02:33:33PM +0530, Sachin Kamat wrote:
> Add of_node_put to decrement the ref count.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Feb 17, 2014 at 04:15:41PM +0900, Milo Kim wrote:
> Thank you. I've fixed things based on your comments.
> Could you check the description below?
> I'd like to get your feedback before sending patch-set v2.
Yes, this looks OK.
signature.asc
Description: Digital signature
On Mon, Feb 17, 2014 at 02:33:32PM +0530, Sachin Kamat wrote:
> Add of_node_put to decrement the ref count.
Applied, thanks.
signature.asc
Description: Digital signature
Sorry, the cover letter was forgotten to send to LKML.
On 02/18/2014 12:24 AM, Lai Jiangshan wrote:
> This patchset moves the worker-destruction(partial) to worker_thread(),
> and worker to be die will perform self-destruction.
>
> This async worker destruction helps us to reduce the mananger's
On Mon, Feb 17, 2014 at 02:33:30PM +0530, Sachin Kamat wrote:
> Add of_node_put to decrement the ref count.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Feb 17, 2014 at 02:33:31PM +0530, Sachin Kamat wrote:
> Add of_node_put to decrement the ref count.
Applied, thanks.
signature.asc
Description: Digital signature
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/bonding/bond_main.c between commit f80889a5b79c ("bonding:
Fix deadlock in bonding driver when using netpoll") from the net tree and
commit 90194264ceff ("bonding: Neaten pr_") from the net-next tree.
I fixed it
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/bonding/bond_3ad.h between commit 163c8ff30dbe ("bonding:
802.3ad: make aggregator_identifier bond-private") from the net tree and
commit 2ea24f2ecfdc ("bonding: Convert c99 comments") from the net-next
tree.
I
1 - 100 of 1536 matches
Mail list logo
