It is observed that sometimes multiple tasks get blocked for long
in the congestion_wait loop below, in shrink_inactive_list. This
is because of vm_stat values not being synced.
(__schedule) from []
(schedule_timeout) from []
(io_schedule_timeout) from []
(congestion_wait) from []
On 21/12/14 19:02, Rickard Strandqvist wrote:
> Removes some functions that are not used anywhere:
> rfbi_init_display() rfbi_display_disable() rfbi_display_enable()
> rfbi_set_interface_timings() rfbi_set_data_lines() rfbi_set_pixel_size()
> rfbi_set_size() rfbi_update() rfbi_configure()
On Tue, Jan 13, 2015 at 12:18:40PM +0530, Sudip Mukherjee wrote:
> On Tue, Jan 13, 2015 at 11:54:27AM +0530, Sudip Mukherjee wrote:
> > On Mon, Jan 12, 2015 at 09:58:17PM -0800, Greg KH wrote:
> > > On Tue, Jan 13, 2015 at 10:53:12AM +0530, Sudip Mukherjee wrote:
> > > >
> > > > any reason why
Hi Thomas,
On Tue, 13 Jan 2015 11:38:14 +0100 (CET)
Thomas Gleixner wrote:
> On Thu, 8 Jan 2015, Boris Brezillon wrote:
> > 1) Is it close to what you had in mind ?
>
> Yes.
>
> > 2) I'm not sure which part of the code should go where, so don't hesitate
> >to point out misplaced sections.
This patch fixes bug described here:
https://lkml.org/lkml/2014/12/22/185
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/core_intr.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc2/core_intr.c b/drivers/usb/dwc2/core_intr.c
index ad43c5b..668c8dd
On 11/12/14 11:04, Asaf Vertz wrote:
> Fixed a coding style error, trailing whitespace.
>
> Signed-off-by: Asaf Vertz
> ---
> drivers/video/vgastate.c | 82
> +++---
> 1 files changed, 41 insertions(+), 41 deletions(-)
>
Thanks, queued for 3.20.
On 01/13/2015 11:18 AM, Robert Baldyga wrote:
> On 01/12/2015 10:35 PM, Paul Zimmerman wrote:
>>> From: Robert Baldyga [mailto:r.bald...@samsung.com]
>>> Sent: Monday, December 22, 2014 6:13 AM
>>>
>>> I have recently noticed problem with DWC2 driver in latest linux-next. I
>>> use it in gadget
On 05/12/14 10:18, Qiang Chen wrote:
> When allocate framebuffer memory using dma_alloc_coherent(),
> we'd better use dma_addr_t instead of phys_addr_t. Because the
> address we got in fact is DMA or bus address for the platform.
>
> This patch also fixes below build warning:
>
On 13/01/15 10:41, Thomas Gleixner wrote:
> On Fri, 9 Jan 2015, Marc Zyngier wrote:
>> Hi Jiang,
>>
>> On 09/01/15 03:07, Jiang Liu wrote:
>>> On 2015/1/9 1:32, Marc Zyngier wrote:
With the landing of stacked irq domains in 3.19, we have ended up in a
situation where we have a stack of
On Mon, 12 Jan 2015, Daniel Lezcano wrote:
> On 01/12/2015 03:04 PM, Nicolas Ferre wrote:
> > Le 18/12/2014 15:05, Nicolas Ferre a écrit :
> > > From: Sylvain Rochet
> > >
> > > Waiting for PIT to stop counting takes a long time:
> > >1/(Master clock/prescaler/PIVR)
> > > = 1/(133 MHz
On Tue, Jan 06, 2015 at 07:06:56PM +0530, Bhuvanchandra DV wrote:
> Add support for clock gating of UART4 and UART5.
> We use these UART's in a (not yet mainlined)
> device tree.
>
> Signed-off-by: Bhuvanchandra DV
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe
On Fri, 9 Jan 2015, Marc Zyngier wrote:
> Hi Jiang,
>
> On 09/01/15 03:07, Jiang Liu wrote:
> > On 2015/1/9 1:32, Marc Zyngier wrote:
> >> With the landing of stacked irq domains in 3.19, we have ended up in a
> >> situation where we have a stack of IRQ controllers, each with their
> >> set of
The DEBUG_UART_PHYS/VIRT value can only be automatically set once
(automatically means set from the DEBUG__ option), which
prevents re-configuring the earlyprintk output for another platform once
the DEBUG_LL output has been selected.
Add a new boolean option (DEBUG_CUSTOM_UART_ADDR) enabling
On Thu, 8 Jan 2015, Boris Brezillon wrote:
> 1) Is it close to what you had in mind ?
Yes.
> 2) I'm not sure which part of the code should go where, so don't hesitate
>to point out misplaced sections.
Looks sane. Nits below.
> 3) Do I need to disable the source irq (the one feeding the
On Tue, Jan 13, 2015 at 10:35:09AM +0100, Rafael J. Wysocki wrote:
> > @@ -51,13 +175,6 @@ EXPORT_SYMBOL_GPL(fwnode_property_present);
> > (val) ? of_property_read_##type##_array((node), (propname), (val),
> > (nval)) \
> > : of_property_count_elems_of_size((node), (propname),
> >
On 11/01/15 23:37, Steven Rostedt wrote:
> On Fri, 9 Jan 2015 16:48:01 +
> Russell King - ARM Linux wrote:
>
>> On Mon, Jan 05, 2015 at 10:19:25AM -0500, Steven Rostedt wrote:
>>> On Mon, 5 Jan 2015 14:54:58 +
>>> Daniel Thompson wrote:
+/* For reliability, we're prepared to waste
On Fri, Jan 09, 2015 at 09:32:35AM -0600, dingu...@opensource.altera.com wrote:
> From: Graham Moore
>
> commit "3157d1ed2309 mtd: denali: remove unnecessary casts" introduced
> an error by using a wrong bitmask.
>
> A uint16_t cast was replaced with & 0xff, should be & 0x.
>
>
Hi Felipe,
On 1 December 2014 at 11:09, Kiran Raparthy wrote:
> Hi Felipe,
>
> On 25 November 2014 at 20:15, Felipe Balbi wrote:
>> On Tue, Nov 25, 2014 at 07:06:18AM +, Peter Chen wrote:
>>>
>>> >
>>> > usb: phy: hold wakeupsource when USB is enumerated in peripheral mode
>>> >
>>> > Some
Since no one had any responses to the original thread, Greg is going to
see that first and apply it and this one will not apply. It's not worth
resending patches for trivial stuff like this anyway...
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe
On 01/13/2015 06:07 PM, MyungJoo Ham wrote:
>>
>> Dear Myungjoo,
>>
>> On 01/13/2015 05:42 PM, MyungJoo Ham wrote:
This patch adds the generic exynos bus frequency driver for memory bus
with DEVFREQ framework. The Samsung Exynos SoCs have the common
architecture
for
Currently it is not possible to exploit FIQ for systems with a GIC, even if
the systems are otherwise capable of it. This patch makes it possible
for IPIs to be delivered using FIQ.
To do so it modifies the register state so that normal interrupts are
placed in group 1 and specific IPIs are
Currently gic_raise_softirq() is locked using upon irq_controller_lock.
This lock is primarily used to make register read-modify-write sequences
atomic but gic_raise_softirq() uses it instead to ensure that the
big.LITTLE migration logic can figure out when it is safe to migrate
interrupts between
On Tue, Jan 13, 2015 at 03:33:12AM +, Rik van Riel wrote:
> On 01/09/2015 09:51 PM, David Lang wrote:
> > On Fri, 9 Jan 2015, Linus Torvalds wrote:
> >
> >> Big pages are a bad bad bad idea. They work fine for databases,
> >> and that's pretty much just about it. I'm sure there are some
> >>
Much of the code sitting in arch/x86/kernel/apic/hw_nmi.c to support safe
all-cpu backtracing from NMI has been copied to printk.c to make it
accessible to other architectures.
Port the x86 NMI backtrace to the generic code.
Signed-off-by: Daniel Thompson
Cc: Steven Rostedt
Cc: Thomas Gleixner
Currently if arch_trigger_all_cpu_backtrace() is called with interrupts
disabled and on a platform the delivers IPI_CPU_BACKTRACE using regular
IRQ requests the system will wedge for ten seconds waiting for the
current CPU to react to a masked interrupt.
This patch resolves this issue by calling
Duplicate the x86 code to trigger a backtrace using an NMI and hook
it up to IPI on ARM. Where it is possible for the hardware to do so the
IPI will be delivered at FIQ level.
Also provide are a few small items of plumbing to hook up the new code.
Signed-off-by: Daniel Thompson
Cc: Steven
Currently there is a quite a pile of code sitting in
arch/x86/kernel/apic/hw_nmi.c to support safe all-cpu backtracing from NMI.
The code is inaccessible to backtrace implementations for other
architectures, which is a shame because they would probably like to be
safe too.
Copy this code into
It is currently possible for FIQ handlers to re-enter gic_raise_softirq()
and lock up.
gic_raise_softirq()
lock(x);
-~-> FIQ
handle_fiq()
gic_raise_softirq()
lock(x); <-- Lockup
arch/arm/ uses IPIs to implement arch_irq_work_raise(),
Hi Thomas, Hi Jason:
Patches 1 to 3 are for you (and should be separable from the rest
of the series). The patches haven't changes since the last time
I posted them. The changes in v14 tidy up the later part of the
patch set in order to share more code between x86 and arm.
This
PACA_DSCR offset macro tracks dscr_default element in the paca
structure. Better change the name of this macro to match that
of the data element it tracks. Makes the code more readable.
Signed-off-by: Anshuman Khandual
---
arch/powerpc/kernel/asm-offsets.c | 2 +-
Currently DSCR (Data Stream Control Register) can be accessed with
mfspr or mtspr instructions inside a thread via two different SPR
numbers. One being the user accessible problem state SPR number 0x03
and the other being the privilege state SPR number 0x11. All access
through the privilege state
From: Colin Cross
debug: prevent entering debug mode on panic/exception.
On non-developer devices, kgdb prevents the device from rebooting
after a panic.
Incase of panics and exceptions, to allow the device to reboot, prevent entering
debug mode to avoid getting stuck waiting for the user to
This patch adds a new documentation file explaining the DSCR
support on powerpc platforms. This explains DSCR related data
structure, code paths and also available user interfaces. Any
further functional changes to the DSCR support in the kernel
should definitely update the documentation here.
The process context switch code no longer uses dscr_default variable
from the sysfs.c file. The variable became unused when we started
storing the CPU specific DSCR value in the PACA structure instead.
This patch just removes this extern declaration. It was originally
added by the following
This patch adds a test which verifies that the DSCR privilege and
problem state SPR read & write accesses while making sure that the
results are always the same irrespective of which SPR number is
being used.
Signed-off-by: Anshuman Khandual
---
tools/testing/selftests/powerpc/dscr/Makefile
This patch adds a test which modifies the DSCR using mtspr instruction
and verifies the change using mfspr instruction. It uses both the
privilege state SPR as well as the problem state SPR for the purpose.
Signed-off-by: Anshuman Khandual
---
tools/testing/selftests/powerpc/dscr/Makefile
This patch adds a test case for the system wide DSCR default
value, which when changed through it's sysfs interface must
be visible to all threads reading DSCR either through the
privilege state SPR or the problem state SPR. The DSCR value
change should be immediate as well.
Signed-off-by:
This patch adds a test case to verify that the changed DSCR value
inside any process would be inherited to it's child across the fork
and exec system call.
Signed-off-by: Anshuman Khandual
---
tools/testing/selftests/powerpc/dscr/Makefile | 2 +-
.../powerpc/dscr/dscr_inherit_exec_test.c
This patch adds a test to verify that the changed DSCR value inside
any process would be inherited to it's child process across the fork
system call.
Signed-off-by: Anshuman Khandual
---
tools/testing/selftests/powerpc/dscr/Makefile | 3 +-
.../selftests/powerpc/dscr/dscr_inherit_test.c
This patch adds some in-code documentation to the DSCR related
code to make it more readable without having any functional
change to it.
Signed-off-by: Anshuman Khandual
---
arch/powerpc/include/asm/processor.h | 9 +
arch/powerpc/kernel/sysfs.c | 38
This patch adds a test to update the system wide DSCR value repeatedly
and then verifies that any thread on any given CPU on the system must
be able to see the same DSCR value whether its is being read through
the problem state based SPR or the privilege state based SPR.
Signed-off-by: Anshuman
This test continuously updates the system wide DSCR default value
in the sysfs interface and makes sure that the same is reflected
across all the sysfs interfaces for each individual CPUs present
on the system.
Signed-off-by: Anshuman Khandual
---
tools/testing/selftests/powerpc/dscr/Makefile
This patch series has patches for POWER DSCR fixes, improvements,
in code documentaion, kernel support user documentation and selftest based
test cases. It has got five test cases which are derived from Anton's DSCR
test bucket which can be listed as follows.
(1)
On Sun, Jan 11, 2015 at 01:55:04PM +0200, Michael S. Tsirkin wrote:
> On Tue, Jan 06, 2015 at 08:08:57PM +0100, Arnd Bergmann wrote:
> > On Tuesday 06 January 2015 17:43:28 Michael S. Tsirkin wrote:
> > >
> > > I tested this on x86 only. Since it's just adding __force, should be
> > > trivially
On 01/12/2015 10:35 PM, Paul Zimmerman wrote:
>> From: Robert Baldyga [mailto:r.bald...@samsung.com]
>> Sent: Monday, December 22, 2014 6:13 AM
>>
>> I have recently noticed problem with DWC2 driver in latest linux-next. I
>> use it in gadget only mode at Samsung platform (Odroid U3) but I believe
On Sun, Jan 11, 2015 at 09:16:23PM +, Ben Hutchings wrote:
> On Sun, 2015-01-11 at 00:23 +, Ben Hutchings wrote:
> > Commit 45e2a9d4701d8c624d4a4bcdd1084eae31e92f58 ("x86, mm: Set NX across
> > entire PMD at boot") has been backported to many stable branches:
> >
> > v3.10.62:
On 03/12/14 23:33, Marek Belisko wrote:
> Add handling for gta04 tv out chain:
> venc -> opa362 -> svideo
>
> Use invert-polarity in venc node because opa362
> is doing polarity inversion also.
>
> Signed-off-by: Marek Belisko
> ---
> arch/arm/boot/dts/omap3-gta04.dtsi | 49
>
On Wed, Dec 17, 2014 at 12:34 AM, Hongzhou Yang
wrote:
> From: Hongzhou Yang
>
> Add devicetree bindings for Mediatek SoC pinctrl driver.
>
> Signed-off-by: Hongzhou Yang
So following from the discussion with Sascha...
(...)
> diff --git
On Di, 2015-01-13 at 09:53 +0530, Rahul Sharma wrote:
> On Mon, Jan 12, 2015 at 5:21 PM, Pablo Neira Ayuso
> wrote:
> > On Mon, Jan 12, 2015 at 04:38:16PM +0530, Rahul Sharma wrote:
> >> Hi Pablo, Hannes
> >>
> >> On Fri, Jan 9, 2015 at 9:20 PM, Hannes Frederic Sowa
> >> wrote:
> >> > On Fr,
On 13/01/15 02:23, Jiang Liu wrote:
> On 2015/1/12 23:01, David Vrabel wrote:
>> On 12/01/15 13:39, Jiang Liu wrote:
>>> Commit b81975eade8c ("x86, irq: Clean up irqdomain transition code")
>>> breaks xen IRQ allocation because xen_smp_prepare_cpus() doesn't invoke
>>> setup_IO_APIC(), so no
Correct the path name for mux to get rid of the following warning:
--->8---
wm8904 1-001a: Control not supported for path ADCL -> [Left] -> AIFOUTL
wm8904 1-001a: ASoC: no dapm match for ADCL --> Left --> AIFOUTL
wm8904 1-001a: ASoC: Failed to add route ADCL -> Left -> AIFOUTL
wm8904 1-001a:
On Mon, 12 Jan 2015 15:44:24 -0800
Mike Turquette wrote:
> Quoting Boris Brezillon (2015-01-12 07:12:50)
> > All slow clk users are not properly requesting it (get + prepare + enable)
> > before using it.
> > If all users properly requesting this clock decide that they don't need it
> > anymore
On Mon, Jan 12, 2015 at 1:22 PM, Sascha Hauer wrote:
> On Sat, Jan 10, 2015 at 10:33:46PM +0100, Linus Walleij wrote:
>> On Tue, Dec 2, 2014 at 2:55 PM, Sascha Hauer wrote:
>> > For the SSP0 it needs the string "ssp0_a_1" which is documented exactly
>> > nowhere.
>>
>> Is this a bug report
On Wed, Dec 03, 2014 at 06:33:57PM +0400, Alexander Kochetkov wrote:
> This pacth series intended for fixing problem reported
> by Tony Lindgren here[1]
>
> One of first four patched could fix the problem.
> Last patch provide event trace so I could resolve problem.
> It could be applied using
On Sun, Nov 30, 2014 at 01:00:01AM +0400, Alexander Kochetkov wrote:
> The first patch fix i2c-omap driver for omap2420, found by code review and
> later reported by Tony Lindgren here[1].
> Candidate for stable?
>
> The second patch unhide the reson of system lockup.
>
> The patch is rebased
On Tue, Jan 06, 2015 at 02:37:53PM +0100, Wolfram Sang wrote:
>
> > We've started upstream work for MT8173[1].
> >
> > We've fixed these issues for new SoC, and we believe it is fully I2C
> > compatible now. We'll add mt8173 support to this driver, so this driver
> > will support both fully I2C
On Mon, Jan 12, 2015 at 04:56:54PM -0500, Chris Metcalf wrote:
> Nack for this patch as-is.
Thanks, I dropped it and the next one from my tree,
looks like you are on track to fixing it all in the
tile tree.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
Fix sparse warning
Fixes: cb442ee1592d2681 (usb: gadget: udc: net2280: Re-enable dynamic debug
messages)
Reported-by: kbuild test robot
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/usb/gadget/udc/net2280.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 13/01/15 08:14, Imre Palik wrote:
> From: "Palik, Imre"
>
> In Dom0's the use of the TSC clocksource (whenever it is stable enough to
> be used) instead of the Xen clocksource should not cause any issues, as
> Dom0 VMs never live-migrated. The TSC clocksource is somewhat more
> efficient
On 01/12/2015 07:36 PM, Roger Pau Monné wrote:
> El 12/01/15 a les 8.09, Bob Liu ha escrit:
>>
>> On 01/09/2015 11:51 PM, Roger Pau Monné wrote:
>>> El 06/01/15 a les 14.19, Bob Liu ha escrit:
When there is no enough free grants, gnttab_alloc_grant_references()
will fail and block
From: Thomas Graf
> Each per bucket lock covers a configurable number of buckets. While
> shrinking, two buckets in the old table contain entries for a single
> bucket in the new table. We need to lock down both while linking.
> Check if they are protected by different locks to avoid a recursive
>
>
> This patch adds the memory bus node for Exynos4x12 SoC. Exynos4x12 SoC has
> two memory bus to translate data between DRAM and eMMC/sub-IPs.
>
> Following list specifies the detailed relation between memory bus clock and
> DMC
> IP in MIF (Memory Interface) block:
> - DMC/ACP clock : DMC
On 01/12/2015 07:36 PM, Roger Pau Monné wrote:
> El 12/01/15 a les 8.09, Bob Liu ha escrit:
>>
>> On 01/09/2015 11:51 PM, Roger Pau Monné wrote:
>>> El 06/01/15 a les 14.19, Bob Liu ha escrit:
When there is no enough free grants, gnttab_alloc_grant_references()
will fail and block
Hi Dave,
> Timely reply. Around i2c_dw_init(), yes. I just discovered this as the source
> of a recent hang that's occuring in the loop in __i2c_dw_enable().
> The hange occurs very infrequently and only, so far, when not built in. A
> block around i2c_dw_disable_int() would make sense as well as
On 01/13/2015 10:34 AM, Bo Shen wrote:
[...]
- { "AIFOUTL", "Left", "ADCL" },
- { "AIFOUTL", "Right", "ADCR" },
- { "AIFOUTR", "Left", "ADCL" },
- { "AIFOUTR", "Right", "ADCR" },
+ { "AIFOUTL Mux", "Left", "ADCL" },
+ { "AIFOUTL Mux", "Right", "ADCR" },
+
On Mon, Jan 12, 2015 at 07:08:36PM -0500, Chris Metcalf wrote:
> On 1/6/2015 10:44 AM, Michael S. Tsirkin wrote:
> >Tile currently does not trigger sparse warnings when get_user
> >causes an illegal assignment across bitwise types.
> >
> >For example:
> >
> >__le32 __user *p;
> >__u32 x;
>
On 01/09/2015 10:30 PM, Fabian Frederick wrote:
>
>
>> On 06 January 2015 at 18:21 Vlastimil Babka wrote:
>>
>>
>> On 01/03/2015 05:04 PM, Fabian Frederick wrote:
>> > suitable_migration_target() is only used by isolate_freepages()
>> > Define it under CONFIG_COMPACTION || CONFIG_CMA is not
On Wed, Dec 17, 2014 at 12:34 AM, Hongzhou Yang
wrote:
> From: Yingjoe Chen
>
> The upcoming MTK pinctrl driver have a big pin table for each SoC
> and we don't want to bloat the kernel binary if we don't need it.
> Add config options so we can build for one SoC only.
>
> Signed-off-by: Yingjoe
X86 Kconfig symbol is X86, not ARCH_X86.
Fixes: c586b3075d5b47d8 (gpio/xilinx: Add support for X86 Arch)
Reported-by: Paul Bolle
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/gpio/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/Kconfig
On Tue, Jan 13, 2015 at 11:35:35AM +0200, Michael S. Tsirkin wrote:
> On Mon, Jan 12, 2015 at 04:56:54PM -0500, Chris Metcalf wrote:
> > Nack for this patch as-is.
> >
> > On 1/6/2015 10:44 AM, Michael S. Tsirkin wrote:
> > >virtio wants to write bitwise types to userspace using put_user.
> > >At
On Tue, Jan 13, 2015 at 10:35:09AM +0100, Rafael J. Wysocki wrote:
> On Monday, January 12, 2015 01:15:44 PM Heikki Krogerus wrote:
> > This extends the Unified Property Interface by adding
> > "Generic Property" to it for cases where device tree or ACPI
> > are not being used.
> >
> > That makes
On Fri, Jan 09, 2015 at 11:26:54AM -0500, Vince Weaver wrote:
>
> On Fri, 9 Jan 2015, Peter Zijlstra wrote:
> > > So is this worth fixing seeing as apparently no one uses this feature?
> >
> > I think there's a fair argument for removing it, Ingo, Acme?
>
> could the functionality be replaced
Paul Zimmerman writes:
> The patch below fixes it. And it seems like the right thing to me,
> since GPIOs should be optional for a generic phy, I would think. But
> my device tree foo is very weak, so I'm not sure.
>
> CCing Robert, who touched the generic phy code last. Robert, what do
> you
On Tue, Jan 13, 2015 at 03:30:34PM +0800, Lai Jiangshan wrote:
> In rcu_gp_init(), rnp->completed equals to rsp->completed in THEORY,
> we don't need to touch it normally. If something goes wrong,
> it will complain and fixup rnp->completed and avoid oops.
>
> Signed-off-by: Lai Jiangshan
On Mon, Jan 12, 2015 at 04:56:54PM -0500, Chris Metcalf wrote:
> Nack for this patch as-is.
>
> On 1/6/2015 10:44 AM, Michael S. Tsirkin wrote:
> >virtio wants to write bitwise types to userspace using put_user.
> >At the moment this triggers sparse errors, since the value is passed
> >through an
Hi Lars-Peter Clausen,
On 01/13/2015 04:56 PM, Lars-Peter Clausen wrote:
On 01/13/2015 06:36 AM, Bo Shen wrote:
Hi Lars-Perter Clausen,
On 01/12/2015 05:30 PM, Lars-Peter Clausen wrote:
On 01/12/2015 04:32 AM, Bo Shen wrote:
[...]
diff --git a/sound/soc/codecs/wm8904.c
Correct the path name for mux to get rid of the following warning:
--->8---
wm8904 1-001a: Control not supported for path ADCL -> [Left] -> AIFOUTL
wm8904 1-001a: ASoC: no dapm match for ADCL --> Left --> AIFOUTL
wm8904 1-001a: ASoC: Failed to add route ADCL -> Left -> AIFOUTL
wm8904 1-001a:
On Tue, Jan 13, 2015 at 09:18:47AM +0100, Christian Borntraeger wrote:
> As we agreed there is no perfect interface regarding val,x vs. x,val.
> But it seems that there is some consensus that I should push something like
> the following (still whitespace damaged) to Linus for 3.19?
> Peter,
Hi, Juri,
13.01.2015, 11:10, "Juri Lelli" :
> Hi all,
>
> really sorry for the huge delay in replying to this! :(
>
> On 07/01/2015 12:29, Kirill Tkhai wrote:
>> On Ср, 2015-01-07 at 08:01 +0100, Luca Abeni wrote:
>>> Hi Kirill,
>>>
>>> On Tue, 06 Jan 2015 02:07:21 +0300
>>> Kirill Tkhai
On Tue, Jan 13, 2015 at 12:35:58AM +0100, Thomas Voegtle wrote:
> On Mon, 12 Jan 2015, Luis Henriques wrote:
>
> >On Mon, Jan 12, 2015 at 09:30:45PM +0100, Thomas Voegtle wrote:
> >>On Mon, 12 Jan 2015, Luis Henriques wrote:
> >>
> >>>This is the start of the review cycle for the Linux
On 01/13/2015 03:42 AM, Aneesh Kumar K.V wrote:
> "Aneesh Kumar K.V" writes:
>
>> Vlastimil Babka writes:
>>
>>> On 12/01/2014 03:06 PM, Aneesh Kumar K.V wrote:
"Kirill A. Shutemov" writes:
> On Mon, Dec 01, 2014 at 11:16:43AM +0530, Aneesh Kumar K.V wrote:
>> This make sure
On Mon, 12 Jan 2015 22:23:45 +0100
Alexandre Belloni wrote:
> Move at91rm9200_idle() along with at91sam9_idle() in clk/at91/pmc.c.
>
> Signed-off-by: Alexandre Belloni
> ---
> Cc: Mike Turquette
>
> Mike, Boris,
> I guess that one can go through the at91 tree unless you have any objections.
Hi,
There's one thing about kmemcg implementation that's bothering me. It's
about arrays holding per-memcg data (e.g. kmem_cache->memcg_params->
memcg_caches). On kmalloc or list_lru_{add,del} we want to quickly
lookup the copy of kmem_cache or list_lru corresponding to the current
cgroup.
On Tue, Jan 13, 2015 at 04:36:53PM +0800, Wang Nan wrote:
> On 2015/1/13 15:10, Jiri Olsa wrote:
> > On Tue, Jan 13, 2015 at 10:54:37AM +0800, Wang Nan wrote:
> >
> > SNIP
> >
> >>
> >> +static int elf_is_exec(int fd, const char *name)
> >> +{
> >> + Elf *elf;
> >> + GElf_Ehdr ehdr;
> >> +
On Fri, 09 Jan 2015 17:39:08 +
Andrew Jackson wrote:
> > + snd_pcm_hw_constraint_minmax(runtime,
> > + SNDRV_PCM_HW_PARAM_CHANNELS,
> > + 1, sad[SAD_MX_CHAN_I]);
>
> In the light of our discussions elsewhere [1], shouldn't
Hi Ricardo,
On Tue, 2015-01-13 at 10:04 +0100, Ricardo Ribalda Delgado wrote:
> Thanks for noticing
>
> Shall I send the patch or you want to do it yourself?
I rather prefer you do it, even if it looks trivial.
Changing that line to
[...] || X86)
will apparently enable a bit of code for
>
> This patch adds the memory bus node for Exynos3250 SoC. Exynos3250 has
> following memory buses to translate data between DRAM and eMMC/sub-IPs.
>
> Following list specifies the detailed relation between memory bus clock and
> DMC
> IP in MIF (Memory Interface) block:
> - DMC clock : DMC
On Monday, January 12, 2015 01:15:44 PM Heikki Krogerus wrote:
> This extends the Unified Property Interface by adding
> "Generic Property" to it for cases where device tree or ACPI
> are not being used.
>
> That makes the Unified Property Interface cover most of the
> cases where information is
>
> Dear Myungjoo,
>
>On 01/13/2015 05:42 PM, MyungJoo Ham wrote:
>>>
>>> This patch adds the generic exynos bus frequency driver for memory bus
>>> with DEVFREQ framework. The Samsung Exynos SoCs have the common architecture
>>> for memory bus between DRAM memory and MMC/sub IP in SoC. This
Did a quick test, looks good on my machine.
Thanks :-)
On Mon, Jan 12, 2015 at 11:23:19AM -0800, Yinghai Lu wrote:
>Some bios put range that is not fully coverred by root bus resources.
>Try to clip them and update them in pci bridge bars.
>
>We'd like to fix other arches instead of just x86.
>
(-)
>
> This patch became c586b3075d5b ("gpio/xilinx: Add support for X86 Arch")
> in today's linux-next (next-20150113). I noticed because a script I use
> to check linux-next spotted a problem in it.
>
>> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
>
Acked-by: MyungJoo Ham
Adding to Chanwoo's reply:
If I understand Chanwoo's intention correctly,
this patchset is to provide a common bus & memory-interface DVFS driver
for several Exynos SoCs, which allows DT to express per-SoC hardware
details so that we do not need to hardcode them with
pio/Kconfig | 4 ++--
> drivers/gpio/gpio-xilinx.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
This patch became c586b3075d5b ("gpio/xilinx: Add support for X86 Arch")
in today's linux-next (next-20150113). I noticed because a script I use
to check linux-next spotted a proble
On Tue, 13 Jan 2015, Sander Eikelenboom wrote:
>
> Monday, January 12, 2015, 4:01:00 PM, you wrote:
>
> > On 12/01/15 13:39, Jiang Liu wrote:
> >> Commit b81975eade8c ("x86, irq: Clean up irqdomain transition code")
> >> breaks xen IRQ allocation because xen_smp_prepare_cpus() doesn't invoke
>
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8fb4ab29bd8400e0060662208573d26b9d91656d
commit: 46919a23ee87bbc4eeb6d958471174e26836f0e1 [2818/3104] usb: gadget: uvc:
configfs support in uvc function
reproduce:
# apt-get install sparse
git checkout
On 01/13/2015 06:36 AM, Bo Shen wrote:
Hi Lars-Perter Clausen,
On 01/12/2015 05:30 PM, Lars-Peter Clausen wrote:
On 01/12/2015 04:32 AM, Bo Shen wrote:
[...]
diff --git a/sound/soc/codecs/wm8904.c b/sound/soc/codecs/wm8904.c
index 4d2d2b1..38582d7 100644
--- a/sound/soc/codecs/wm8904.c
+++
drivers/usb/gadget/function/uvc_configfs.c:46:28: sparse: symbol
'to_uvcg_control_header' was not declared. Should it be static?
drivers/usb/gadget/function/uvc_configfs.c:138:25: sparse: symbol
'uvcg_control_header_type' was not declared. Should it be static?
Dear Myungjoo,
On 01/13/2015 05:42 PM, MyungJoo Ham wrote:
>>
>> This patch adds the generic exynos bus frequency driver for memory bus
>> with DEVFREQ framework. The Samsung Exynos SoCs have the common architecture
>> for memory bus between DRAM memory and MMC/sub IP in SoC. This driver can
This patch fixes: 'omap_hwmod: gpmc: _wait_target_disable failed'
error during suspend.
This is because smart idle is broken.
Tested in dra7-evm D1 board.
Signed-off-by: Keerthy
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Tue, Dec 16, 2014 at 3:18 AM, Ray Jui wrote:
> This GPIO driver supports all 3 GPIO controllers in the Broadcom Cygnus
> SoC. The 3 GPIO controllers are 1) the ASIU GPIO controller, 2) the
> chipCommonG GPIO controller, and 3) the ALWAYS-ON GPIO controller
>
> Signed-off-by: Ray Jui
>
901 - 1000 of 2050 matches
Mail list logo
