From: Oleksandr Andrushchenko
Implement ALSA driver operations including:
- start/stop period interrupt emulation
- manage frontend/backend shraed buffers
- manage Xen bus event channel state
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/xen-front.c | 175 +++
From: Oleksandr Andrushchenko
Implement shared buffer handling according to the
para-virtualized sound device protocol at xen/interface/io/sndif.h:
- manage buffer memory
- handle granted references
- handle page directories
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/xen-front.c
From: Oleksandr Andrushchenko
Implement frontend to backend communication according to
the para-virtualized sound protocol: xen/interface/io/sndif.h.
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/xen-front.c | 302 +++---
1 file changed, 288 i
From: Oleksandr Andrushchenko
Introduce Kconfig option to enable Xen para-virtualized sound
frontend driver. Also add sound frontend to the Makefile.
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/Kconfig | 12
sound/drivers/Makefile | 2 ++
2 files changed, 14 inserti
From: Oleksandr Andrushchenko
Front sound driver has no real interrupts, so
playback/capture period passed interrupt needs to be emulated:
this is done via timer. Add required timer operations,
this is based on sound/drivers/dummy.c.
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/xen
Below is the list of build error/warning regressions/improvements in
v4.13-rc3[1] compared to v4.12[2].
Summarized:
- build errors: +2/-
- build warnings: +1336/-908
JFYI, when comparing v4.13-rc3[1] to v4.13-rc2[3], the summaries are:
- build errors: +2/-
- build warnings: +495/-395
Hap
From: Oleksandr Andrushchenko
Initialize virtual sound card with streams according to the
Xen store configuration.
Add stubs for stream PCM operations.
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/xen-front.c | 232 ++
1 file changed, 232
On 08/07/2017 03:41 AM, Weilong Chen wrote:
Hi Minyard,
I test this patch, it works.
Thanks.
Thanks, I added a Tested-by: for you and it's queued for the next release.
If it's urgent I can send it in now.
I also added this for the stable kernels 3.16 and later.
-corey
On 2017/7/30 10:20,
On 04/08/17 20:32, Guenter Roeck wrote:
> On Fri, Aug 04, 2017 at 03:31:42PM +0100, Sudeep Holla wrote:
[...]
>> +platform_set_drvdata(pdev, scmi_sensors);
>> +
>> +hwdev = devm_hwmon_device_register_with_groups(dev, "scmi_sensors",
>> +
From: Oleksandr Andrushchenko
1. Create event channels for all configured streams and publish
corresponding ring references and event channels in Xen store,
so backend can connect.
2. Implement event channel interrupt handler.
3. Create and destroy event channels with respect to Xen bus state.
S
Hi Jacob,
On Mon, 2017-08-07 at 19:06 +0800, Jacob Chen wrote:
[...]
> >> > --- a/drivers/media/i2c/ov5647.c
> >> > +++ b/drivers/media/i2c/ov5647.c
> >> > @@ -253,6 +253,10 @@ static int ov5647_stream_on(struct v4l2_subdev *sd)
> >> > {
> >> > int ret;
> >> >
> >> > + ret = ov5647_
On Mon, Aug 7, 2017 at 2:24 PM, Geert Uytterhoeven wrote:
> JFYI, when comparing v4.13-rc3[1] to v4.13-rc2[3], the summaries are:
> - build errors: +2/-
Known sh-randconfig issues that pop up from time to time.
> [1]
> http://kisskb.ellerman.id.au/kisskb/head/16f73eb02d7e1765ccab3d2018e0bd98e
From: Oleksandr Andrushchenko
Add essential driver private info structure, initialize
locks and implement probe/remove of the Xen frontend
driver.
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/xen-front.c | 27 +++
1 file changed, 27 insertions(+)
diff --git
From: Oleksandr Andrushchenko
Read configuration values from Xen store according
to xen/interface/io/sndif.h protocol:
- introduce configuration structures for different
components, e.g. sound card, device, stream
- read PCM HW parameters, e.g rate, format etc.
- detect stream type (capture/pla
From: Oleksandr Andrushchenko
Implement essential initialization of the sound driver:
- introduce required data structures
- handle driver registration
- handle sound card registration
- register sound driver on backend connection
- remove sound driver on backend disconnect
Signed-off-by: Oleksa
On 2017-08-07 10:55, Chanwoo Choi wrote:
Hi,
On 2017년 08월 07일 13:47, gsant...@codeaurora.org wrote:
On 2017-08-04 20:42, Chanwoo Choi wrote:
Hi,
On Fri, Aug 4, 2017 at 12:57 PM, wrote:
Hi,
Adding error checks to devfreq userspace governor, the current
implementation results in setting wro
From: Oleksandr Andrushchenko
Initial handling for Xen bus states: implement
Xen bus state machine for the front driver according to
the state diagram and recovery flow from sound para-virtualized
protocol: xen/interface/io/sndif.h.
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/xen-
From: Oleksandr Andrushchenko
Introduce skeleton of the para-virtualized Xen sound
frontend driver. This patch only adds required
essential stubs.
Signed-off-by: Oleksandr Andrushchenko
---
sound/drivers/xen-front.c | 78 +++
1 file changed, 78 inser
On Mon, Aug 07, 2017 at 02:11:39PM +0200, Paolo Bonzini wrote:
> You could also add a module parameter to the driver, and set it to 64 on
> the kernel command line (there is an example in
> drivers/scsi/vmw_pvscsi.c of how to do it).
[Proviso: I've not tested the performance of difference values,
From: Oleksandr Andrushchenko
This patch series adds support for Xen [1] para-virtualized
sound frontend driver. It implements the protocol from
include/xen/interface/io/sndif.h with the following limitations:
- mute/unmute is not supported
- get/set volume is not supported
Volume control is not
To 74hc595 and 74lv595, there is an OE(low active) input pin.
To some boards, this pin is controller by GPIO, so handling
this pin in driver. When driver probe, use GPIOD_OUT_LOW flag
when requesting the gpio, so OE is set to low when probe.
Signed-off-by: Peng Fan
Cc: Linus Walleij
---
drivers
There is an OE(low active) input pin for 74hc595 and 74lv595.
To some boards, the OE pin is controlled by GPIO, so add an
optional property "enable-gpios".
Signed-off-by: Peng Fan
Cc: Rob Herring
Cc: Linus Walleij
---
Documentation/devicetree/bindings/gpio/gpio-74x164.txt | 3 +++
1 file chang
On 08/07/2017 06:45 PM, Paolo Bonzini wrote:
On 07/08/2017 10:44, Longpeng(Mike) wrote:
+
+ /*
+* Intel sdm vol3 ch-25.1.3 says: The “PAUSE-loop exiting”
+* VM-execution control is ignored if CPL > 0. So the vcpu
+* is always exiting with CPL=0 if it uses PLE.
T
On Mon, Aug 7, 2017 at 4:27 AM, Vivek Gautam
wrote:
> On Thu, Jul 13, 2017 at 5:20 PM, Rob Clark wrote:
>> On Thu, Jul 13, 2017 at 1:35 AM, Sricharan R
>> wrote:
>>> Hi Vivek,
>>>
>>> On 7/13/2017 10:43 AM, Vivek Gautam wrote:
Hi Stephen,
On 07/13/2017 04:24 AM, Stephen Boyd
On Aug 7 2017 21:18, Oleksandr Andrushchenko wrote:
Your first patch includes code difference under line 26, thus it
expects existence of a file 'sound/drivers/xen-front.c' in tree.
However, the file is not introduced in any upstream yet; at least,
Linus's tree and Iwai-san's tree.
I missed th
On 08/07/2017 03:30 PM, Takashi Sakamoto wrote:
On Aug 7 2017 21:18, Oleksandr Andrushchenko wrote:
Your first patch includes code difference under line 26, thus it
expects existence of a file 'sound/drivers/xen-front.c' in tree.
However, the file is not introduced in any upstream yet; at lea
Hi Peng,
On Mon, Aug 7, 2017 at 9:27 AM, Peng Fan wrote:
> To 74hc595 and 74lv595, there is an OE(low active) input pin.
> To some boards, this pin is controller by GPIO, so handling
> this pin in driver. When driver probe, use GPIOD_OUT_LOW flag
> when requesting the gpio, so OE is set to low wh
The early device registration made possible a race leading to allocations
of disks with wrong minors.
This patch moves the device registration further down the loop_init
function to make the race infeasible.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Anton Volk
"Reizer, Eyal" writes:
> The following commits:
> c815fde wlcore: spi: Populate config firmware data
> d776fc8 wlcore: sdio: Populate config firmware data
It's recommended to use 12 chars when abbreviating commit ids so the
format should be this:
c815fdebef44 wlcore: spi: Populate config firmwa
Below is the list of build error/warning regressions/improvements in
v4.13-rc4[1] compared to v4.12[2].
Summarized:
- build errors: +1/-
- build warnings: +1462/-1120
JFYI, when comparing v4.13-rc4[1] to v4.13-rc3[3], the summaries are:
- build errors: +1/-2
- build warnings: +457/-541
H
On 07/08/17 00:35, Daniel Borkmann wrote:
> On 08/03/2017 06:11 PM, Edward Cree wrote:
>> Unifies adjusted and unadjusted register value types (e.g. FRAME_POINTER is
>> now just a PTR_TO_STACK with zero offset).
>> Tracks value alignment by means of tracking known & unknown bits. This
>> also
On Mon, Aug 7, 2017 at 9:27 AM, Peng Fan wrote:
> + chip->enable_gpio = devm_gpiod_get(&spi->dev, "enable",
> GPIOD_OUT_LOW);
> + if (IS_ERR(chip->enable_gpio)) {
> + dev_dbg(&spi->dev, "No enable-gpios property\n");
> + chip->enable_gpio = NULL;
Also, th
I saw unpaired spi clock disable warnings when suspend/unbind spi device.
Fix them follow spi-s3c64xx.c.
Jeffy Chen (3):
spi: rockchip: Slightly rework return value handling
spi: rockchip: Fix clock handling in remove
spi: rockchip: Fix clock handling in suspend/resume
drivers/spi/spi-r
Slightly rework return value handling, no functional changes.
Signed-off-by: Jeffy Chen
---
drivers/spi/spi-rockchip.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c
index 0b4a52b..5497650 1
We are assuming clocks enabled when calling rockchip_spi_remove, which
is not always true. Those clocks might already been disabled by the
runtime PM at that time.
Call pm_runtime_get_sync before trying to disable clocks to avoid that.
Signed-off-by: Jeffy Chen
---
drivers/spi/spi-rockchip.c |
On Mon, Aug 07, 2017 at 11:20:10AM +0530, Neeraj Upadhyay wrote:
> Pending cbs check in rcu_prepare_for_idle is inversed
> in the sense that, it should accelerate if there are
> pending cbs; but, the check does the opposite. So,
> fix it.
>
> Fixes: 15fecf89e46a ("srcu: Abstract multi-tail callbac
The runtime suspend callback might be called by pm domain framework at
suspend_noirq stage. It would try to disable the clocks which already
been disabled by rockchip_spi_suspend.
Call pm_runtime_force_suspend/pm_runtime_force_resume when
suspend/resume to avoid that.
Signed-off-by: Jeffy Chen
-
On Mon, Aug 7, 2017 at 2:39 PM, Geert Uytterhoeven wrote:
> JFYI, when comparing v4.13-rc4[1] to v4.13-rc3[3], the summaries are:
> - build errors: +1/-2
+ /home/kisskb/slave/src/arch/sh/drivers/dma/dma-sh.c: error:
'CONFIG_NR_ONCHIP_DMA_CHANNELS' undeclared here (not in a function):
=> 376:1
On 08/04/2017 11:36 AM, Mark Salyzyn wrote:
> On 08/03/2017 06:18 PM, Prarit Bhargava wrote:
>
>> diff --git a/arch/arm/configs/aspeed_g4_defconfig
>> b/arch/arm/configs/aspeed_g4_defconfig
>> index cfc2465e8b77..6c73c305ad17 100644
>> --- a/arch/arm/configs/aspeed_g4_defconfig
>> +++ b/arch/arm
On Thu, Aug 3, 2017 at 1:06 PM, Masahiro Yamada
wrote:
> This GPIO controller device is used on UniPhier SoCs.
>
> Signed-off-by: Masahiro Yamada
(...)
> +static const u32 uniphier_gpio_irq_parent_hwirqs[] = {
> + 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95,
> + 18
On 01/08/17 17:56, Mason wrote:
> This controller maps 128 input lines to 24 output lines.
> The output lines are routed to GIC SPI 0 to 23.
> This driver muxes LEVEL_HIGH IRQs onto output line 0,
> and gives every EDGE_RISING IRQ a dedicated output line.
> ---
> Changes from v5 to v6:
> Add suspen
On Thu, Aug 3, 2017 at 2:25 PM, Joseph Chen wrote:
> RK805 is one of Rockchip PMICs family, it has 2 output only GPIOs.
>
> This driver is also designed for other Rockchip PMICs to expend.
> Different PMIC maybe have different pin features, for example,
> RK816 has one pin which can be used for T
On 7.8.2017 11:50, Julia Lawall wrote:
> The sdhci_pltfm_data structure is only passed as the second argument
> of sdhci_pltfm_init, which is const, while the sdhci_ops structure
> is only stored in the ops field of a sdhci_pltfm_data structure,
> which is also const. Thus both kinds of structures
On Wed, Aug 02, 2017 at 03:24:05PM +0200, Peter Zijlstra wrote:
> On Wed, Aug 02, 2017 at 02:10:02PM +0100, Brendan Jackman wrote:
> > We use task_util in find_idlest_group via capacity_spare_wake. This
> > task_util is updated in wake_cap. However wake_cap is not the only
> > reason for ending up
On Mon, Aug 07, 2017 at 03:37:50PM +0300, Anton Volkov wrote:
> +err_out:
> return err;
Any reason you can't just use return err; at the respective callsites?
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumsh...@suse.de
The synchronization type that was used earlier to guard the loop that
deletes unused log buffers may lead to a situation that prevents any
thread from going through the loop.
The patch deletes previously used synchronization mechanism and moves
the loop under the spin_lock so the similar cases won
From: Markus Elfring
Date: Mon, 7 Aug 2017 14:48:14 +0200
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (5):
Delete an error message for a failed memory allocation in three functions
Adjust 44 checks for null pointers
Delete an unnecessary
On 28/07/17 15:06, Marc Gonzalez wrote:
> On 27/07/2017 20:17, Florian Fainelli wrote:
>
>> On 07/26/2017 12:13 PM, Måns Rullgård wrote:
>>
>>> Florian Fainelli writes:
>>>
On 07/25/2017 06:29 AM, Måns Rullgård wrote:
> Marc Gonzalez writes:
>
>> On 25/07/2017 15:16, Måns Ru
On Thu, Aug 3, 2017 at 11:21 PM, Julia Lawall wrote:
> These watchdog_ops and watchdog_info structures are only stored
> in the ops and info fields of a watchdog_device structure,
> respectively, which are const. Thus make the watchdog_ops and
> watchdog_info structures const as well.
>
> Done w
On Fri, Aug 4, 2017 at 12:00 AM, Gustavo A. R. Silva
wrote:
> platform_get_irq() returns an error code, but the gpio-msic driver
> ignores it and always returns -EINVAL. This is not correct, and
> prevents -EPROBE_DEFER from being propagated properly.
>
> Notice that platform_get_irq() no longer
From: Markus Elfring
Date: Mon, 7 Aug 2017 13:24:59 +0200
Omit an extra message for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
Sig
From: Markus Elfring
Date: Mon, 7 Aug 2017 14:00:44 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The script “checkpatch.pl” pointed information out like the following.
Comparison to NULL could be written …
Thus fix affected source code places.
On Mon, Aug 07, 2017 at 02:15:51PM +0200, Peter Zijlstra wrote:
> On Fri, Aug 04, 2017 at 04:50:54PM +0800, 石祤 wrote:
> > From: "leilei.lin"
> >
> > A performance issue caused by less strickly check in task
> > sched when these tasks were once attached by per-task perf_event.
> >
> > A task will
From: Markus Elfring
Date: Mon, 7 Aug 2017 14:10:35 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: void function return statements are not generally useful
Thus remove such a statement in the affected function.
Signed-off-by: Markus Elfring
---
drivers/
Signed-off-by: Joel Fernandes
---
samples/bpf/README.rst | 10 ++
1 file changed, 10 insertions(+)
diff --git a/samples/bpf/README.rst b/samples/bpf/README.rst
index 79f9a58f1872..2b906127ef54 100644
--- a/samples/bpf/README.rst
+++ b/samples/bpf/README.rst
@@ -64,3 +64,13 @@ It is also
BPF samples fail to build when cross-compiling for ARM64 because of incorrect
pt_regs param selection. This is because clang defines __x86_64__ and
bpf_headers thinks we're building for x86. Since clang is building for the BPF
target, it shouldn't make assumptions about what target the BPF program
The series adds cross compiler support for BPF samples and fixes issues
building for arm64.
Tested on my arm64 platform with good results, for x86 I have only build tested
it. There are no errors on building, however there is a build warning for x86
which I haven't yet gotten rid off (I believe th
From: Markus Elfring
Date: Mon, 7 Aug 2017 14:18:50 +0200
Add a missing character in this description.
Signed-off-by: Markus Elfring
---
drivers/block/skd_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c
index 8e2c89
When cross-compiling the bpf sample map_perf_test for aarch64, I find that
__NR_getpgrp is undefined. This causes build errors. This syscall is deprecated
and requires defining __ARCH_WANT_SYSCALL_DEPRECATED. To avoid having to define
that, just use a different syscall (getppid) for the array map s
When cross compiling, bpf samples use HOSTCC, however what we really want is to
use the cross compiler to build for the cross target since that is what will
help run the BPF target code. Detect this and also set -static as LDFLAGS
since often times we don't have control over what C library the cro
inline assembly has haunted building samples on arm64 for quite sometime.
This patch uses the pre-processor to noop all occurences of inline asm when
compiling the BPF sample for the BPF target.
This patch reintroduces inclusion of asm/sysregs.h which needs to be included
to avoid compiler errors
On Fri, Aug 4, 2017 at 4:22 AM, Masahiro Yamada
wrote:
> Update subsystem wide for consistency.
>
> Signed-off-by: Masahiro Yamada
OK then.
Patch applied.
Yours,
Linus Walleij
The series adds cross compiler support for BPF samples and fixes issues
building for arm64.
Tested on my arm64 platform with good results, for x86 I have only build tested
it. There are no errors on building, however there is a build warning for x86
which I haven't yet gotten rid off (I believe th
From: Markus Elfring
Date: Mon, 7 Aug 2017 14:34:33 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: Prefer ARRAY_SIZE(skd_chkstat_table)
Thus use this macro.
Signed-off-by: Markus Elfring
---
drivers/block/skd_main.c | 2 +-
1 file changed, 1 insertion(+
BPF samples fail to build when cross-compiling for ARM64 because of incorrect
pt_regs param selection. This is because clang defines __x86_64__ and
bpf_headers thinks we're building for x86. Since clang is building for the BPF
target, it shouldn't make assumptions about what target the BPF program
When cross compiling, bpf samples use HOSTCC, however what we really want is to
use the cross compiler to build for the cross target since that is what will
help run the BPF target code. Detect this and also set -static as LDFLAGS
since often times we don't have control over what C library the cro
Signed-off-by: Joel Fernandes
---
samples/bpf/README.rst | 10 ++
1 file changed, 10 insertions(+)
diff --git a/samples/bpf/README.rst b/samples/bpf/README.rst
index 79f9a58f1872..2b906127ef54 100644
--- a/samples/bpf/README.rst
+++ b/samples/bpf/README.rst
@@ -64,3 +64,13 @@ It is also
inline assembly has haunted building samples on arm64 for quite sometime.
This patch uses the pre-processor to noop all occurences of inline asm when
compiling the BPF sample for the BPF target.
This patch reintroduces inclusion of asm/sysregs.h which needs to be included
to avoid compiler errors
What this patch does:
Current implementation of store_freq function in devfreq
userspace governor executes further, even if error is returned
from sscanf. This will result in setting up wrong frequency value.
This patch adds proper error check to bail out if
store_freq function of devfreq userspace governor
executes further, even if error is returned from sscanf,
this will result in setting up wrong frequency value.
Add proper error check to bail out if any error is returned.
Signed-off-by: Santosh Mardi
---
drivers/devfreq/governor_userspace.c | 5
On 07/08/2017 14:27, Richard W.M. Jones wrote:
> Also I noticed this code in virtio_scsi.c:
>
> cmd_per_lun = virtscsi_config_get(vdev, cmd_per_lun) ?: 1;
> shost->cmd_per_lun = min_t(u32, cmd_per_lun, shost->can_queue);
>
> but setting cmd_per_lun (as a qemu virtio-scsi-pci param
When cross-compiling the bpf sample map_perf_test for aarch64, I find that
__NR_getpgrp is undefined. This causes build errors. This syscall is deprecated
and requires defining __ARCH_WANT_SYSCALL_DEPRECATED. To avoid having to define
that, just use a different syscall (getppid) for the array map s
This is more of a style-oriented suggestion. This kind of template is
commonly used in other modules.
Regards,
Anton
On 07.08.2017 15:54, Johannes Thumshirn wrote:
On Mon, Aug 07, 2017 at 03:37:50PM +0300, Anton Volkov wrote:
+err_out:
return err;
Any reason you can't just use retur
On Tue, Aug 1, 2017 at 4:54 PM, Icenowy Zheng wrote:
> The V3s pin controller doesn't have the bank 0 (starts at address
> 0x200), which is like A33. However, this is not workarounded when
> developing the driver, which makes IRQ not working.
>
> Fix the IRQ bank base.
>
> Fixes: 56d9e4a76039 ("p
On Fri, Aug 4, 2017 at 6:01 AM, Masahiro Yamada
wrote:
> Since commit 58957d2edfa1 ("pinctrl: Widen the generic pinconf argument
> from 16 to 24 bits"), the generic pinconf arguments are handled by u32.
>
> UniPhier pinctrl drivers do not support debouncing, so u16 is working,
> but align the arg
Oleksandr Andrushchenko wrote:
> On 08/07/2017 01:27 PM, Clemens Ladisch wrote:
>> You have to implement period interrupts (and the .pointer callback)
>> based on when the samples are actually moved from/to the backend.
>
> Do you think I can implement this in a slightly different way,
> without a
On Fri, Aug 4, 2017 at 6:47 AM, Masahiro Yamada
wrote:
> Detected by sparse.
>
> Signed-off-by: Masahiro Yamada
Patch applied.
Yours,
Linus Walleij
When the process exit races with outstanding mcopy_atomic, it would be
better to return ESRCH error. When such race occurs the process and it's mm
are going away and returning "no such process" to the uffd monitor seems
better fit than ENOSPC.
Suggested-by: Michal Hocko
Cc: Andrea Arcangeli
Cc:
On Fri, Aug 4, 2017 at 6:47 AM, Masahiro Yamada
wrote:
> Detected by sparse.
>
> Signed-off-by: Masahiro Yamada
Patch applied.
Yours,
Linus Walleij
On Fri, Aug 4, 2017 at 6:49 AM, Masahiro Yamada
wrote:
> Sparse reports "warning: incorrect type in return expression (different
> address spaces)" because nmk_gpio_populate_chip() is supposed to return
> (struct nmk_gpio_chip *) whereas devm_ioremap_resource() returns
> (void __iomem *). ERR_CA
On Mon, Aug 7, 2017 at 6:06 AM, Joel Fernandes wrote:
> inline assembly has haunted building samples on arm64 for quite sometime.
> This patch uses the pre-processor to noop all occurences of inline asm when
> compiling the BPF sample for the BPF target.
>
> This patch reintroduces inclusion of as
On Fri, Aug 4, 2017 at 6:52 AM, Masahiro Yamada
wrote:
> Sparse reports "warning: incorrect type in assignment (different
> address spaces)".
>
> Signed-off-by: Masahiro Yamada
Patch applied.
Yours,
Linus Walleij
On Mon, Aug 07, 2017 at 07:04:46PM +0800, Miles Chen wrote:
> The commit f80fb3a3d508 ("arm64: add support for kernel ASLR")
> moved module virtual address to
> [module_alloc_base, module_alloc_base + MODULES_VSIZE).
>
> Display module information of the virtual kernel
> memory layout by using mod
On 07/08/2017 14:28, Longpeng(Mike) wrote:
> * kvm_arch_spin_in_kernel() returns whether the vcpu (which exits due to
> spinlock) is CPL=0. It only be called by kvm_vcpu_on_spin(), and the
> input vcpu is 'me' which get a PAUSE exit now. *
>
> I split kvm_arch_vcpu_in_kernel(in RFC) into two funct
On Fri, Aug 4, 2017 at 7:47 AM, Keerthy wrote:
> The patch adds keystone-k2g compatible, specific properties and
> an example. The patch also adds the details of supported SoCs
> for each compatible.
>
> Signed-off-by: Keerthy
> Acked-by: Rob Herring
> ---
>
> Changes in v4:
>
> * Changed doc
On 7 August 2017 at 14:16, Will Deacon wrote:
> On Mon, Aug 07, 2017 at 07:04:46PM +0800, Miles Chen wrote:
>> The commit f80fb3a3d508 ("arm64: add support for kernel ASLR")
>> moved module virtual address to
>> [module_alloc_base, module_alloc_base + MODULES_VSIZE).
>>
>> Display module informati
在 2017-08-07 21:09,Linus Walleij 写道:
On Tue, Aug 1, 2017 at 4:54 PM, Icenowy Zheng wrote:
The V3s pin controller doesn't have the bank 0 (starts at address
0x200), which is like A33. However, this is not workarounded when
developing the driver, which makes IRQ not working.
Fix the IRQ bank ba
On Thu, Aug 3, 2017 at 6:36 PM, Mika Westerberg
wrote:
> This driver adds pinctrl/GPIO support for Intel Denverton SoC. The GPIO
> controller is based on the same hardware design that is already used in
> Intel Sunrisepoint so we leverage the core driver here.
>
> Signed-off-by: Mika Westerberg
On 7/8/2017 02:35, Andy Shevchenko wrote:
> On Sat, Aug 5, 2017 at 6:18 PM, Hao Wei Tee wrote:
>> On 30/5/2017 21:22, Andy Shevchenko wrote:
>>> On Sun, May 28, 2017 at 4:47 PM, Hao Wei Tee wrote:
On 5/27/17 3:31 PM, Hao Wei Tee wrote:
> This exposes the battery conservation mode present
On 07/07/17 08:26, Ludovic Barre wrote:
> From: Ludovic Barre
>
> -prepare to manage multi-bank
> -prepare to manage registers offset by compatible
>
> Signed-off-by: Ludovic Barre
> ---
> drivers/irqchip/irq-stm32-exti.c | 137
> ++-
> 1 file changed, 91 i
On Fri, Aug 4, 2017 at 4:59 AM, Masahiro Yamada
wrote:
> pinconf_set_config() is called by pinctrl_gpio_set_config().
> If a GPIO driver is backed by a pinctrl driver and it does not
> support .pin_config_set() hook, it causes NULL pointer dereference.
>
> Fixes: 15381bc7c7f5 ("pinctrl: Allow con
Hello.
While searching for races in the Linux kernel I've come across
"drivers/watchdog/pc87413_wdt.ko" module. Here is a question that I came
up with while analyzing results. Lines are given using the info from
Linux v4.12.
Consider the following case:
Thread 1: Th
This is an user visible API so make sure you CC linux-api (added)
On Sun 06-08-17 10:04:23, Rik van Riel wrote:
> v2: fix MAP_SHARED case and kbuild warnings
>
> Introduce MADV_WIPEONFORK semantics, which result in a VMA being
> empty in the child process after fork. This differs from MADV_DONTFO
On 8/3/17 10:47 PM, Keerthy wrote:
66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs
functional. 9 banks with 16 gpios making a total of 144. The second
instance has only the GPIO0:GPIO67 functional and rest are marked
reserved.
Signed-off-by: Keerthy
Acked-by: Linus Walleij
Hi Joel,
On 4 August 2017 at 17:40, Joel Fernandes wrote:
> The PELT signal (sa->load_avg and sa->util_avg) are not updated if the amount
> accumulated during a single update doesn't cross a period boundary. This is
> fine in cases where the amount accrued is much smaller than the size of a
> sin
On Mon, Aug 07, 2017 at 04:09:12PM +0300, Anton Volkov wrote:
> This is more of a style-oriented suggestion. This kind of template is
> commonly used in other modules.
Yes but there is no point in using gotos here (i.e. cleanup to be done), you
an just return directly.
And yes it is a minor nit.
On Sun, Aug 6, 2017 at 4:00 PM, Ludovic Desroches
wrote:
> Update deprecated references to Documentation/pinctrl.txt since it has been
> moved to Documentation/driver-api/pinctl.rst.
>
> Signed-off-by: Ludovic Desroches
> Fixes: 5a9b73832e9e ("pinctrl.txt: move it to the driver-api book")
Patch
Michal Hocko wrote:
> Hi,
> there are two issues this patch series attempts to fix. First one is
> something that has been broken since MMF_UNSTABLE flag introduction
> and I guess we should backport it stable trees (patch 1). The other
> issue has been brought up by Wenwei Tao and Tetsuo Handa has
On Mon, Aug 07, 2017 at 02:26:21PM +0300, Igor Stoppa wrote:
> On 04/08/17 11:12, Michal Hocko wrote:
> > On Fri 04-08-17 11:02:46, Igor Stoppa wrote:
>
> [...]
>
> >> struct page {
> >> /* First double word block */
> >> unsigned long flags; /* Atomic flags, some possibly
> >>
On (08/07/17 08:41), Prarit Bhargava wrote:
[..]
> >> +static int printk_time_set(const char *val, const struct kernel_param *kp)
> >> +{
> >> +char *param = strstrip((char *)val);
> >> +int _printk_time;
> >> +
> >> +if (strlen(param) != 1)
> >> +return -EINVAL;
> > (see below)
301 - 400 of 971 matches
Mail list logo