Ping...
Thanks,
Feng
> -Original Message-
> From: Wu, Feng
> Sent: Wednesday, December 03, 2014 3:39 PM
> To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
> g...@kernel.org; pbonz...@redhat.com; dw...@infradead.org;
> j...@8bytes.org; alex.william...@redhat.com;
On Fri, Dec 05, 2014 at 06:53:03PM +, Catalin Marinas wrote:
> On Fri, Dec 05, 2014 at 06:39:45PM +, Catalin Marinas wrote:
> >
> > Does your system have an L2 cache? What's the SoC topology, can PCIe see
> > such L2 cache (or snoop the L1 caches)?
>
> BTW, if you really have a PL310-like
On 2014-12-08 at 14:36:24 +0100, Pramod Gurav
wrote:
> Folder soc/ was sourced twice somehow. Remove duplicate entry.
I already sent a patch for this a while ago [1], though it wasn't
applied yet.
[1] http://thread.gmane.org/gmane.linux.kernel/1831623
--
To unsubscribe from this list: send the
Hi list,
On platforms which has native usb hosts/phys and pci-dwc3 controller, the dwc3
core may get the wrong usb2_phy and usb3_phy by devm_usb_get_phy(). It depends
on which usb phy driver is initialized firstly, the usb_phy_generic or the
native/real usb phy driver.
Before all old USB phy libr
Hi,
On Fri, 5 Dec 2014, Alexander Graf wrote:
> I don't have a full distribution for you yet, but we'll start to switch
> to the 2.25 branch soon.
>
> Michael, what are you plans on when a first armv7 Factory build based on
> 2.25 would be available?
2.25 isn't released yet, but I just submit
Still using outlook, but will limit the line length, I hope that works for the
moment. Attached is a log with the requested information, it is a little
bit non-standard though. The dump code from the mm was copied in
the driver and called from there, mapping the prints back to our local
printf, but
Thanks. :-)
On Mon, Dec 8, 2014 at 7:08 PM, Tobias Klauser wrote:
> On 2014-12-08 at 14:36:24 +0100, Pramod Gurav
> wrote:
>> Folder soc/ was sourced twice somehow. Remove duplicate entry.
>
> I already sent a patch for this a while ago [1], though it wasn't
> applied yet.
>
> [1] http://thread
On 2014/12/8 21:22, Jon Medhurst (Tixy) wrote:
> On Mon, 2014-12-08 at 20:31 +0800, Wang Nan wrote:
>> On 2014/12/8 20:06, Wang Nan wrote:
>>> On 2014/12/8 19:50, Jon Medhurst (Tixy) wrote:
On Mon, 2014-12-08 at 19:15 +0800, Wang Nan wrote:
> On 2014/12/8 19:04, Jon Medhurst (Tixy) wrote:
On Mon, 08 Dec 2014, Arnd Bergmann wrote:
> On Monday 08 December 2014 13:00:09 Lee Jones wrote:
> > On Mon, 08 Dec 2014, Arnd Bergmann wrote:
> >
> > > On Monday 08 December 2014 12:06:19 Stephen Rothwell wrote:
> > > > Hi Stephen,
> > > >
> > > > Today's linux-next merge of the bcm2835 tree go
Hi Lee,
On Thu, 04 Dec 2014, Lee Jones wrote:
> ST's Common Clk Framework is now available. This patch ensures the FSM
> makes use of it by obtaining and enabling the EMI clock if provided. If
> system fails to provide the EMI clock FSM uses its original default
> rate.
I'm not sure I understa
On Mon, 8 Dec 2014 14:27:01 +1100
Anton Blanchard wrote:
> I have a busy ppc64le KVM box where guests sometimes hit the infamous
> "kernel BUG at kernel/smpboot.c:134!" issue during boot:
>
> BUG_ON(td->cpu != smp_processor_id());
>
> Basically a per CPU hotplug thread scheduled on the wrong C
On 12/08/2014 02:22 PM, Arnd Bergmann wrote:
On Monday 08 December 2014 12:53:30 Lee Jones wrote:
This is a new driver which controls the SPI component of ST's
Synchronous Serial Controller (SSC).
How does this related to the i2c driver for drivers/i2c/busses/i2c-st.c?
Could you have the same
Hi Lee,
> On Thu, 04 Dec 2014, Lee Jones wrote:
>
> > ST's Common Clk Framework is now available. This patch ensures the FSM
> > makes use of it by obtaining and enabling the EMI clock if provided. If
> > system fails to provide the EMI clock FSM uses its original default
> > rate.
>
>
>
> I'm
On Fri, Dec 05, 2014 at 12:13:18AM +0100, Peter Hüwe wrote:
> Am Mittwoch, 3. Dezember 2014, 03:28:35 schrieb Stefan Berger:
> > On 12/02/2014 05:31 PM, Jarkko Sakkinen wrote:
> > > +
> > > +/**
> > > + * tpm2_startup() - send startup command to the TPM chip
> > > + * @chip:TPM chip
This adds support for Diolan DLN2 USB-SPI adapter.
Information about the USB protocol interface can be found in the
Programmer's Reference Manual [1], see section 5.4.6 for the SPI
master module commands and responses.
[1] https://www.diolan.com/downloads/dln-api-manual.pdf
Signed-off-by: Lauren
From: Masami Hiramatsu
Pass the original kprobe for preparing an optimized kprobe arch-dep
part, since for some architecture (e.g. ARM32) requires the information
in original kprobe.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Wang Nan
---
arch/x86/kernel/kprobes/opt.c | 3 ++-
include/lin
This patch prohibits probing instructions for which the stack
requirements are unable to be determined statically. Some test cases
are found not work again after the modification, this patch also
removes them.
Signed-off-by: Wang Nan
Reviewed-by: Jon Medhurst
v1 -> v2:
- Use MAX_STACK_SIZE mac
This is v15 patch series of kprobeopt related code. V14 uses
stop_machine() incorrectly, this version fixes it.
Previous discussion can be found from:
https://lkml.org/lkml/2014/12/8/21
https://lkml.org/lkml/2014/12/4/942
https://lkml.org/lkml/2014/12/4/4
https://lkml.org/lkml/2014/12/1/64
https:
In discussion on LKML (https://lkml.org/lkml/2014/11/28/158), Russell
King suggests to move all probe related code to arch/arm/probes. This
patch does the work. Due to dependency on 'arch/arm/kernel/patch.h', this
patch also moves patch.h to 'arch/arm/include/asm/patch.h', and related
'#include' di
This patch introdces 'checker' to decoding phase, and calls checkers
when instruction decoding. This allows further decoding for specific
instructions. This patch introduces a stub call of checkers in kprobe
arch_prepare_kprobe() as an example and for further expansion.
Signed-off-by: Wang Nan
R
From: Jon Medhurst
These have extra 'checker' functions associated with them so
lets make sure those get covered by testing.
Signed-off-by: Jon Medhurst
Signed-off-by: Wang Nan
v1 -> v2:
- Move to arch/arm/probes/ .
---
arch/arm/probes/kprobes/test-arm.c | 17 +++--
arch/arm/p
On Mon, Dec 08, 2014 at 11:05:17PM +1100, Stephen Rothwell wrote:
> Hi Mark,
>
> After merging the spi tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/spi/spi-dln2.c: In function 'dln2_spi_copy_from_buf':
> drivers/spi/spi-dln2.c:415:4: error: implicit declar
This patch introduce kprobeopt for ARM 32.
Limitations:
- Currently only kernel compiled with ARM ISA is supported.
- Offset between probe point and optinsn slot must not larger than
32MiB. Masami Hiramatsu suggests replacing 2 words, it will make
things complex. Futher patch can make suc
This patch uses the previously introduced checker functionality on
store instructions to record their stack consumption information to
arch_probes_insn.
Signed-off-by: Wang Nan
Signed-off-by: Jon Medhurst
Reviewed-by: Jon Medhurst
v1 -> v2:
- Bugfix and code improvements following Tixy's sugg
On Sat, 6 Dec 2014 16:38:57 -0500
John de la Garza wrote:
> -When the kobject is removed from the kernel (details on how to do that is
> +When the kobject is removed from the kernel (details on how to do that are
Makes sense, applied to the docs tree.
Thanks,
jon
--
To unsubscribe from this li
In discussion on LKML (https://lkml.org/lkml/2014/11/28/158), Russell
King suggests to move all probe related code to arch/arm/probes. This
patch does the work. Due to dependency on 'arch/arm/kernel/patch.h', this
patch also moves patch.h to 'arch/arm/include/asm/patch.h', and related
'#include' di
This is v15 patch series of kprobeopt related code. V14 uses
stop_machine() incorrectly, this version fixes it.
Previous discussion can be found from:
https://lkml.org/lkml/2014/12/8/21
https://lkml.org/lkml/2014/12/4/942
https://lkml.org/lkml/2014/12/4/4
https://lkml.org/lkml/2014/12/1/64
https:
This patch uses the previously introduced checker functionality on
store instructions to record their stack consumption information to
arch_probes_insn.
Signed-off-by: Wang Nan
Signed-off-by: Jon Medhurst
Reviewed-by: Jon Medhurst
---
v1 -> v2:
- Bugfix and code improvements following Tixy's s
On 12/06/2014 02:07 PM, Lad, Prabhakar wrote:
> From: Benoit Parrot
>
> This patch adds Video Processing Front End (VPFE) driver for
> AM437X family of devices
> Driver supports the following:
> - V4L2 API using MMAP buffer access based on videobuf2 api
> - Asynchronous sensor/decoder sub device
On Mon, Dec 08, 2014 at 12:24:27PM +0200, Jani Nikula wrote:
> On Sun, 07 Dec 2014, Julia Lawall wrote:
> > Replace a misspelled function name by %s and then __func__.
> >
> > This was done using Coccinelle, including the use of Levenshtein distance,
> > as proposed by Rasmus Villemoes.
> >
> > Si
This patch introdces 'checker' to decoding phase, and calls checkers
when instruction decoding. This allows further decoding for specific
instructions. This patch introduces a stub call of checkers in kprobe
arch_prepare_kprobe() as an example and for further expansion.
Signed-off-by: Wang Nan
R
This patch introduce kprobeopt for ARM 32.
Limitations:
- Currently only kernel compiled with ARM ISA is supported.
- Offset between probe point and optinsn slot must not larger than
32MiB. Masami Hiramatsu suggests replacing 2 words, it will make
things complex. Futher patch can make suc
From: Masami Hiramatsu
Pass the original kprobe for preparing an optimized kprobe arch-dep
part, since for some architecture (e.g. ARM32) requires the information
in original kprobe.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Wang Nan
---
arch/x86/kernel/kprobes/opt.c | 3 ++-
include/lin
This patch prohibits probing instructions for which the stack
requirements are unable to be determined statically. Some test cases
are found not work again after the modification, this patch also
removes them.
Signed-off-by: Wang Nan
Reviewed-by: Jon Medhurst
---
v1 -> v2:
- Use MAX_STACK_SIZE
From: Jon Medhurst
These have extra 'checker' functions associated with them so
lets make sure those get covered by testing.
Signed-off-by: Jon Medhurst
Signed-off-by: Wang Nan
---
v1 -> v2:
- Move to arch/arm/probes/ .
---
arch/arm/probes/kprobes/test-arm.c | 17 +++--
arch/ar
Compilation with #define STRICT_MM_TYPECHECKS in arch/powerpc/include/asm/page.h
fails due to missing use of pgprot_val() when using pgprot_t objects.
arch/powerpc/mm/pgtable_32.c: In function '__ioremap_caller':
arch/powerpc/mm/pgtable_32.c:185:9: error: invalid operands to binary | (have
'long
This patch fixes a section mismatch warning
WARNING: vmlinux.o(.text+0x213b6): Section mismatch in reference from the
function chrp_init_early() to the variable .init.data:boot_command_line
The function chrp_init_early() references
the variable __initdata boot_command_line.
This is often because
flush_op is unambiguously defined by feature_flush:
REQ_FUA | REQ_FLUSH -> BLKIF_OP_WRITE_BARRIER
REQ_FLUSH -> BLKIF_OP_FLUSH_DISKCACHE
0 -> 0
and thus can be removed. This is just a cleanup.
The patch was suggested by Boris Ostrovsky.
Signed-off-by: Vitaly Kuznetsov
---
The patch is
On Mon, Dec 08, 2014 at 10:32:49AM -0200, Paulo Zanoni wrote:
> 2014-12-08 6:42 GMT-02:00 Daniel Vetter :
> > On Sun, Dec 07, 2014 at 07:29:17PM +0100, Rickard Strandqvist wrote:
> >> Remove the function intel_output_name() that is not used anywhere.
> >>
> >> This was partially found by using a st
On Mon, Dec 08, 2014 at 11:47:46AM +0530, Vinod Koul wrote:
> On Mon, Nov 17, 2014 at 02:41:54PM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > As we discussed a couple of weeks ago, this is the third attempt at
> > creating a generic behaviour for slave capabilities retrieval so that
> > generic lay
On Mon, Dec 08, 2014 at 01:31:35PM +, Viresh Kumar wrote:
> On 8 December 2014 at 18:20, Javi Merino wrote:
> > Is this loop pointless? I seem to recall that it was needed but I
> > forgot the details. If you think it is, I can remove it.
>
> Yes it is pointless. The CPUs you are iterating
Hello,
On Vi, 2014-12-05 at 02:15 +, Jonathan Cameron wrote:
> On 04/12/14 13:00, Teodora Baluta wrote:
> > This patchset adds support for fingerprint sensors through the IIO
> > interface.
> > This way userspace applications collect information in a uniform way. All
> > processing would be d
Linus,
Updates for the ftrace self tests:
o Added kprobes on ftrace testcase
o Sort test cases
o Add file to hold helper functions
o Use logfile name supported by busybox's mktemp
o Clear trace buffer after running kprobe test
o Fix show descriptions when run on dash shell
o Add --verbose
On 12/08/2014 12:20 AM, Paul E. McKenney wrote:
> I have seen this caused by lost IPIs, but you have to lose two of them,
> which seems less than fully likely.
It does seem that it can cause full blown stalls as well, just pretty
rarely (notice the lack of any prints before):
[11373.032327] audit
On Mon, Dec 08, 2014 at 07:00:47PM +0530, Vinod Koul wrote:
> On Mon, Dec 08, 2014 at 10:32:47AM +0100, Ludovic Desroches wrote:
> > On Mon, Dec 08, 2014 at 11:47:46AM +0530, Vinod Koul wrote:
> > > On Mon, Nov 17, 2014 at 02:41:54PM +0100, Maxime Ripard wrote:
> > > > Hi,
> > > >
> > > > As we di
Hi Lee,
On Thu, 04 Dec 2014, Lee Jones wrote:
> From: Christophe Kerello
>
> This patch adds a mask to be able to get the right boot device selection.
Have you seen this series I posted https://lkml.org/lkml/2014/11/19/71?
It is trying to consolodate the way the various STI drivers are handli
On Sun, 7 Dec 2014, Vladimir Davydov wrote:
> diff --git a/mm/slub.c b/mm/slub.c
> index 95d214255663..7ddf01e2a465 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -2450,6 +2450,7 @@ redo:
>
> slab_post_alloc_hook(s, gfpflags, object);
>
> + memcg_kmem_put_cache(s);
> return object
On Fri, Dec 05, 2014 at 07:04:12PM +, Javi Merino wrote:
> From: Dave Martin
>
> If a trace event contains an array, there is currently no standard
> way to format this for text output. Drivers are currently hacking
> around this by a) local hacks that use the trace_seq functionailty
> direc
On 12/08/2014 06:07 AM, Kirill Smelkov wrote:
> In mutex destroy code currently we pass to debug_check_no_locks_freed()
>
> [mem_from, mem_end)
>
> address region. But debug_check_no_locks_freed() accepts
>
> mem_from, mem_*len*
>
> i.e. second parameter is region length, not end addres
On Monday 08 December 2014 13:47:38 Hante Meuleman wrote:
> Still using outlook, but will limit the line length, I hope that works for the
> moment. Attached is a log with the requested information, it is a little
> bit non-standard though. The dump code from the mm was copied in
> the driver and c
This fix an error handling bug reported by Beniamino, this is based on
mtk intpol patches [1]
Joe.C
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/305808.html
of_io_request_and_map() return ERR_PTR wrapped error code instead of
NULL when fail, fix code i
On Fri 05-12-14 16:41:38, K. Y. Srinivasan wrote:
> Andy Whitcroft initially saw this deadlock. We
> have seen this as well. Here is the original description of the
> problem (and a potential solution) from Andy:
>
> https://lkml.org/lkml/2014/3/14/451
>
> Here is an excerpt from that mail:
>
>
Linus,
You and Andrew brought up some issues with the original patch set.
Here's the thread:
http://lkml.kernel.org/r/20140619213329.478113...@goodmis.org
Your concern was moving "trace_seq.c" into lib/ as a file named
"trace_" and functions starting with "trace_" had nothing to do with
the g
The main purpose of this patchset is to use the driver on a PCI mapped fpga.
This patchset also converts the driver to platform device, so it will support
hot plugged devices and rmmod.
Ricardo Ribalda Delgado (4):
gpio/xilinx: remove offset property
gpio/xilinx: Convert the driver to platfor
Core can be accessed via PCIe on X86 platform.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/gpio/Kconfig | 4 ++--
drivers/gpio/gpio-xilinx.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
index 0959ca9..7f8ba83 1006
This way the driver can me unloaded.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/gpio/gpio-xilinx.c | 52 +++---
1 file changed, 45 insertions(+), 7 deletions(-)
diff --git a/drivers/gpio/gpio-xilinx.c b/drivers/gpio/gpio-xilinx.c
index 1199a31..f9
On Mon, 8 Dec 2014 10:05:28 -0500
Steven Rostedt wrote:
> This code solves the issue of performing stack dumps from NMI context.
> The issue is that printk() is not safe from NMI context as if the NMI
> were to trigger when a printk() was being performed, the NMI could
> deadlock from the printk
This way we do not need to transverse the device tree manually and we
support hot plugged devices.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/gpio/gpio-xilinx.c | 27 ++-
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/drivers/gpio/gpio-xilinx.c b/
On Monday 08 December 2014 13:49:03 Lee Jones wrote:
> On Mon, 08 Dec 2014, Arnd Bergmann wrote:
>
> > On Monday 08 December 2014 13:00:09 Lee Jones wrote:
> > > On Mon, 08 Dec 2014, Arnd Bergmann wrote:
> > >
> > > > On Monday 08 December 2014 12:06:19 Stephen Rothwell wrote:
> > > > > Hi Stephe
Good day,This email is sequel to an ealier sent message of which you have
not responded.I have a personal charity project which I will want you to
execute on my behalf.Please kindly get back to me with this code
MHR/3910/2014 .You can reach me on mrsalimqa...@gmail.com .
Thank you
Salim Qadri
--
Instead of calculating the register offset per call, pre-calculate it on
probe time.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/gpio/gpio-xilinx.c | 33 +++--
1 file changed, 11 insertions(+), 22 deletions(-)
diff --git a/drivers/gpio/gpio-xilinx.c b/drivers/
On 11/06/14 14:41, Bart Van Assche wrote:
With kernel 3.18-rc3 and with can_queue=62 I can trigger a hang in
bt_get() easily.
(once more replying to my own e-mail)
Hello Jens,
Finally I found the time to look further into this. The patch below
seems to be sufficient to prevent this hang. How
On 12/07/2014 02:20 PM, Julia Lawall wrote:
Replace a misspelled function name by %s and then __func__.
The function name contains pcie, not pci as in the string.
This was done using Coccinelle, including the use of Levenshtein distance,
as proposed by Rasmus Villemoes.
Signed-off-by: Julia La
Sorry about sending two versions in such quick order -
it turns out v1 was broken on modular kernels,
so I'm sending v2 to make these configs testable as well.
virtio 1.0 support for virtio-pci isn't ready yet.
Therefore, this patchset doesn't make any functional changes.
Instead, this simply refa
should be
struct foo {
}
not
struct foo
{
}
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c
index ee1b54c..6f3db1f 100644
--- a/drivers/virtio/
We don't need to go from vq to vq info on
data path, so using direct vq->priv pointer for that
seems like a waste.
Let's build an array of vq infos, then we can use vq->index
for that lookup.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 56 +---
On Sat, Dec 6, 2014 at 9:02 PM, Pali Rohár wrote:
> On Saturday 06 December 2014 13:49:54 Pavel Machek wrote:
>
> /**
> + * request_firmware_prefer_user: - prefer usermode helper for loading
> firmware
> + * @firmware_p: pointer to firmware image
> + * @name: name of firmware file
> + * @device
There's been a lot of changes since 2007.
List main authors, add Red Hat copyright.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.h| 5 -
drivers/virtio/virtio_pci.c| 5 -
drivers/virtio/virtio_pci_legacy.c | 5 -
3 files changed, 12 insertions(+), 3
kbuild does not seem to like it when we name source
files same as the module.
Let's rename virtio_pci -> virtio_pci_common,
and get rid of #include-ing c files.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/{virtio_pci.h => virtio_pci_common.h} | 4 ++--
drivers/virtio/{virtio_pci.c => vi
Move everything dealing with legacy devices out to virtio_pci_legacy.c.
Expose common code APIs in virtio_pci.h
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.h| 133
drivers/virtio/virtio_pci.c| 420 ++---
drivers/vir
config vector setup is version specific, do it indirectly.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c
index 68023e5..c8ca3f7 1
On Mon, Dec 08, 2014 at 04:01:32PM +0100, Arnd Bergmann wrote:
> In your log, I see this message:
>
> [0.00] PL310 OF: cache setting yield illegal associativity
> [0.00] PL310 OF: -1069781724 calculated, only 8 and 16 legal
> [0.00] L2C-310 enabling early BRESP for Cortex-A
VQ setup is mostly version-specific, add another level of indirection to
split the version-independent code out.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 69 ++---
1 file changed, 46 insertions(+), 23 deletions(-)
diff --git a/d
Use isr field instead of direct access to ioaddr.
This way generalizes easily to virtio 1.0.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c
index
VQ deletion is mostly version-specific, add another level of indirection
to split the version-independent code out.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 27 ---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git a/drivers/virtio/vi
slightly reduce the amount of pointer chasing this needs to do.
More importantly, this will easily generalize to virtio 1.0.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/virtio/virtio_pci.c b/dr
On Monday 08 December 2014 16:18:18 Ming Lei wrote:
> On Sat, Dec 6, 2014 at 9:02 PM, Pali Rohár
wrote:
> > On Saturday 06 December 2014 13:49:54 Pavel Machek wrote:
> > /**
> >
> > + * request_firmware_prefer_user: - prefer usermode helper
> > for loading firmware + * @firmware_p: pointer to f
On Monday 08 December 2014 15:17:33 Russell King - ARM Linux wrote:
> On Mon, Dec 08, 2014 at 04:01:32PM +0100, Arnd Bergmann wrote:
> > In your log, I see this message:
> >
> > [0.00] PL310 OF: cache setting yield illegal associativity
> > [0.00] PL310 OF: -1069781724 calculated,
The loop for measuring the square wave periods over some cycles is
refactored to be more easily readable. This includes avoiding a
"by-hand-implemented" for loop with a "real" one and adding some
comments.
Furthermore the following compiler warning is avoided by this patch:
drivers/misc/ioc4.c: In
On 12/08/2014 09:33 AM, Sasha Levin wrote:
> On 12/08/2014 12:20 AM, Paul E. McKenney wrote:
>> > I have seen this caused by lost IPIs, but you have to lose two of them,
>> > which seems less than fully likely.
> It does seem that it can cause full blown stalls as well, just pretty
> rarely (notice
On Mon, Dec 08, 2014 at 08:49:31AM -0600, Christoph Lameter wrote:
> On Sun, 7 Dec 2014, Vladimir Davydov wrote:
>
> > diff --git a/mm/slub.c b/mm/slub.c
> > index 95d214255663..7ddf01e2a465 100644
> > --- a/mm/slub.c
> > +++ b/mm/slub.c
> > @@ -2450,6 +2450,7 @@ redo:
> >
> > slab_post_alloc_
From: Peter Rosin
When the codec is connected using i2c, it will only auto-increment
register addresses if msb (0x80) of the register address byte is set.
Signed-off-by: Peter Rosin
---
sound/soc/codecs/pcm512x-i2c.c |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/
On Mon, Dec 8, 2014 at 11:22 PM, Pali Rohár wrote:
> On Monday 08 December 2014 16:18:18 Ming Lei wrote:
>> On Sat, Dec 6, 2014 at 9:02 PM, Pali Rohár
> wrote:
>> > On Saturday 06 December 2014 13:49:54 Pavel Machek wrote:
>> > /**
>> >
>> > + * request_firmware_prefer_user: - prefer usermode he
On Sat, Nov 29, 2014 at 11:49:04AM +0530, Muthu Mani wrote:
> Adds support for USB-I2C/GPIO interfaces of Cypress Semiconductor
> CYUSBS234 USB-Serial Bridge controller.
>
> Details about the device can be found at:
> http://www.cypress.com/?rID=84126
>
> Signed-off-by: Muthu Mani
> Signed-off-b
On Fri, 5 Dec 2014 19:04:12 +
"Javi Merino" wrote:
> +static const char *
> +ftrace_print_array_seq(struct trace_seq *p, const void *buf, int buf_len,
> +bool (*iterator)(struct trace_seq *p, const char *prefix,
> + const void **buf,
On Sun, Dec 7, 2014 at 2:21 PM, Julia Lawall wrote:
> Replace a misspelled function name by %s and then __func__.
>
> This was done using Coccinelle, including the use of Levenshtein distance,
> as proposed by Rasmus Villemoes.
>
> Signed-off-by: Julia Lawall
Looks fine to me. For consistency,
On Monday 08 December 2014 16:28:10 Richard Leitner wrote:
> The loop for measuring the square wave periods over some cycles is
> refactored to be more easily readable. This includes avoiding a
> "by-hand-implemented" for loop with a "real" one and adding some
> comments.
>
> Furthermore the follo
Hi,
So this set of patches adds YUV support for MDP4 and MDP5. This only concerns
the public planes (using ViG pipes).
The fun part was to rebase things on top of atomic but things worked out fine.
I was able to test this for MDP5 on a 8084 target. I cannot say the same for
MDP4 for which I don't
YUV support addition implies that sub-modules of the ViG pipes
need to be configured: Color Space Converter (CSC) and Scaler are
the main components used to convert YUV to RGB data. Note that
the output of a pipe has to be in RGB888 format since only this
format is understood by the (layer) mixers.
From: Beeresh Gopal
The patch add support for YUV frame format
for MDP4 platform.
Signed-off-by: Beeresh Gopal
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp4/mdp4_plane.c | 104 +++---
1 file changed, 95 insertions(+), 9 deletions(-)
diff --git a/driver
Both MDP4 and MDP5 share some code as far as YUV support is
concerned. This change adds this information and will be followed
by the actual MDP4 and MDP5 YUV support patches.
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.h | 19 --
drivers/gpu/drm/msm/mdp/mdp5/mdp
On Mon, Dec 08, 2014 at 11:53:33AM +0100, Ingo Molnar wrote:
>
> * Frederic Weisbecker wrote:
>
> > Ingo,
> >
> > Please pull the perf/core-v3 branch that can be found at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> > perf/core-v3
> >
> > HEAD: 3674
This change adds the NV12 format support for public planes.
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5_plane.c | 213 +++---
drivers/gpu/drm/msm/msm_fb.c | 2 +-
2 files changed, 194 insertions(+), 21 deletions(-)
diff --git a/drive
On Mon, 2014-12-08 at 16:28 +0100, Richard Leitner wrote:
> The loop for measuring the square wave periods over some cycles is
> refactored to be more easily readable. This includes avoiding a
> "by-hand-implemented" for loop with a "real" one and adding some
> comments.
>
> Furthermore the follow
Isolate the SRCU functions and data structures within CONFIG_SRCU so that there
is a compile time failure if srcu is used when not enabled. This was decided to
be better than waiting until link time for a failure to occur.
Signed-off-by: Pranith Kumar
CC: Paul E. McKenney
CC: Josh Triplett
CC:
On Mon, Dec 08, 2014 at 12:55:38PM +, Johannes Stezenbach wrote:
> On Fri, Dec 05, 2014 at 06:53:03PM +, Catalin Marinas wrote:
> > On Fri, Dec 05, 2014 at 06:39:45PM +, Catalin Marinas wrote:
> > >
> > > Does your system have an L2 cache? What's the SoC topology, can PCIe see
> > > su
On Mon, Dec 08, 2014 at 09:33:29AM -0500, Sasha Levin wrote:
> On 12/08/2014 12:20 AM, Paul E. McKenney wrote:
> > I have seen this caused by lost IPIs, but you have to lose two of them,
> > which seems less than fully likely.
>
> It does seem that it can cause full blown stalls as well, just pret
On Mon, 08 Dec 2014 16:46:31 +0100
Arnd Bergmann wrote:
> On Monday 08 December 2014 16:28:10 Richard Leitner wrote:
> >
> > Signed-off-by: Richard Leitner
>
> Acked-by: Arnd Bergmann
>
>
> With the changed loop, do you still get a warning if you
> remove the extra 'start = ktime_get_ns()'
On Mon, Dec 08, 2014 at 10:28:53AM -0500, Sasha Levin wrote:
> On 12/08/2014 09:33 AM, Sasha Levin wrote:
> > On 12/08/2014 12:20 AM, Paul E. McKenney wrote:
> >> > I have seen this caused by lost IPIs, but you have to lose two of them,
> >> > which seems less than fully likely.
> > It does seem th
> On Sat, Nov 29, 2014 at 11:49:04AM +0530, Muthu Mani wrote:
> > Adds support for USB-I2C/GPIO interfaces of Cypress Semiconductor
> > CYUSBS234 USB-Serial Bridge controller.
> >
> > Details about the device can be found at:
> > http://www.cypress.com/?rID=84126
> >
> > Signed-off-by: Muthu Mani
601 - 700 of 733 matches
Mail list logo
