On Wed, 5 Feb 2014, Peter Zijlstra wrote:
> On Wed, Feb 05, 2014 at 02:37:29PM -0500, Vince Weaver wrote:
> > On Wed, 5 Feb 2014, Vince Weaver wrote:
> >
> > > Has someone actually hit this bug? People used PAPI/perfctr on these
> > > machines for years, and it uses rdpmc by default so I would
On Wed, Feb 05, 2014 at 12:15:33PM +0400, Vladimir Davydov wrote:
> Commit c65c1877bd68 ("slub: use lockdep_assert_held") requires
> remove_partial() to be called with n->list_lock held, but free_partial()
> called from kmem_cache_close() on cache destruction does not follow this
> rule, leading to
On Wed, 5 Feb 2014, Kamil Debski wrote:
> Hi Alan,
>
> Thank you for your review.
You're welcome.
> >
> > > Change the phy provider used from the old one using the USB phy
> > You have removed all the OTG stuff from the driver. This wasn't
> > mentioned in the patch description, and it has no
On Wed, Feb 05, 2014 at 02:37:29PM -0500, Vince Weaver wrote:
> On Wed, 5 Feb 2014, Vince Weaver wrote:
>
> > Has someone actually hit this bug? People used PAPI/perfctr on these
> > machines for years, and it uses rdpmc by default so I would think it would
> > show up if it were an issue. I s
On Wed, Feb 05, 2014 at 01:24:59PM -0500, Gene Heskett wrote:
> >/home/gene/src/linux-3.2.40/Documentation/usb/gadget_multi.txt:
> >MBL_400944.UNOFFICIAL FOUND
>
> You will see more history.
>
> So that file needs sanitized. I was under the impression that a file with
> the .txt extension was s
On Wed, Feb 05, 2014 at 02:29:36PM -0500, Vince Weaver wrote:
> from the document you linked it looks like it was fixed by the Pentium
> Pro stepping sB1 (6.1.9).
OK, I'll add a boot_cpu_data.x86_mask >= 0xB1 test.
> Has someone actually hit this bug? People used PAPI/perfctr on these
> machin
Add bindings for TI Async External Memory Interface (AEMIF) controller.
The Async External Memory Interface (EMIF16/AEMIF) controller is intended to
provide a glue-less interface to a variety of asynchronous memory devices like
ASRA M, NOR and NAND memory. A total of 256M bytes of any of these mem
Add new AEMIF driver for EMIF16 Texas Instruments controller.
The EMIF16 module is intended to provide a glue-less interface to
a variety of asynchronous memory devices like ASRA M, NOR and NAND
memory. A total of 256M bytes of any of these memories can be
accessed at any given time via 4 chip sele
On Wed, Feb 05, 2014 at 08:20:12PM +0100, Peter Zijlstra wrote:
> On Wed, Feb 05, 2014 at 02:16:43PM -0500, Vince Weaver wrote:
> > On Wed, 5 Feb 2014, Peter Zijlstra wrote:
> >
> > > P6 class machines can die hard when PCE gets enabled due to CPU
> > > errata. The safe way it so disable it by def
These patches introduce Async External Memory Interface (EMIF16/AEMIF)
controller driver for Davinci/Keystone archs.
For more informations see documentation:
Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
OMAP-L138 - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
Kestone - http://
On Wed, 5 Feb 2014, Vince Weaver wrote:
> Has someone actually hit this bug? People used PAPI/perfctr on these
> machines for years, and it uses rdpmc by default so I would think it would
> show up if it were an issue. I should check the perfctr code to see if it
> had some sort of check.
I
On Wed, Feb 05, 2014 at 10:07:50AM +, Grant Likely wrote:
> On Tue, 04 Feb 2014 13:09:33 +0100, Marek Szyprowski
> wrote:
> > From: Grant Likely
> > +/reserved-memory node
> > +-
> > +#address-cells, #size-cells (required) - standard definition
> > +- Should use the s
Acked-by: Christoph Lameter
--
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.html
Please read the FAQ at http://www.tux.org/lkml/
From: Ville Syrjälä
For gen2 devices we're going to need another way to determine the
stolen memory base address. Make that into a vfunc as well.
Also drop the bogus inline keyword from gen8_stolen_size().
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: x...@kernel.org
Cc: linux
From: Ville Syrjälä
There isn't an explicit stolen memory base register on gen2.
Some old comment in the i915 code suggests we should get it via
max_low_pfn_mapped, but that's clearly a bad idea on my MGM.
The e820 map in said machine looks like this:
[0.00] BIOS-e820: [mem 0x000
From: Ville Syrjälä
Ingo asked me to post the x86 bits as a standalone series. So here it is.
So the series adds the Intel gen2 graphics stolen memory reservation quirks
to arch/x86. These are not unlike the quirks we have for later gens, except
it's a bit more work to dig out the correct range
From: Ville Syrjälä
Print an informative message when reserving the graphics stolen
memory region in the early quirk.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: x...@kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ville Syrjälä
---
arch/x86/kernel/early-quirks.c
On Wed, 5 Feb 2014, Peter Zijlstra wrote:
> On Wed, Feb 05, 2014 at 02:16:43PM -0500, Vince Weaver wrote:
> > On Wed, 5 Feb 2014, Peter Zijlstra wrote:
> >
> > > P6 class machines can die hard when PCE gets enabled due to CPU
> > > errata. The safe way it so disable it by default and keep it disa
On Wed, 5 Feb 2014, Fengguang Wu wrote:
> > I think this is the inlined add_full() and should be fixed with
> > http://marc.info/?l=linux-kernel&m=139147105027693 that has been added to
> > the -mm tree and should now be in next. Is this patch included for this
> > kernel?
>
> Hi David,
>
>
Hello.
On 02/05/2014 10:01 PM, Matt Porter wrote:
[...]
This series adds support for PWM capture devices within IIO and
adds a TI ECAP IIO driver.
PWM capture devices are supported using a new IIO "pulse" channel type.
The IIO ECAP driver implements interrupt driven triggered buffer capt
On Wed, 5 Feb 2014, Peter Zijlstra wrote:
> P6 class machines can die hard when PCE gets enabled due to CPU
> errata. The safe way it so disable it by default and keep it disabled.
>
> See errata 26:
so you take an errata applicable to a subset of Pentium Pro steppings and
apply it to the whole
On Wed, Feb 05, 2014 at 02:16:43PM -0500, Vince Weaver wrote:
> On Wed, 5 Feb 2014, Peter Zijlstra wrote:
>
> > P6 class machines can die hard when PCE gets enabled due to CPU
> > errata. The safe way it so disable it by default and keep it disabled.
> >
> > See errata 26:
>
> so you take an err
On 01/28/2014 04:36 PM, Peter De Schrijver wrote:
> Implement fuse driver for Tegra20, Tegra30, Tegra114 and Tegra124.
I assume most of this code is simply cut/paste from the existing code in
arch/arm/mach-tegra/? If so, "git format-patch -C" would have been
useful to highlight what changed when d
On Tue, Feb 04, 2014 at 09:57:49AM +0100, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.14-rc1[1] compared to v3.13[2].
>
[ ... ]
> *** ERRORS ***
>
> 9 regressions:
> + /scratch/kisskb/src/arch/powerpc/kernel/exceptions-64s.S: Error: atte
Add missing interrupt properties to the ecap0, ecap1, and ecap2
nodes.
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am33xx.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 6d95d3d..b4139ba 100644
--- a/arch/arm
Add the pulse driver subdirectory when configuring and building
IIO.
Signed-off-by: Matt Porter
---
drivers/iio/Kconfig | 1 +
drivers/iio/Makefile | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
index 5dd0e12..286acc3 100644
--- a/drivers/iio/Kco
Add standard ABI entries for pulse capture devices. Also add
a separate ABI entry for the TI ECAP driver polarity option.
Signed-off-by: Matt Porter
---
Documentation/ABI/testing/sysfs-bus-iio | 18 ++
Documentation/ABI/testing/sysfs-bus-iio-pulse-tiecap | 9 +++
Add a channel type to support pulse width capture devices.
These devices capture the timing of a PWM signal based on a
configurable trigger
Signed-off-by: Matt Porter
---
drivers/iio/industrialio-core.c | 1 +
include/linux/iio/types.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/
Adds support for capturing PWM signals using the TI ECAP peripheral.
This driver supports triggered buffer capture of pulses on multiple
ECAP instances. In addition, the driver supports configurable polarity
of the signal to be captured.
Signed-off-by: Matt Porter
---
drivers/iio/pulse/Kconfig
Changes since v2:
- Remove various unneeded field initialization
- Call iio_triggered_buffer_cleanup() on remove
Changes since v1:
- Rebased to 3.14-rc1
- Renamed in_pulse_polarity to pulse_polarity
- Added ABI entries for pulse devices and TI ECAP
This ser
The IIO TI ECAP driver depends on the TI PWMSS management
driver in this subsystem. Enable PWMSS when the IIO TI ECAP
driver is selected.
Signed-off-by: Matt Porter
---
drivers/pwm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconf
On 5 February 2014 02:03, Linus Walleij wrote:
> On Mon, Feb 3, 2014 at 10:43 PM, Markus Mayer wrote:
>
>> Add Broadcom's upstreaming mailing list address to MODULE_AUTHOR.
>>
>> Signed-off-by: Markus Mayer
>
> Hm OK not that this is used very much, and nothing to argue about
> so patch applied.
On 02/05/2014 07:41 PM, Rob Herring wrote:
On Wed, Feb 5, 2014 at 10:18 AM, Ivan Khoronzhuk wrote:
On 02/05/2014 04:39 PM, Rob Herring wrote:
On Wed, Feb 5, 2014 at 7:47 AM, Ivan Khoronzhuk
wrote:
This patch provides bindings for the 64-bit timer in the KeyStone
architecture devices. The ti
On 01/28/2014 04:36 PM, Peter De Schrijver wrote:
> This driver allows userspace to read the raw efuse data. Its userspace
> interface is modelled after the sunxi_sid driver which provides similar
> functionality for some Allwinner SoCs. It has been tested on
> Tegra20 (ventana), Tegra30 (beaverboa
On 01/28/2014 04:36 PM, Peter De Schrijver wrote:
> All fuse related functionality is now provided by the tegra fuse driver.
> Hence all the fuse related files in mach-tegra can be removed.
It's probably worth squashing this into patch 5, since that's what makes
these files unused.
--
To unsubscri
On Wed, Feb 05, 2014 at 05:48:35PM +, Adam Thomson wrote:
> +#ifdef CONFIG_OF
> +#include
> +#include
> +#endif /* CONFIG_OF */
Don't do ifdefs for includes like this, it's not worth it.
> + for_each_child_of_node(nproot, np) {
> + if (!of_node_cmp(np->name,
> +
On Wed, Feb 5, 2014 at 6:55 PM, Peter Zijlstra wrote:
> On Wed, Feb 05, 2014 at 06:19:27PM +0100, Stephane Eranian wrote:
>> On Fri, Jan 3, 2014 at 6:48 AM, Yan, Zheng wrote:
>> > If two tasks were both forked from the same parent task, Events in their
>> > perf
>> > task contexts can be the sam
On 01/28/2014 04:36 PM, Peter De Schrijver wrote:
> Enable building the fuse drivers.
This isn't really about enabling them. It's about changing which Tegra
fuse driver is built. Perhaps rephrase this more as:
ARM: tegra: build fuse driver from drivers/misc instead
The Tegra fuse code has moved
On 01/28/2014 04:36 PM, Peter De Schrijver wrote:
> Add efuse bindings for Tegra20, Tegra30, Tegra114 and Tegra124.
> diff --git a/Documentation/devicetree/bindings/fuse/fuse-tegra.txt
> b/Documentation/devicetree/bindings/fuse/fuse-tegra.txt
> +- clocks: Should contain a pointer to the fuse clo
From: Glauber Costa
When a memcg is destroyed, it won't be imediately released until all
objects are gone. This means that if a memcg is restarted with the very
same workload - a very common case, the objects already cached won't be
billed to the new memcg. This is mostly undesirable since a cont
Hi,
This is the 15th iteration of Glauber Costa's patch-set implementing slab
shrinking on memcg pressure. The main idea is to make the list_lru structure
used by most FS shrinkers per-memcg. When adding or removing an element from a
list_lru, we use the page information to figure out which memcg
There are several FS shrinkers, including super_block::s_shrink, that
keep reclaimable objects in the list_lru structure. That said, to turn
them to memcg-aware shrinkers, it is enough to make list_lru per-memcg.
This patch does the trick. It adds an array of LRU lists to the list_lru
structure, o
From: Glauber Costa
I caught myself doing something like the following outside memcg core:
memcg_id = -1;
if (memcg && memcg_kmem_is_active(memcg))
memcg_id = memcg_cache_id(memcg);
to be able to handle all possible memcgs in a sane manner. In particular, the
roo
From: Glauber Costa
Those structures are only used for memcgs that are effectively using
kmemcg. However, in a later patch I intend to use scan that list
inconditionally (list empty meaning no kmem caches present), which
simplifies the code a lot.
So move the initialization to early kmem creatio
I am going to use these macros in next patches, so let's move them to
the header. These macros are very handy and they depend only on
mem_cgroup_iter(), which is already public, so I guess it's worth it.
Signed-off-by: Vladimir Davydov
Cc: Glauber Costa
Cc: Michal Hocko
Cc: Johannes Weiner
Cc:
From: Glauber Costa
Each caller of memcg_cache_id ends up sanitizing its parameters in its own way.
Now that the memcg_cache_id itself is more robust, we can consolidate this.
Also, as suggested by Michal, a special helper memcg_cache_idx is used when the
result is expected to be used directly a
We are going to make the FS shrinker memcg-aware. To achieve that, we
will have to pass the memcg to scan to the nr_cached_objects and
free_cached_objects VFS methods, which currently take only the NUMA node
to scan. Since the shrink_control structure already holds the node, and
the memcg to scan w
To make list_lru per-memcg, I'll have to add some code that might sleep
to list_lru_destroy(), but it is impossible to do now, because
list_lru_destroy() is currently called by destroy_super(), which can be
called in atomic context from __put_super().
To overcome this, in this patch I make __put_s
From: Glauber Costa
When we delete kmem-enabled memcgs, they can still be zombieing around
for a while. The reason is that the objects may still be alive, and we
won't be able to delete them at destruction time.
The only entry point for that, though, are the shrinkers. The shrinker
interface, ho
On Wed, 2014-02-05 at 17:52 +0800, Fabian Frederick wrote:
> Adding generic fsdevel section for ADFS.
> I guess status can be considered 'orphan' like affs and befs.
and cramfs and efs and hfs and hfsplus too.
Other fs/ directories without MAINTAINERS sections:
fs/devpts
fs/exportfs
fs/isofs
fs/
Now, to make any list_lru-based shrinker memcg aware we should only
initialize its list_lru as memcg-enabled. Let's do it for the general FS
shrinker (super_block::s_shrink) and mark it as memcg aware.
There are other FS-specific shrinkers that use list_lru for storing
objects, such as XFS and GFS
On 01/28/2014 04:36 PM, Peter De Schrijver wrote:
> All fuse related functionality will move to a driver in the following patches.
> To prepare for this, export all the required functionality in a global header
> file and move all users of fuse.h to tegra-soc.h
The patch subject and description do
From: Glauber Costa
During the past weeks, it became clear to us that the shrinker interface
we have right now works very well for some particular types of users,
but not that well for others. The latter are usually people interested
in one-shot notifications, that were forced to adapt themselves
NUMA aware slab shrinkers use the list_lru structure to distribute
objects coming from different NUMA nodes to different lists. Whenever
such a shrinker needs to count or scan objects from a particular node,
it issues commands like this:
count = list_lru_count_node(lru, sc->nid);
f
This patch makes direct reclaim path shrink slab not only on global
memory pressure, but also when we reach the user memory limit of a
memcg. To achieve that, it makes shrink_slab() walk over the memcg
hierarchy and run shrinkers marked as memcg-aware on the target memcg
and all its descendants. Th
On Sat, Jan 25, 2014 at 07:19:06PM +0100, Sebastian Hesselbarth wrote:
> This patch set fixes clk init order that went upside-down with
> v3.14. I haven't really investigated what caused this, but I assume
> it is related with DT node reordering by addresses.
>
> Anyway, with v3.14 for MVEBU SoCs,
On Wed, Feb 05, 2014 at 05:48:32PM +, Adam Thomson wrote:
> Currently the I2C device Ids conflict for the MFD and CODEC so
> cannot be both instantiated on one platform. This patch updates
> the Ids and names to make them unique from each other.
Acked-by: Mark Brown
signature.asc
Descriptio
On Wednesday 05 February 2014, Gene Heskett wrote:
>Greetings;
>
>I recently brought a daily system scan by clamscan back to life, and its
>emailing me this:
>
>/home/gene/src/linux-3.8.2/Documentation/usb/gadget_multi.txt:
>MBL_400944.UNOFFICIAL FOUND
>/home/gene/src/linux-3.12.6/Documentation/usb
Instead of "#ifdef CONFIG_OF" use "IS_ENABLED(CONFIG_OF)"
option for DT code to avoid if-deffery in code.
Also, modify code as per coding style.
Signed-off-by: Manish Badarkhe
---
Changes since V1:
1. fix build break when CONFIG_OF is not set.
:100644 100644 162a0fa... 862cc81... M drivers/regu
On 02/05/2014 07:07 PM, Jean-Francois Moine wrote:
On Wed, 05 Feb 2014 10:19:22 +0100
Lars-Peter Clausen wrote:
So, in the CODEC, I don't see how I could update the parameters
dictated by the EDID otherwise in changing the DAI driver parameters.
The startup function is the right place. But
On Wed, Feb 05, 2014 at 10:00:15AM -0800, Bjorn Andersson wrote:
> On Tue, Feb 4, 2014 at 12:00 PM, Mark Brown wrote:
> > So we should be changing the code to allow a set_voltage() that sets the
> > voltage to the existing voltage regardless of constraints allowing a
> > change then - that's what
On 5 February 2014 18:04, Leif Lindholm wrote:
> From: Ard Biesheuvel
>
> Loading unauthenticated FDT blobs directly from storage is a security hazard,
> so this should only be allowed when running with UEFI Secure Boot disabled.
>
> Signed-off-by: Ard Biesheuvel
> Signed-off-by: Leif Lindholm
On 02/03/2014 10:59 PM, Hugh Dickins wrote:
On Mon, 3 Feb 2014, Sasha Levin wrote:
On 04/25/2013 10:01 PM, Dave Jones wrote:
On Thu, Apr 25, 2013 at 08:51:27PM -0400, Sasha Levin wrote:
> On 04/24/2013 06:46 PM, Andrew Morton wrote:
> > Guys, did this get fixed?
>
> I've stopped see
On 02/05/2014 09:00 AM, Peter Oberparleiter wrote:
>
> Could you give this patch a try? It is a variation of the approach
> proposed in the discussion mentioned earlier and fixes the problem
> on my system.
>
I would rather suggest that we explicitly disable gcov etc. from these
kinds of small,
On Tue, Feb 4, 2014 at 11:38 PM, Geert Uytterhoeven
wrote:
> Apparently commit 5c766d642bcaffd0c2a5b354db2068515b3846cf ("ipv4:
> introduce address lifetime") forgot to take into account the addition of
> struct ifa_cacheinfo in inet_nlmsg_size(). Hence add it, like is already
> done for ipv6.
>
>
On Tue, Feb 04, 2014 at 10:41:15PM -0800, Guenter Roeck wrote:
> On 02/04/2014 01:09 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.13.2 release.
> >There are 140 patches in this series, all will be posted as a response
> >to this one. If anyone has any iss
On Wed, Feb 5, 2014 at 6:30 PM, Cong Wang wrote:
> On Tue, Feb 4, 2014 at 11:38 PM, Geert Uytterhoeven
> wrote:
>> Apparently commit 5c766d642bcaffd0c2a5b354db2068515b3846cf ("ipv4:
>> introduce address lifetime") forgot to take into account the addition of
>> struct ifa_cacheinfo in inet_nlmsg_s
On Wed, Feb 5, 2014 at 7:57 AM, Kamil Debski wrote:
> Hi Olof,
>
> Thank you for your review.
>
>> From: Olof Johansson [mailto:o...@lixom.net]
>> Sent: Wednesday, January 29, 2014 9:55 PM
>>
>> Hi,
>>
>> On Wed, Jan 29, 2014 at 9:29 AM, Kamil Debski
>> wrote:
>> > Change the phy provider used fr
Bug Report Filed: https://bugzilla.kernel.org/show_bug.cgi?id=70081
Linux Version [3.13]
Configuration: Default configuration for x86
In function (drm_crtc_init) in file (linux-3.13/drivers/gpu/drm/drm_crtc.c):
The structure (crtc->mutex) gets successfully locked at line (636) by
(drm_modeset_loc
On Wed, 05 Feb 2014 10:19:22 +0100
Lars-Peter Clausen wrote:
> > So, in the CODEC, I don't see how I could update the parameters
> > dictated by the EDID otherwise in changing the DAI driver parameters.
> >
>
> The startup function is the right place. But instead of modifying the DAI
> use sn
Signed-off-by: Laszlo Papp
---
Documentation/devicetree/bindings/leds/leds-gpio.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/leds/leds-gpio.txt
b/Documentation/devicetree/bindings/leds/leds-gpio.txt
index df1b308..00e94fe 100644
--- a/
On Fri, Jan 3, 2014 at 6:48 AM, Yan, Zheng wrote:
> When the LBR call stack is enabled, it is necessary to save/restore
> the LBR stack on context switch. The solution is saving/restoring
> the LBR stack to/from task's perf event context.
>
> The LBR stack is saved/restored only when there are eve
init_inodecache is only called by __init init_adfs_fs.
Signed-off-by: Fabian Frederick
---
fs/adfs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/adfs/super.c b/fs/adfs/super.c
index 7b3003c..15796f8 100644
--- a/fs/adfs/super.c
+++ b/fs/adfs/super.c
@@ -265,7 +26
init_inodecache is only called by __init init_ufs_fs.
Signed-off-by: Fabian Frederick
---
fs/ufs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ufs/super.c b/fs/ufs/super.c
index 329f2f5..5a7502e 100644
--- a/fs/ufs/super.c
+++ b/fs/ufs/super.c
@@ -1453,7 +1453,7
Signed-off-by: Adam Thomson
---
drivers/hwmon/da9055-hwmon.c |7 ++-
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/hwmon/da9055-hwmon.c b/drivers/hwmon/da9055-hwmon.c
index 029ecab..1867682 100644
--- a/drivers/hwmon/da9055-hwmon.c
+++ b/drivers/hwmon/da9055-hwmo
On Wed, Feb 05, 2014 at 06:19:27PM +0100, Stephane Eranian wrote:
> On Fri, Jan 3, 2014 at 6:48 AM, Yan, Zheng wrote:
> > If two tasks were both forked from the same parent task, Events in their
> > perf
> > task contexts can be the same. Perf core optimizes context switch oout in
> > this
> > c
Signed-off-by: Adam Thomson
---
drivers/rtc/rtc-da9055.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-da9055.c b/drivers/rtc/rtc-da9055.c
index 48cb2ac..6e06840 100644
--- a/drivers/rtc/rtc-da9055.c
+++ b/drivers/rtc/rtc-da9055.c
@@ -301,8 +301,7 @@
Signed-off-by: Adam Thomson
---
drivers/mfd/da9055-core.c | 46 -
1 files changed, 0 insertions(+), 46 deletions(-)
diff --git a/drivers/mfd/da9055-core.c b/drivers/mfd/da9055-core.c
index caf8dcf..5cf8ca6 100644
--- a/drivers/mfd/da9055-core.c
+++
On Wed, Feb 05, 2014 at 05:03:53PM +, Leif Lindholm wrote:
> A new macro for setting/clearing bits in the SCTLR.
>
> Signed-off-by: Leif Lindholm
> Suggested-by: Will Deacon
> Cc: Will Deacon
> ---
> arch/arm/include/asm/assembler.h | 14 ++
> 1 file changed, 14 insertions(+)
On Tue, Feb 4, 2014 at 12:00 PM, Mark Brown wrote:
> On Tue, Feb 04, 2014 at 11:09:03AM -0800, Bjorn Andersson wrote:
>
>> I have a regulator that's being configured from DT as:
>> regulator-min-microvolt = <295>;
>> regulator-max-microvolt = <295>;
>
>> In the consumer I do regulator_set_
Signed-off-by: Adam Thomson
---
Documentation/devicetree/bindings/mfd/da9055.txt | 73 ++
drivers/mfd/da9055-i2c.c |8 +++
2 files changed, 81 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/da9055.txt
dif
On Wed 05-02-14 11:45:43, Johannes Weiner wrote:
> On Wed, Feb 05, 2014 at 05:19:40PM +0100, Michal Hocko wrote:
> > On Wed 05-02-14 10:28:21, Johannes Weiner wrote:
> > > Here is the only exception to the above: swapout records maintain
> > > permanent css references, so they prevent css_free() fr
2014-02-05 Grygorii Strashko :
> Hi All,
> On 02/05/2014 05:06 PM, Illia Smyrnov wrote:
>> Commit 313a76e (ARM: OMAP2+: hwmod: Fix SOFTRESET logic) introduced
>> softreset bit cleaning right after set one. It is caused L3 error for
>> OMAP4 ISS because ISS register write occurs when ISS reset proce
On Wed, Feb 05, 2014 at 06:08:02AM -0800, Mike Turquette wrote:
> Quoting Sebastian Hesselbarth (2014-01-25 10:19:06)
> > This patch set fixes clk init order that went upside-down with
> > v3.14. I haven't really investigated what caused this, but I assume
> > it is related with DT node reordering
On 02/05, Denys Vlasenko wrote:
>
> In prepend_name(), *buflen < dlen + 1 comparison is buggy
> because dlen has unsigned data type, and we can reach this location
> with *buflen == -1.
because, say, path_with_deleted() doesn't check the result of
prepend(), and prepend() updates *buflen unconditi
This patch series provides the following updates for DA9055 drivers:
- Fixes an issue with da9055 driver initialisation (conflicting device ids) of
PMIC (MFD) and CODEC drivers.
- Add initial DT support for DA9055 related drivers, including binding
documentation.
- Remove conflicting use
Using platform_get_irq_byname() to retrieve the IRQ number
returns the VIRQ number rather than the local IRQ number for
the device. Passing that value then into regmap_irq_get_virq()
causes a failure because the function is expecting the local
IRQ number (e.g. 0, 1, 2, 3, etc). This patch removes u
On Wed, Feb 5, 2014 at 10:18 AM, Ivan Khoronzhuk wrote:
>
> On 02/05/2014 04:39 PM, Rob Herring wrote:
>>
>> On Wed, Feb 5, 2014 at 7:47 AM, Ivan Khoronzhuk
>> wrote:
>>>
>>> This patch provides bindings for the 64-bit timer in the KeyStone
>>> architecture devices. The timer can be configured as
Currently the I2C device Ids conflict for the MFD and CODEC so
cannot be both instantiated on one platform. This patch updates
the Ids and names to make them unique from each other.
It should be noted that the I2C addresses for both PMIC and CODEC
are modifiable so instantiation of the two are kep
Signed-off-by: Adam Thomson
---
Documentation/devicetree/bindings/sound/da9055.txt | 22
sound/soc/codecs/da9055.c |8 +++
2 files changed, 30 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/sound/da9055.
Signed-off-by: Adam Thomson
---
drivers/regulator/da9055-regulator.c | 59 +++---
1 files changed, 54 insertions(+), 5 deletions(-)
diff --git a/drivers/regulator/da9055-regulator.c
b/drivers/regulator/da9055-regulator.c
index 7f34020..bc41137 100644
--- a/drivers
Adding generic fsdevel section for ADFS.
I guess status can be considered 'orphan' like affs and befs.
Signed-off-by: Fabian Frederick
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b2cf5cf..237d34e 100644
--- a/MAINTAINERS
+++ b/MAINTAI
> For the record, even with a (currently) modern CPU such as a
> Xeon E5-2630 @ 2.30GHz, the script takes 4m30s on 3.14-rc1
> i386 allyesconfig. And since it runs single threaded at the end
> of the build, it really adds that amount to the wall time spent
> on the build. So enthusiastically Acked,
In prepend_name(), *buflen < dlen + 1 comparison is buggy
because dlen has unsigned data type, and we can reach this location
with *buflen == -1.
The fix casts dlen to int.
Bug reports:
https://bugzilla.redhat.com/show_bug.cgi?id=1050964
https://bugzilla.redhat.com/show_bug.cgi?id=1060384
Signed
On Wed, 2014-02-05 at 17:03 +, Leif Lindholm wrote:
> From: Roy Franz
>
> Add a wrapper for printk to standardize the prefix for informational and
> error messages from the EFI stub.
trivia:
> diff --git a/drivers/firmware/efi/efi-stub-helper.c
> b/drivers/firmware/efi/efi-stub-helper.c
[]
On Fri, Jan 3, 2014 at 6:48 AM, Yan, Zheng wrote:
> When the LBR call stack is enabled, it is necessary to save/restore
> the LBR stack on context switch. We can use pmu specific data to
> store LBR stack when task is scheduled out. This patch adds code
> that allocates the pmu specific data.
>
Re
On Wed, Feb 5, 2014 at 9:05 AM, David Laight wrote:
> From: Dan Williams
>> Yes, but I think we need to centralize the context under which
>> commands are submitted. The complicating factor is the mix of
>> synchronous command submission and interrupt driven asynchronous
>> command queuing. I th
On Fri, Jan 3, 2014 at 6:48 AM, Yan, Zheng wrote:
> If two tasks were both forked from the same parent task, Events in their perf
> task contexts can be the same. Perf core optimizes context switch oout in this
> case.
>
> Previous patch inroduces pmu specific data. The data is task specific, so w
+ Bjorn, linux-pci
Bjorn,
It looks like this didn't get Cc'd to linux-pci. Here's a link:
http://www.spinics.net/lists/arm-kernel/msg299721.html
On Wed, Feb 05, 2014 at 04:47:10PM +0100, Thomas Petazzoni wrote:
> Dear Jean-Jacques Hiblot,
>
> On Fri, 10 Jan 2014 11:23:51 +0100, Jean-Jacque
On 01/14/2014 04:58 AM, Wolfram Sang wrote:
> devm_ioremap_resource does sanity checks on the given resource. No need to
> duplicate this in the driver.
Applied to Tegra's for-3.15/drivers branch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
501 - 600 of 890 matches
Mail list logo