[PATCH v3 1/2] iio: Implement counter channel type and info constants

Quadrature encoders, such as rotary encoders and linear encoders, are devices which are capable of encoding the relative position and direction of motion of a shaft. This patch introduces several IIO constants for supporting quadrature encoder counter devices. IIO_COUNT: Current count (main

Re: [PATCH] staging: lustre: clean function declarations in class_obd.c up

On Thu, Sep 15, 2016 at 09:51:27PM +0800, Baoyou Xie wrote: > We get 2 warnings when building kernel with W=1: Don't do that! :) > > drivers/staging/lustre/lustre/obdclass/linux/linux-module.c:413:5: warning: > no previous prototype for 'class_procfs_init' [-Wmissing-prototypes] >

Re: [PATCH] staging: rts5208: Comparisons should place the constant on the right side of the test

On Thu, Sep 15, 2016 at 04:29:54PM +0200, Sergio Paracuellos wrote: > Signed-off-by: Sergio Paracuellos > --- > drivers/staging/rts5208/rtsx_card.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/staging/rts5208/rtsx_card.c >

[PATCH v3 2/2] iio: 104-quad-8: Add IIO support for the ACCES 104-QUAD-8

The ACCES 104-QUAD-8 is a general purpose quadrature encoder counter/interface board. The 104-QUAD-8 is capable of monitoring the outputs of eight encoders via four on-board LSI/CSI LS7266R1 24-bit dual-axis quadrature counter chips. Core functions handled by the LS7266R1, such as direction and

[PATCH v5 6/8] iommu/amd: Do not re-enable dev table entries in kdump

This enabling should have been done in normal kernel. It's unnecessary to enable it again in kdump kernel. And clean up the function comments of init_device_table_dma. Signed-off-by: Baoquan He --- drivers/iommu/amd_iommu_init.c | 10 +++--- 1 file changed, 7

[PATCH v5 5/8] iommu/amd: copy old trans table from old kernel

Here several things need be done: 1) If iommu is pre-enabled in a normal kernel, just disable it and print warning. 2) If failed to copy dev table of old kernel, continue to proceed as it does in normal kernel. 3) Re-enable event/cmd buffer and install the new DTE table to reg. 4) Flush all

[PATCH v5 7/8] iommu/amd: Don't update domain info to dte entry at iommu init stage

AMD iommu creates protection domain and assign each device to it during iommu driver initialization stage. This happened just after system pci bus scanning stage, and much earlier than device driver init stage. So at this time if in kdump kernel the domain info, especially pte_root, can't be

[PATCH] selftests: Move networking/timestamping from Documentation

Remove networking from Documentation Makefile to move the test to selftests. Update networking/timestamping Makefile to work under selftests. These tests will not be run as part of selftests suite and will not be included in install targets. They can be built and run separately for now. This is

Re: [RFC PATCH v2 05/11] ACPI: platform: setup MSI domain for ACPI based platform device

On 15/09/16 15:05, Hanjun Guo wrote: > Hi Marc, > > Thanks for your review, reply inline. > > On 09/14/2016 11:45 PM, Marc Zyngier wrote: >> On 14/09/16 15:21, Hanjun Guo wrote: >>> From: Hanjun Guo >>> >>> With the platform msi domain created, we can set up the msi

Re: [Nbd] [RESEND][PATCH 0/5] nbd improvements

Josef, > On 15 Sep 2016, at 14:57, Josef Bacik wrote: > > This isn't an NBD problem, this is an application problem. The application > must wait for all writes it cares about _before_ issuing a flush. This is > the same as for normal storage as it is for NBD. It is not NBD's

Re: [PATCH v3 3/3] ASoC: sun4i-codec: Add custom regmap configs for the A10 and A20 variants.

On Thu, Sep 15, 2016 at 10:39 PM, Danny Milosavljevic wrote: > ASoC: sun4i-codec: Add custom regmap configs for the A10 and A20 variants. The commit message should be a straight forward description about what the patch does and why you did it, not a direct copy of the

Re: [PATCH] kvm: x86: correctly reset dest_map->vector when restoring LAPIC state

