On Fri, Sep 5, 2014 at 7:58 AM, Guenter Roeck wrote:
>>
>> Yeah, I've fixed it. I'll run dos2unix for every patch file.
>>
>
> Yes, it now works. Wonder how it comes that the patch in Greg's patch tree
> didn't have the problem. Any idea ?
>
I am interested in the answer to your question. I
Hi Peter and all,
Did you get a chance to review these patches?
Zheng is away. Should I re-send the patches?
Thanks,
Kan
>
> For many profiling tasks we need the callgraph. For example we often need
> to see the caller of a lock or the caller of a memcpy or other library
> function
> to
On Fri, 5 Sep 2014 16:15:33 +0200
Alexandre Belloni wrote:
> Actually register clocks from device tree when using the common clock
> framework.
>
> Signed-off-by: Alexandre Belloni
Acked-by: Boris Brezillon
> ---
> arch/arm/mach-at91/board-dt-rm9200.c | 11 ++-
> 1 file changed,
(2014/09/05 17:28), Vladimir Davydov wrote:
Hi Kamezawa,
Thanks for reading this :-)
On Fri, Sep 05, 2014 at 07:03:57AM +0900, Kamezawa Hiroyuki wrote:
(2014/09/04 23:30), Vladimir Davydov wrote:
- memory.limit - container can't use memory above this
- memory.memsw.limit - container
On Fri, 05 Sep 2014, Borislav Petkov wrote:
> On Thu, Sep 04, 2014 at 02:45:10PM -0300, Henrique de Moraes Holschuh wrote:
> > Can we get it backported to -stable, please (3.10 and later)?
>
> I don't see how stable rules apply here.
It would be better if this functionality was generally
On 09/05/2014 04:14 PM, Gaël PORTAY wrote:
Shutdown properly the timer counter block by masking interruptions. Otherwise,
a segmentation may happen when kexec-ing a new kernel (see backtrace below).
An interruption may happen before the handler is set, leading to a kernel
segmentation fault.
The ADV7604 has thirteen 256-byte maps that can be accessed via the main
I²C ports. Each map has it own I²C address and acts
as a standard slave device on the I²C bus.
If nothing is defined, it uses default addresses.
The main purpose is using two adv76xx on the same i2c bus.
Signed-off-by:
On Fri, Sep 05, 2014 at 12:40:22AM -0700, Todd Poynor wrote:
> On Tue, Sep 2, 2014 at 7:54 AM, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Sep 02, 2014 at 05:19:18PM +0530, Kiran Kumar Raparthy wrote:
> ...
> >> diff --git a/drivers/usb/phy/otg-wakeupsource.c
> >>
This allows specifying I²C secodnary addresses different from default ones.
Signed-off-by: Jean-Michel Hautbois
---
drivers/media/i2c/adv7604.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/i2c/adv7604.c b/drivers/media/i2c/adv7604.c
index 8336c02..75613a4 100644
---
On 09/05/2014 01:31 AM, Francis Moreau wrote:
> On 08/10/2014 09:54 AM, Peter Kieser wrote:
>>
>> On 2014-08-05 9:58 AM, Jens Axboe wrote:
>>> On 08/04/2014 10:33 PM, Kent Overstreet wrote:
Hey Jens, here's the pull request for 3.17 - typically late, but lots of
tasty
fixes in this
Actually register clocks from device tree when using the common clock
framework.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/board-dt-rm9200.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-at91/board-dt-rm9200.c
On Fri, Sep 05, 2014 at 04:32:48PM +0900, Joonsoo Kim wrote:
> I also test another approach, such as allocate freepage in CMA
> reserved region as late as possible, which is also similar to your
> suggestion and this doesn't works well. When reclaim is started,
> too many pages reclaim at once,
On Fri, Sep 05, 2014 at 12:47:16AM -0700, Luis R. Rodriguez wrote:
> Ah -- well without it the way we "find" drivers that need this new
> "async feature" is by a bug report and folks saying their system can't
> boot, or they say their device doesn't come up. That's all. Tracing
> this to systemd
kaslr's action is splitted into 2 parts. The 1st is getting available memory
slots and randomly choose the kernel relocation address. After decompression
of kernel to the chosen place, the 2nd part begin to check if kaslr has got
a relocation address, and will do the relocations handling if yes.
Hi Arnd,
On 02/09/14 20:51, Arnd Bergmann wrote:
> On Saturday 30 August 2014 00:10:39 Andre Przywara wrote:
>> On 08/29/2014 07:59 PM, Arnd Bergmann wrote:
>>> On Friday 29 August 2014 17:13:23 Andre Przywara wrote:
The ARM Server Base System Architecture (SBSA) describes a generic
Now kaslr makes kernel image size changable, not the fixed size 512M.
So KERNEL_IMAGE_SIZE need be exported to VMCOREINFO, otherwise makedumfile
will crash.
Signed-off-by: Baoquan He
---
kernel/kexec.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/kexec.c b/kernel/kexec.c
index
On Thu, 2014-09-04 at 17:51 -0700, Andy Lutomirski wrote:
> On Thu, Sep 4, 2014 at 5:29 PM, Toshi Kani wrote:
> > On Thu, 2014-09-04 at 16:34 -0700, Andy Lutomirski wrote:
> >> On Thu, Sep 4, 2014 at 4:19 PM, Henrique de Moraes Holschuh
> >> wrote:
> >> > On Thu, 04 Sep 2014, H. Peter Anvin
Em Fri, Sep 05, 2014 at 10:22:40AM +0300, Adrian Hunter escreveu:
> On 09/05/2014 07:59 AM, Namhyung Kim wrote:
> > +++ b/tools/perf/util/machine.c
> > @@ -1060,10 +1060,14 @@ static int
> > machine__process_kernel_mmap_event(struct machine *machine,
> >
On Thu, Sep 04, 2014 at 03:30:42PM -0700, Cong Wang wrote:
> __thaw_task() no longer clears frozen flag since commit a3201227f803
> (freezer: make freezing() test freeze conditions in effect instead of
> TIF_FREEZE).
>
> Cc: David Rientjes
> Cc: "Rafael J. Wysocki"
> Cc: Tejun Heo
> Cc:
Earlier it's reported kexec can't load kernel on system with over 4G
memory and kdump didn't work when set crashkenrel=xx, high when kaslr
is compiled. They didn't work though nokaslr is set in cmdline as long
as it's compiled in. This is caused by not checking if the kernel
decompression output
From: Dave Young
X86 will pass setup_data region while necessary, these regions could be
overwitten by kernel due to kaslr.
Thus iterate and add setup regions to mem_avoid[] in this patch.
Up to now there isn't a official data to state the maximal entries
setup data could use. So just set max
Currently kaslr enabling can extend the kernel virtual address space
to 1G, next is for modules. So if kernel is loaded to above 1G, system
running will be exceptional, This happened when kexec/kdump load kernel.
So add a check to see if the decompression output region is contained
in 1G.
Em Fri, Sep 05, 2014 at 11:42:59AM +0300, Adrian Hunter escreveu:
> On 09/04/2014 06:19 PM, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Sep 04, 2014 at 03:32:08PM +0300, Adrian Hunter escreveu:
> No I was meaning something different. For example, 'perf record' opens an
> event for 2 processes
On 09/05/2014 04:16 AM, bharata@gmail.com wrote:
> From: Bharata B Rao
>
> - ibm,rtas-configure-connector should treat the RTAS data as big endian.
> - Treat ibm,ppc-interrupt-server#s as big-endian when setting
> smp_processor_id during hotplug.
>
> Signed-off-by: Bharata B Rao
> ---
>
Hello,
On Thu, Sep 04, 2014 at 03:30:41PM -0700, Cong Wang wrote:
...
> Cc: David Rientjes
> Cc: Michal Hocko
> Cc: "Rafael J. Wysocki"
> Cc: Tejun Heo
> Cc: Andrew Morton
> Acked-by: Michal Hocko
> Signed-off-by: Cong Wang
Prolly should sta...@vger.kernel.org?
> +static bool
On Fri, Sep 05, 2014 at 01:42:09AM +0400, Sergei Shtylyov wrote:
> From: Antoine Tenart
>
> The USB PHY member of the HCD structure is renamed to 'usb_phy' and
> modifications are done in all drivers accessing it.
> This is in preparation to adding the generic PHY support.
>
> Signed-off-by:
On Friday 05 September 2014 13:51:47 Mark Rutland wrote:
> On Fri, Sep 05, 2014 at 12:05:52PM +0100, Russell King - ARM Linux wrote:
> > On Fri, Sep 05, 2014 at 12:45:47PM +0200, Robert Richter wrote:
> > > On 05.09.14 10:32:40, Russell King - ARM Linux wrote:
> > > No, we need it just to enable
Am 05.09.2014 15:57, schrieb Guenter Roeck:
> On 09/05/2014 02:32 AM, Paul Bolle wrote:
>> Guenter, Richard,
>>
>> On Thu, 2014-06-19 at 03:53 +0800, Lennox Wu wrote:
>>> 2014-06-18 17:10 GMT+08:00 Paul Bolle :
> On Wed, 2014-04-16 at 20:30 +0200, Paul Bolle wrote:
> On Thu, 2014-04-17 at
On Thu, Sep 04, 2014 at 05:08:45PM +0530, Varun Sethi wrote:
> iommu_group_get_for_dev determines the iommu group for the PCI device and adds
> the device to the group.
>
> In the PAMU driver we were again adding the device to the same group without
> checking
> if the device already had an
On Thu, 4 Sep 2014 10:50:14 -0700
Christoph Hellwig wrote:
> On Thu, Sep 04, 2014 at 08:38:37AM -0400, Jeff Layton wrote:
> > There was only one place where we still could free a file_lock while
> > holding the i_lock -- lease_modify. Add a new list_head argument to the
> > lm_change operation,
Some I2C devices have multiple addresses assigned, for example each address
corresponding to a different internal register map page of the device.
So far drivers which need support for this have handled this with a driver
specific and non-generic implementation, e.g. passing the additional address
On Thu, 4 Sep 2014 10:50:43 -0700
Christoph Hellwig wrote:
> Looks good, but I'd rather merge it into the patch that changes the
> semantics.
>
> Reviewed-by: Christoph Hellwig
Fair enough. I'll merge the changes to the Documentation in with the
patches that change them.
--
Jeff Layton
--
On Fri, 2014-09-05 at 12:23 +0200, Ingo Molnar wrote:
> * Toshi Kani wrote:
>
> > On Thu, 2014-09-04 at 14:31 -0600, Toshi Kani wrote:
> > > On Thu, 2014-09-04 at 17:11 -0300, Henrique de Moraes Holschuh wrote:
> > > > On Thu, 04 Sep 2014, Toshi Kani wrote:
> > > > > This patch sets WT to the
On 09/05/2014 12:55 AM, Li Zefan wrote:
Li,
it would be great if you can send me information about your -stable queue,
ie how you maintain it and where it is located. This will enable me to
continue testing the stable queue for the 3.4 kernel.
Thanks for testing LTS kernels!
This is my
On Fri, Sep 5, 2014 at 10:52 AM, Pali Rohár wrote:
> So what is your suggestion for identifing board (name/type) which
> will work with any kernel (and will not be broken again by kernel
> later)?
$ cat /sys/bus/soc/devices/soc0/machine
Freescale i.MX6 Quad SABRE Smart Device Board
--
To
On Fri, Sep 05, 2014 at 02:52:05PM +0100, Pali Rohár wrote:
> On Friday 05 September 2014 15:45:42 Mark Rutland wrote:
> > On Fri, Sep 05, 2014 at 12:38:40PM +0100, Pali Rohár wrote:
> > > On Wednesday 18 June 2014 18:54:24 Pali Rohár wrote:
> > > > Machine name from board description is some
On 09/05/2014 02:32 AM, Paul Bolle wrote:
Guenter, Richard,
On Thu, 2014-06-19 at 03:53 +0800, Lennox Wu wrote:
2014-06-18 17:10 GMT+08:00 Paul Bolle :
On Wed, 2014-04-16 at 20:30 +0200, Paul Bolle wrote:
On Thu, 2014-04-17 at 01:29 +0800, Lennox Wu wrote:
OK, we will merge it into our tree.
In the Dell XPS 13 9333, it appears that sometimes the bus get confused
and corrupts the incoming data. It fills the input report with the
sentinel value "ff". Synaptics told us that such behavior does not comes
from the touchpad itself, so we filter out such reports here.
Unfortunately, we can
With scsi-mq I think many LLDs probably have a new
race possibility between a surprise rmmod of the LLD
and another thread presenting a new command at about
the same time (or another thread's command completing
around that time). Does anything above the LLD stop
this happening?
Looking at
From: Richard Weinberger
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger
Acked-by: Lennox Wu
Cc: Paul Bolle
[Guenter Roeck: Merge with 3.17-rc3; update headline]
Signed-off-by: Guenter Roeck
---
Jiri, can you please take this through trivial ?
Thanks,
Guenter
On Fri, Sep 05, 2014 at 08:43:57AM -0400, Johannes Weiner wrote:
> Dave Hansen reports a massive scalability regression in an uncontained
> page fault benchmark with more than 30 concurrent threads, which he
> bisected down to 05b843012335 ("mm: memcontrol: use root_mem_cgroup
> res_counter") and
Hi,
This patch series adds support for AFTR idle mode on boards with
secure firmware enabled and allows EXYNOS cpuidle driver usage on
Exynos4x12 SoCs.
It has been tested on Trats2 board (using Exynos4412 SoC with secure
firmware enabled) on which AFTR mode reduces power consumption by ~12%
when
On Thu, Sep 04, 2014 at 05:40:20PM +0200, Peter Zijlstra wrote:
> On Thu, Sep 04, 2014 at 03:33:40PM +0200, Frederic Weisbecker wrote:
> > > Why not something like the below; then it becomes a compile time matter.
> >
> > Problem is that some archs only have that information at runtime.
> > See
On Fri, Sep 05, 2014 at 07:25:14PM +0800, Su, Friendy wrote:
> This issue is found on a mother board whose BIOS reports wrong
> IOAPIC devid in IVHD table. Without this fix, the early mapped
> does not really override IVHD. So that the wrong reported IOAPIC
> does not work.
The problem you
Add S5P_CENTRAL_SEQ_OPTION register setup to cpuidle AFTR mode code
by moving the relevant code from exynos_pm_suspend() (used only by
suspend) to exynos_pm_central_suspend() (used by both suspend and
AFTR). Without this setup AFTR mode doesn't show any benefit over
WFI one (at least on
On Friday 05 September 2014 15:45:42 Mark Rutland wrote:
> On Fri, Sep 05, 2014 at 12:38:40PM +0100, Pali Rohár wrote:
> > On Wednesday 18 June 2014 18:54:24 Pali Rohár wrote:
> > > Machine name from board description is some generic name
> > > on DT kernel. DT provides machine name property which
* Move cp15 registers saving to exynos_save_cp15() helper and add
additional helper usage to do_idle firmware method.
* Use resume firmware method instead of exynos_cpu_restore_register()
and skip exynos_cpu_save_register() on boards with secure firmware
enabled.
* Use sysram_ns_base_addr
Register cpuidle platform device on Exynos4x12 SoCs allowing EXYNOS
cpuidle driver usage on these SoCs.
AFTR mode reduces power consumption on Trats2 board (Exynos4412 SoC
with secure firmware enabled) by ~12% when EXYNOS cpuidle driver is
enabled (in both cases the default exynos_defconfig
Replace EXYNOS_BOOT_VECTOR_ADDR and EXYNOS_BOOT_VECTOR_FLAG macros
by exynos_boot_vector_addr() and exynos_boot_vector_flag() static
inlines.
This patch shouldn't cause any functionality changes.
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
Acked-by: Daniel Lezcano
---
v6:
On some platforms (i.e. EXYNOS ones) more than one idle mode is
available and we need to distinguish them in firmware do_idle method.
Add mode parameter to do_idle firmware method and AFTR mode support
to EXYNOS do_idle implementation.
This change is a preparation for adding secure firmware
interrupted_kernel_fpu_idle() tries to detect if kernel_fpu_begin()
is safe or not. In particular it should obviously deny the nested
kernel_fpu_begin() and this logic doesn't look clean.
If use_eager_fpu() == T we rely on a) __thread_has_fpu() check in
interrupted_kernel_fpu_idle(), and b) on
On Fri, Sep 05, 2014 at 12:38:40PM +0100, Pali Rohár wrote:
> On Wednesday 18 June 2014 18:54:24 Pali Rohár wrote:
> > Machine name from board description is some generic name on DT
> > kernel. DT provides machine name property which is specific
> > for board, so use it instead generic one when
According to the comment and the changelog in 5187b28f "x86: Allow FPU
to be used at interrupt time even with eagerfpu", the __thread_has_fpu()
check was added to avoid the nested kernel_fpu_begin(). Now that we have
in_kernel_fpu we can remove this check and always return true.
math_state_restore() can race with kernel_fpu_begin() if irq comes
right after __thread_fpu_begin(), __save_init_fpu() will overwrite
fpu->state we are going to restore.
Add 2 simple helpers, kernel_fpu_disable() and kernel_fpu_enable()
which simply set/clear in_kernel_fpu, and change
Cosmetic. Every caller of restore_fpu_checking() does drop_init_fpu()
on failure, add the trivial helper and update the callers.
Signed-off-by: Oleg Nesterov
---
arch/x86/include/asm/fpu-internal.h | 15 +++
arch/x86/kernel/i387.c |8 +++-
Hello,
Suresh, please review when you have time. FYI, I will be travelling
till Sep 10 and I won't be able to reply.
Not for inclusion yet, just for review.
v2:
1-3: No changes except the minor updates in the changelogs
and comments
4-5: New. 5/5 is purely
Now that we have in_kernel_fpu we can remove __thread_clear_has_fpu()
in __kernel_fpu_begin(). And this allows to replace the asymmetrical
and nontrivial use_eager_fpu+tsk_used_math check in kernel_fpu_end()
with the same __thread_has_fpu().
The logic becomes really simple; if _begin() does
On Fri, Sep 5, 2014 at 11:47 AM, Russell King - ARM Linux
wrote:
> On Mon, Sep 01, 2014 at 02:53:40PM +0200, Anders Berg wrote:
>> The AXM55xx device has a ARM PL022 SSP controller with an extension that
>> enables the control of up to five chip select signals. This driver implements
>> the logic
On Thu, 4 Sep 2014 10:53:34 -0700
Christoph Hellwig wrote:
> On Thu, Sep 04, 2014 at 08:38:43AM -0400, Jeff Layton wrote:
> > The contents of an fl_owner_t have morphed a bit over the years, fix up
> > the comments to account for the changes.
>
> Instead of listing all the owners I'd just put
On Thu, 4 Sep 2014 11:07:25 -0700
Christoph Hellwig wrote:
> On Thu, Sep 04, 2014 at 08:38:40AM -0400, Jeff Layton wrote:
> > Eliminate an unneeded "flock" variable. We can use "fl" as a loop cursor
> > everywhere. Add a any_leases_conflict helper function as well to
> > consolidate a bit of
On 4 September 2014 02:26, Peter Zijlstra wrote:
> On Tue, Sep 02, 2014 at 02:18:16PM -0600, Mathieu Poirier wrote:
>> Pawell, many thanks for looping me in.
>>
>> I am definitely not a perf-internal guru and as such won't be able to
>> comment on the implementation. On the flip side it is easy
Hello.
On 09/05/2014 01:03 PM, Geert Uytterhoeven wrote:
Add RCAN clock support to the R-Car generation 2 CPG driver. This clock
gets
derived from the USB_EXTAL clock by dividing it by 6. The layout of
RCANCKCR
register is close to those of the clocks supported by the 'clk-div6'
driver
but has
From: Colin Ian King
The DSP_NEVER_DEFINED #ifdef is confusing, it slips in an
extra } which is not required because the previous code is
indented incorrectly. Correct the identation and remove the
extraneous DSP_NEVER_DEFINED
Signed-off-by: Colin Ian King
---
drivers/isdn/mISDN/dsp_cmx.c |
When running a 32-bit inputattach utility in a 64-bit system, there will be
error code "inputattach: can't set device type". This is caused by the serport
device driver not supporting compat_ioctl, so that SPIOCSTYPE ioctl fails.
Signed-off-by: John Sung
---
drivers/input/serio/serport.c |
Hello,
This patch change the way zram uses `notify_free' stat attr. Currently,
this attr accounts only swap free notifications, iow used only when zram
device is a swap device. The patch preserves the existing behaviour and
additionally makes `notify_free' universal, so it's also used by zram to
notify_free device attribute accounts the number of slot free notifications
and internally represents the number of zram_free_page() calls. Slot free
notifications are sent only when device is used as a swap device, hence
notify_free is used only for swap devices. Since f4659d8e620d08 (zram:
On Fri, Sep 05, 2014 at 12:05:52PM +0100, Russell King - ARM Linux wrote:
> On Fri, Sep 05, 2014 at 12:45:47PM +0200, Robert Richter wrote:
> > On 05.09.14 10:32:40, Russell King - ARM Linux wrote:
> > > On Fri, Sep 05, 2014 at 09:46:42AM +0200, Robert Richter wrote:
> > > > From: Radha Mohan
On 09/02/2014 11:05 PM, Alex Williamson wrote:
> On Mon, 2014-09-01 at 14:52 +0200, Eric Auger wrote:
>> This RFC proposes an integration of "ARM: Forwarding physical
>> interrupts to a guest VM" (http://lwn.net/Articles/603514/) in
>> KVM.
>>
>> It enables to transform a VFIO platform driver IRQ
On Fri, Sep 5, 2014 at 1:48 AM, Robert Richter wrote:
> From: Robert Richter
>
> Move dtbs install rules to Makefile.dtbinst. This change is needed to
> implement support for dts vendor subdirs. The change makes Makefiles
> easier and smaller as no longer the dtbs_install rule needs to be
>
On Fri, Sep 5, 2014 at 1:48 AM, Robert Richter wrote:
> From: Robert Richter
>
> Moving dts files to vendor subdirs.
>
> Signed-off-by: Robert Richter
> ---
> arch/arm64/boot/dts/Makefile | 4 +-
> arch/arm64/boot/dts/apm-mustang.dts | 34 --
>
Dave Hansen reports a massive scalability regression in an uncontained
page fault benchmark with more than 30 concurrent threads, which he
bisected down to 05b843012335 ("mm: memcontrol: use root_mem_cgroup
res_counter") and pin-pointed on res_counter spinlock contention.
That change relied on
Hi Denys,
(2014/09/04 21:54), Denys Vlasenko wrote:
> Since xop and evex prefixes are extensions of vex mechanism,
> they have similar bit layouts, and they can never be combined
> (an instruction can have only one of them),
> (ab)use insn->vex_prefix to store data of xop and evex too.
>
> Users
On Fri, 2014-09-05 at 11:37 +0200, Geert Uytterhoeven wrote:
> On Thu, Sep 4, 2014 at 4:26 PM, Andy Shevchenko
> wrote:
> > Test different scenarios of function calls located in lib/hexdump.c.
> >
> > Currently hex_dump_to_buffer() is only tested and test data is provided for
> > little endian
From: Peter Hurley
> [ +cc linux-arm ]
>
> Hi David,
>
> On 09/05/2014 04:30 AM, David Laight wrote:
> > I've seen gcc generate 32bit accesses for 16bit structure members on arm.
> > It does this because of the more limited range of the offsets for the 16bit
> > access.
> > OTOH I don't know if
Cleanup a little the SMP/hotplug code for Exynos by:
1. Moving completely all functions from hotplug.c into the platsmp.c;
2. Deleting the hotplug.c file.
After recent cleanups (e.g. 75ad2ab28f0f "ARM: EXYNOS: use
v7_exit_coherency_flush macro for cache disabling") there was only CPU
power down
On Thu, Sep 04, 2014 at 01:27:26PM -0700, Dave Hansen wrote:
> On 09/04/2014 07:27 AM, Michal Hocko wrote:
> > Ouch. free_pages_and_swap_cache completely kills the uncharge batching
> > because it reduces it to PAGEVEC_SIZE batches.
> >
> > I think we really do not need PAGEVEC_SIZE batching
The __ref annotation for exynos_cpu_die() is not needed because the
function does not reference any __init/__exit symbol or call.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Tomasz Figa
---
Changes since v4:
1. Rebase on linux-next-20140804.
2. Add Reviewed-by Tomasz Figa.
---
On Exynos4 USE_DELAYED_RESET_ASSERTION must be set in
ARM_COREx_OPTION register during CPU power down. This is the proper way
of powering down CPU on Exynos4.
Additionally on Exynos4212 without this the CPU clock down feature won't
work after powering down some CPU and the online CPUs will work
On 09/05/2014 02:09 PM, Matt Fleming wrote:
> (Adding linux-efi)
>
> On Fri, 05 Sep, at 08:51:31AM, Francis Moreau wrote:
>> [ +0.45] RIP: 0010:[<>] [< (null)>]
>> (null)
>> [ +0.46] RSP: 0018:8800b4001da8 EFLAGS: 00010002
>> [ +0.32] RAX:
[ +cc linux-arm ]
Hi David,
On 09/05/2014 04:30 AM, David Laight wrote:
> I've seen gcc generate 32bit accesses for 16bit structure members on arm.
> It does this because of the more limited range of the offsets for the 16bit
> access.
> OTOH I don't know if it ever did this for writes - so it
On Friday 05 September 2014 14:04:18 Paul Bolle wrote:
>
> On Thu, 2014-09-04 at 18:02 +0200, Arnd Bergmann wrote:
> > I think it would be nice if you could submit a patch to remove the
> > drivers from ASoC, then we can see if anybody complains.
>
> Just to know what I'm getting my self into:
On wto, 2014-08-05 at 17:07 +0200, Daniel Lezcano wrote:
> On 08/05/2014 04:26 PM, Krzysztof Kozlowski wrote:
> > On 05.08.2014 16:03, Daniel Lezcano wrote:
> >> On 08/05/2014 03:34 PM, Bartlomiej Zolnierkiewicz wrote:
> >>> Hi,
> >>>
> >>> This patch series adds support for AFTR idle mode on
On 5 September 2014 14:19, Preeti U Murthy wrote:
> Hi Vincent,
>
> On 09/03/2014 10:28 PM, Vincent Guittot wrote:
>> On 3 September 2014 14:21, Preeti U Murthy wrote:
>>> Hi,
>>
>> Hi Preeti,
>>
>>>
>>> There are places in kernel/sched/fair.c in the load balancing part where
>>> rq->nr_running
On Friday 05 September 2014 15:14:33 Stanimir Varbanov wrote:
> + VADC_CHAN(LR_MUX1_BAT_THERM, 0) /* 0x30 */
> + VADC_CHAN(LR_MUX2_BAT_ID, 0)
> + VADC_CHAN(LR_MUX3_XO_THERM, 0)
> + VADC_CHAN(LR_MUX4_AMUX_THM1, 0)
> + VADC_CHAN(LR_MUX5_AMUX_THM2, 0)
> +
On 5 September 2014 14:06, Preeti U Murthy wrote:
> Hi Vincent,
>
> On 08/26/2014 04:36 PM, Vincent Guittot wrote:
>> If the CPU is used for handling lot of IRQs, trig a load balance to check if
>> it's worth moving its tasks on another CPU that has more capacity.
>>
>> As a sidenote, this will
The added gpio-gate-clock is a basic clock that can be enabled and
disabled trough a gpio output. The DT binding document for the clock
is also added. For EPROBE_DEFER handling the registering of the clock
has to be delayed until of_clk_get() call time.
Signed-off-by: Jyri Sarha
---
This is my
Hi Vincent,
On 09/03/2014 10:28 PM, Vincent Guittot wrote:
> On 3 September 2014 14:21, Preeti U Murthy wrote:
>> Hi,
>
> Hi Preeti,
>
>>
>> There are places in kernel/sched/fair.c in the load balancing part where
>> rq->nr_running is used as against cfs_rq->nr_running. At least I could
>> not
On Friday 05 September 2014 12:02:01 Shevchenko, Andriy wrote:
> > irq = irq_of_parse_and_map(node, 0);
> > If (!irq) {
> > pp->irq = -1;
> > return;
> > } else {
> > pp->irq = irq;
> > }
> > Then the code looks strange.
> >
> > How do you think?
>
> If I understood correctly you messed up with
On 09/05, Denys Vlasenko wrote:
>
> On Thu, Sep 4, 2014 at 4:24 PM, Oleg Nesterov wrote:
> > Does this replace the previous series (which at first glance looks
> > pretty much the same) ?
>
> All 5 patches (two patch sets)
FYI, I obvoiuosly can't take the 1st series which changes lib/insn.c ;)
Document DT binding for Qualcomm SPMI PMIC voltage ADC
driver.
Signed-off-by: Stanimir Varbanov
Signed-off-by: Ivan T. Ivanov
---
.../devicetree/bindings/iio/adc/qcom,spmi-vadc.txt | 110
1 files changed, 110 insertions(+), 0 deletions(-)
create mode 100644
The voltage ADC is peripheral of Qualcomm SPMI PMIC chips. It has
15bits resolution and register space inside PMIC accessible across
SPMI bus.
The vadc driver registers itself through IIO interface.
Signed-off-by: Stanimir Varbanov
Signed-off-by: Ivan T. Ivanov
---
drivers/iio/adc/Kconfig
Introduce inital support for VADC inside Qualcomm SPMI PMICs.
The vadc driver is reworked version of the same downstream
driver but now it is implemented through Industrial IO core.
Comments are welcome!
regards,
Stan
Stanimir Varbanov (2):
iio: vadc: Qualcomm SPMI PMIC voltage ADC driver
On Fri, Sep 05, 2014 at 01:38:40PM +0200, Pali Rohár wrote:
> On Wednesday 18 June 2014 18:54:24 Pali Rohár wrote:
> > Machine name from board description is some generic name on DT
> > kernel. DT provides machine name property which is specific
> > for board, so use it instead generic one when
On Fri, Sep 5, 2014 at 3:55 AM, Michael Neuling wrote:
> On Fri, 2014-09-05 at 09:13 +0200, Gabriel Paubert wrote:
>> On Fri, Sep 05, 2014 at 03:28:47PM +1000, Michael Neuling wrote:
>> > The Debian powerpc little endian architecture is called ppc64le. This
>>
>> Huh? ppc64le or ppc64el?
>
>
On Thu, Sep 4, 2014 at 4:24 PM, Oleg Nesterov wrote:
> Does this replace the previous series (which at first glance looks
> pretty much the same) ?
All 5 patches (two patch sets) I sent yesterday are resends.
They apply cleanly to current Linus' git.
I should have marked them as such. Sorry
On Fri, Sep 05, 2014 at 05:55:18PM +1000, Michael Neuling wrote:
> On Fri, 2014-09-05 at 09:13 +0200, Gabriel Paubert wrote:
> > On Fri, Sep 05, 2014 at 03:28:47PM +1000, Michael Neuling wrote:
> > > The Debian powerpc little endian architecture is called ppc64le. This
> >
> > Huh? ppc64le or
(Adding linux-efi)
On Fri, 05 Sep, at 08:51:31AM, Francis Moreau wrote:
> [ +0.45] RIP: 0010:[<>] [< (null)>] (null)
> [ +0.46] RSP: 0018:8800b4001da8 EFLAGS: 00010002
> [ +0.32] RAX: 80050033 RBX: 880406288000 RCX:
>
Hi Vincent,
On 08/26/2014 04:36 PM, Vincent Guittot wrote:
> If the CPU is used for handling lot of IRQs, trig a load balance to check if
> it's worth moving its tasks on another CPU that has more capacity.
>
> As a sidenote, this will note generate more spurious ilb because we already
> trig an
On Thursday, September 04, 2014 10:39 PM, Marek Vasut wrote:
> On Wednesday, August 13, 2014 at 11:46:54 AM, Yuan Yao wrote:
> > Add dma support for i2c. This function depend on DMA driver.
> > You can turn on it by write both the dmas and dma-name properties in
> > dts node. DMA is optional, even
Hi Arnd,
On Thu, 2014-09-04 at 18:02 +0200, Arnd Bergmann wrote:
> I think it would be nice if you could submit a patch to remove the
> drivers from ASoC, then we can see if anybody complains.
Just to know what I'm getting my self into: whom would you expect to
send me agitated messages once
501 - 600 of 1674 matches
Mail list logo
