On Wed, Mar 04, 2015 at 03:16:07PM +0100, Rafael J. Wysocki wrote:
> Sort of. What we need is a "do not touch PIC/PIT" bit for the code that
> tries to fall back to them in some cases (which may appear to work if
> the hardware is physically there, but it may confuse the platform).
Can "some
>
>
> * Liang, Kan wrote:
>
> > > * tip-bot for Kan Liang wrote:
> > >
> > > > --- a/kernel/events/core.c
> > > > +++ b/kernel/events/core.c
> > > > @@ -4446,7 +4446,7 @@ static int perf_mmap(struct file *file, struct
> > > vm_area_struct *vma)
> > > > * If we have rb pages ensure
On 03/03/2015 10:06 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.71 release.
There are 53 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 03/04/2015 02:53 PM, David Vrabel wrote:
On 04/03/15 13:31, Juergen Gross wrote:
On 03/02/2015 12:39 PM, David Vrabel wrote:
On 26/02/15 13:35, Juergen Gross wrote:
Introduces the Xen pvUSB backend. With pvUSB it is possible for a Xen
domU to communicate with a USB device assigned to that
Hi All,
We've seen a number of reports where people see:
[ 20.499427] intel_soc_dts_thermal: request_threaded_irq ret -22
[ 20.519160] intel_soc_dts_thermal: request_threaded_irq ret -22
[ 20.532660] intel_soc_dts_thermal: request_threaded_irq ret -22
in their boot logs. They view this
On 03/03/2015 01:29 AM, Jeff Layton wrote:
>> Hmm, are you sure about that? I read the code this way that when a lock
>> is added to flock_list it stays on that CPU. The locks are not moved
>> from one flock_list to another during their existent.
>>
>
> Yes, I'm sure. When a file lock is
On Wednesday, March 04, 2015 04:47:11 PM Jiang Liu wrote:
> When parsing resources for PCI host bridge, we should ignore resources
> consumed by host bridge itself and only report window resources available
> to child PCI busses.
>
> Signed-off-by: Jiang Liu
Queued up for 4.0-rc3, thanks!
>
On Wednesday, March 04, 2015 04:47:12 PM Jiang Liu wrote:
> Some BIOSes report incorrect length for ACPI address space descriptors,
> so relax the checks to avoid regressions. This issue has appeared several
> times as:
> 3162b6f0c5e1 ("PNPACPI: truncate _CRS windows with _LEN > _MAX - _MIN + 1")
On 02/02/2015 10:31 PM, Alban Crequy wrote:
> Hello,
>
> Thanks for updating the man page.
>
> On 12 December 2014 at 22:54, Eric W. Biederman wrote:
> (...)
>> Furthermore to preserve in some form the useful applications that have
>> been setting gid_map without privilege the file
On Wed, Mar 04, 2015 at 08:26:33AM +0100, Ingo Molnar wrote:
> Since most CPUs we care about have ERMS, wouldn't it be better to
> patch in the actual memcpy_erms sequence into the primary memcpy()
> function? It's just about 9 bytes AFAICT.
Actually, most set REP_GOOD - all Intel family 6 and
On Wednesday, March 04, 2015 12:56:20 PM Geert Uytterhoeven wrote:
> If CONFIG_SMP=n, does not include , causing:
>
> drivers/cpufreq/ppc-corenet-cpufreq.c: In function 'corenet_cpufreq_cpu_init':
> drivers/cpufreq/ppc-corenet-cpufreq.c:173:3: error: implicit declaration of
> function
> -Original Message-
> From: linux-iio-ow...@vger.kernel.org [mailto:linux-iio-
> ow...@vger.kernel.org] On Behalf Of Adriana Reus
> Sent: Monday, February 23, 2015 4:41 PM
> To: ji...@kernel.org; linux-...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; Pandruvada, Srinivas; Reus,
When perf probe tries to add a probe in a binary using symbol name, it
sometimes failed since some symbols were discard during loading dso.
When it resolves an address to symbol, it'd be better to have just one
symbol at given address. But for finding address from symbol, it'd be
better to keep
On Wednesday, March 04, 2015 10:50:11 AM Borislav Petkov wrote:
> On Wed, Mar 04, 2015 at 12:43:08AM -0800, Arjan van de Ven wrote:
> > >
> > >Using 'acpi_gbl_reduced_hardware' flag outside the ACPI code
> > >is a mistake.
> >
> > ideally, the presence of that flag in the firmware table will
Memory blocks can be onlined in random order. When this order is not natural
some memory pages are not onlined because of the redundant check in
hv_online_page().
Here is a real world scenario:
1) Host tries to hot-add the following (process_hot_add):
pg_start=rg_start=0x48000, pfn_cnt=111616,
On 04/03/15 13:31, Juergen Gross wrote:
> On 03/02/2015 12:39 PM, David Vrabel wrote:
>> On 26/02/15 13:35, Juergen Gross wrote:
>>> Introduces the Xen pvUSB backend. With pvUSB it is possible for a Xen
>>> domU to communicate with a USB device assigned to that domU. The
>>> communication is all
It currently prevents adding probes in weak symbols. But there're cases
that given name is an only weak symbol so that we cannot add probe.
$ perf probe -x /usr/lib/libc.so.6 -a calloc
Failed to find symbol calloc in /usr/lib/libc-2.21.so
Error: Failed to add events.
$ nm
2015-03-02 23:56 GMT+09:00 Gilad Broner :
> From: Sujit Reddy Thumma
>
> Use fault-injection framework to simulate error conditions
> in the controller and verify error handling mechanisms
> implemented in UFS host controller driver.
>
> This is used only during development and hence
> guarded by
On 03/04/2015 02:41 PM, Ian Campbell wrote:
On Wed, 2015-03-04 at 14:31 +0100, Juergen Gross wrote:
- move module to appropriate location in kernel tree
drivers/xen/ is the correct location for this driver.
Hmm, so you regard placement of xen-netback under drivers/net and
xen-blkback under
Hello Doug,
On 03/03/2015 08:05 PM, Javier Martinez Canillas wrote:
> On 03/03/2015 06:24 PM, Doug Anderson wrote:
>>>
>>> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
>>> index f2452148c8da..8551400d57e4 100644
>>> --- a/drivers/regulator/core.c
>>> +++
On Wed, 2015-03-04 at 14:31 +0100, Juergen Gross wrote:
> >> - move module to appropriate location in kernel tree
> >
> > drivers/xen/ is the correct location for this driver.
>
> Hmm, so you regard placement of xen-netback under drivers/net and
> xen-blkback under drivers/block as wrong? I've
traps.c defines the function fixup_bad_iret used in this file only
and in some assembly. No header file declares this function so,
add a prototype for fixup_bad_iret above the function definition.
This also satisfies the following gcc(-Wmissing-prototypes) warning:
arch/x86/kernel/traps.c:500:24:
setup.c defines xen_pvmmu_arch_setup and xen_ignore_unusable
used only in this file. So mark them static.
This eliminates the following gcc warnings:
arch/x86/xen/setup.c:561:6: warning: no previous prototype for
‘xen_ignore_unusable’ [-Wmissing-prototypes]
arch/x86/xen/setup.c:831:13: warning:
mmu.c defines the following functions:
__visible pteval_t xen_pte_val(pte_t pte)
__visible pgdval_t xen_pgd_val(pgd_t pgd)
__visible pte_t xen_make_pte(pteval_t pte)
__visible pgd_t xen_make_pgd(pgdval_t pgd)
__visible pmdval_t xen_pmd_val(pmd_t pmd)
__visible pmd_t xen_make_pmd(pmdval_t pmd)
enlighten.c defines xen_start_kernel which is used only in this
file and is not defined in any header file. So add a proto-
type for the same above the function definition.
This satisfies the -Wmissing-prototypes gcc warning:
arch/x86/xen/enlighten.c:1534:34: warning: no previous prototype for
xen_flush_tlb_all is defined only in mmu.c, so mark it static.
This eliminates the following gcc warning:
arch/x86/xen/mmu.c:1211:6: warning: no previous prototype for
‘xen_flush_tlb_all’ [-Wmissing-prototypes]
Signed-off-by: Darshana Padmadas
---
arch/x86/xen/mmu.c | 2 +-
1 file changed, 1
On 4 March 2015 at 13:08, Rafał Miłecki wrote:
> On 4 March 2015 at 07:19, Rafał Miłecki wrote:
>> On 3 March 2015 at 22:16, Chen Gang wrote:
>>> bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
>>> or will cause building break for allmodconfig under c6x:
>>>
>>> CC
process.c defines function __switch_to_xtra which has a prototype
in arch/x86/include/asm/switch_to.h. Include this header file
for function prototype for __switch_to_xtra.
This eliminates the following warning:
arch/x86/kernel/process.c:200:6: warning: no previous prototype for
hpet.c defines the function EVT_TO_HPET_DEV internally. No other
file defines this function. So make this function static.
This eliminates the following warning:
arch/x86/kernel/hpet.c:55:25: warning: no previous prototype for
‘EVT_TO_HPET_DEV’ [-Wmissing-prototypes]
Signed-off-by: Darshana
smp.c defines smp_reboot_interrupt used in this file and
in some assembly, so add a prototype for the same in smp.c
This eliminates the following warning:
arch/x86/kernel/smp.c:171:27: warning: no previous prototype for
‘smp_reboot_interrupt’ [-Wmissing-prototypes]
Signed-off-by: Darshana
kvm.c defines functions kvm_guest_cpu_init and kvm_init_debugfs
internally. No other file defines these, so make them static.
This also eliminates the following warnings:
arch/x86/kernel/kvm.c:334:6: warning: no previous prototype for
‘kvm_guest_cpu_init’ [-Wmissing-prototypes]
signal.c defines the function sys32_x32_rt_sigreturn, which is
used in this file and some assembly. So add a prototype for the
function.
This eliminates the following warning:
arch/x86/kernel/signal.c:784:17: warning: no previous prototype for
‘sys32_x32_rt_sigreturn’ [-Wmissing-prototypes]
cpu/intel_cacheinfo.c defines two functions amd_get_l3_disable_slot
and amd_set_l3_disable_slot. No other file uses these functions.
So make these static.
This eliminates the following warnings:
arch/x86/kernel/cpu/intel_cacheinfo.c:349:5: warning: no previous prototype for
cpu/mcheck/mce.c defines mce_chrdev_write. No other file
uses or defines this function, so make this static.
This eliminates the follwing warning:
arch/x86/kernel/cpu/mcheck/mce.c:1981:9: warning: no previous prototype for
‘mce_chrdev_write’ [-Wmissing-prototypes]
Signed-off-by: Darshana
compressed/eboot.c defines an internal function
setup_graphics(struct boot_params *boot_params). No
other file refers to this function with the same
parameters so make this function static.
This eliminates the following warning:
arch/x86/boot/compressed/eboot.c:1004:6: warning: no previous
GCC warns about functions without previous
prototypes i.e -Wmissing-prototypes warnings.
In the following patches the following fixes have
been adopted to eliminate these warnings:
- Functions defined in a file, that are internal
to that file have been made static.
- Header files
Include header file string.h that declares prototypes for functions defined
in string.c.
This eliminates the following warnings:
arch/x86/boot/string.c:18:5: warning: no previous prototype for ‘memcmp’
[-Wmissing-prototypes]
arch/x86/boot/compressed/../string.c:18:5: warning: no previous
compressed/misc.c declares internal function decompress_kernel
used only in this file and in some assembly. Add a prototype for
the function.
This eliminates the followig warning:
arch/x86/boot/compressed/misc.c:369:28: warning: no previous prototype for
‘decompress_kernel’
nosyscall.c declares function compat_ni_syscall that returns
long datatype. compat_ni_syscall is also defined in syscall_ia32.c
but returns void. Add prototype for this function.
This eliminates the following warning:
arch/x86/ia32/nosyscall.c:4:6: warning: no previous prototype for
On 03/02/2015 12:39 PM, David Vrabel wrote:
On 26/02/15 13:35, Juergen Gross wrote:
Introduces the Xen pvUSB backend. With pvUSB it is possible for a Xen
domU to communicate with a USB device assigned to that domU. The
communication is all done via the pvUSB backend in a driver domain
(usually
On 3 March 2015 at 16:11, Lee Jones wrote:
> Signed-off-by: Lee Jones
> ---
> .../devicetree/bindings/mailbox/sti-mailbox.txt| 66
> ++
> 1 file changed, 66 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mailbox/sti-mailbox.txt
>
> diff --git
On 3 March 2015 at 16:11, Lee Jones wrote:
> ---
> drivers/mailbox/Kconfig | 7 +
> drivers/mailbox/Makefile | 2 +
> drivers/mailbox/mailbox-sti.c | 664
> ++
> include/linux/mailbox_sti.h | 128
>
How about the header in
Some ARM platforms mux the PMU interrupt of every core into a single
SPI. On such platforms if the PMU of any core except 0 raises an interrupt
then it cannot be serviced and eventually, if you are lucky, the spurious
irq detection might forcefully disable the interrupt.
On these SoCs it is not
On Wed, Mar 04, 2015 at 01:09:51PM +0100, Vlastimil Babka wrote:
> On 03/04/2015 12:52 PM, Kirill A. Shutemov wrote:
> >On Mon, Feb 23, 2015 at 05:21:31PM +0100, Vlastimil Babka wrote:
> >>On 02/12/2015 05:18 PM, Kirill A. Shutemov wrote:
> >>>@@ -1052,21 +1052,24 @@ void page_add_anon_rmap(struct
Hello,
we are running hundreds of containers and we got some valid requests from
customers that want to be able to change their
container's hostname using the sysctl command.
The current implementation does not allow each UTS namespace to change its own
hostname.
So we sponsored the
Hi Javi,
your commit 8754d5115693 ("thermal: introduce the Power Allocator
governor") is included in today's linux-next tree (i.e.,
next-20150304).
This patch adds a select on the Kconfig symbol THERMAL_POWER_ACTOR.
However, THERMAL_POWER_ACTOR is not defined so that this select
Hello,
I have a question regarding the synchronization mechanism between
wait_for_completion_interruptible_timeout() & complete(). I used
complete() API in the ISR Tx interrupt path and
wait_for_completion_interruptible_timeout() in struct file_operations
.write method.
Let assume a scenario in
On Tue 2015-03-03 17:02:22, Josh Poimboeuf wrote:
> It's possible for klp_register_patch() to see a module before the COMING
> notifier is called, or after the GOING notifier is called.
>
> That can cause all kinds of ugly races. As Pter Mladek reported:
>
> "The problem is that we do not
virtio spec requires that all drivers set DRIVER_OK
before using devices. While balloon isn't yet
included in the virtio 1 spec, previous spec versions
also required this.
virtio balloon might violate this rule: probe calls
kthread_run before setting DRIVER_OK, which might run
immediately and
Le 02/03/2015 10:32, Bo Shen a écrit :
> Hi Nicolas,
>
> On 02/10/2015 09:55 AM, Bo Shen wrote:
>> This patch series enable usb device support on at91sam9n12ek board.
>>
>> Changes in v2:
>>- Base on next-20150209 (so, remove the modification of udc driver).
>>- Add pinctrl for usb1 vbus
W dniu 24.02.2015 09:24, Mark Brown pisze:
> On Sun, Feb 15, 2015 at 11:11:43PM +0100, Maciej S. Szmigiero wrote:
>> of_property_read_u32_array returns 0 on success, so the return value
>> shouldn't be inverted twice,
>> first on assignment then in condition expression.
>
> This doesn't apply to
On 03/04/2015 12:49 AM, Greg KH wrote:
On Tue, Mar 03, 2015 at 07:31:58PM -0500, Michel Machado wrote:
Hi Daniel,
We're fine with clearly marking Linux XIA as being under staging
as well as helping to define this review process for network stacks.
With regard to staging, the code there is
On Wed, Jan 21, 2015 at 10:33 PM, Olliver Schinagl
wrote:
> From: Olliver Schinagl
>
> The gpio binding document says that new code should always use named
> gpios. Patch 40b73183 added support to parse a list of gpios from child
> nodes, but does not make it possible to use named gpios. This
On Sun, Feb 8, 2015 at 1:34 PM, Nicholas Mc Guire wrote:
> return type of read_i2c() is int not u32. As the assignments to status
> are consistent with int here its type is changed to int.
>
> Signed-off-by: Nicholas Mc Guire
Acked-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe
On Wed, Mar 04, 2015 at 08:35:52PM +0800, Chih-Chiang Chang wrote:
> On 2015/2/24 下午 10:13, Mark Brown wrote:
> > I would have expected the headphone volume control to be a stereo
> > (double) control - same for speakers.
> The nau8824 related registers which control left/right volume are
On Sun, Feb 8, 2015 at 1:34 PM, Nicholas Mc Guire wrote:
> return type of wait_for_completion_timeout is unsigned long not int. as
> timeout is used for wait_for_completion_timeout exclusively here its
> type is simply changed to unsigned long.
>
> Signed-off-by: Nicholas Mc Guire
Acked-by:
On Wednesday 04 March 2015 06:17 PM, Sylwester Nawrocki wrote:
Hi,
On 04/03/15 13:24, Kishon Vijay Abraham I wrote:
This patch doesn't apply on 4.0-rc1. Can to refresh it to mainline
latest?
It depends on Axel's previous patch: "phy: exynos-mipi-video: Fixup
the test for state->regmap".
>From fe37688e226f83ba477a3c2fbc1e64946cd4ec4e Mon Sep 17 00:00:00 2001
From: Chih-Chiang Chang
Date: Wed, 4 Mar 2015 20:03:21 +0800
Subject: [PATCH v2] ASoC: Add support for NAU8824 codec to ASoC
Signed-off-by: Chih-Chiang Chang
---
include/sound/nau8824.h| 22 ++
On 04.03.2015 07:14, Greg Kroah-Hartman wrote:
> 3.18-stable review patch. If anyone has any objections, please let me know.
I thought I replied earlier today but I cannot seem to find it coming back via
the mailing list. Hope this is not duplicating too much... There was a
regression with that
I have constantly stumbled upon "kernel BUG at mm/rmap.c:399!" after
upgrading to 3.19 and had no luck with 4.0-rc1 neither.
So, after looking into new logic introduced by 7a3ef208e662 ("mm: prevent
endless growth of anon_vma hierarchy"), I found chances are that
unlink_anon_vmas() is called
On Thu, Feb 5, 2015 at 4:49 PM, Geert Uytterhoeven
wrote:
> The pcf857x GPIO and interrupt controller uses dummy_irq_chip, which
> does not implement irq_chip.irq_set_wake() and does not set
> IRQCHIP_SKIP_SET_WAKE.
>
> This causes two s2ram issues if wake-up is enabled for the pcf857x GPIO
>
Check for null before being dereferenced to avoid a invalid null
dereference.
Found using Coccinelle.
Signed-off-by: Tapasweni Pathak
Acked-by: Julia Lawall
---
drivers/scsi/ufs/ufshcd.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/ufs/ufshcd.c
On Thu, Feb 5, 2015 at 4:49 PM, Geert Uytterhoeven
wrote:
> Switch the PCF857x GPIO driver to use the gpiolib irqchip helpers.
> This driver uses a nested threaded interrupt, hence handle_nested_irq()
> and gpiochip_set_chained_irqchip() must be used.
>
> Note that this removes the checks added
On 2015/2/24 下午 10:13, Mark Brown wrote:
> On Sun, Feb 15, 2015 at 03:49:30PM +0800, Wan Zongshun wrote:
>
>> +/* SP Class-D mute control */
>> +SOC_DOUBLE("HP Playback Switch", NAU8824_HP_MUTE, NAU8824_L_MUTE_SFT,
>> +NAU8824_R_MUTE_SFT, 1, 1),
>> +
Hi,
On 04/03/15 13:24, Kishon Vijay Abraham I wrote:
> This patch doesn't apply on 4.0-rc1. Can to refresh it to mainline
> latest?
It depends on Axel's previous patch: "phy: exynos-mipi-video: Fixup
the test for state->regmap". Are there any issues even with that patch
applied ?
--
Thanks
(2015/03/04 19:01), He Kuang wrote:
> A double free occurred when get source file path failed. If lr->path
> failed to assign a new value, it will be freed as the old path and then
> be freed again during line_range__clear(), and causes this:
>
> $ perf probe -L do_execve -k vmlinux
> ***
Hello,
On Wed, Mar 04, 2015 at 09:47:47PM +1100, Michael Ellerman wrote:
> On Tue, 2015-03-03 at 17:05 -0700, Shuah Khan wrote:
> > On 02/27/2015 08:16 PM, Namhyung Kim wrote:
> > > On Tue, Feb 24, 2015 at 01:24:59PM -0500, Dave Jones wrote:
> > >> On Tue, Feb 24, 2015 at 11:22:58AM -0700, Shuah
On Wednesday 04 March 2015 05:30 PM, Sebastian Hesselbarth wrote:
> On 03/04/2015 11:46 AM, Vineet Gupta wrote:
>> > On Wednesday 04 March 2015 02:30 PM, Sebastian Hesselbarth wrote:
>>> >> On 04.03.2015 04:11, Jisheng Zhang wrote:
>>> On Tue, 3 Mar 2015 06:56:59 -0800
>>> Alexey Brodkin
The 'stack_size' argument is never used to pass a stack size. It's only used
when
forking a kernel thread, in which case it is an argument which should be passed
to the 'main' function which the kernel thread executes. Hence, rename it to
'kthread_arg'.
Signed-off-by: Alex Dowad
---
Hi,
On Wed, Mar 04, 2015 at 09:23:01PM +0900, Namhyung Kim wrote:
> On Tue, Mar 03, 2015 at 03:26:35PM +0100, Jiri Olsa wrote:
> > diff --git a/tools/build/tests/features/Makefile
> > b/tools/build/tests/features/Makefile
> > new file mode 100644
> > index ..31782a1d3758
> > --- /dev/null
On Tue, Mar 03, 2015 at 09:16:08AM +0800, Qiao Zhou wrote:
> Below are the refinements.
> 1. Set DMA abort bit when disabling dma channel. This will clear
> the remaining data in dma FIFO, to fix channel-swap issue.
> 2. Read DMA HW pointer when updating DMA status. Previously dma
> position is
Hi Jean,
See reply at v4.
On 02/26/2015 10:50 AM, Jean Delvare wrote:
Hi Ivan, Mark and all,
Le Tuesday 03 February 2015 à 17:48 +0200, Ivan Khoronzhuk a écrit :
On 02/03/2015 04:58 PM, Mark Salter wrote:
On Wed, 2015-01-28 at 14:39 +0200, Ivan Khoronzhuk wrote:
Some utils, like dmidecode
Hi Jean.
On 02/26/2015 11:41 AM, Jean Delvare wrote:
Replying to myself...
On Thu, 26 Feb 2015 09:50:42 +0100, Jean Delvare wrote:
Please also note that the recently released version 3.0.0 of the SMBIOS
specification introduces a new entry point format, and the firmware is
allowed to
(2015/03/04 16:52), Naohiro Aota wrote:
> If we use lazy matching, it failed to open a souce file if perf command
> is invoked outside of compilation directory:
>
> $ perf probe -a '__schedule;clear_*'
> Failed to open kernel/sched/core.c: No such file or directory
> Error: Failed to add
Hi,
I wanted to give the new kernel a try, but the cryptsetup fails with:
[8.747114] localhost.localdomain systemd-cryptsetup[280]: Set cipher aes,
mode xts-plain64, key size 256 bits for device /dev/disk/[...]
[9.265258] localhost.localdomain kernel: device-mapper: table: 254:0:
crypt:
On 02/26/2015 11:36 AM, Jean Delvare wrote:
Hi Ivan,
Sorry for the late review.
On Wed, 4 Feb 2015 19:06:03 +0200, Ivan Khoronzhuk wrote:
Some utils, like dmidecode and smbios, need to access SMBIOS entry
table area in order to get information like SMBIOS version, size, etc.
Currently it's
On Wed, Mar 04, 2015 at 12:00:16PM +, Sudeep Holla wrote:
> This patch removes the redundant sysfs cacheinfo code by reusing
> the newly introduced generic cacheinfo infrastructure through the
> commit 246246cbde5e ("drivers: base: support cpu cache information
> interface to userspace via
Hi,
On Friday 27 February 2015 06:57 PM, Sylwester Nawrocki wrote:
On 27/02/15 04:50, Axel Lin wrote:
he state->regmap is initialized by devm_regmap_init_mmio().
So it's fine to use spin_lock rather than mutex to protct state->regmap rmw
operations.
Signed-off-by: Axel Lin
---
Hi Sylwester,
On Tue, Mar 03, 2015 at 03:26:35PM +0100, Jiri Olsa wrote:
> diff --git a/tools/build/tests/features/Makefile
> b/tools/build/tests/features/Makefile
> new file mode 100644
> index ..31782a1d3758
> --- /dev/null
> +++ b/tools/build/tests/features/Makefile
> @@ -0,0 +1,23 @@
> +all:
On 03/03/15 15:53, Sudeep Holla wrote:
On 02/03/15 11:29, Suzuki K. Poulose wrote:
From: "Suzuki K. Poulose"
This patch separates the PMU driver code from the low level
CCI driver code.
Introduces config options for both.
ARM_CCI400_PORT_CTRL - controls the low level driver code for
On 03/03/15 16:00, Sudeep Holla wrote:
On 02/03/15 11:29, Suzuki K. Poulose wrote:
From: "Suzuki K. Poulose"
This series enables the PMU monitoring support for CCI400 on ARM64.
The existing CCI400 driver code is a mix of PMU driver and the MCPM
driver code. The MCPM driver is only used on
On 03/03/15 15:35, Sudeep Holla wrote:
On 02/03/15 11:29, Suzuki K. Poulose wrote:
From: "Suzuki K. Poulose"
No functional changes, only code re-arrangements for easier split of the
PMU code vs low level driver code. Extracts the port handling code
to cci_probe_ports().
Signed-off-by:
On 03/03/15 at 08:14am, Yinghai Lu wrote:
> On Tue, Mar 3, 2015 at 3:42 AM, Baoquan He wrote:
> >
> > Here input means the region where kernel was linked to load?
> >
> > In normal kernel the linked address is 0x100. In your input region
> > the result of ALIGN(0x13f5ed3b4,
On 03/04/2015 12:52 PM, Kirill A. Shutemov wrote:
On Mon, Feb 23, 2015 at 05:21:31PM +0100, Vlastimil Babka wrote:
On 02/12/2015 05:18 PM, Kirill A. Shutemov wrote:
@@ -1052,21 +1052,24 @@ void page_add_anon_rmap(struct page *page,
* Everybody else should continue to use page_add_anon_rmap
2015-03-03 20:43 GMT+01:00 Paul Bolle :
> Maxime Coquelin schreef op ma 02-03-2015 om 17:53 [+0100]:
>> Do you agree if I define it like this:
>>
>> config ARMV7M_SYSTICK
>> bool "Clocksource driver for ARMv7-M System timer"
>> depends on OF && (CPU_V7M || COMPILE_TEST)
>> select
On 4 March 2015 at 07:19, Rafał Miłecki wrote:
> On 3 March 2015 at 22:16, Chen Gang wrote:
>> bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
>> or will cause building break for allmodconfig under c6x:
>>
>> CC [M] drivers/bcma/driver_pcie2.o
>>
Commit ddd4dd8ddf784 (thermal: extend the cooling device API to include
power information) added stubs for newly introduced functions when
!CONFIG_THERMAL but did not provide names for the parameters which is
a syntax error causing build errors in such configurations. Add names to
fix the issue.
On Mon, Mar 02, 2015 at 01:36:51PM +, Wu, Feng wrote:
>
>
> > -Original Message-
> > From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> > Sent: Friday, February 27, 2015 7:41 AM
> > To: Wu, Feng
> > Cc: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
> >
SF Markus Elfring writes:
> From: Markus Elfring
> Date: Wed, 4 Feb 2015 19:30:23 +0100
>
> The release_firmware() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected by using the Coccinelle
On Mon, Mar 02, 2015 at 08:28:01PM +0100, Arnd Bergmann wrote:
> On Monday 02 March 2015 23:24:24 Kedareswara rao Appana wrote:
> > This patch moves the xilinx_dma.h header file
> > to the include/linux/dma.
> >
> > Signed-off-by: Kedareswara rao Appana
>
> Please move this header file to
Explanation of several properties, which allow PWM fan working as a cooling
device, have been embraced in this commit.
Signed-off-by: Lukasz Majewski
Acked-by: Eduardo Valentin
---
Changes for v2:
- Rename cooling-pwm-values to cooling-levels
- Remove default-pulse-width property and stick to
It was necessary to decouple code handling writing to sysfs from the one
responsible for setting PWM of the fan.
Due to that, new __set_pwm() method was extracted, which is responsible for
only setting new PWM duty cycle.
Signed-off-by: Lukasz Majewski
---
Changes for v2:
- None
Changes for v3:
From: Kamil Debski
Add pwm-fan node to the Odroid-U3 board file to enable PWM control of the
cooling fan. In addition, add the "pwm" label to the pwm@139D node
in the exynos4412.dtsi.
Signed-off-by: Kamil Debski
Signed-off-by: Lukasz Majewski
---
Changes since v1:
- added pwm label to the
The PWM FAN device can now be used as a thermal cooling device. Necessary
infrastructure has been added in this commit.
Signed-off-by: Lukasz Majewski
Acked-by: Eduardo Valentin
---
Changes for v2:
- Replace pwm_fan_cooling_states with pwm_fan_cooling_levels
- Update ctx->pwm_fan_state when
This patch provides code for reading PWM FAN configuration data via
device tree. The pwm-fan can work with full speed when configuration
is not provided. However, errors are propagated when wrong DT bindings
are found.
Additionally the struct pwm_fan_ctx has been extended.
Signed-off-by: Lukasz
With those bindings it is possible to use pwm-fan device available in
Odroid U3 as a cooling device.
Signed-off-by: Lukasz Majewski
Acked-by: Eduardo Valentin
---
Changes for v2:
- Rename cooling-pwm-values property to cooling-levels
Changes for v3:
- Change patch's topic to "ARM dts"
- Reduce
Presented patches add support for Odroid's U3 optional CPU FAN, which uses PWM
subsystem for low level control.
After successful probe it registers itself as a cooling device for thermal
subsystem.
This driver also supports devices without DTS specified.
To provide correct functionality, new
On 03/04/2015 11:46 AM, Vineet Gupta wrote:
On Wednesday 04 March 2015 02:30 PM, Sebastian Hesselbarth wrote:
On 04.03.2015 04:11, Jisheng Zhang wrote:
On Tue, 3 Mar 2015 06:56:59 -0800
Alexey Brodkin wrote:
This allows utilization of probe deferral if master interrupt controller
was not yet
This patch removes the redundant sysfs cacheinfo code by reusing
the newly introduced generic cacheinfo infrastructure through the
commit 246246cbde5e ("drivers: base: support cpu cache information
interface to userspace via sysfs")
The private pointer provided by the cacheinfo is used to
Mike,
Do you want me to resend this set with Robert's Reviewed-by applied,
or are you happy to apply it yourself?
> v2 => v3:
> - Ensure DT actually reflects h/w
> - i.e. Nodes should not contain a mishmash of different IP
> blocks, but should identify related h/w. In the current
>
801 - 900 of 2430 matches
Mail list logo
