[PATCH v9 0/7] usb: add support for Intel dual role port mux

Intel SOC chips are featured with USB dual role. The host role is provided by Intel xHCI IP, and the gadget role is provided by IP from designware. Tablet platform designs always share a single port for both host and gadget controllers. There is a mux to switch the port to the right controller

[PATCH v9 2/7] usb: mux: add generic code for dual role port mux

Several Intel platforms implement USB dual role by having completely separate xHCI and dwc3 IPs in PCH or SOC silicons. These two IPs share a single USB port. There is another external port mux which controls where the data lines should go. While the USB controllers are part of the silicon, the

[PATCH v9 4/7] usb: mux: add driver for Intel drcfg controlled port mux

Several Intel PCHs and SOCs have an internal mux that is used to share one USB port between device controller and host controller. The mux is handled through the Dual Role Configuration Register. Signed-off-by: Heikki Krogerus Signed-off-by: Lu Baolu

Re: [PATCH] autofs: don't stuck in a loop if vfs_write returns an error

On Tue, 2016-05-24 at 09:34 +0800, Ian Kent wrote: > On Mon, 2016-05-23 at 14:50 -0700, Andrei Vagin wrote: > > Hi Ian, > > > > When are you going to apply this patch? We can't test linux-next without it. > > I though I sent this with the last series but I can't see that I have. > > I have the

[PATCH v9 6/7] usb: pci-quirks: add Intel USB drcfg mux device

In some Intel platforms, a single usb port is shared between USB host and device controllers. The shared port is under control of a switch which is defined in the Intel vendor defined extended capability for xHCI. This patch adds the support to detect and create the platform device for the port

[PATCH v9 5/7] mfd: intel_vuport: Add Intel virtual USB port MFD Driver

Some Intel platforms have an USB port mux controlled by GPIOs. There's a single ACPI platform device that provides 1) USB ID extcon device; 2) USB vbus regulator device; and 3) USB port switch device. This MFD driver will split these 3 devices for their respective drivers. [baolu: removed .owner

[PATCH v9 7/7] MAINTAINERS: add maintainer entry for Intel USB dual role mux drivers

Add a maintainer entry for Intel USB dual role mux drivers and add myself as a maintainer. Signed-off-by: Lu Baolu --- MAINTAINERS | 10 ++ 1 file changed, 10 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index ed1229e..edaeebe 100644 --- a/MAINTAINERS

[PATCH v9 3/7] usb: mux: add driver for Intel gpio controlled port mux

