On 06/30/2014 08:33 PM, Felipe Balbi wrote:
On Tue, Jun 24, 2014 at 02:16:35PM +0200, Robert Baldyga wrote:
On 06/23/2014 08:27 PM, Felipe Balbi wrote:
Hi,
On Mon, Jun 23, 2014 at 08:07:43AM +0200, Robert Baldyga wrote:
On 06/19/2014 05:08 PM, Felipe Balbi wrote:
On Mon, Jun 16, 2014 at
On 07/01/2014 01:41 PM, Mike Galbraith wrote:
On Tue, 2014-07-01 at 10:57 +0800, Michael wang wrote:
IMHO, currently the generic scheduler just try to take care both latency
and throughput, both will take a little damage but won't be damaged too
much, they just sacrificed for each other...
On Mon, Jun 30, 2014 at 7:07 PM, Peter De Schrijver
pdeschrij...@nvidia.com wrote:
On Mon, Jun 30, 2014 at 11:40:54AM +0200, Sachin Kamat wrote:
‘all_lists’ and ‘orphan_list’ is accessed only when DEBUG_FS is defined.
Thus, make their compilation conditional to fix the below warnings introduced
Hi Sören,
On Mon, 30 Jun 2014 17:12:23 -0700
Sören Brinkmann soren.brinkm...@xilinx.com wrote:
Hi Boris,
On Mon, 2014-06-30 at 09:27PM +0200, Boris BREZILLON wrote:
Hello Soren,
On Mon, 30 Jun 2014 09:56:33 -0700
Soren Brinkmann soren.brinkm...@xilinx.com wrote:
Introduce a
This patch cleans up the endianness conversions in the gdm72xx driver:
- Directly use the generic byte-reordering macros for endianness
conversion instead of some custom-defined macros.
- Convert values on the constant side instead of the variable side when
appropriate.
- Add endianness
On Mon, 30 Jun 2014, Nicholas Krause wrote:
Fixes a null pointer in appleir_input_configured due to reading
into wrong size array. Changed the variable to input_dev-keycodemax.
This is a stale changelog from the previous buggy version.
Signed-off-by: Nicholas Krause xerofo...@gmail.com
---
From: Edward Allcutt edward.allc...@openmarket.com
Date: Mon, 30 Jun 2014 16:16:02 +0100
This is explicitly described as an eventuality that hosts must deal
with by the standard (RFC 1191) since older standards specified that
those bits must be zero.
...
One example I have seen is an OpenBSD
On Tue, Jul 01, 2014 at 08:39:06AM +0200, Jiri Kosina wrote:
On Mon, 30 Jun 2014, Nicholas Krause wrote:
Fixes a null pointer in appleir_input_configured due to reading
into wrong size array. Changed the variable to input_dev-keycodemax.
This is a stale changelog from the previous buggy
On Tue, 1 Jul 2014, Mateusz Guzik wrote:
Fixes a null pointer in appleir_input_configured due to reading
into wrong size array. Changed the variable to input_dev-keycodemax.
This is a stale changelog from the previous buggy version.
Signed-off-by: Nicholas Krause
Around Mon 30 Jun 2014 23:04:59 -0400 or thereabout, Nicholas Krause wrote:
This patch removes the uneeded variables memory start and memory
stated in FIXME message before declaring this variables as extern
unsigned longs.
Thanks for cleaning, I will append it to my for-linus branch. Queuing
From: Anil Belur ask...@gmail.com
- this patch fixes jiffies comparision with a safer function to prevent
any overflows
Signed-off-by: Anil Belur ask...@gmail.com
---
drivers/staging/speakup/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
MAX77836 has the same Fuel Gauge as MAX17040/17048. The max17040 driver
can be safely re-used. The patch adds MAX77836 ID to array of
i2c_device_id.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Cc: Anton Vorontsov an...@enomsg.org
Cc:
Add support for MAX77836 charger to the max14577 driver. The MAX77836
charger is almost the same as 14577 model except:
- No dead-battery detection;
- Support for special charger (like in MAX77693);
- Support for DX over-voltage protection (like in MAX77693);
- Lower values of charging current
This patch prepares for changing the max14577 charger driver to allow
configuring battery-dependent settings from DTS.
The patch moves from regulator driver to MFD core driver and exports:
- function for calculating register value for charger's current;
- table of limits for chargers (MAX14577,
Add document describing device tree bindings for MAX14577 MFD
drivers: MFD core, extcon, regulator and charger.
Both MAX14577 and MAX77836 chipsets are documented.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Cc: Tomasz Figa
Hi,
This is resend of second part of patches adding support for MAX77836
device to the max14577 drivers. The first part (main MFD, extcon
and regulator drivers) was merged already.
The patches 1, 2 and 3 depends on each other so they should be
pulled at once. Patches 4 and 5 can be applied
Remove hard-coded values for:
- Fast Charge current,
- End Of Charge current,
- Fast Charge timer,
- Overvoltage Protection Threshold,
- Battery Constant Voltage,
and use DTS to configure them. This allows using the max14577 charger
driver with different batteries.
Now the charger driver
On Sat, Jun 28, 2014 at 11:48:40PM +0200, Rickard Strandqvist wrote:
Removal of a struct that is never used
This was found using a static code analysis program called cppcheck
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
It wasn't even used on the initial
This patch fix checkpath WARNING: Missing a blank line after declarations
Signed-off-by: Raphaël Poggi poggi.r...@gmail.com
---
drivers/staging/media/lirc/lirc_imon.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/staging/media/lirc/lirc_imon.c
This patch fix checkpath WARNING: void function return statements are not
generally useful.
The removed return were useless in that case.
Signed-off-by: Raphaël Poggi poggi.r...@gmail.com
---
drivers/staging/media/lirc/lirc_imon.c |6 --
1 file changed, 6 deletions(-)
diff --git
commit 1a680b7c moved pcie_aspm_powersave_config_link() out of
pci_raw_set_power_state() to pci_set_power_state() which would enable
ASPM. But, with commit db288c9c, which re-introduced the following check
./drivers/pci/pci.c: pci_set_power_state()
+ /* Check if we're already there */
+ if
On Tue, 1 Jul 2014 08:32:14 +0200
Boris BREZILLON boris.brezil...@free-electrons.com wrote:
Hi Sören,
On Mon, 30 Jun 2014 17:12:23 -0700
Sören Brinkmann soren.brinkm...@xilinx.com wrote:
Hi Boris,
On Mon, 2014-06-30 at 09:27PM +0200, Boris BREZILLON wrote:
Hello Soren,
On
On 07/01/2014 01:09 AM, Kees Cook wrote:
On Fri, Jun 27, 2014 at 5:05 PM, Alexei Starovoitov a...@plumgrid.com wrote:
Hi All,
this patch set demonstrates the potential of eBPF.
First patch net: filter: split filter.c into two files splits eBPF interpreter
out of networking into kernel/bpf/.
From: Bryan O'Donoghue bryan.odonog...@intel.com
The EHCI packet buffer in/out threshold is programmable for Intel Quark X1000
USB host controller, and the default value is 0x20 dwords. The in/out threshold
can be programmed to 0x80 dwords (512 Bytes) to maximize the perfomrance,
but only when
From: Alvin (Weike) Chen alvin.c...@intel.com
Hi,
Intel Quark X1000 consists of one USB host controller which can be PCI
enumerated. And the exsiting EHCI-PCI framework supports it with the
default packet buffer in/out threshold. We reconfigure the in/out threshold
as maximal as possible to
Fabian Frederick f...@skynet.be writes:
Fix checkpatch warning:
WARNING: kfree(NULL) is safe this check is probably not required
Cc: Larry Finger larry.fin...@lwfinger.net
Cc: Jes Sorensen jes.soren...@redhat.com
Cc: linux-wirel...@vger.kernel.org
Signed-off-by: Fabian Frederick
Fabian Frederick f...@skynet.be writes:
Fix checkpatch warning:
WARNING: kfree(NULL) is safe this check is probably not required
Cc: Larry Finger larry.fin...@lwfinger.net
Cc: Jes Sorensen jes.soren...@redhat.com
Cc: linux-wirel...@vger.kernel.org
Signed-off-by: Fabian Frederick
On Tue, Jul 1, 2014 at 1:30 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
From: Luis R. Rodriguez mcg...@suse.com
Now that the udev firmware loader is optional request_firmware()
will not provide any information on the kernel ring buffer if
direct firmware loading failed and udev
Peter,
On Tue, Jul 01, 2014 at 08:21:14AM +0800, Peter Chen wrote:
On Mon, Jun 30, 2014 at 03:33:13PM +0200, Antoine Ténart wrote:
On Fri, Jun 27, 2014 at 11:25:07AM +0800, Peter Chen wrote:
On Tue, Jun 24, 2014 at 12:35:16PM +0200, Antoine Ténart wrote:
ifneq ($(CONFIG_OF),)
On Mon, Jun 30, 2014 at 04:33:05PM +0100, Mark Rutland wrote:
On Mon, Jun 30, 2014 at 04:19:06PM +0100, Maxime Ripard wrote:
On Mon, Jun 30, 2014 at 03:20:54PM +0100, Mark Rutland wrote:
Hi Maxime,
On Mon, Jun 30, 2014 at 02:20:54PM +0100, Maxime Ripard wrote:
The Allwinner A31
Inline.
On 01/07/14 00:08, Stephen Warren wrote:
On 06/27/2014 02:11 AM, Mikko Perttunen wrote:
This adds support for hardware-tracked trip points to the device tree
thermal sensor framework.
The framework supports an arbitrary number of trip points. Whenever
the current temperature is
+#ifdef CONFIG_PARPORT_1284
+MODULE_PARM_DESC(force_epp, Do not disable EPP when it is detected to
be broken (default is false));
I think this needs some more explanation - how about
Disable check for broken Intel EPP hardware that gives false positives on
2002 and newer hardware
I would
On Mon, Jun 30, 2014 at 12:11:35PM -0700, Guenter Roeck wrote:
The kernel core now supports a notifier call chain to restart the system.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
arch/arm64/kernel/process.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
On 2014-07-01 04:15, Hui Wang wrote:
On 06/30/2014 02:45 PM, Jan Kiszka wrote:
On 2014-06-30 04:04, Hui Wang wrote:
On 06/29/2014 07:33 PM, Jan Kiszka wrote:
On 2013-11-27 07:47, Hui Wang wrote:
Most Thinkpad Edge series laptops use conexant codec, so far although
the codecs have different
On Tue, 01 Jul 2014, Krzysztof Kozlowski wrote:
This is resend of second part of patches adding support for MAX77836
device to the max14577 drivers. The first part (main MFD, extcon
and regulator drivers) was merged already.
The patches 1, 2 and 3 depends on each other so they should be
On Mon, 30 Jun 2014, Nishanth Menon wrote:
reg_info is a generic term which might cause conflict at a later point
in time. To prevent such a thing from occuring in future, rename to
palmas_reg_info.
Signed-off-by: Nishanth Menon n...@ti.com
---
drivers/regulator/palmas-regulator.c |4
On Mon, 30 Jun 2014 07:45:43 -0700
Greg Kroah-Hartman gre...@linuxfoundation.org wrote:
From: Of Richard Leitner
Replaces all hardcoded ttyGS strings with the PREFIX macro.
Due to the fact the strings are spread over different source files
the
PREFIX definition is
From: Yang Wei wei.y...@windriver.com
The pair read/write of accessing pci confiuration space function
has already protected by pci_lock. so remove nano_lock.
Signed-off-by: Yang Wei wei.y...@windriver.com
---
arch/arm/mach-sa1100/pci-nanoengine.c |9 -
1 file changed, 9
On Fri, Jun 27, 2014 at 01:01:03AM +0200, Gregory CLEMENT wrote:
The last patch removed a direct access to the SCU register by an
access through the new scu_standby_enable() function. For this one I
have just checked that the kernel can be built using the
imx_v6_v7_defconfig config, but I
On Mon, Jun 30, 2014 at 10:49:03AM -0500, Christoph Lameter wrote:
On Fri, 27 Jun 2014, Joonsoo Kim wrote:
Christoph,
Is it tolerable result for large scale system? Or do we need to find
another solution?
The overhead is pretty intense but then this is a rare event I guess?
Yes,
Inline.
On 30/06/14 23:48, Stephen Warren wrote:
On 06/27/2014 02:11 AM, Mikko Perttunen wrote:
This adds the soctherm thermal sensing and management unit to the
Tegra124 device tree along with the four thermal zones it exports.
diff --git a/arch/arm/boot/dts/tegra124.dtsi
On 2014-6-30 18:46, Catalin Marinas wrote:
On Fri, Jun 27, 2014 at 04:49:36AM +0100, Hanjun Guo wrote:
diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
index 7de5e3f..33d6dbb 100644
--- a/drivers/acpi/Kconfig
+++ b/drivers/acpi/Kconfig
@@ -8,10 +8,10 @@ config ACPI_SCAN_BIOS_NOT_EFI
On Mon, Jun 30, 2014 at 04:39:09PM -0700, Andrew Morton wrote:
I can fix it and resubmit if you like.
OK. How about we wait for -rc6 or thereabouts? That should minimise
the pain profile.
Or just drop it. This is the perfect example for a patch having
absolutely no real benefit and
Below is the list of build error/warning regressions/improvements in
v3.16-rc3[1] compared to v3.15-rc8[2].
Summarized:
- build errors: +19/-3
- build warnings: +89/-68
JFYI, when comparing v3.16-rc3[1] to v3.16-rc2[3], the summaries are:
- build errors: +5/-63
- build warnings: +35/-38
* Jason Cooper ja...@lakedaemon.net [140630 12:30]:
Whole series applied to irqchip/crossbar, I'll give it a day or two in
-next, then I'll merge it into irqchip/core.
Tony: Right now, it's immutable unless you tell me I applied something
incorrectly. Once it goes into irqchip/core, it's
On Tue, Jul 1, 2014 at 9:58 AM, Geert Uytterhoeven ge...@linux-m68k.org wrote:
JFYI, when comparing v3.16-rc3[1] to v3.16-rc2[3], the summaries are:
- build errors: +5/-63
+ /scratch/kisskb/src/kernel/bounds.c: error: -mcall-aixdesc must be
big endian: = 1:0
+
On Mon, Jun 30, 2014 at 03:09:14PM -0700, Andrew Morton wrote:
On Mon, 30 Jun 2014 22:51:21 +0100 Mel Gorman mgor...@suse.de wrote:
That's a large change in system time. Does this all include kswapd
activity?
I don't have a profile to quantify that exactly. It takes 7 hours to
On 06/28/2014 02:06 AM, Alexei Starovoitov wrote:
Safety of eBPF programs is statically determined by the verifier, which detects:
- loops
- out of range jumps
- unreachable instructions
- invalid instructions
- uninitialized register access
- uninitialized stack access
- misaligned stack access
On Sat, Jun 28, 2014 at 02:47:04PM +0530, Raghavendra K T wrote:
In virtualized environment there are mainly three problems
related to spinlocks that affects performance.
1. LHP (lock holder preemption)
2. Lock Waiter Preemption (LWP)
3. Starvation/fairness
Though Ticketlocks solve
Inline.
On 01/07/14 00:23, Stephen Warren wrote:
On 06/27/2014 02:11 AM, Mikko Perttunen wrote:
This adds support for the Tegra SOCTHERM thermal sensing and management
system found in the Tegra124 system-on-chip. This initial driver supports
the four thermal zones with hardware-tracked trip
On Mon, Jun 30, 2014 at 09:01:07PM -0600, Jens Axboe wrote:
I appreciate very much that one of you may queue these two
patches into your tree so that userspace work can be kicked off,
since Michael has acked both patches and all comments have
been addressed already.
Given that Michael also
On Mon, Jun 30, 2014 at 03:22:24PM -0700, Andi Kleen wrote:
I'm also interested in the behaviour of CondChgd bit on Ivy Bridge
processors.
The intended meaning of CondChgd is that a hardware debugger has taken over
the
PMU. It shouldn't really be set in other circumstances.
The SDM
On Mon, Jun 30, 2014 at 01:39:39PM -0700, Andrew Morton wrote:
On Mon, 30 Jun 2014 21:03:17 +0200 Fabian Frederick f...@skynet.be wrote:
proc_uid_seq_operations, proc_gid_seq_operations and
proc_projid_seq_operations
are only called in proc_id_map_open with seq_open as
const struct
Commit 71e3aac (thp: transparent hugepage core) adds copy_pte_range
prototype to huge_mm.h. I'm not sure why (or if) this function have
been used outside of memory.c, but it currently isn't.
This patch makes copy_pte_range() static again.
Signed-off-by: Jerome Marchand jmarc...@redhat.com
---
On Tue, Jun 24, 2014 at 11:34:54AM +0800, Michael wang wrote:
On 06/23/2014 05:42 PM, Peter Zijlstra wrote:
[snip]
+}
Still completely hate this, it doesn't make sense conceptual sense what
so ever.
Yeah... and now I agree your opinion that this could not address all the
cases after
depends on PCI
select PNP
- default y
+ default y if !ARM64
For the benefit of single Image, I think you can default to y here.
It ok to me. if we default to y here, devicetree will not be unflattened
in default, is it ok to you? you can refer to [PATCH 12/13] ARM64 / ACPI:
node isn't changed, so we don't need to retreive this structure
everytime we move the object. Maybe compiler do this optimization,
but making it explicitly is better.
Acked-by: Christoph Lameter c...@linux.com
Signed-off-by: Joonsoo Kim iamjoonsoo@lge.com
---
mm/slab.c |3 +--
1 file
Factor out initialization of array cache to use it in following patch.
Acked-by: Christoph Lameter c...@linux.com
Signed-off-by: Joonsoo Kim iamjoonsoo@lge.com
---
mm/slab.c | 33 +++--
1 file changed, 19 insertions(+), 14 deletions(-)
diff --git a/mm/slab.c
On Mon, Jun 30, 2014 at 09:56:33AM -0700, Soren Brinkmann wrote:
Introduce a new API function to find the rate a clock can provide which
is closest to a given rate.
clk_round_rate() leaves it to the clock driver how rounding is done.
Commonly implementations round down due to use-cases that
BAD_ALIEN_MAGIC value isn't used anymore. So remove it.
Acked-by: Christoph Lameter c...@linux.com
Signed-off-by: Joonsoo Kim iamjoonsoo@lge.com
---
mm/slab.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/mm/slab.c b/mm/slab.c
index 7820a45..60c9e11 100644
---
slab_should_failslab() is called on every allocation, so to optimize it
is reasonable. We normally don't allocate from kmem_cache. It is just
used when new kmem_cache is created, so it's very rare case. Therefore,
add unlikely macro to help compiler optimization.
Acked-by: David Rientjes
Hi Stefano,
On 30/06/14 20:09, Stefano Stabellini wrote:
On Wed, 25 Jun 2014, Anup Patel wrote:
Hi Marc,
On Wed, Jun 25, 2014 at 2:58 PM, Marc Zyngier marc.zyng...@arm.com wrote:
So far, GICv2 has been used in with EOImode == 0. The effect of this
mode is to perform the priority drop and
In free_block(), if freeing object makes new free slab and number of
free_objects exceeds free_limit, we start to destroy this new free slab
with holding the kmem_cache node lock. Holding the lock is useless and,
generally, holding a lock as least as possible is good thing. I never
measure
This patchset does some clean-up and tries to remove lockdep annotation.
Patches 1~2 are just for really really minor improvement.
Patches 3~9 are for clean-up and removing lockdep annotation.
There are two cases that lockdep annotation is needed in SLAB.
1) holding two node locks
2) holding two
Now, we have separate alien_cache structure, so it'd be better to hold
the lock on alien_cache while manipulating alien_cache. After that,
we don't need the lock on array_cache, so remove it.
Acked-by: Christoph Lameter c...@linux.com
Signed-off-by: Joonsoo Kim iamjoonsoo@lge.com
---
Currently, we use array_cache for alien_cache. Although they are mostly
similar, there is one difference, that is, need for spinlock.
We don't need spinlock for array_cache itself, but to use array_cache for
alien_cache, array_cache structure should have spinlock. This is needless
overhead, so
Now, there is no code to hold two lock simultaneously, since
we don't call slab_destroy() with holding any lock. So, lockdep
annotation is useless now. Remove it.
v2: don't remove BAD_ALIEN_MAGIC in this patch. It will be removed
in the following patch.
Acked-by: Christoph Lameter
I haven't heard that this alien cache lock is contended, but to reduce
chance of contention would be better generally. And with this change,
we can simplify complex lockdep annotation in slab code.
In the following patch, it will be implemented.
Acked-by: Christoph Lameter c...@linux.com
On 06/28/2014 02:06 AM, Alexei Starovoitov wrote:
User interface:
cat bpf_123 /sys/kernel/debug/tracing/__event__/filter
where 123 is an id of the eBPF program priorly loaded.
__event__ is static tracepoint event.
(kprobe events will be supported in the future patches)
eBPF programs can call
On Mon, Jun 30, 2014 at 10:43:42PM +0100, Mark Brown wrote:
On Mon, Jun 30, 2014 at 06:21:15PM +0100, Mark Rutland wrote:
On Mon, Jun 30, 2014 at 06:10:59PM +0100, Dan Murphy wrote:
+Optional properties:
+- power-gpio - gpio pin to enable/disable the device
The code below seems to
On 07/01/2014 04:20 PM, Peter Zijlstra wrote:
[snip]
Just wondering could we make this another scheduler feature?
No; sched_feat() is for debugging, BIG CLUE: its guarded by
CONFIG_SCHED_DEBUG, anybody using it in production or anywhere else is
broken.
If people are using it, I should
On 2014년 06월 30일 22:25, Krzysztof Kozlowski wrote:
Fix a NULL pointer exception when main exynos drm driver was probed
successfully but no components were added (e.g. by incomplete DTS). In
such case the exynos_drm_load() is never called and drvdata is NULL.
Right, it's good report. Applied.
On Tue, Jul 1, 2014 at 10:17 AM, Christoph Hellwig h...@infradead.org wrote:
On Mon, Jun 30, 2014 at 01:39:39PM -0700, Andrew Morton wrote:
On Mon, 30 Jun 2014 21:03:17 +0200 Fabian Frederick f...@skynet.be wrote:
proc_uid_seq_operations, proc_gid_seq_operations and
On Tue, 1 Jul 2014, David Miller wrote:
From: Edward Allcutt edward.allc...@openmarket.com
Date: Mon, 30 Jun 2014 16:16:02 +0100
This is explicitly described as an eventuality that hosts must deal
with by the standard (RFC 1191) since older standards specified that
those bits must be zero.
From: Jianqun Xu x...@rock-chips.com
This patch is to add driver for I2S controller in RK3xxx SoCs.
Jianqun Xu (2):
ASoC: dt-bindings: add rockchip i2s bindings
ASoC: add driver for Rockchip RK3xxx I2S controller
.../devicetree/bindings/sound/rockchip-i2s.txt | 45 ++
From: Jianqun Xu x...@rock-chips.com
Add devicetree bindings for i2s controller found on rk3066, rk3188 and rk3288
processors from rockchip.
Signed-off-by: Jianqun Xu x...@rock-chips.com
---
.../devicetree/bindings/sound/rockchip-i2s.txt | 45
1 file changed, 45
On Mon, Jun 30, 2014 at 04:17:10PM -0700, Bryan Wu wrote:
On Mon, Jun 30, 2014 at 4:33 AM, Jiri Kosina jkos...@suse.cz wrote:
On Mon, 30 Jun 2014, Johan Hovold wrote:
I think the better place is HID/input tree, since this patch depends
on the initial one which is not in my tree.
I'm
From: Jianqun Xu x...@rock-chips.com
Add driver for I2S controller in Rockchip RK3xxx SoCs.
This driver patch has been tested on the RK3288 SDK board.
Signed-off-by: Jianqun Xu x...@rock-chips.com
---
sound/soc/Kconfig |1 +
sound/soc/Makefile|1 +
From: Jianqun Xu x...@rock-chips.com
Add driver for I2S controller in Rockchip RK3xxx SoCs.
This driver patch has been tested on the RK3288 SDK board.
Signed-off-by: Jianqun Xu x...@rock-chips.com
---
sound/soc/Kconfig |1 +
sound/soc/Makefile|1 +
On Tue, Jul 01, 2014 at 09:37:39AM +0100, jianqun wrote:
From: Jianqun Xu x...@rock-chips.com
Add devicetree bindings for i2s controller found on rk3066, rk3188 and rk3288
processors from rockchip.
Signed-off-by: Jianqun Xu x...@rock-chips.com
---
On 07/01/2014 02:21 AM, Peter Chen wrote:
On Mon, Jun 30, 2014 at 03:33:13PM +0200, Antoine Ténart wrote:
On Fri, Jun 27, 2014 at 11:25:07AM +0800, Peter Chen wrote:
On Tue, Jun 24, 2014 at 12:35:16PM +0200, Antoine Ténart wrote:
+
+static const struct of_device_id ci_hdrc_generic_of_match[]
On Tue, Jul 01, 2014 at 04:38:58PM +0800, Michael wang wrote:
On 07/01/2014 04:20 PM, Peter Zijlstra wrote:
[snip]
Just wondering could we make this another scheduler feature?
No; sched_feat() is for debugging, BIG CLUE: its guarded by
CONFIG_SCHED_DEBUG, anybody using it in
On Tue, Jul 01, 2014 at 09:47:38AM +0100, jianqun wrote:
From: Jianqun Xu x...@rock-chips.com
Add driver for I2S controller in Rockchip RK3xxx SoCs.
This driver patch has been tested on the RK3288 SDK board.
Signed-off-by: Jianqun Xu x...@rock-chips.com
---
sound/soc/Kconfig
I already send this series before (in time for 3.16) and AFAIK we agreed
on going with this series instead of the incomplete fix for the related oops
which now has been merged as commit d137be00ee017bc40e6027cb66d667a2e0b450fd
I still believe that this series is the more correct fix, as
Hi,
On 07/01/2014 11:05 AM, Lee Jones wrote:
I already send this series before (in time for 3.16) and AFAIK we agreed
on going with this series instead of the incomplete fix for the related oops
which now has been merged as commit d137be00ee017bc40e6027cb66d667a2e0b450fd
I still believe that
At Mon, 30 Jun 2014 12:45:54 -0400,
Valdis Kletnieks wrote:
Seeing this on a Dell Latitude E6530 - kernel lives for just a few
seconds before committing hari-kiri trying to initialize the sound chipset.
The bug has been fixed yesterday, so today's next tree should work.
Let me know if you
On Mon, 30 Jun 2014, Paul Bolle pebo...@tiscali.nl wrote:
Kernels v3.16-rc2 and v3.16-rc3 trigger a new (for me) warning. (I never
booted v3.16-rc1). Machine is a, rather outdated, ThinkPad X41 (ie,
single core i686).
WARNING: CPU: 0 PID: 221 at drivers/gpu/drm/i915/intel_display.c:1274
On Mon, Jun 30, 2014 at 03:28:14PM -0700, Andy Lutomirski wrote:
On Mon, Jun 30, 2014 at 3:28 AM, David Drysdale drysd...@google.com wrote:
Signed-off-by: David Drysdale drysd...@google.com
---
man2/cap_rights_get.2 | 126
++
1 file
On 27.06.2014 20:04, mathieu.poir...@linaro.org wrote:
From: Mathieu Poirier mathieu.poir...@linaro.org
Support for the 2 PTMs, 3 ETMs, funnel, TPIU and replicator
connected to the ETB are included. Proper handling of the
ITM and the replicator linked to it along with the CTIs
and SWO are not
On Tue, Jul 01, 2014 at 09:20:20AM +0100, Hanjun Guo wrote:
depends on PCI
select PNP
- default y
+ default y if !ARM64
For the benefit of single Image, I think you can default to y here.
It ok to me. if we default to y here, devicetree will not be unflattened
in default, is
WARNING: drivers/built-in.o(.data+0x10258):
Section mismatch in reference from the variable ppc_corenet_clk_driver
to the (unknown reference) .init.rodata:(unknown)
The variable ppc_corenet_clk_driver references
the (unknown reference) __initconst (unknown)
If the reference is valid then annotate
At Tue, 1 Jul 2014 11:54:24 +0800,
Ming Lei wrote:
On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
From: Luis R. Rodriguez mcg...@suse.com
Now that the udev firmware loader is optional request_firmware()
will not provide any information on the kernel
On Mon, 30 Jun 2014, Hans de Goede wrote:
We cannot register supply alias in mfd_add_device before calling
platform_add_device because platform-dev's name must be set before registering
the aliases which happens from platform_add_device.
So stop registering supply aliases from
On 07/01/2014 03:38 PM, Jan Kiszka wrote:
On 2014-07-01 04:15, Hui Wang wrote:
On 06/30/2014 02:45 PM, Jan Kiszka wrote:
On 2014-06-30 04:04, Hui Wang wrote:
On 06/29/2014 07:33 PM, Jan Kiszka wrote:
On 2013-11-27 07:47, Hui Wang wrote:
Most Thinkpad Edge series laptops use conexant codec,
On 07/01/2014 02:09 PM, jianqun wrote:
From: Jianqun Xu x...@rock-chips.com
[...]
+
+static int rockchip_i2s_hw_params(struct snd_pcm_substream *substream,
+ struct snd_pcm_hw_params *params, struct snd_soc_dai *dai)
Proper indentation for function arguments, otherwise checkpatch.pl
On Mon, Jun 30, 2014 at 04:04:08PM -0700, David Rientjes wrote:
It's unnecessary to excessively spam the kernel log anytime the BTS buffer
cannot be allocated, so make this allocation __GFP_NOWARN.
The user probably will want to at least find some artifact that the
allocation has failed in
The current AT91 DT boards have a completely generic init_time definition.
Remove them from the machine declaration.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/mach-at91/board-dt-sam9.c | 11 ---
arch/arm/mach-at91/board-dt-sama5.c | 10 --
2
We can use the generic request_irq now to register a timer interrupt handler,
instead of the more complex setup_irq.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/mach-at91/at91sam926x_time.c | 20 ++--
1 file changed, 6 insertions(+), 14 deletions(-)
All the panic messages hardcode the same prefix. Define the pr_fmt macro to
unify its definition.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/mach-at91/at91sam926x_time.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git
Now that we don't depend on anyting in the mach-at91 directory, we can just
move the driver to where it belongs.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/mach-at91/Kconfig | 6 --
arch/arm/mach-at91/Makefile
1 - 100 of 1422 matches
Mail list logo
