On Wed, May 02, 2012 at 09:36:51PM -0700, Dmitry Torokhov wrote:
> Hi Sven,
>
> On Sat, Apr 07, 2012 at 08:38:33PM +0200, Sven Neumann wrote:
> > Hi,
> >
> > On 07.04.12 09:02, Dmitry Torokhov wrote:
> > >On Fri, Apr 06, 2012 at 10:40:07PM -0700, Olof Johansson wrote:
> > >>This seems to have bee
Hi Shan,
2012/7/12 shan kang :
> Hello,
>I wonder why smp_mb() is not needed in the "__mutex_fastpath_lock"
> and "__mutex_fastpath_unlock" functions which are located in the
> "arch/arm/include/asm/mutex.h"?
>I think "dmb" instruction is necessary there.
Why necessary? Could you explain
On Thursday, July 12, 2012 2:55 PM, Vivek Gautam wrote:
>
> This patch adds support to parse probe data for
> ehci driver for exynos using device tree
>
> Signed-off-by: Thomas Abraham
> Signed-off-by: Abhilash Kesavan
> Signed-off-by: Vivek Gautam
>
> diff --git a/drivers/usb/host/ehci-s5p.c
On Thursday, July 12, 2012 2:55 PM, Vivek Gautam wrote:
>
> This patch adds support to parse probe data for
> ohci driver for exynos using device tree.
>
> Signed-off-by: Thomas Abraham
> Signed-off-by: Abhilash Kesavan
> Signed-off-by: Vivek Gautam
>
> diff --git a/drivers/usb/host/ohci-exyn
On Fri, Jul 13, 2012 at 7:33 AM, Joe Perches wrote:
> Convert the existing uses of random_ether_addr to
> the new eth_random_addr.
>
> Signed-off-by: Joe Perches
For the rt2x00 parts:
Acked-by: Gertjan van Wingerde
> ---
> drivers/net/wireless/adm8211.c |2 +-
> drivers/net/w
2012/07/13 1:50, Toshi Kani wrote:
On Thu, 2012-07-12 at 20:28 +0900, Yasuaki Ishimatsu wrote:
acpi_bus_trim() stops removing devices, when acpi_bus_remove() return error
number. But acpi_bus_remove() cannot return error number correctly.
acpi_bus_remove() only return -EINVAL, when dev argument
* Kukjin Kim [120712 15:13]:
>
> +1 same here, I'm interested in ARM mini-summit :)
Yeah me too!
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.htm
Hi Miklos,
Thank you for your comments.
(2012/07/12 19:13), Miklos Szeredi wrote:
HAYASAKA Mitsuo writes:
Hi Yuan and Han-Wen,
Thank you for your comments.
(2012/07/06 22:58), Han-Wen Nienhuys wrote:
On Fri, Jul 6, 2012 at 2:53 AM, Liu Yuan wrote:
On 07/05/2012 06:50 PM, Mitsuo Hayasak
On Fri, 2012-07-13 at 09:51 +0800, Zhang Rui wrote:
> On 四, 2012-07-12 at 04:54 -0600, R, Durgadoss wrote:
> > Hi,
> >
> > > -Original Message-
> > > From: Wei Ni [mailto:w...@nvidia.com]
> > > Sent: Thursday, July 12, 2012 3:53 PM
> > > To: Zhang, Rui; Brown, Len; a...@linux-foundation.or
On Do, 12.07.2012, 23:35, Stephen Hemminger wrote:
> On Thu, 12 Jul 2012 22:55:57 +0200
> "Piotr Sawuk" wrote:
>
>> + * Federico D. Sacerdoti: Added TCP health monitoring.
>
> Please don't do this.
> The kernel community no longer maintains a list of contributors
> in the comments. The h
Hi Pantelis,
In case you do not know the process of ARM core patches. You need to
put the patch into Russell's patch system [1] after review gets done.
Then the patch will show up on Russell's git tree.
Regards,
Shawn
[1] http://www.arm.linux.org.uk/developer/patches/
On Fri, May 25, 2012 at 0
On 五, 2012-07-13 at 15:30 +0800, Wei Ni wrote:
> On Fri, 2012-07-13 at 09:51 +0800, Zhang Rui wrote:
> > On 四, 2012-07-12 at 04:54 -0600, R, Durgadoss wrote:
> > > Hi,
> > >
> > > > -Original Message-
> > > > From: Wei Ni [mailto:w...@nvidia.com]
> > > > Sent: Thursday, July 12, 2012 3:53
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. The changes are limited to
adding new VID/PID combinations to drivers to enable support for new
versions of hardware, most notably hardware found
BCM63XX implements the clk interface, but does not advertise it.
Signed-off-by: Jonas Gorski
---
This fixes a build failure in linux-next caused by
5afae362dc79cb8b6b3965422d13d118c63d4ee4 ("clk: Add non CONFIG_HAVE_CLK
routines"):
CC arch/mips/bcm63xx/clk.o
arch/mips/bcm63xx/clk.c:285:5
Hi Ted,
Did you get time to check this patch?
If possible, can you collect the patch from the last sent mail?
On Tue, Jul 10, 2012 at 9:56 PM, Ashish Sangwan
wrote:
> Whether to continue removing extents or not is decided by the return value
> of function ext4_ext_more_to_rm() which checks 2 cond
Am Freitag, den 13.07.2012, 02:16 +0300 schrieb Michael S. Tsirkin:
> My concern was people will ask for more and more stuff that pci
> sysfs already has.
> If we do add these is there a way to not duplicate code from pci?
I have some concerns about the placing for the BAR mapping code inside
the
Use 'u32' for the LLI structure members, which are defined by hardware to be
32-bit. dma_addr_t is much more vague about its actual size.
Signed-off-by: Andy Shevchenko
---
drivers/dma/dw_dmac.c |7 ++-
drivers/dma/dw_dmac_regs.h |6 +++---
2 files changed, 5 insertions(+), 8 de
Signed-off-by: Andy Shevchenko
---
drivers/dma/dw_dmac.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/dw_dmac.c b/drivers/dma/dw_dmac.c
index 9151511..db56ef4 100644
--- a/drivers/dma/dw_dmac.c
+++ b/drivers/dma/dw_dmac.c
@@ -413,7 +413,7 @@ static void dwc_s
The default values are filled to support at least mem-to-mem tests provided by
dmatest module. It makes sense to choose the 4 bytes (2 least significant bits)
alignment by the default.
Signed-off-by: Andy Shevchenko
---
drivers/dma/dw_dmac.c |6 ++
1 file changed, 6 insertions(+)
diff -
On Fri, 2012-07-13 at 15:41 +0800, Zhang Rui wrote:
> On 五, 2012-07-13 at 15:30 +0800, Wei Ni wrote:
> > Our tegra thermal framework also will use the generic thermal layer. It
> > will register the cooling device, and run the throttling in this generic
> > framework.
> > But we have a special mech
* Oleg Nesterov [2012-07-08 22:30:11]:
> Kill insert_vm_struct()->uprobe_mmap(). It is not needed, nobody
> except arch/ia64/kernel/perfmon.c uses insert_vm_struct(vma) with
> vma->vm_file != NULL.
>
Right, but somebody else might start using this later.
I cant think of a use case though.
> An
On Thu, Jun 28, 2012 at 01:59:19PM +0300, Mika Westerberg wrote:
> This is similar than what is done for other busses before (PCI, I2C, SPI,
> platform). It reduces a lot of unnecessary boilerplate code from modules.
>
> We also remove following redundant check on few drivers:
>
> if (acpi_
* Oleg Nesterov [2012-07-08 22:30:08]:
> Kill copy_vma()->uprobe_mmap(new_vma), it is absolutely wrong.
>
> This new_vma was just initialized to represent the new unmapped area,
> [vm_start, vm_end) was returned by get_unmapped_area() in the caller.
>
> This means that uprobe_mmap()->get_user_p
On Thu 12-07-12 15:42:53, Hugh Dickins wrote:
> On Thu, 12 Jul 2012, Andrew Morton wrote:
> > On Thu, 12 Jul 2012 09:05:01 +0200
> > Michal Hocko wrote:
> >
> > > When we are back to the patch. Is it going into 3.5? I hope so and I
> > > think it is really worth stable as well. Andrew?
> >
> > W
Hi,
looks like [1] is fixing my suspend/resume problem with v3.5-rc6+
(attached call-trace is with a v3.5-rc6 kernel before the commit got
upstream).
Thanks for the fix!
I am wondering if those new-lines are intended (see attachment)?
- Sedat -
P.S.: Commit details
commit dc332fdf9f373a87b1e2f
It would be nice to keep spear-devel in cc, as this is the second
platform that uses this driver.
On Fri, Jul 13, 2012 at 9:09 AM, Andy Shevchenko
wrote:
> The default values are filled to support at least mem-to-mem tests provided by
> dmatest module. It makes sense to choose the 4 bytes (2 leas
On Fri, Jul 13, 2012 at 9:09 AM, Andy Shevchenko
wrote:
> Signed-off-by: Andy Shevchenko
> ---
> drivers/dma/dw_dmac.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/dw_dmac.c b/drivers/dma/dw_dmac.c
> index 9151511..db56ef4 100644
> --- a/drivers/dma/dw_
On Fri, Jul 13, 2012 at 9:09 AM, Andy Shevchenko
wrote:
> Use 'u32' for the LLI structure members, which are defined by hardware to be
> 32-bit. dma_addr_t is much more vague about its actual size.
>
> Signed-off-by: Andy Shevchenko
> ---
> drivers/dma/dw_dmac.c |7 ++-
> drivers/dm
Hi Joe,
> On 13 July 2012 07:13, Joe Perches wrote:
>
> The @smsc.com email address is bouncing.
> Should it be removed from MAINTAINERS or switched to this
> @shawell.net address?
It should be changed, I posted a patch to do this back in April - I guess
it didn't get picked up. Did I need to C
On 13/07/12 08:58, Jonas Gorski wrote:
> BCM63XX implements the clk interface, but does not advertise it.
>
> Signed-off-by: Jonas Gorski
> ---
>
> This fixes a build failure in linux-next caused by
> 5afae362dc79cb8b6b3965422d13d118c63d4ee4 ("clk: Add non CONFIG_HAVE_CLK
> routines"):
>
> CC
When populate pages across a mem boundary at bootup, the page count
populated isn't correct. This is due to mem populated to non-mem
region and ignored.
Pfn range is also wrongly aligned when mem boundary isn't page aligned.
-v2: If xen_do_chunk fail(populate), abort this chunk and any others.
S
On Wed, May 30, 2012 at 11:43:05AM +0200, Karol Lewandowski wrote:
> This commit fixes warning introduced in 27452498a ("i2c-s3c2410: Rework
> device type handling"):
>
> drivers/i2c/busses/i2c-s3c2410.c: In function 's3c24xx_get_device_quirks':
> drivers/i2c/busses/i2c-s3c2410.c:125: warning:
This patchset implements bio-based IO path for virito-blk to improve
performance.
Fio test shows bio-based IO path gives the following performance improvement:
1) Ramdisk device
With bio-based IO path, sequential read/write, random read/write
IOPS boost : 28%, 24%, 21%, 16%
This patch introduces bio-based IO path for virtio-blk.
Compared to request-based IO path, bio-based IO path uses driver
provided ->make_request_fn() method to bypasses the IO scheduler. It
handles the bio to device directly without allocating a request in block
layer. This reduces the IO path in
On Thu, Jul 12, 2012 at 10:02 PM, Bjorn Helgaas wrote:
> Why don't you fix this right where the problem occurs, in
> __reserve_region_with_split(), with something like this:
>
> if (end > conflict->start && conflict->start > start)
> __reserve_region_with_split(root, start
Split the mapping code in blk_rq_map_sg() to a helper
__blk_segment_map_sg(), so that other mapping function, e.g.
blk_bio_map_sg(), can share the code.
Cc: Jens Axboe
Cc: Tejun Heo
Cc: Shaohua Li
Cc: linux-kernel@vger.kernel.org
Suggested-by: Tejun Heo
Suggested-by: Jens Axboe
Signed-off-by:
Add a helper to map a bio to a scatterlist, modelled after
blk_rq_map_sg.
This helper is useful for any driver that wants to create
a scatterlist from its ->make_request_fn method.
Changes in v2:
- Use __blk_segment_map_sg to avoid duplicated code
- Add cocbook style function comment
Cc: Jens
On Fri, Jul 13, 2012 at 11:26 AM, viresh kumar wrote:
> It would be nice to keep spear-devel in cc, as this is the second
> platform that uses this driver.
I used to get the list of recipients via get_maintainer script. Will
try to not forget about that address in the future.
>> The default value
Even if cpu_down() fails, acpi_processor_remove() continues to remove the cpu.
But in this case, it should return error number since some process may run on
the cpu. If the cpu has a running process and the cpu is turned the power off,
the system may not work well.
Reviewed-by: Srivatsa S. Bhat
S
Hello,
[I added git@vger.k.o to Cc: please strip the recipents accordingly if
you reply.]
On Fri, Jul 13, 2012 at 09:02:56AM +1000, Marc Reilly wrote:
> Hi Uwe,
>
> > This series was tested on a Phytec pcm038 (mc13783 on spi) using
> > traditional boot (i.e. not dt) and on a i.MX53 based machine
Even if acpi_processor_handle_eject() offlines cpu, there is a chance
to online the cpu after that. So the patch closes the window by using
get/put_online_cpus().
Why does the patch change _cpu_up() logic?
The patch cares the race of hot-remove cpu and _cpu_up(). If the patch
does not change it,
acpi_bus_trim() stops removing devices, when acpi_bus_remove() return error
number. But acpi_bus_remove() cannot return error number correctly.
acpi_bus_remove() only return -EINVAL, when dev argument is NULL. Thus even if
device cannot be removed correctly, acpi_bus_trim() ignores and continues to
Hi folks,
[I am resending to fix the broken thread in the previous one.]
This patchset adds vhost-blk support. vhost-blk is a in kernel virito-blk
device accelerator. Compared to userspace virtio-blk implementation, vhost-blk
gives about 5% to 15% performance improvement.
Asias He (5):
aio: E
This is useful for people who want to create an eventfd in kernel,
e.g. vhost-blk.
Cc: Alexander Viro
Cc: Jeff Moyer
Cc: Michael S. Tsirkin
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: k...@vger.kernel.org
Cc: virtualizat...@lists.linux-foundation.org
Signed-off-by: As
vhost-blk is a in kernel virito-blk device accelerator.
This patch is based on Liu Yuan's implementation with various
improvements and bug fixes. Notably, this patch makes guest notify and
host completion processing in parallel which gives about 60% performance
improvement compared to Liu Yuan's i
This is useful for people who want to use aio in kernel, e.g. vhost-blk.
Cc: Benjamin LaHaise
Cc: Alexander Viro
Cc: Jeff Moyer
Cc: James Bottomley
Cc: Michael S. Tsirkin
Cc: linux-...@kvack.org
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: k...@vger.kernel.org
Cc: vi
vhost-net's feature does not deseve the name VHOST_FEATURES. Use
VHOST_NET_FEATURES instead.
Cc: Michael S. Tsirkin
Cc: linux-kernel@vger.kernel.org
Cc: k...@vger.kernel.org
Cc: virtualizat...@lists.linux-foundation.org
Signed-off-by: Asias He
---
drivers/vhost/net.c |4 ++--
drivers/vhos
On 13/07/12 09:45, Andy Shevchenko wrote:
>> > To understand it more, what does this mean? We will not support
>> > transfers with unaligned
>> > addresses/length to word size?
> The dmatest module uses those constants to get source, destination
> addresses and length of the test data aligned. On t
Currently, vhost-net is the only consumer of vhost infrastructure. So
vhost infrastructure and vhost-net driver are in a single module.
Separating this as a vhost.ko module and a vhost-net.ko module makes it
is easier to share code with other vhost drivers, e.g. vhost-blk.ko,
tcm-vhost.ko.
Cc: Mi
On Thu, Jul 12, 2012 at 8:40 PM, Valentin, Eduardo
wrote:
> Amit,
>
> On Thu, Jul 12, 2012 at 4:41 PM, Amit Daniel Kachhap
> wrote:
>> This patchset introduces a new generic cooling device based on cpufreq
>> that can be used on non-ACPI platforms. As a proof of concept, we have
>> drivers for t
At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
> sysfs files are created. But there is no code to remove these files. The patch
> implements the function to remove them.
>
> Note : The code does not free firmware_ma
For example, in the following scenario, Process2 may get the wrong value;
Process1:
mutex_lock(&lock);
write data; (store operation)
mutex_unlock(&lock);
Process2:
mutex_lock(&lock);
read data; (load operation)
mutex_unlock(&lock);
Suppose Process1 gets the lock first, write data and unlock. If
On 12 July 2012 18:24, Thomas Abraham wrote:
> Some platforms allow for clock gating and control of bus interface unit clock
> and card interface unit clock. Add support for clock lookup of optional biu
> and ciu clocks for clock gating and clock speed determination.
>
> Signed-off-by: Abhilash Ke
On Thu, Jul 12, 2012 at 10:02:42AM -0700, Paul E. McKenney wrote:
> On Fri, Jul 13, 2012 at 12:57:38AM +0800, Fengguang Wu wrote:
> > On Thu, Jul 12, 2012 at 09:43:08AM -0700, Paul E. McKenney wrote:
> > > On Wed, Jul 11, 2012 at 12:49:24AM -0700, Paul E. McKenney wrote:
> > > > On Tue, Jul 10, 201
From: "G.Shark Jeong"
LM3554 :
The LM3554 is a 2 MHz fixed-frequency synchronous boost
converter with 1.2A dual high side led drivers.
Datasheet: www.ti.com
G.Shark Jeong (1):
leds: Add LED driver for lm3554 chip
drivers/leds/Kconfig |8 +
drivers/leds/Makefile
From: "G.Shark Jeong"
LM3554 :
The LM3554 is a 2 MHz fixed-frequency synchronous boost
converter with 1.2A dual high side led drivers.
Datasheet: www.ti.com
Signed-off-by: G.Shark Jeong
---
drivers/leds/Kconfig |8 +
drivers/leds/Makefile |1 +
This patch is a driver for SiS964 I2C bus.
It was forked from i2c-sis630 and modified with SiS datasheets.
Tested with kmemleak.
Signed-off-by: Amaury Decrême
---
Documentation/i2c/busses/i2c-sis964 | 34 ++
MAINTAINERS | 16 +
drivers/i2c/busses/Kconfig |
On 07/13/2012 05:19 AM, Rob Herring wrote:
What's implemented in Linux should not define the binding. The binding
should describe the hardware.
[...]
True, but not your problem to implement. A binding doesn't necessarily
mean there is a full Linux implementation. We just don't want to create
some
On Fri, Jul 13, 2012 at 10:10:52AM +0100, shan kang wrote:
> For example, in the following scenario, Process2 may get the wrong value;
> Process1:
> mutex_lock(&lock);
> write data; (store operation)
> mutex_unlock(&lock);
>
> Process2:
> mutex_lock(&lock);
> read data; (load operation)
> mutex_u
Hi,
while dealing with [1], I saw this mei-related infos in dmesg when
doing a suspend + resume (see [1] for more logs):
[17046.348467] [] mei_pci_suspend+0x78/0xd0 [mei]
[17047.460315] mei :00:16.0: irq 47 for MSI/MSI-X
[17047.460512] mei :00:16.0: request_threaded_irq failed: irq = 47.
On Thu, Jul 05, 2012 at 05:02:12PM -0700, Colin Cross wrote:
[...]
> KGDB can obviously only be enabled on development
> devices, although perhaps a more limited KDB could be left enabled.
Um, I would argue about 'obviously'. :-) It doesn't require
CONFIG_DEBUG_INFO (-g) or something like this, so
On Fri, 13 Jul 2012, Mike Galbraith wrote:
> On Thu, 2012-07-12 at 15:31 +0200, Thomas Gleixner wrote:
> > Bingo, that makes it more likely that this is caused by copying w/o
> > initializing the lock and then freeing the original structure.
> >
> > A quick check for memcpy finds that __btrfs_clo
On Fri, Jul 13, 2012 at 05:43:30AM +, AnilKumar, Chimata wrote:
> Thanks much, are you going to push reset of the patches in this series?
No, there's no dependency so I'd expect them to be applied by the
architecture maintainers.
signature.asc
Description: Digital signature
On Fri, 2012-07-13 at 16:11 +0800, Wei Ni wrote:
> On Fri, 2012-07-13 at 15:41 +0800, Zhang Rui wrote:
> > On 五, 2012-07-13 at 15:30 +0800, Wei Ni wrote:
> > > Our tegra thermal framework also will use the generic thermal layer. It
> > > will register the cooling device, and run the throttling in t
Yes, a customer reported an issue to me.
After my investigation, I found the problem may be the lack of "dmb"
in mutex_lock and mutex_unlock functions.
Moreover, the issue could be resolved after the "dmb" was added.
2012/7/13 Will Deacon :
> On Fri, Jul 13, 2012 at 10:10:52AM +0100, shan kang wro
On Thu, 12 Jul 2012, Chris Mason wrote:
> On Thu, Jul 12, 2012 at 05:07:58AM -0600, Thomas Gleixner wrote:
> > On Thu, 12 Jul 2012, Mike Galbraith wrote:
> > > crash> struct rt_mutex 0x8801770601c8
> > > struct rt_mutex {
> > > wait_lock = {
> > > raw_lock = {
> > > slock = 7966
> >
Hi,
On Fri, 13 Jul 2012 00:33:07 +0300, Sami Liedes wrote:
> Hi,
>
> Kernel 3.4.4 with kmemcheck enabled does not correctly boot on my
> system, which is a x86-64, Core i7 Sandy Bridge computer with Asus
> P8P67-EVO motherboard. The errors seem to be related to ACPI, but
> there may be other thin
On Fri, Jul 13, 2012 at 11:56 AM, viresh kumar wrote:
> I wanted to ask, will normal memcpy for anybody will work with unaligned
> addresses
> with this patch? I believe they will.
Hmm... I just rechecked and it seems it works without this patch. I
didn't remember why this patch still in my pool.
2012/7/13 Andrew Morton :
> On Thu, 12 Jul 2012 20:04:53 +0900
> Akinobu Mita wrote:
>
>> The function dup_task() may fail at the following function calls in
>> the following order.
>>
>> 0) alloc_task_struct_node()
>> 1) alloc_thread_info_node()
>> 2) arch_dup_task_struct()
>>
>> Error by 0) is n
On Fri, Jul 13, 2012 at 11:47 AM, Sedat Dilek wrote:
> Hi,
>
> while dealing with [1], I saw this mei-related infos in dmesg when
> doing a suspend + resume (see [1] for more logs):
>
> [17046.348467] [] mei_pci_suspend+0x78/0xd0 [mei]
> [17047.460315] mei :00:16.0: irq 47 for MSI/MSI-X
> [17
On 07/13/2012 11:43 AM, Christian Borntraeger wrote:
On 13/07/12 05:35, Raghavendra K T wrote:
maybe define static inline access functions in kvm_host.h that are no-ops
if CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT is not set.
As I already said, can you have a look at using access functions?
Yes. w
On Fri, 2012-07-13 at 11:52 +0200, Thomas Gleixner wrote:
> On Fri, 13 Jul 2012, Mike Galbraith wrote:
> > On Thu, 2012-07-12 at 15:31 +0200, Thomas Gleixner wrote:
> > > Bingo, that makes it more likely that this is caused by copying w/o
> > > initializing the lock and then freeing the original
> -Original Message-
> From: Sedat Dilek [mailto:sedat.di...@gmail.com]
> Sent: Friday, July 13, 2012 12:48 PM
> To: Winkler, Tomas
> Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Roland Dreier
> Subject: [3.5-rc6+] mei: irq: request_threaded_irq is missing the
> IRQF_ONESHOT flag
>
> H
Hi all,
Here is v2 for the KGDB FIQ debugger, the changes include:
- Per Colin Cross' suggestion, we should not enter the debugger on any
received byte (this might be a problem when there's a noise on the
serial line). So there is now an additional patch that implements
"knocking" to the KD
Currently kernel never set KGDB_REASON_NMI. We do now, when we enter
KGDB/KDB from an NMI.
This is not to be confused with kgdb_nmicallback(), NMI callback is
an entry for the slave CPUs during CPUs roundup, but REASON_NMI is the
entry for the master CPU.
Signed-off-by: Anton Vorontsov
---
kern
The FIQ debugger may be used to debug situations when the kernel stuck
in uninterruptable sections, e.g. the kernel infinitely loops or
deadlocked in an interrupt or with interrupts disabled.
By default KGDB FIQ is disabled in runtime, but can be enabled with
kgdb_fiq.enable=1 kernel command line
As Colin Cross noticed, serial ports could be noisy, so occasional
characters once in a while are possible. So, considering the noise
possibility, entering the debugger on any received byte is unacceptable
for production devices.
This changes KGDB FIQ behaviour in a such way so that we have to typ
If enabled, kernel will able to enter KGDB upon serial line activity on
UART ports.
Note that even with this patch and CONFIG_KGDB_FIQ is enabled, you still
need to pass kgdb_fiq.enable=1 kernel command line option, otherwise UART
will behave in a normal way.
By default UART0 is used, but this ca
This makes the code more izolated.
The downside of this is that we now have an additional branch and the
code itself is 8 bytes longer. But on the bright side, this new layout
can be more cache friendly since cr_alignment address might be already
in the cache line (not that I measured anything, it
Just a couple of calls to manage VIC FIQ routing. We'll use them for
KGDB FIQ support on ARM Versatile machines.
Signed-off-by: Anton Vorontsov
---
arch/arm/common/vic.c | 28
arch/arm/include/asm/hardware/vic.h |2 ++
2 files changed, 30 insertio
The new arch callback should manage NMIs that usually cause KGDB to
enter. That is, not all NMIs should be enabled/disabled, but only
those that issue kgdb_handle_exception().
We must mask it as serial-line interrupt can be used as an NMI, so
if the original KGDB-entry cause was say a breakpoint,
Just move the macros into header file as we would want to use them for
KGDB FIQ entry code.
The following macros were moved:
- svc_entry
- usr_entry
- kuser_cmpxchg_check
- vector_stub
To make kuser_cmpxchg_check actually work across different files, we
also have to make kuser_cmpxchg64_fixu
From: fangxiaozhi
1. This patch is based on the kernel of 3.5-rc6
2. In this patch, we add new micro for matching the series USB devices with
vendor ID and interface information.
3. In this patch, we add new declarations into option.c to support the new
interfaces of Huawei Data Card devices.
S
Il 04/10/2011 21:34, Greg KH ha scritto:
> diff --git a/drivers/staging/hv/hyperv_vmbus.h b/drivers/hv/hyperv_vmbus.h
> similarity index 99%
> rename from drivers/staging/hv/hyperv_vmbus.h
> rename to drivers/hv/hyperv_vmbus.h
> index 3d2d836..8261cb6 100644
> --- a/drivers/staging/hv/hyperv_vmbus.
On Fri, 2012-07-13 at 09:30 +0100, Steve Glendinning wrote:
> > On 13 July 2012 07:13, Joe Perches wrote:
> > The @smsc.com email address is bouncing.
> > Should it be removed from MAINTAINERS or switched to this
> > @shawell.net address?
>
> It should be changed, I posted a patch to do this back
On Fri, 13 Jul 2012, Mike Galbraith wrote:
> On Fri, 2012-07-13 at 11:52 +0200, Thomas Gleixner wrote:
> > On Fri, 13 Jul 2012, Mike Galbraith wrote:
> > > On Thu, 2012-07-12 at 15:31 +0200, Thomas Gleixner wrote:
> > > > Bingo, that makes it more likely that this is caused by copying w/o
> > > >
On Fri, Jul 13, 2012 at 12:15 PM, Winkler, Tomas
wrote:
>
>
>> -Original Message-
>> From: Sedat Dilek [mailto:sedat.di...@gmail.com]
>> Sent: Friday, July 13, 2012 12:48 PM
>> To: Winkler, Tomas
>> Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Roland Dreier
>> Subject: [3.5-rc6+] mei: ir
On 13/07/12 11:04, Andy Shevchenko wrote:
> On Fri, Jul 13, 2012 at 11:56 AM, viresh kumar wrote:
>> I wanted to ask, will normal memcpy for anybody will work with unaligned
>> addresses
>> with this patch? I believe they will.
> Hmm... I just rechecked and it seems it works without this patch. I
On Fri, Jul 13, 2012 at 1:30 PM, viresh kumar wrote:
> Sorry, got confused now. What works without this patch? And what doesn't work
> without it?
It seems this patch is redundant.
--
With Best Regards,
Andy Shevchenko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
> acpi_memory_device_remove() has been prepared to remove physical memory.
> But, the function only frees acpi_memory_device currentlry.
>
> The patch adds following functions into acpi_memory_device_remove():
> - offline memory
> - remove physi
On Thu, Jul 12, 2012 at 09:59:49AM +0100, Andrew Morton wrote:
> > >
> > > Could we do this purely in Kconfig? Add a new
> > > CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION and always set it true if
> > > CONFIG_ARCH_WANT_OLD_COMPAT_IPC?
[...]
> It would be best to change both as a separate patch.
On Fri, Jul 13, 2012 at 12:29 PM, Sedat Dilek wrote:
> On Fri, Jul 13, 2012 at 12:15 PM, Winkler, Tomas
> wrote:
>>
>>
>>> -Original Message-
>>> From: Sedat Dilek [mailto:sedat.di...@gmail.com]
>>> Sent: Friday, July 13, 2012 12:48 PM
>>> To: Winkler, Tomas
>>> Cc: Thomas Gleixner; LKML;
Although for the most part, the AB8500 uses common bindings, some
of the ways in which they are used differ slightly to the common
uses of those bindings. To clear up some of these varying concepts
we provide some documentation describing each of the properties and
how they are used.
Signed-off-by
Doing some enhancements in the tps6586x core driver which is
based on some recent driver framework enhancements.
Following are highlights of changes:
- Use devm for allocation to remove the code for freeing it.
- Use regmap i2c for register access in place of direct i2c apis.
This will give the d
To cache the interrupt mask register, use the regmap RB_TREE
cache-ing mechanism in place of implementing it locally.
Signed-off-by: Laxman Dewangan
---
drivers/mfd/tps6586x.c | 24
1 files changed, 16 insertions(+), 8 deletions(-)
diff --git a/drivers/mfd/tps6586x.c
Converting the gpio driver of tps6586x to a platform
driver in place of registering the gpio through core
driver.
The motivation of the change is:
- This is inline with the mfd drivers implementation.
- This will move the related gpio support to gpio driver
folder where all gpio related drivers a
The GPIO functionality of device tps6586x is added through
platform gpio driver and it can be register as the mfd sub
device and hence removing the duplicates code which register
the gpio functionality from core driver.
Signed-off-by: Laxman Dewangan
---
drivers/mfd/Kconfig|2 +-
drivers
On Fri, Jul 13, 2012 at 04:26:26AM -0600, Thomas Gleixner wrote:
> On Fri, 13 Jul 2012, Mike Galbraith wrote:
> > On Fri, 2012-07-13 at 11:52 +0200, Thomas Gleixner wrote:
> > > On Fri, 13 Jul 2012, Mike Galbraith wrote:
> > > > On Thu, 2012-07-12 at 15:31 +0200, Thomas Gleixner wrote:
> > > > >
Allocate memory for device state using devm_kzalloc(), get the
IRQ using devm_request_irq().
All to simplify accounting and letting the kernel do the
garbage-collection.
Signed-off-by: Laxman Dewangan
---
drivers/mfd/tps6586x.c | 23 ---
1 files changed, 8 insertions(+), 15
Using regmap apis for accessing the device registers.
Signed-off-by: Laxman Dewangan
---
drivers/mfd/Kconfig|1 +
drivers/mfd/tps6586x.c | 157 ++--
2 files changed, 47 insertions(+), 111 deletions(-)
diff --git a/drivers/mfd/Kconfig b/driver
1 - 100 of 408 matches
Mail list logo