2016-09-14 23:48+0200, Paolo Bonzini: > When userspace sends KVM_SET_LAPIC, KVM schedules a check between > the vCPU's IRR and ISR and the IOAPIC redirection table, in order > to re-establish the IOAPIC's dest_map (the list of CPUs servicing > the real-time clock interrupt with the corresponding

Re: [PATCH v2] leds: Introduce userspace leds driver

On 09/15/2016 09:54 AM, Jacek Anaszewski wrote: Hi Pavel, On 09/15/2016 03:01 PM, Pavel Machek wrote: Hi! @@ -0,0 +1,23 @@ +/* + * Userspace driver support for leds subsystem + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU

Re: [Nbd] [RESEND][PATCH 0/5] nbd improvements

Eric, > I doubt that qemu-nbd would ever want to support the situation with more > than one client connection writing to the same image at the same time; > the implications of sorting out data consistency between multiple > writers is rather complex and not worth coding into qemu. So I think >

Re: [RFC PATCH v2 11/11] irqchip: mbigen: promote mbigen init

On 14/09/16 15:21, Hanjun Guo wrote: > From: Hanjun Guo > > mbigen is an irqchip and it needs to be probed before > devices, same logic is used for SMMU and etc., let's > use arch_initcall instead of platform init for mbigen. > > Cc: Marc Zyngier >

Re: [PATCH v3] leds: Introduce userspace leds driver

On 09/15/2016 09:54 AM, Jacek Anaszewski wrote: Hi Pavel, On 09/15/2016 03:08 PM, Pavel Machek wrote: Hi! +if (copy_from_user(>user_dev, buffer, + sizeof(struct uleds_user_dev))) { +ret = -EFAULT; +goto out; +} + +if (!udev->user_dev.name[0]) { +

Re: [PATCH v3 03/15] lockdep: Refactor lookup_chain_cache()

On 13 September 2016 at 04:45, Byungchul Park wrote: > @@ -2215,6 +2178,75 @@ cache_hit: > return 1; > } > > +/* > + * Look up a dependency chain. > + */ > +static inline struct lock_chain *lookup_chain_cache(u64 chain_key) > +{ > + struct hlist_head

Re: [PATCH v2] PM / Domains: Allow holes in genpd_data.domains array

On 15 September 2016 at 14:05, Tomeu Vizoso wrote: > In platforms such as Rockchip's, the array of domains isn't always > filled without holes, as which domains are present depend on the > particular SoC revision. > > By allowing holes to be in the array, such SoCs can

[PATCH] drm/radeon/radeon_device: remove unused function

We get 2 warnings when building kernel with W=1: drivers/gpu/drm/radeon/radeon_device.c:1961:5: warning: no previous prototype for 'radeon_debugfs_init' [-Wmissing-prototypes] drivers/gpu/drm/radeon/radeon_device.c:1966:6: warning: no previous prototype for 'radeon_debugfs_cleanup'

Re: lockdep: incorrect deadlock warning with two GPIO expanders

2016-09-15 15:39 GMT+02:00 Peter Zijlstra : > On Thu, Sep 15, 2016 at 03:20:58PM +0200, Bartosz Golaszewski wrote: >> 2016-09-15 14:41 GMT+02:00 Linus Walleij : >> >> So can't you walk up that and see if you encounter the exact same driver >> >>

Re: [PATCH] [SCSI] wd719x: Avoid calling request_firmware under spinlock

On 15/09/2016 15:08, John Garry wrote: On 15/09/2016 14:48, Vaishali Thakkar wrote: It is preferrable to use request_firmware where sleeping is allowed. Using it under spinlock can cause blocking. Here, the function wd719x_chip_init calls request_firmware while holding a spinlock. So, let's

[PATCH v1 3/3] usb: gadget: NCM: differentiate consumed packets from dropped packets

From: Torsten Polle dev_kfree_skb_any() is used to free packets that are dropped by the network stack. Therefore the function should not be used for packets that have been successfully processed by the network stack. Instead dev_consume_skb_any() has to be used for such

[PATCH V3 0/3] net-next: dsa: add QCA8K support

This series is based on the AR8xxx series posted by Matthieu Olivari in may 2015. The following changes were made since then * fixed the nitpicks from the previous review * updated to latest API * turned it into an mdio device * added callbacks for fdb, bridge offloading, stp, eee, port status *

crypto-caamhash: Fine-tuning for several function implementations

From: Markus Elfring Date: Thu, 15 Sep 2016 16:27:23 +0200 Some update suggestions were taken into account from static source code analysis. Markus Elfring (6): Use kmalloc_array() in ahash_setkey() Rename jump labels in ahash_setkey() Rename a jump label in

Re: Crashing 'kzm' target in next-20160913 due to 'gpio: mxc: shift gpio_mxc_init() to subsys_initcall level'

On 09/15/2016 07:23 AM, Uwe Kleine-König wrote: On Thu, Sep 15, 2016 at 04:35:04PM +0300, Vladimir Zapolskiy wrote: Hi Guenter, On 09/14/2016 06:20 AM, Guenter Roeck wrote: Hi Vladimir, your commit e188cbf7564f ("gpio: mxc: shift gpio_mxc_init() to subsys_initcall level") in -next causes

Re: [PATCH v2 1/3] drivers/of: recognize status property of dt memory nodes

On Thu, Sep 15, 2016 at 08:43:08AM -0500, Rob Herring wrote: On Wed, Sep 14, 2016 at 3:06 PM, Reza Arbab wrote: + status = of_get_flat_dt_prop(node, "status", NULL); + add_memory = !status || !strcmp(status, "okay"); Move this into it's own function to

Re: [PATCH] leds: Introduce userspace leds driver

Hi Pavel, On 09/15/2016 02:41 PM, Pavel Machek wrote: Hi! Thanks for the patch. It is very nice. I have only one minor remark in the code. I think that it would be good to add a documentation for this driver to Documentation/leds, with exemplary C program instead of python one. The program

Re: [tip:x86/vdso] x86/vdso: Only define map_vdso_randomized() if CONFIG_X86_64

On 09/15/2016 01:44 PM, tip-bot for Ingo Molnar wrote: Commit-ID: 3947f49302e4d1576ee58addd8d20b477faef5ea Gitweb: http://git.kernel.org/tip/3947f49302e4d1576ee58addd8d20b477faef5ea Author: Ingo Molnar AuthorDate: Thu, 15 Sep 2016 08:56:21 +0200 Committer: Ingo

[GIT PULL] Block fixes for 4.8-rc

Hi Linus, A set of fixes for the current series in the realm of block. Like the previous pull request, the meat of it are fixes for the nvme fabrics/target code. Outside of that, just one fix from Gabriel for not doing a queue suspend if we didn't get the admin queue setup in the first place.

Re: [PATCH V5] leds: trigger: Introduce a USB port trigger

On 09/15/2016 03:33 PM, Rafał Miłecki wrote: On 15 September 2016 at 14:56, Pavel Machek wrote: On Fri 2016-09-09 13:31:10, Rafał Miłecki wrote: On 9 September 2016 at 13:05, Greg KH wrote: On Fri, Sep 09, 2016 at 05:34:40PM +0800, Peter Chen wrote:

Re: [PATCH v3] leds: Introduce userspace leds driver

Hi Pavel, On 09/15/2016 03:35 PM, Pavel Machek wrote: Hi! + if (copy_from_user(>user_dev, buffer, + sizeof(struct uleds_user_dev))) { + ret = -EFAULT; + goto out; + } + + if (!udev->user_dev.name[0]) { + ret

Re: [PATCH v2] leds: Introduce userspace leds driver

Hi Pavel, On 09/15/2016 03:01 PM, Pavel Machek wrote: Hi! @@ -0,0 +1,23 @@ +/* + * Userspace driver support for leds subsystem + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License as published by + * the Free

Re: [PATCH v3] leds: Introduce userspace leds driver

Hi Pavel, On 09/15/2016 03:08 PM, Pavel Machek wrote: Hi! + if (copy_from_user(>user_dev, buffer, + sizeof(struct uleds_user_dev))) { + ret = -EFAULT; + goto out; + } + + if (!udev->user_dev.name[0]) { + ret

Re: [PATCH V3 1/3] Documentation: devicetree: add qca8k binding

B1;2802;0cOn Thu, Sep 15, 2016 at 04:26:39PM +0200, John Crispin wrote: > Add device-tree binding for ar8xxx switch families. > > Cc: devicet...@vger.kernel.org > Signed-off-by: John Crispin Reviewed-by: Andrew Lunn Andrew

[PATCH v5 0/8] Fix kdump faults on system with amd iommu

This is v5 post. In fact in v3 the solution is correct. Just unluckily I got a AMD machine with bnx2 NIC which can't reset itself during driver init. It made me very unconfident with my understanding about the fix. Now with below fix the AMD machine with bnx2 NIC can also work well to dump and

Re: [PATCH v2 6/8] ARM: dts: sun9i: a80-optimus: Add AXP806 PMIC device node and regulators

On Thu, Sep 15, 2016 at 10:33:50PM +0800, Chen-Yu Tsai wrote: > Hi Maxime, > > On Sat, Aug 27, 2016 at 3:55 PM, Chen-Yu Tsai wrote: > > The AXP806 PMIC is the secondary PMIC. It provides various supply > > voltages for the SoC and other peripherals. The PMIC's interrupt > > line

[PATCH v5 3/8] iommu/amd: Define bit fields for DTE particularly

In amd-vi spec several bits of IO PTE fields and DTE fields are similar so that both of them can share the same MACRO definition. However defining their respecitve bit fields can make code more read-able. So do it in this patch. Signed-off-by: Baoquan He ---

[PATCH 2/4] drm/sun4i: dotclock: Fix clock rate read back calcation

When reading back the divider set in the register, we mask off the bits that aren't part of the divider. Unfortunately the mask used here was not converted from the field width. Fix this by converting the field width to a proper bit mask. Fixes: 9026e0d122ac ("drm: Add Allwinner A10 Display

[PATCH 0/4] drm/sun4i: rgb and dotclock misc fixes and improvements

Hi Maxime, Here are a few small fixes and improvements to the sun4i drm driver. Patch 1 declares the LCD panel RGB interface encoder and connector types as MIPI DPI. AFAIK DPI is the parallel RGB variant. Patch 2 fixes the weird clock rates I was getting on the dot clock when testing the

[PATCH 4/4] drm/sun4i: dotclock: Round to closest clock rate

With display pixel clocks we want to have the closest possible clock rate, to minimize timing and refresh rate skews. Whether the actual clock rate is higher or lower than the requested rate is less important. Also check candidates against the requested rate, rather than the ideal parent rate,

Re: [PATCH 4/7 v3] sched: propagate load during synchronous attach/detach

On Thu, Sep 15, 2016 at 02:11:49PM +0100, Dietmar Eggemann wrote: > On 12/09/16 08:47, Vincent Guittot wrote: > > +/* Take into account change of load of a child task group */ > > +static inline void > > +update_tg_cfs_load(struct cfs_rq *cfs_rq, struct sched_entity *se) > > +{ > > + struct

[PATCH 1/4] drm/sun4i: rgb: Declare RGB encoder and connector as MIPI DPI

The 18 or 24 bit parallel RGB LCD panel interface found on Allwinner SoCs matches the description of MIPI DPI. Declare the RGB encoder and connector as MIPI DPI. Signed-off-by: Chen-Yu Tsai --- drivers/gpu/drm/sun4i/sun4i_rgb.c | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [patch] leds: add driver for Mellanox systems leds

Hi Pavel, On 09/15/2016 02:52 PM, Pavel Machek wrote: Hi! +++ b/MAINTAINERS @@ -7655,6 +7655,14 @@ W: http://www.mellanox.com Q: http://patchwork.ozlabs.org/project/netdev/list/ F: drivers/net/ethernet/mellanox/mlxsw/ +MELLANOX MLXCPLD LED DRIVER +M: Vadim Pasternak

Re: Crashing 'kzm' target in next-20160913 due to 'gpio: mxc: shift gpio_mxc_init() to subsys_initcall level'

On Thu, Sep 15, 2016 at 04:35:04PM +0300, Vladimir Zapolskiy wrote: > Hi Guenter, > > On 09/14/2016 06:20 AM, Guenter Roeck wrote: > > Hi Vladimir, > > > > your commit e188cbf7564f ("gpio: mxc: shift gpio_mxc_init() to > > subsys_initcall level") > > in -next causes the following crash when

[PATCH v1 0/3] Usb gadget ncm code cleanup

This patchset consists of some code cleanup in usb gadget ncm code. Note: Testing has only been done on an ARM i.MX6 based platform. Torsten Polle (3): usb: gadget: NCM: link socket buffers to the device for tx packets usb: gadget: NCM: link socket buffers to the device for received

[PATCH v1 1/3] usb: gadget: NCM: link socket buffers to the device for tx packets

From: Torsten Polle Socket buffers should be linked to the (network) device that allocated the buffers. Signed-off-by: Torsten Polle Signed-off-by: Harish Jenny K N --- drivers/usb/gadget/function/f_ncm.c |3 +++ 1

Re: lockdep: incorrect deadlock warning with two GPIO expanders

On Thu, Sep 15, 2016 at 04:08:52PM +0200, Bartosz Golaszewski wrote: > 2016-09-15 15:39 GMT+02:00 Peter Zijlstra : > > In any case, if this fails, we can always punt and simply count the > > total number of instances of this driver on the system and go with that. > > > >

[PATCH 4/6] crypto-caamhash: Return a value directly in caam_hash_cra_init()

From: Markus Elfring Date: Thu, 15 Sep 2016 14:56:12 +0200 * Return a value at the end without storing it in an intermediate variable. * Delete the local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring

[PATCH][V2] nbd: add multi-connection support

NBD can become contended on its single connection. We have to serialize all writes and we can only process one read response at a time. Fix this by allowing userspace to provide multiple connections to a single nbd device. This coupled with block-mq drastically increases performance in

Re: [RFC 0/4] mm, oom: get rid of TIF_MEMDIE

Hi Michal, On Thu, Sep 01, 2016 at 11:51:00AM +0200, Michal Hocko wrote: > Hi, > this is an early RFC to see whether the approach I've taken is acceptable. > The series is on top of the current mmotm tree (2016-08-31-16-06). I didn't > get to test it so it might be completely broken. > > The

[PATCH 5/6] crypto-caamhash: Delete an unnecessary initialisation in seven functions

From: Markus Elfring Date: Thu, 15 Sep 2016 15:24:02 +0200 The local variable "ret" will be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 6/6] crypto-caamhash: Move common error handling code in two functions

From: Markus Elfring Date: Thu, 15 Sep 2016 16:00:55 +0200 Move statements for error handling which were identical in two if branches to the end of these functions. Signed-off-by: Markus Elfring --- drivers/crypto/caam/caamhash.c |

Re: [PATCH v2 1/5] drm/amdgpu: squash lines for simple wrapper functions

On Wed, Sep 14, 2016 at 10:39 AM, Masahiro Yamada wrote: > Remove unneeded variables and assignments. > > Signed-off-by: Masahiro Yamada Applied to drm-misc Sean > --- > > drivers/gpu/drm/amd/amdgpu/dce_virtual.c | 6 +- >

Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1

On Wed, Sep 14, 2016 at 12:09:49PM +0200, Greg KH wrote: > I'll send out a follow-up set of "simple" patches that just add the > files to the kernel tree, to give people an idea of the code involved. > Overall, it's a tiny stand-alone driver subsystem, only 37k lines, that > implements a protocol

Re: [PATCH v2 2/5] drm/radeon: squash lines for simple wrapper functions

On Wed, Sep 14, 2016 at 10:39 AM, Masahiro Yamada wrote: > Remove unneeded variables and assignments. > > Signed-off-by: Masahiro Yamada Applied to drm-misc Sean > --- > > drivers/gpu/drm/radeon/cik.c | 6 +- >

Re: blk-mq: allow passing in an external queue mapping V3

On 09/15/2016 08:42 AM, Christoph Hellwig wrote: On Thu, Sep 15, 2016 at 08:34:42AM -0600, Jens Axboe wrote: I was going to ask about splitting it, but that looks fine, I can pull that in. The series looks fine to me. My only real concern is giving drivers the flexibility to define mappings, I

Re: [PATCH v2 4/5] drm/qxl: squash lines for simple wrapper functions

On Thu, Sep 15, 2016 at 9:47 AM, Gustavo Padovan wrote: > 2016-09-14 Masahiro Yamada : > >> Remove unneeded variables and assignments. >> >> Signed-off-by: Masahiro Yamada >> --- >> >>

Re: [PATCH 4/7 v3] sched: propagate load during synchronous attach/detach

On Mon, Sep 12, 2016 at 09:47:49AM +0200, Vincent Guittot wrote: > +static inline void > +update_tg_cfs_load(struct cfs_rq *cfs_rq, struct sched_entity *se) > +{ > + struct cfs_rq *gcfs_rq = group_cfs_rq(se); > + long delta, load = gcfs_rq->avg.load_avg; > + > + /* If the load of group

Re: [PATCH 13/13] blk-mq: get rid of the cpumask in struct blk_mq_tags

> +static int blk_mq_create_mq_map(struct blk_mq_tag_set *set, > + const struct cpumask *affinity_mask) > { > + int queue = -1, cpu = 0; > + > + set->mq_map = kzalloc_node(sizeof(*set->mq_map) * nr_cpu_ids, > + GFP_KERNEL, set->numa_node); > + if

Re: [PATCH v5 0/5] dts: sun8i-h3: complete UART I2C for H3

On Mon, Sep 12, 2016 at 08:12:42PM +0200, jo...@kippendief.biz wrote: > From: Jorik Jonker > > This is my fifth attempt to complete the UART/I2C definitions on H3. > > Many thanks to Maxime and Chen-Yu for helping me understand the > philosophy behind the DTS/DTSI

pull-request: wireless-drivers-next 2016-09-15

Hi Dave, here's the first pull request for 4.9. The ones I want to point out are the FIELD_PREP() and FIELD_GET() macros added to bitfield.h, which are reviewed by Linus, and make it possible to remove util.h from mt7601u. Also we have new HW support to various drivers and other smaller

Re: [PATCH 2/2] x86, kvm: use kvmclock to compute TSC deadline value

2016-09-07 00:29+0200, Paolo Bonzini: > Bad things happen if a guest using the TSC deadline timer is migrated. > The guest doesn't re-calibrate the TSC after migration, and the > TSC frequency can and will change unless your processor supports TSC > scaling (on Intel this is only Skylake) or your

[PATCH v5 1/8] iommu/amd: Detect pre enabled translation

Add functions to check whether translation is already enabled in IOMMU. Signed-off-by: Baoquan He --- drivers/iommu/amd_iommu_init.c | 25 + drivers/iommu/amd_iommu_proto.h | 1 + drivers/iommu/amd_iommu_types.h | 4 3 files changed, 30

[PATCH 2/2] x86/tsc: Add additional Intel CPU models to crystal_khz whitelist

In commit aa297292d708 ("x86/tsc: Enumerate SKL cpu_khz and tsc_khz via CPUID"), the kernel added support for Intel processors which had a different CPU base-frequency and TSC frequency. The turbostat utility has been updated with KBL and SKX processors, and they should also be added to the

Re: [PATCH] drm/sti: mark symbols static where possible

Acked-by: Vincent Abriou On 09/15/2016 01:39 PM, Baoyou Xie wrote: > We get 4 warnings when building kernel with W=1: > drivers/gpu/drm/sti/sti_gdp.c:476:5: warning: no previous prototype for > 'sti_gdp_field_cb' [-Wmissing-prototypes] >

Re: [PATCH 2/2] x86/tsc: Add additional Intel CPU models to crystal_khz whitelist

On Thu, Sep 15, 2016 at 11:04:18AM -0400, Prarit Bhargava wrote: > +++ b/arch/x86/kernel/tsc.c > @@ -689,11 +689,18 @@ unsigned long native_calibrate_tsc(void) > switch (boot_cpu_data.x86_model) { > case INTEL_FAM6_SKYLAKE_MOBILE: > case

[PATCH] usb: gadget: udc: atmel: fix endpoint name

Since commit c32b5bcfa3c4 ("ARM: dts: at91: Fix USB endpoint nodes"), atmel_usba_udc fails with: [ cut here ] WARNING: CPU: 0 PID: 0 at include/linux/usb/gadget.h:405 ecm_do_notify+0x188/0x1a0 Modules linked in: CPU: 0 PID: 0 Comm: swapper Not tainted 4.7.0+ #15 Hardware

Re: [PATCH v3 2/3] ASoC: rename "SUN4I_CODEC_SYS_VERI" to "SUN7I_CODEC_AC_DAC_CAL"; rename "SUN4I_CODEC_AC_MIC_PHONE_CAL" to "SUN7I_CODEC_AC_MIC_PHONE_CAL".

On Thu, Sep 15, 2016 at 10:39 PM, Danny Milosavljevic wrote: > This patch renames some sun7i-only registers to reflect that fact. The subject line is way longer than it should be. Perhaps you could use the above message as the description part of the subject? ChenYu > >

Re: Hibernation broken since commit 274ad65c9d02 ("drm/radeon: hard reset r600 and newer GPU when hibernating.")

> On Mon, Sep 5, 2016 at 10:25 PM, Jerome Glisse wrote: > >> Recently I got myself a new laptop with the following integrated GPU: > >> > >> 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > >> Mullins [Radeon R3 Graphics] (rev 40) > >> > >> I found

Re: [PATCH 2/2] mfd: wm8994-core: Don't use managed regulator bulk get API

On 15-09-16, 15:47, Mark Brown wrote: > On Thu, Sep 15, 2016 at 04:47:01PM +0530, Viresh Kumar wrote: > > > Fix the kernel warnings and crashes by moving away from managed > > regulator bulk get API by using regulator_bulk_get() and explicitly > > calling regulator_put() for all the supplies in

[PATCH v3] mtd: introduce the mtd_pairing_scheme concept

MLC and TLC NAND devices are using NAND cells exposing more than one bit, but instead of attaching all the bits in a given cell to a single NAND page, each bit is usually attached to a different page. This concept is called 'page pairing', and has significant impacts on the flash storage usage.

[PATCH v5 2/8] iommu/amd: add early_enable_iommu() wrapper function

Move per iommu enabling code into a wrapper function early_enable_iommu(). This can make later kdump change easier. Signed-off-by: Baoquan He --- drivers/iommu/amd_iommu_init.c | 24 ++-- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git

Re: [PATCH] dmaengine: DW DMAC: split pdata to hardware properties and platform quirks

Hi Eugeniy, [auto build test ERROR on slave-dma/next] [also build test ERROR on next-20160915] [cannot apply to linus/master linux/master v4.8-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --b

[PATCH v1 3/3] perf/x86/intel/pt: Do validate the size of a kernel address filter

Right now, the kernel address filters in PT are prone to integer overflow that may happen in adding filter's size to its offset to obtain the end of the range. Such an overflow would also throw a #GP in the PT event configuration path. Fix this by explicitly validating the result of this

[PATCH v1 1/3] perf/x86/intel/pt: Fix an off-by-one in address filter configuration

PT address filter configuration requires that a range is specified by its first and last address, but at the moment we're obtaining the end of the range by adding user specified size to its start, which is off by one from what it actually needs to be. Fix this and make sure that zero-sized

RE: [PATCH -next] staging: fsl-mc: use list_del_init instead of list_del/INIT_LIST_HEAD

> -Original Message- > From: Wei Yongjun [mailto:weiyj...@gmail.com] > Sent: Wednesday, September 14, 2016 9:27 PM > To: J . German Rivera ; Stuart Yoder > ; Greg Kroah- > Hartman ; German Rivera

Re: [PATCH 4/7 v3] sched: propagate load during synchronous attach/detach

On 15/09/16 15:31, Vincent Guittot wrote: > On 15 September 2016 at 15:11, Dietmar Eggemann > wrote: [...] >> Wasn't 'consuming <1' related to 'NICE_0_LOAD' and not >> scale_load_down(gcfs_rq->tg->shares) before the rewrite of PELT (v4.2, >>

[GIT PULL rcu/next] RCU commits for 4.9

Hello, Ingo, This series contains the following changes: 1. Documentation updates, again just some simple changes. Yes, I am getting behind on design-level updates. :-/ http://lkml.kernel.org/g/20160822151413.ga6...@linux.vnet.ibm.com 2. Expedited grace-period

[PATCH V3 04/10] dmaengine: qcom_hidma: configure DMA and MSI for OF

Configure the DMA bindings for the device tree based firmware. Signed-off-by: Sinan Kaya --- drivers/dma/qcom/hidma_mgmt.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/dma/qcom/hidma_mgmt.c b/drivers/dma/qcom/hidma_mgmt.c index

[PATCH V3 08/10] dmaengine: qcom_hidma: add a common API to setup the interrupt

Introducing the hidma_ll_setup_irq function to set up the interrupt type externally from the OS interface. Signed-off-by: Sinan Kaya --- drivers/dma/qcom/hidma.h| 2 ++ drivers/dma/qcom/hidma_ll.c | 27 +++ 2 files changed, 25 insertions(+), 4

[PATCH V3 07/10] dmaengine: qcom_hidma: bring out interrupt cause

Bring out the interrupt cause to the top level so that MSI interrupts can be hooked at a later stage. Signed-off-by: Sinan Kaya --- drivers/dma/qcom/hidma_ll.c | 72 + 1 file changed, 34 insertions(+), 38 deletions(-) diff --git

[PATCH V3 02/10] Documentation: DT: qcom_hidma: correct spelling mistakes

Fix the spelling mistakes and extra and statements in the sentences. Acked-by: Rob Herring Signed-off-by: Sinan Kaya --- Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH V3 05/10] dmaengine: qcom_hidma: make pending_tre_count atomic

Getting ready for the MSI interrupts. The pending_tre_count is used in the interrupt handler to make sure all outstanding requests are serviced. Making it atomic so that it can be updated from multiple contexts. Signed-off-by: Sinan Kaya --- drivers/dma/qcom/hidma.h |

[PATCH V3 01/10] Documentation: DT: qcom_hidma: update binding for MSI

Adding a new binding for qcom,hidma-1.1 to distinguish HW supporting MSI interrupts from the older revision. Signed-off-by: Sinan Kaya --- Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff

Re: [PATCH v3 15/15] lockdep: Crossrelease feature documentation

On 13 September 2016 at 04:45, Byungchul Park wrote: > This document describes the concept of crossrelease feature, which > generalizes what causes a deadlock and how can detect a deadlock. > > Signed-off-by: Byungchul Park > --- >

Re: [PATCH 2/2] x86/tsc: Add additional Intel CPU models to crystal_khz whitelist

On Thu, Sep 15, 2016 at 04:08:36PM +, Brown, Len wrote: > > + crystal_khz = 24000;/* 25.0 MHz */ > > I guess I prefer no comment over an incorrect comment. > >From this I take it it should really have been 24 MHz and it could have joined the existing case. I assumed

Re: [PATCH v3) posix-timers: make it configurable

On Wed, Sep 14, 2016 at 8:47 PM, Nicolas Pitre wrote: > Many embedded systems typically don't need them. This removes about > 22KB from the kernel binary size on ARM when configured out. > > Corresponding syscalls are routed to a stub logging the attempt to > use those

Re: [PATCH v3) posix-timers: make it configurable

On Thu, 15 Sep 2016, John Stultz wrote: > On Wed, Sep 14, 2016 at 8:47 PM, Nicolas Pitre > wrote: > > Many embedded systems typically don't need them. This removes about > > 22KB from the kernel binary size on ARM when configured out. > > > > Corresponding syscalls

Re: [PATCH v4 4/4] regulator: Prevent falling too fast

Hi Mark, El Thu, Sep 15, 2016 at 03:39:45PM +0100 Mark Brown ha dit: > On Tue, Sep 13, 2016 at 10:21:40AM -0700, Matthias Kaehlcke wrote: > > > Optimizing the delay time depends on the SoC; we have not measured > > this across a wide variety of devices and thus have very conservative > >

Re: rcu_sched self-detected stall on CPU

Sorry!! Alec Ari On Thu, Sep 15, 2016 at 1:22 AM, Mike Galbraith wrote: > On Wed, 2016-09-14 at 23:02 -0500, NTU wrote: >> [ 26.542980] Call Trace: >> [ 26.542983] [] ? 0xa7fbd7c1 >> [ 26.542985] [] ? 0xa7f17d35 >> [ 26.542986] [] ?

Re: [PATCH] staging: rts5208: Comparisons should place the constant on the right side of the test

That's true. It seems that checkpatch script is getting a false positive. Just trying to do checkpatch happy. Sorry for inconvenience. I'll be careful with Changelog stuff from now. Thanks for advice. Cheers, Sergio Paracuellos El 2016年09月15日 a las 16:51, Greg KH escribió: On Thu,

[PATCH V3 09/10] dmaengine: qcom_hidma: protect common data structures

When MSI interrupts are supported, error and the transfer interrupt can come from multiple processor contexts. Each error interrupt is an MSI interrupt. If the channel is disabled by the first error interrupt, the remaining error interrupts will gracefully return in the interrupt handler. If an

[PATCH V3 03/10] of: irq: make of_msi_configure accessible from modules

The of_msi_configure routine is only accessible by the built-in kernel drivers. Export this function so that modules can use it too. This function is useful for configuring MSI on child device tree nodes on hierarchical objects. Acked-by: Rob Herring Signed-off-by: Sinan Kaya

[PATCH V3 10/10] dmaengine: qcom_hidma: add MSI support for interrupts

The interrupts can now be delivered as platform MSI interrupts on newer platforms. The code looks for a new OF and ACPI strings in order to enable the functionality. Signed-off-by: Sinan Kaya --- drivers/dma/qcom/hidma.c| 129

[PATCH V3 06/10] dmaengine: qcom_hidma: make error and success path common

Remove code duplication by feeding the error code from outside into successful data transfer handler. Signed-off-by: Sinan Kaya --- drivers/dma/qcom/hidma_ll.c | 34 ++ 1 file changed, 10 insertions(+), 24 deletions(-) diff --git

Re: [PATCH v2 07/19] remoteproc: Add new resource type for resource table spare bytes

On Wed 31 Aug 13:50 PDT 2016, Loic Pallardy wrote: > To allow resource appending to an existing resource table, > remoteproc framework should get information about resource > table spare area. With current resource table construction, > remoteproc is not able to identify by itself any free

Re: [PATCH 4/7 v3] sched: propagate load during synchronous attach/detach

On Thu, Sep 15, 2016 at 06:36:53PM +0100, Dietmar Eggemann wrote: > > We did however loose a lot on why and how min(1, runnable_avg) is a > > sensible thing to do... > > Do you refer to the big comment on top of this if condition in the old > code in __update_group_entity_contrib()? The last two

[PATCH 1/1] rapidio/rio_cm: avoid GFP_KERNEL in atomic context

As reported by Alexey Khoroshilov (see https://lkml.org/lkml/2016/9/9/737): riocm_send_close() is called from rio_cm_shutdown() under spin_lock_bh(idr_lock), but riocm_send_close() uses a GFP_KERNEL allocation. Fix by taking riocm_send_close() outside of spinlock protected

Re: [PATCH 4/4] input: serio: Replace timeval by timespec64

On Tue, Sep 13, 2016 at 8:13 AM, Arnd Bergmann wrote: > On Tuesday, September 13, 2016 7:10:05 AM CEST Deepa Dinamani wrote: >> struct timeval is not y2038 safe. >> All references to timeval will be deleted from the >> kernel to make it y2038 safe. >> Replace its uses by y2038 safe

Re: [PATCH v2 3/3] remoteproc: core: add rproc ops for memory allocation

On Tue 06 Sep 00:39 PDT 2016, Loic Pallardy wrote: > Remoteproc core is currently using dma_alloc_coherent for > carveout and vring allocation. > It doesn't allow to support specific use cases like fixed memory > region or internal RAM support. > > Two new rproc ops (alloc and free) is added to

<    1   2   3   4   5   6   7   8   9   10   >