In some Intel platforms, a single usb port is shared between USB host and device controller. The shared port is under control of GPIO pins. This patch adds the support for USB GPIO controlled port mux. [baolu: removed .owner per platform_no_drv_owner.cocci] [baolu: extcon usage reviewed by

[PATCH v9 1/7] regulator: fixed: add support for ACPI interface

Add support to retrieve fixed voltage configure information through ACPI interface. This is needed for Intel Bay Trail devices, where a GPIO is used to control the USB vbus. Signed-off-by: Lu Baolu --- drivers/regulator/fixed.c | 46

Re: [PATCH] block: correctly fallback for zeroout

On Thu, May 26, 2016 at 11:08:14AM -0700, Shaohua Li wrote: > -int blkdev_issue_discard(struct block_device *bdev, sector_t sector, > - sector_t nr_sects, gfp_t gfp_mask, unsigned long flags) > +static int do_blkdev_issue_discard(struct block_device *bdev, sector_t > sector, We've

[PATCH 0/3] mmc: sunxi: Fix MMC DDR modes for Allwinner A80

Hi everyone, This series fixes and re-enables eMMC HS-DDR support for Allwinner A80 SoC. The issue with the original code was the mmc clock timings were incorrect, and thus we had disabled HS-DDR on A80 for the previous release. Patch 1 is a fix for mmc core. Arnd's patch to remove IS_ERR_VALUE

[PATCH 2/3] mmc: sunxi: Fix DDR MMC timings for A80

The MMC clock timings were incorrectly calculated, when the conversion from delay value to delay phase was done. The 50M DDR and 50M DDR 8bit timings are off, and make eMMC DDR unusable. Unfortunately it seems different controllers on the same SoC have different timings. The new settings are

[PATCH 3/3] mmc: sunxi: Re-enable eMMC HS-DDR modes on Allwinner A80

Now the the HS-DDR mode clock timings have been corrected, we can re-enable these modes on the A80. Signed-off-by: Chen-Yu Tsai --- drivers/mmc/host/sunxi-mmc.c | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/mmc/host/sunxi-mmc.c b/drivers/mmc/host/sunxi-mmc.c

Re: [4.1.x -- 4.6.x and probably HEAD] Reproducible unprivileged panic/TLB BUG on sparc via a stack-protected rt_sigaction() ka_restorer, courtesy of the glibc testsuite

From: Nick Alcock Date: Fri, 27 May 2016 14:19:27 +0100 > The only difference between the two series above is that in the crashing > series, the ka_restorer stub functions __rt_sigreturn_stub and > __sigreturn_stub (on sparc32) and __rt_sigreturn_stub (on sparc64) get >

[PATCH 1/3] mmc: fix mmc mode selection for HS-DDR and higher

When IS_ERR_VALUE was removed from the mmc core code, it was replaced with a simple not-zero check. This does not work, as the value checked is the return value for mmc_select_bus_width, which returns the set bit width on success. This made eMMC modes higher than HS-DDR unusable. Fix this by

[PATCH v6] input: tablet: add Pegasus Notetaker tablet driver

This adds a driver for the Pegasus Notetaker Pen. When connected, this uses the Pen as an input tablet. This device was sold in various different brandings, for example "Pegasus Mobile Notetaker M210", "Genie e-note The Notetaker", "Staedtler Digital ballpoint pen 990 01",

Re: [RFC PATCH v2] tools: iio: Rename generic_buffer to iio_generic_buffer

On 24/05/16 16:03, Daniel Baluta wrote: > This makes it clear that generic_buffer is an IIO tool > and also complies with filename conventions in tools/iio. > > Signed-off-by: Daniel Baluta Pretty uncontroversial bit of common sense to my mind ;) Applied to the togreg

Re: tty/vt/keyboard: out of bounds access in do_compute_shiftstate

Hi! (Vojtech added to cc list. This is history.) > I've hit the following while fuzzing with syzkaller inside a KVM tools guest > running the latest -next kernel: What does syzkaller do? Random syscalls? > [ 2662.777566] BUG: KASAN: global-out-of-bounds in >

Re: [PATCH] iio: magnetometer: bmc150: Document Bosch supported chips

On 24/05/16 13:42, Daniel Baluta wrote: > bmc150 driver supports also BMC156 and BMM150 chips. > > Signed-off-by: Daniel Baluta Good to clean this sort of thing up. Applied, thanks. Jonathan > --- > drivers/iio/magnetometer/Kconfig | 2 ++ > 1 file changed, 2

Re: [PATCH 2/2] test/hash: Fix warning in preprocessor symbol evaluation

> But here's an alternative. Geert, what do you think of this? Never mind; that doesn't work. Plain gcc-4.9 passes, it, but it's the "-Wundef" flag that the kernel uses that triggers it. So we're back to Geert's original suggestion. Acked-by: George Spelvin ==>$

Re: [PATCH 4/7] x86/dumpstack: If addr_limit is non-default, display it

On May 29, 2016 11:42 AM, "Boris Petkov" wrote: > > Andy Lutomirski wrote: > >Easier said than done. struct thread_info doesn't have addr_limit on > >sensible architectures (e.g. sparc), and I'd rather not stick a bunch > >of ifdefs in generic code. > > It's

Re: [PATCH 1/2] iio: generic_buffer: Cleanup when receiving signals

On 23/05/16 17:10, Crestez Dan Leonard wrote: > On 05/21/2016 07:28 PM, Jonathan Cameron wrote: >> On 20/05/16 16:55, Peter Meerwald-Stadler wrote: >>> This also drops all the code freeing string buffers at the end of main. Memory is freed when the process exits anyway so there's no

[[DEBUG] force CONFIG_DEBUG_UACCESS] 8829c7a53e: BUG: tried to access memory at 0x7f962a0f while not in USER_DS

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/uaccess commit 8829c7a53e1b4e44f6c24c6d165cf9d1cf8b1f14 ("[DEBUG] force CONFIG_DEBUG_UACCESS") on test machine: vm-lkp-wsx03-yocto-i386: 1 threads qemu-system-i386 -enable-kvm with 320M

Re: [PATCH v2 1/2] iio: generic_buffer: Cleanup when receiving signals

On 29/05/16 20:14, Jonathan Cameron wrote: > On 23/05/16 17:07, Crestez Dan Leonard wrote: >> This will clean (disable buffer/trigger/channels) when doing >> something like a CTRL-C. Otherwise restarting generic_buffer requires a >> manual echo 0 > buffer/enable >> >> This also cleanup up all the

Re: [PATCH v2 1/2] iio: generic_buffer: Cleanup when receiving signals

On 23/05/16 17:07, Crestez Dan Leonard wrote: > This will clean (disable buffer/trigger/channels) when doing > something like a CTRL-C. Otherwise restarting generic_buffer requires a > manual echo 0 > buffer/enable > > This also cleanup up all the code freeing string buffers at > the end of main.

Re: [PATCH v2 2/2] iio: generic_buffer: Add --device-num option

On 23/05/16 17:07, Crestez Dan Leonard wrote: > This makes it possible to distinguish between iio devices with the same > name. > > Signed-off-by: Crestez Dan Leonard I'm a cheapskate and never had more than one of a given part ;) Hence clearly never thought this

Re: [Revert "ppdev] 1701f68040: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)

On Sun, May 29, 2016 at 09:25:28AM -0700, Linus Torvalds wrote: > On Sun, May 29, 2016 at 8:28 AM, kernel test robot > wrote: > > > > 0day kernel testing robot got the below dmesg and the first bad commit is > > This bisection seems unlikely. > > I *think* what is going

Re: [PATCH 1/3] iio: st_sensors: Init trigger before irq request

On 24/05/16 22:54, Linus Walleij wrote: > On Tue, May 24, 2016 at 2:33 PM, Crestez Dan Leonard > wrote: >> [Me] >>> However I think my patch fixing the thread issue will collide >>> by being close in context to this so it'd be great if you >>> could resend it on top of

Re: [PATCH 2/3] iio: st_sensors: Disable DRDY at init time

On 24/05/16 12:28, Linus Walleij wrote: > On Fri, May 13, 2016 at 8:43 PM, Crestez Dan Leonard > wrote: > >> This fixes odd behavior after reboot. >> >> The fact that we set the device to powerdown mode is not sufficient to >> prevent DRDY being active because we might

Re: [PATCH] dell-smm-hwmon: Cache fan_type() calls and use fan_status() for fan detection

I have just tested removing i8k_get_fan_type() function from the dell-smm-hwmon driver in the kernel on my Dell Inspiron 580 and the fan speed problem goes away. My patch simply replaced fan_type with fan_status in i8k_init_hwmon and used the index as the type in i8k_hwmon_show_fan_label

Re: [PATCH 3/3] iio: st_sensors: Use level interrupts

On 24/05/16 13:35, Crestez Dan Leonard wrote: > On 05/24/2016 02:40 PM, Linus Walleij wrote: >> On Fri, May 13, 2016 at 8:43 PM, Crestez Dan Leonard >> wrote: >> >>> As far as I can tell DRDY for ST sensors behaves as a level rather than >>> edge interrupt. Registering

Re: [PATCHv3 1/7] iio: generic_buffer: Cleanup when receiving signals

On 23/05/16 19:39, Crestez Dan Leonard wrote: > This will clean (disable buffer/trigger/channels) when doing > something like a CTRL-C. Otherwise restarting generic_buffer requires a > manual echo 0 > buffer/enable > > This also cleanup up all the code freeing string buffers at > the end of main.

Re: [PATCHv3 2/7] iio: generic_buffer: Add --device-num option

On 23/05/16 19:39, Crestez Dan Leonard wrote: > This makes it possible to distinguish between iio devices with the same > name. > > Signed-off-by: Crestez Dan Leonard Applied. > --- > tools/iio/generic_buffer.c | 69 > ++ >

Re: [PATCHv3 3/7] iio: generic_buffer: Add --trigger-num option

On 23/05/16 19:39, Crestez Dan Leonard wrote: > Signed-off-by: Crestez Dan Leonard Again, sensible and straight forward. Thanks, Jonathan > --- > tools/iio/generic_buffer.c | 34 +- > 1 file changed, 29 insertions(+), 5 deletions(-) >

Re: [RFC 0/7] Deal with iio trigger names

On 23/05/16 19:39, Crestez Dan Leonard wrote: > IIO documents that trigger names are unique but does not actually guarantee > this. You can easily create a software trigger with a duplicate name if you > enable CONFIG_IIO_HRTIMER_TRIGGER: > > mkdir /sys/kernel/config/iio/triggers/hrtimer/\

Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

On 23/05/16 19:40, Crestez Dan Leonard wrote: > The trigger name is documented as unique but drivers are currently > allowed to register triggers with duplicate names. This should be > considered a bug since it makes the 'current_trigger' interface > unusable. > > Signed-off-by: Crestez Dan

Re: [PATCH 3/3] input: touchscreen: mxs-lradc: Add support for touchscreen

> + if (of_property_read_u32(node, "fsl,settling", )) { > + ts->settling_delay = 10; > + } else { > + if (adapt < 1 || adapt > LRADC_DELAY_DELAY_MASK) { > + dev_err(ts->dev, "Invalid settling delay (%u)\n", > +

[x86/uaccess] 3964262746: BUG: uaccess fault at kernel address 0x8011e000 with KERNEL_DS

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/uaccess commit 396426274682b471f3fb5ed2f4c3295c8e360d63 ("x86/uaccess: OOPS or warn on a fault with KERNEL_DS and !pagefault_disabled()") on test machine: vm-intel12-openwrt-i386: 1

Re: [PATCH] mm: memcontrol: fix possible css ref leak on oom

On Fri, May 27, 2016 at 01:36:29PM -0400, Johannes Weiner wrote: > On Mon, May 23, 2016 at 07:02:10PM +0300, Vladimir Davydov wrote: > > mem_cgroup_oom may be invoked multiple times while a process is handling > > a page fault, in which case current->memcg_in_oom will be overwritten > > leaking

[path v2 0/7] Add DRM driver for Hisilicon Hibmc

This patch set adds a new drm driver for Hisilicon Hibmc. Hibmc is a base board management controller, usually it is used on server for Out-of-band management purpose. In this patch set, we just support basic function for Hibmc display subsystem. Hibmc display subsystem is connected to host CPU by

[path v2 3/7] drm/hisilicon/hibmc: Add crtc for DE

Add crtc funcs and helper funcs for DE. Signed-off-by: Rongrong Zou Signed-off-by: Jianhua Li --- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c | 307 drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.h | 29 +++

[path v2 1/7] drm/hisilicon/hibmc: Add hisilicon hibmc drm master driver

Add DRM master driver for Hisilicon Hibmc SoC which used for Out-of-band management. Blow is the general hardware connection, both the Hibmc and the host CPU are on the same mother board. +--+ +--+ | | PCIe | Hibmc | |host CPU( |<->| display | |arm64,x86)|

[path v2 2/7] drm/hisilicon/hibmc: Add plane for DE

Add plane funcs and helper funcs for DE. Signed-off-by: Rongrong Zou Signed-off-by: Jianhua Li --- drivers/gpu/drm/hisilicon/hibmc/Makefile| 2 +- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c | 170

[path v2 4/7] drm/hisilicon/hibmc: Add encoder for VDAC

Add encoder funcs and helpers for VDAC. Signed-off-by: Rongrong Zou Signed-off-by: Jianhua Li --- drivers/gpu/drm/hisilicon/hibmc/Makefile | 2 +- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 6 ++

[path v2 5/7] drm/hisilicon/hibmc: Add connector for VDAC

Add connector funcs and helper funcs for VDAC. Signed-off-by: Rongrong Zou Signed-off-by: Jianhua Li --- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 21 ++ drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h | 3 +-

[path v2 6/7] drm/hisilicon/hibmc: Add support for frame buffer

Add support for fbdev. Signed-off-by: Rongrong Zou Signed-off-by: Jianhua Li --- drivers/gpu/drm/hisilicon/hibmc/Makefile | 2 +- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 20 ++ drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h

[path v2 7/7] drm/hisilicon/hibmc: Add maintainer for Hibmc DRM

Signed-off-by: Rongrong Zou Signed-off-by: Jianhua Li --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index f466673..a8a62e0 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3957,6 +3957,13 @@ T:

Re: [PATCH 1/1] iio: light: Added CM36672 Proximity Sensor Driver.

On Sat, 28 May 2016, Kevin Tsai wrote: > Added Vishay Capella CM36672 Proximity Sensor IIO driver. Support both > ACPI and Device Tree. comments below > Signed-off-by: Kevin Tsai > --- > .../devicetree/bindings/i2c/trivial-devices.txt| 1 + >

Re: [Intel-gfx] 4.7-rc0: redshift stopped working on intel display

Could you try to apply the following patch [1], hopefully this fixes the issue for you. [1] https://patchwork.freedesktop.org/patch/89111/

[PATCH] MIPS: ralink: fix spis group pinmux

pwm function for spis conflicts with uart2 and uart1, fix this by changing it to pwm_uart2, which reflects the real use of these pins with these pinmux (2 for pwm and 2 for uart). Signed-off-by: Álvaro Fernández Rojas --- arch/mips/ralink/mt7620.c | 2 +- 1 file changed, 1

Re: [PATCH] Rename other copy of hash_string to hashlen_string

Hi Georges, On Sun, May 29, 2016 at 7:26 AM, George Spelvin wrote: > The original name was simply hash_string(), but that conflicted with a > function with that name in drivers/base/power/trace.c, and I decided that > calling it "hashlen_" was better anyway. > > But

Re: [PATCH v3 07/10] : Add support for architecture-specific functions

Hi George, I see this has been applied in the mean time, but improvements never hurt... On Sat, May 28, 2016 at 9:57 PM, George Spelvin wrote: > --- /dev/null > +++ b/lib/test_hash.c > @@ -0,0 +1,250 @@ > +/* > + * Test the various integer hash functions. h64 (or

Re: [PATCH 05/54] MAINTAINERS: Add file patterns for rockchip device tree bindings

Hi Heiko, On Sun, May 22, 2016 at 11:27 AM, Heiko Stuebner wrote: > Am Sonntag, 22. Mai 2016, 11:05:42 schrieb Geert Uytterhoeven: >> Submitters of device tree binding documentation may forget to CC >> the subsystem maintainer if this is missing. > > The "N: rockchip" line at

Re: Nokia N900: musb is in wrong state after boot

On Saturday 23 January 2016 13:57:32 Pali Rohár wrote: > On Thursday 21 January 2016 20:21:13 Tony Lindgren wrote: > > * joerg Reisenweber [160121 10:45]: > > > On Thu 21 January 2016 09:41:46 Tony Lindgren wrote: > > > > Then for supporting the USB host mode.. We should add

[RFT][PATCH RESEND] regulator: max8973: Fix setting ramp delay

Current code can set ramp delay to a wrong setting that the return value from .set_voltage_time_sel is not enough for proper delay. Fix the logic in .set_ramp_delay and also remove unused ret_val variable. Signed-off-by: Axel Lin --- RESEND: Fix typo in subject line, it's

Re: [PATCH trivial] include/linux/memblock.h: Clean up code for several trivial details

On Sun, 2016-05-29 at 22:36 +0800, cheng...@emindsoft.com.cn wrote: > From: Chen Gang > > Correct the function parameters alignment, since original code already > use both tabs and white spaces together for the incorrect parameters > alignment functions. > > If one

Re: [PATCH] Rename other copy of hash_string to hashlen_string

> That version fails the test. On m68k/ARAnyM: > > test_hash: hashlen_string(256..256) returned length 1, expected 0 Just kill me. :-( I didn't change that code, so I didn't re-test it. But I changed the test. diff --git a/fs/namei.c b/fs/namei.c index aefba699..dcb85255 100644 ---

[PATCH 2/2] staging: slicoss: fix camel case check

From: Jaime Arrocha Fixed several checks about camel case use provided by checkpatch.pl. CHECK: Avoid CamelCase Changes verified to work by compiling module. Signed-off-by: Jaime Arrocha --- drivers/staging/slicoss/slic.h| 30

[PATCH 1/2] staging: slicoss: fix coding style spacing issues

From: Jaime Arrocha This patch fixes spacing in variable declarations. This patch series does not depend on each other. Signed-off-by: Jaime Arrocha --- drivers/staging/slicoss/slic.h | 280 - 1 file changed,

Re: [PATCH v3 1/2] mm, kasan: improve double-free detection

On Tue, May 24, 2016 at 8:30 PM, Kuthonuzo Luruo wrote: > Currently, KASAN may fail to detect concurrent deallocations of the same > object due to a race in kasan_slab_free(). This patch makes double-free > detection more reliable by serializing access to KASAN object

dma_declare_coherent_memory fails for RAM allocated memory

Hi, When trying to declare and use DT reserved memory region on ARM (OMAP3), dma_declare_coherent_memory() fails in memremap(). This is from today's master: [ cut here ] WARNING: CPU: 0 PID: 1 at kernel/memremap.c:111 memremap+0x118/0x194 memremap attempted on ram

Re: [PATCH v3 1/2] mm, kasan: improve double-free detection

On Sun, May 29, 2016 at 4:45 PM, Luruo, Kuthonuzo wrote: >> > +/* flags shadow for object header if it has been overwritten. */ >> > +void kasan_mark_bad_meta(struct kasan_alloc_meta *alloc_info, >> > + struct kasan_access_info *info) >> > +{ >> > + u8

Re: [PATCH v2] gpu: drm: amd: amdkfd: Remove create_workqueue()

On Thu, May 26, 2016 at 10:37 PM, Bhaktipriya Shridhar wrote: > alloc_workqueue replaces deprecated create_workqueue(). > > create_workqueue has been replaced with alloc_workqueue with max_active > as 0 since there is no need for throttling the number of active work

[PATCH trivial] include/linux/memblock.h: Clean up code for several trivial details

From: Chen Gang Correct the function parameters alignment, since original code already use both tabs and white spaces together for the incorrect parameters alignment functions. If one line can hold one statement within 80 columns, let it in one line (original code did

Re: [RFT v3] drm: use late_initcall() for amdkfd and radeon

On Fri, May 27, 2016 at 4:18 AM, Luis R. Rodriguez wrote: > To get KFD support in radeon we need the following > initialization to happen in this order, their > respective driver file that has its init routine > listed next to it: > > 0. AMD IOMMUv1:

RE: [PATCH v3 1/2] mm, kasan: improve double-free detection

> >> > +/* flags shadow for object header if it has been overwritten. */ > >> > +void kasan_mark_bad_meta(struct kasan_alloc_meta *alloc_info, > >> > + struct kasan_access_info *info) > >> > +{ > >> > + u8 *datap = (u8 *)_info->data; > >> > + > >> > + if u8

Re: [PATCH v2 4/7] iio: inv_mpu6050: Cache non-volatile bits of user_ctrl

On 18/05/16 16:00, Crestez Dan Leonard wrote: > Signed-off-by: Crestez Dan Leonard Kind of a pity we have to do this, but fair enough! Jonathan > --- > drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 2 ++ > drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c| 9 ++---

Re: [PATCH v2 3/7] iio: inv_mpu6050: Only toggle DATA_RDY_EN in inv_reset_fifo

On 18/05/16 16:00, Crestez Dan Leonard wrote: > Signed-off-by: Crestez Dan Leonard Looks good to me. Jonathan > --- > drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c| 13 - > drivers/iio/imu/inv_mpu6050/inv_mpu_trigger.c | 3 ++- > 2 files changed, 10

Re: [PATCH v4 3/3] drm: Add helper for simple display pipeline

Den 12.05.2016 20:25, skrev Noralf Trønnes: Provides helper functions for drivers that have a simple display pipeline. Plane, crtc and encoder are collapsed into one entity. Cc: jsa...@ti.com Signed-off-by: Noralf Trønnes --- [...] diff --git

Re: [RFC v2 7/7] iio: inv_mpu6050: Expose channels from slave sensors

On 18/05/16 16:00, Crestez Dan Leonard wrote: > This works by copying the iio_chan_specs from the slave device and > republishing them as if they belonged to the MPU itself. All > read/write_raw operations are forwarded to the other driver. > > The original device is still registered with linux

[PATCH v4 1/2] mm, kasan: improve double-free detection

Currently, KASAN may fail to detect concurrent deallocations of the same object due to a race in kasan_slab_free(). This patch makes double-free detection more reliable by serializing access to KASAN object metadata. New functions kasan_meta_lock() and kasan_meta_unlock() are provided to

Re: [Revert "ppdev] 1701f68040: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)

On Sun, May 29, 2016 at 8:28 AM, kernel test robot wrote: > > 0day kernel testing robot got the below dmesg and the first bad commit is This bisection seems unlikely. I *think* what is going on is that the previous kernels ended up with boot failures: >

Re: [PATCH 1/1] iio: light: Added CM36672 Proximity Sensor Driver.

On 29/05/16 09:55, Peter Meerwald-Stadler wrote: > On Sat, 28 May 2016, Kevin Tsai wrote: > >> Added Vishay Capella CM36672 Proximity Sensor IIO driver. Support both >> ACPI and Device Tree. > > comments below > >> Signed-off-by: Kevin Tsai >> --- >> +#ifdef

[GIT PULL] SCSI fixes for 4.7-rc1

This is a set of four fixes noticed in the merge window. The aacraid one is an optimisation, the mp3sas one fixes a spurious printk, the sd_check_events one fixes a theoretical race and the failed zero length commands fixes a bug in our completion/retry routines that has been causing problems in

Re: [PATCH 4/7] x86/dumpstack: If addr_limit is non-default, display it

On Wed, May 25, 2016 at 4:32 AM, Borislav Petkov wrote: > On Tue, May 24, 2016 at 03:48:41PM -0700, Andy Lutomirski wrote: >> This will help debug OOPSes related to USER_DS vs KERNEL_DS. >> >> Signed-off-by: Andy Lutomirski >> --- >>

Re: [PATCH 3/3] input: touchscreen: mxs-lradc: Add support for touchscreen

On 28/05/16 18:45, Ksenija Stanojević wrote: > On Sun, May 1, 2016 at 6:47 PM, Jonathan Cameron wrote: >> On 29/04/16 12:49, Ksenija Stanojevic wrote: >>> Add mxs-lradc touchscreen driver. >>> >>> Signed-off-by: Ksenija Stanojevic >> The only real

Re: [PATCH 7/7] x86/uaccess: OOPS or warn on a fault with KERNEL_DS and !pagefault_disabled()

On Wed, May 25, 2016 at 8:33 AM, Borislav Petkov wrote: > On Tue, May 24, 2016 at 03:48:44PM -0700, Andy Lutomirski wrote: >> + if (unlikely(!is_user_ds && !pagefault_disabled())) { >> + if (extra < TASK_SIZE_MAX) { >> + /* >> +

Linux 4.7-rc1

Usually I close the merge window on a Sunday afternoon, but I've been known to be annoyed with stragglers and close things a day early. This time, to spice things up, I decided to just release on Sunday morning instead. [ And yes, before you ask , my life really is boring if this is "spicing

[PATCH] regulator: palmas: Remove *rdev[PALMAS_NUM_REGS] from struct palmas_pmic

Current code uses devm_regulator_register(), so *rdev[PALMAS_NUM_REGS] is no longer required. Signed-off-by: Axel Lin --- drivers/regulator/palmas-regulator.c | 12 include/linux/mfd/palmas.h | 1 - 2 files changed, 13 deletions(-) diff --git

[PATCH RFT] regulator: max8972: Fix setting ramp delay

Current code can set ramp delay to a wrong setting that the return value from .set_voltage_time_sel is not enough for proper delay. Fix the logic in .set_ramp_delay and also remove unused ret_val variable. Signed-off-by: Axel Lin --- drivers/regulator/max8973-regulator.c |

[PATCH] fs/namei.c. If we way we want zero-length string support, mean it

>From 4b237fc0c5addf58ef0e0bbd3740d64007c36375 Mon Sep 17 00:00:00 2001 From: George Spelvin Date: Sun, 29 May 2016 08:05:56 -0400 Subject: [PATCH] fs/namei.c. If we way we want zero-length string suppor mean it. hash_name() is not changed for speed, but the more

[PATCH] fs/namei.c: Update !CONFIG_DCACHE_WORD_ACCESS case

>From be5e653c0d5ec890c32a48851dcd0a347df8e5fa Mon Sep 17 00:00:00 2001 From: George Spelvin Date: Sun, 29 May 2016 01:23:14 -0400 Subject: [PATCH] fs/namei.c: Update !CONFIG_DCACHE_WORD_ACCESS case A couple of late changes to the previous patch didn't update the

[PATCH] kprobes: fix a comment typo

Just fix a typo in the code comment. Signed-off-by: Jinbum Park --- arch/arm/probes/kprobes/opt-arm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/probes/kprobes/opt-arm.c b/arch/arm/probes/kprobes/opt-arm.c index bcdecc2..073c0ba 100644

RE: [PATCH v3 1/2] mm, kasan: improve double-free detection

> > +/* flags shadow for object header if it has been overwritten. */ > > +void kasan_mark_bad_meta(struct kasan_alloc_meta *alloc_info, > > + struct kasan_access_info *info) > > +{ > > + u8 *datap = (u8 *)_info->data; > > + > > + if u8 *)info->access_addr +

Re: [PATCH v2 2/7] iio: inv_mpu6050: Initial regcache support

On 20/05/16 12:01, Crestez Dan Leonard wrote: > On 05/20/2016 09:39 AM, Peter Rosin wrote: >> On 2016-05-20 04:34, Matt Ranostay wrote: >>> On Wed, May 18, 2016 at 8:00 AM, Crestez Dan Leonard >>> wrote: Signed-off-by: Crestez Dan Leonard

[PATCH v3] gpu: drm: amd: amdkfd: Remove create_workqueue()

alloc_workqueue replaces deprecated create_workqueue(). create_workqueue has been replaced with alloc_workqueue with max_active as 0 since there is no need for throttling the number of active work items. WQ_MEM_RECLAIM has not been set to because kfd_process_wq will not be used in memory reclaim

Re: [PATCH v2 6/7] iio: inv_mpu6050: Reformat sample for active scan mask

On 18/05/16 16:00, Crestez Dan Leonard wrote: > Right now it is possible to only enable some of the x/y/z channels, for > example you can enable accel_z without x or y but if you actually do > that what you get is actually only the x channel. > > Fix this by reformatting the hardware sample to

[PATCH] Documentation/zh_CN: update Chinese version CodingStyle

Chinese version CodingStyle is a little outdate, it should be updated. This patch sync with the latest CodingStyle of all changes, new chapters (chapter 19 and chapter 20) have been translated. Signed-off-by: Andy Deng --- Documentation/zh_CN/CodingStyle | 581

Re: [PATCH v2] gpu: drm: amd: amdkfd: Remove create_workqueue()

Thanks Oded. Sending v3 right away :) On Sun, May 29, 2016 at 8:31 PM, Oded Gabbay wrote: > On Thu, May 26, 2016 at 10:37 PM, Bhaktipriya Shridhar > wrote: >> alloc_workqueue replaces deprecated create_workqueue(). >> >> create_workqueue has been

Re: [PATCH 1/1 v3] hwmon: add support for Sensirion SHT3x sensors

On 05/26/2016 12:25 AM, Pascal Sachs wrote: From: David Frey This driver implements support for the Sensirion SHT3x-DIS chip, a humidity and temperature sensor. Temperature is measured in degrees celsius, relative humidity is expressed as a percentage. In the sysfs

Re: [PATCH v2 1/7] iio: inv_mpu6050: Do burst reads using spi/i2c directly

On 18/05/16 16:00, Crestez Dan Leonard wrote: > Using regmap_read_bulk is wrong because it assumes that a range of > registers is being read. In our case reading from the fifo register will > return multiple values but this is *not* auto-increment. > > This currently works by accident. > >

Re: [PATCH 1/1 v3] hwmon: add support for Sensirion SHT3x sensors

On 05/26/2016 12:25 AM, Pascal Sachs wrote: From: David Frey This driver implements support for the Sensirion SHT3x-DIS chip, a humidity and temperature sensor. Temperature is measured in degrees celsius, relative humidity is expressed as a percentage. In the sysfs

[PATCH v4 0/2] KASAN double-free detection

Submitting v4 for your review/consideration. First patch provides more reliable double-free detection for KASAN. Second patch provides new double-free tests for 'test_kasan'. "Lock break" on out-of-bounds (OOB) write detection in patch v3 suffers from one fatal flaw: it's not possible to

[PATCH v4 2/2] kasan: add double-free tests

This patch adds new tests for KASAN double-free error detection when the same slab object is concurrently deallocated. Signed-off-by: Kuthonuzo Luruo --- Changes in v4: - There are *no* changes for v4. Changes in v3: - concurrent double-free test simplified to use

Re: [PATCH 5/7] x86/uaccess: Warn on uaccess faults other than #PF

On Wed, May 25, 2016 at 2:49 AM, Borislav Petkov wrote: > On Tue, May 24, 2016 at 03:48:42PM -0700, Andy Lutomirski wrote: >> If a uaccess instruction fails due to an8 error other than #PF, >> warn. If the fault is #GP, it most likely indicates access to a >> non-canonical

Re: [PATCH 1/1] iio: light: Added CM36672 Proximity Sensor Driver.

On 29/05/16 01:42, Kevin Tsai wrote: > Added Vishay Capella CM36672 Proximity Sensor IIO driver. Support both > ACPI and Device Tree. > > Signed-off-by: Kevin Tsai There are quite a few odd bits around the event handling. I think you failed to register the events

Re: [PATCH 2/3] iio: adc: mxs-lradc: Add support for adc driver

On 28/05/16 18:49, Ksenija Stanojević wrote: > On Sun, May 1, 2016 at 6:38 PM, Jonathan Cameron wrote: >> On 29/04/16 12:48, Ksenija Stanojevic wrote: >>> Add mxs-lradc adc driver. >>> >>> Signed-off-by: Ksenija Stanojevic >> Mostly looking good.

Re: [PATCH 4/7] x86/dumpstack: If addr_limit is non-default, display it

On Wed, May 25, 2016 at 4:39 AM, Borislav Petkov wrote: > On Tue, May 24, 2016 at 03:48:41PM -0700, Andy Lutomirski wrote: >> This will help debug OOPSes related to USER_DS vs KERNEL_DS. >> >> Signed-off-by: Andy Lutomirski >> --- >>

Re: [PATCH] kcov: add AFL-style tracing

On Sat, May 21, 2016 at 6:07 PM, Vegard Nossum wrote: > From: Quentin Casasnovas > > AFL uses a fixed-size buffer (typically 64 KiB) where each byte is > a counter representing how many times an A -> B branch was taken. > Of course, since

Re: [PATCH] iio: Documentation: fix in_*_scale kernel version

On 22/05/16 14:30, Alexandre Belloni wrote: > v3.21 doesn't exist, the first apparition of a in_.*_scale file was in v3.2 > > Signed-off-by: Alexandre Belloni Not that simple as this explicitly in_*_scale in the events directory. First instance of that is

  1   2   3   4   5   6   >