[PATCHv6 4/4] hwmon: da9052: add support for TSI channel

TSI channel has a 4 channel mux connected to it and is normally used for touchscreen support. The hardware may alternatively use it as general purpose adc. Signed-off-by: Sebastian Reichel --- drivers/hwmon/da9052-hwmon.c | 249

[PATCHv6 3/4] hwmon: da9052: replace S_IRUGO with 0444

Fix checkpatch warnings about S_IRUGO being less readable than providing the permissions octal as '0444'. Signed-off-by: Sebastian Reichel --- drivers/hwmon/da9052-hwmon.c | 36 ++-- 1 file changed, 18 insertions(+), 18

[PATCHv6 1/4] mfd: da9052: add register details for TSI

Add register details an channels definition for using the TSI registers in the hwmon driver. Signed-off-by: Sebastian Reichel --- include/linux/mfd/da9052/da9052.h | 6 ++ include/linux/mfd/da9052/reg.h| 11 ++- 2 files changed, 16

[PATCHv6 2/4] mfd: da9052: make touchscreen registration optional

If the touchscreen pins are used as general purpose analogue input, the touchscreen driver should not be used. The pins will be handled by the existing hwmon driver instead. Signed-off-by: Sebastian Reichel --- drivers/mfd/da9052-core.c | 26

Re: [RFC 11/13] gpio-switch is for some reason neccessary for camera to work.

Hi! > On Tue, Feb 14, 2017 at 02:40:19PM +0100, Pavel Machek wrote: > > Probably something fun happening in userspace. > > What's the status of this one? > > I don't think it has a chance to be merged in the foreseeable future. Why > is it needed? Good question. And agreed that this one is not

Re: [PATCH 1/2] dt-binding: mfd: Add Maxim/Dallas DS1374 MFD device binding

On Thu, 13 Jul 2017, Moritz Fischer wrote: > This adds a binding for the Maxim/Dallas DS1374 MFD. > > Signed-off-by: Moritz Fischer > --- > Changes from RFC: > - dallas,ds1374-mode -> dallas,mode > - Clarified examples > - dallas,remap-reset property > > On second thoughts the

Re: [PATCH V3 1/5] drivers/fmc: remove unused variable

> Again, I do not like to take patches without any changelog text at all > :( Sorry, I added this after the "---" line. I thought it was this one the missing item: V3 (Alessandro): fixed From line in patch, added alessandro's acked-by V2 (Pat): added Tested-by and incorrect From line V1

Re: [PATCH 2/2] mfd: intel_soc_pmic: Differentiate between Bay and Cherry Trail CRC variants

On Mon, 17 Jul 2017, Andy Shevchenko wrote: > On Mon, 2017-07-17 at 11:59 +0100, Lee Jones wrote: > > On Sat, 01 Jul 2017, Hans de Goede wrote: > > > > > Both Bay and Cherry Trail devices may be used together with a > > > Crystal Cove > > > PMIC. Each platform has its own variant of the PMIC,

Re: [PATCH] serial: 8250: fix error handling in of_platform_serial_probe()

On 18.07.2017 10:27, Greg Kroah-Hartman wrote: > On Sat, Jul 01, 2017 at 01:49:29AM +0300, Alexey Khoroshilov wrote: >> clk_disable_unprepare(info->clk) is missed in of_platform_serial_probe(), >> while irq_dispose_mapping(port->irq) is missed in of_platform_serial_setup(). >> >> Found by Linux

Re: [RFC PATCH v2] Bluetooth: btusb: Fix memory leak in play_deferred

Am Dienstag, den 18.07.2017, 08:44 +0200 schrieb Marcel Holtmann: > > diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c > > index 0d533b2..a22a08b 100644 > > --- a/drivers/bluetooth/btusb.c > > +++ b/drivers/bluetooth/btusb.c > > @@ -3260,19 +3260,33 @@ static int

Re: [PATCH 1/2] Input: axp20x-pek: add support for AXP221 PEK

Hi Maxime, On 17/07/2017 13:29, Maxime Ripard wrote: > Hi, > > On Mon, Jul 17, 2017 at 11:53:06AM +0200, Quentin Schulz wrote: >> The AXP221 has different values for startup time bits from the AXP20X. >> >> This patch introduces a different platform_device_id to the driver and >> adds the

Re: [PATCH v4 0/2] Add basic support for Mediatek MT2712 SoC

Hi Matthias, Just a gentle ping. Should I rebase to 4.13-rc1 and send v5? Thanks yt.shen On Thu, 2017-06-22 at 17:32 +0800, YT Shen wrote: > MT2712 is a SoC based on 64bit ARMv8 architecture. > MT2712 share many HW IP with MT8173. This patchset was tested on MT2712 > evaluation board, and

Re: [PATCH 2/2] xen: dont fiddle with event channel masking in suspend/resume

On Mon, 17 Jul 2017, Juergen Gross wrote: > Instead of fiddling with masking the event channels during suspend > and resume handling let do the irq subsystem do its job. It will do > the mask and unmask operations as needed. > > Signed-off-by: Juergen Gross Acked-by: Thomas

[GIT PULL] Immutable branch between MFD, ARM and I2C due for the v4.14 merge window

Enjoy! The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: Linux v4.13-rc1 (2017-07-15 15:22:10 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-arm-i2c-v4.14 for you to fetch changes up to

[PATCH v3] mm/vmalloc: terminate searching since one node found

It is no need to find the very beginning of the area within alloc_vmap_area, which can be done by judging each node during the process For current approach, the worst case is that the starting node which be found for searching the 'vmap_area_list' is close to the 'vstart', while the final

Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

On Mon, Jul 17, 2017 at 4:29 PM, Michal Hocko wrote: > On Mon 17-07-17 15:27:31, Zhaoyang Huang wrote: >> From: Zhaoyang Huang >> >> It is no need to find the very beginning of the area within >> alloc_vmap_area, which can be done by judging

Re: [linux-sunxi] [PATCH v2 2/2] pinctrl: sunxi: add support of R40 to A10 pinctrl driver

On Tue, Jul 18, 2017 at 3:42 PM, Icenowy Zheng wrote: > R40 is said to be an upgrade of A20, and its pin configuration is also > similar to A20 (and thus similar to A10). > > Add support for R40 to the A10 pinctrl driver. > > Signed-off-by: Icenowy Zheng

Re: [PATCH v2] mfd: Add missing Kconfig dependency for TPS65086

On Mon, 17 Jul 2017, Michal Simek wrote: > MTF_CORE should be enabled when driver is enabled. > > Without this patch you can configure: > CONFIG_MFD_CORE is not set > CONFIG_MFD_TPS65086=y > > which ends up with compilation error: > drivers/mfd/tps65086.o: In function `tps65086_probe': >

Re: [PATCH v2] mm/page_alloc: Wait for oom_lock before retrying.

On Tue 18-07-17 06:42:31, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Sun 16-07-17 19:59:51, Tetsuo Handa wrote: > > > Since the whole memory reclaim path has never been designed to handle the > > > scheduling priority inversions, those locations which are assuming that > > > execution of

Re: [PATCH v2 1/2] staging: gs_fpgaboot: add buffer overflow checks

On Mon, Jul 17, 2017 at 08:47:25PM -0400, Jacob von Chorus wrote: > -static void readinfo_bitstream(char *bitdata, char *buf, int *offset) > +static int readinfo_bitstream(char *bitdata, char *buf, int size, int > *offset) > { > char tbuf[64]; > s32 len; > @@ -59,9 +59,15 @@ static

Re: [PATCH] perf/x86/intel: Add proper condition to run sched_task callbacks

On Mon, Jul 17, 2017 at 05:01:56PM +0200, Jiri Olsa wrote: > The x86 pmu currently uses the sched_task callback for 2 functions: > - PEBS drain > - save/restore LBR data > > They are both triggered once the x86 pmu is registered with > perf_sched_cb_inc call (within pmu::add callback),

[PATCH] x86: kernel: acpi: fix an invalid argument passing in io_apic.c

I'm Seunghun Han, and I work for National Security Research Institute of South Korea. I found a kernel panic while I tested latest kernel version. The kernel panic log is as follows: >[0.058851] BUG: unable to handle kernel NULL pointer dereference at >0010 >[0.06] IP:

[PATCHv6 0/4] DA9052 hardware monitoring improvements

Hi, GE Healthcare's PPD [0] uses DA9053's touchscreen pins for hardware monitoring purposes. This adds support for the feature. The proposed merge solution is, that mfd queues the mfd patches and provides an immutable branch for hwmon, since the last patch depends on the other ones. [0]

Re: [PATCH 1/4] drm/atomic: implement drm_atomic_helper_commit_tail for runtime_pm users

Hi Laurent, On Fri, Jul 14, 2017 at 02:43:12AM +0300, Laurent Pinchart wrote: > Hi Maxime, > > Thank you for the patch. > > On Thursday 13 Jul 2017 16:41:13 Maxime Ripard wrote: > > The current drm_atomic_helper_commit_tail helper works only if the CRTC is > > accessible, and documents an

[PATCH 1/2] dt-bindings: dma: Add Spreadtrum SC9860 DMA controller

This patch adds the binding documentation for Spreadtrum SC9860 DMA controller device. Signed-off-by: Baolin Wang --- Documentation/devicetree/bindings/dma/sprd-dma.txt | 41 1 file changed, 41 insertions(+) create mode 100644

[PATCH 2/2] dma: Add Spreadtrum DMA controller driver

This patch adds the DMA controller driver for Spreadtrum SC9860 platform. Signed-off-by: Baolin Wang --- drivers/dma/Kconfig |7 + drivers/dma/Makefile |1 + drivers/dma/sprd-dma.c | 1451 ++

Re: [Xen-devel] [PATCH v1] xen/grant-table: log the lack of grants

On 07/07/17 20:23, Wengang Wang wrote: > log a message when we enter this situation: > 1) we already allocated the max number of available grants from hypervisor > and > 2) we still need more (but the request fails because of 1)). > > Sometimes the lack of grants causes IO hangs in xen_blkfront

Re: [PATCH] serial: 8250: fix error handling in of_platform_serial_probe()

On Sat, Jul 01, 2017 at 01:49:29AM +0300, Alexey Khoroshilov wrote: > clk_disable_unprepare(info->clk) is missed in of_platform_serial_probe(), > while irq_dispose_mapping(port->irq) is missed in of_platform_serial_setup(). > > Found by Linux Driver Verification project (linuxtesting.org). > >

Re: [PATCH v6 00/16] perf tool: add meta-data header support for pipe-mode

On Mon, Jul 17, 2017 at 09:25:33PM -0700, David Carrillo-Cisneros wrote: > v6: - Avoid buffer resize that would overflow event's header size. hi, for the patchset Acked-by: Jiri Olsa thanks, jirka

[PATCH 2/2] Staging: iio: light: tsl2x7x_core.c: Replace symbolic permission with octal permission

Replace symbolic permissions with their octect representation to fix checkpatch warnings. Signed-off-by: Jaya Durga --- drivers/staging/iio/light/tsl2x7x_core.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git

[PATCH] dt-bindings: add compatible string of Allwinner H5 Mali-450 MP4 GPU

Allwinner H5 has a Mali-450 MP4 GPU, which has a reset line like other Allwinner SoCs with Mali Utgard, but it's a Mali-450, so it needs a new compatible. Add the new compatible to Mali Utgard binding document. Signed-off-by: Icenowy Zheng ---

Re: [PATCH][xen-next] xen/pvcalls: fix null pointer reference on sock_release call

On 11/07/17 21:41, Colin King wrote: > From: Colin Ian King > > Currently a sock_release on map->sock will result in a null pointer > deference on map when map is null. Instead, the sock_relase sould > be on sock and not map->sock. > > Detected by CoverityScan,

Re: [PATCH] xen/x86: Don't BUG on CPU0 offlining

On 26/06/17 18:39, Vitaly Kuznetsov wrote: > CONFIG_BOOTPARAM_HOTPLUG_CPU0 allows to offline CPU0 but Xen HVM guests > BUG() in xen_teardown_timer(). Remove the BUG_ON(), this is probably a > leftover from ancient times when CPU0 hotplug was impossible, it works > just fine for HVM. > >

Re: [Xen-devel] [PATCH v1] xen/grant-table: log the lack of grants

On 07/07/17 20:23, Wengang Wang wrote: > log a message when we enter this situation: > 1) we already allocated the max number of available grants from hypervisor > and > 2) we still need more (but the request fails because of 1)). > > Sometimes the lack of grants causes IO hangs in xen_blkfront

Re: [PATCH v3] staging: unisys: visorbus: Constify attribute_group structures.

On Tue, Jul 18, 2017 at 01:24:42PM +0530, Arvind Yadav wrote: > attribute_group are not supposed to change at runtime. All functions > working with attribute_group provided by work > with const attribute_group. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav

Re: [PATCH 1/3] mfd: syscon: update Atmel SMC binding doc

On Tue, 11 Jul 2017, Ludovic Desroches wrote: > A new compatible string is introduced for SMC on sama5d2 to manage a > different layout of the registers. > > Signed-off-by: Ludovic Desroches > --- > Documentation/devicetree/bindings/mfd/atmel-smc.txt | 1 + > 1

Re: [PATCH v3] staging: unisys: visorbus: Constify attribute_group structures.

Hi Greg, On Tuesday 18 July 2017 01:30 PM, Greg KH wrote: On Tue, Jul 18, 2017 at 01:24:42PM +0530, Arvind Yadav wrote: attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs

Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible

On Tue, Jul 18, 2017 at 09:57:55AM +0200, Stephan Müller wrote: > --- /dev/null > +++ b/include/crypto/jitterentropy.h > @@ -0,0 +1,80 @@ > +/* > + * Copyright (C) 2017, Stephan Mueller > + * > + * Redistribution and use in source and binary forms, with or without > + *

Re: [PATCH v7 2/3] media: i2c: adv748x: add adv748x driver

Hi Kieran, A few more minor matters that you might want to address on top of Hans's pull request. On Thu, Jul 06, 2017 at 12:01:16PM +0100, Kieran Bingham wrote: ... > +static int adv748x_afe_g_input_status(struct v4l2_subdev *sd, u32 *status) > +{ > + struct adv748x_afe *afe =

Re: [PATCH] Coccinelle report script for refcounters

On Tue, 18 Jul 2017, Elena Reshetova wrote: > The below script can be used to detect potential misusage > of atomic_t type and API for reference counting purposes. > Now when we have a dedicated refcount_t type and API with > security protection implemented, people should be using it > instead.

Re: [PATCH 3/7] phy: qcom-qmp: Fix phy pipe clock name

Bjorn, On Mon, Jul 17, 2017 at 03:30:47PM -0700, Bjorn Andersson wrote: > On Mon 17 Jul 05:03 PDT 2017, Varadarajan Narayanan wrote: > > > Presently, the phy pipe clock's name is assumed to be either > > usb3_phy_pipe_clk_src or pcie_XX_pipe_clk_src (where XX is the > > phy lane's number).

Re: [RFC PATCH v12 1/4] crypto: make Jitter RNG directly accessible

Am Dienstag, 18. Juli 2017, 11:02:02 CEST schrieb Arnd Bergmann: Hi Arnd, > > I can see why the jitterentropy implementation avoids using kernel headers, > the problem now is that part of it gets moved into a new header, and that > already violates the original principle. > > From my reading of

Re: [PATCH] gpu: host1x: Free the IOMMU domain when there is no device to attach

Hi Mikko, On 11/07/17 07:43, Mikko Perttunen wrote: > Thanks for the patch, didn't consider this case. I really need to get > together some system to automatically test on multiple platforms.. :) We already have the infrastructure in place to do this, however, at the moment we are just making

Re: [PATCH] perf probe: Fix build failure for get_target_map()

Arnaldo Carvalho de Melo writes: > Em Mon, Jul 17, 2017 at 04:02:22PM +0530, Ravi Bangoria escreveu: >> Commit 801bc8193463 ("perf probe: Allow placing uprobes in >> alternate namespaces.") is causing a build failure on powerpc: >> >> error: incompatible type for argument 2

[PATCH] usb: gadget: udc: fix the kernel NULL pointer in composite_setup

the patch is for fix the below kernel panic: BUG: unable to handle kernel NULL pointer dereference at 002a IP: [] composite_setup+0x3d/0x1830 PGD 27525b067 PUD 27525a067 PMD 0 Oops: 0002 [#1] PREEMPT SMP Call Trace: [] ? dwc3_trace+0x52/0x60 [] ? get_parent_ip+0xd/0x50 []

Re: [PATCH v3 1/4] mfd: cros_ec: Get rid of cros_ec_check_features from cros_ec_dev.

On Mon, 17 Jul 2017, Enric Balletbo Serra wrote: > Hi Gwendal, > > 2017-07-13 22:33 GMT+02:00 Gwendal Grignou : > > On Wed, Jul 12, 2017 at 3:13 AM, Enric Balletbo i Serra > > wrote: > >> The cros_ec_dev driver should be used only to expose

Re: [PATCH] perf/x86/intel: Add proper condition to run sched_task callbacks

On Tue, Jul 18, 2017 at 11:14:44AM +0200, Peter Zijlstra wrote: > On Mon, Jul 17, 2017 at 05:01:56PM +0200, Jiri Olsa wrote: > > The x86 pmu currently uses the sched_task callback for 2 functions: > > - PEBS drain > > - save/restore LBR data > > > > They are both triggered once the x86 pmu is

Re: [PATCHv2 0/6] Motorola Droid 4 Audio Support

Hi, On Mon, Jul 17, 2017 at 10:48:33PM -0700, Tony Lindgren wrote: > * Sebastian Reichel [170717 07:14]: > > Hi, > > > > On Mon, Jul 17, 2017 at 03:17:10AM -0700, Tony Lindgren wrote: > > > * Sebastian Reichel [170717

[PATCH V3 4/5] drivers/fmc: change registration prototype

From: Federico Vaga Permit use of either fmc_device_register_n or fmc_device_register_n_gw depending on the type of device in use. Signed-off-by: Federico Vaga Tested-by: Pat Riehecky Acked-by: Alessandro Rubini

[PATCH V3 0/5] Update kernel to latest FMC bus release

Version 3: fixed From: line to set Federico Vaga as author, added my Acked-by: line. removed drivers_other@kernel-bugs as recipient (NXDOMAIN) Version 2 (posted by Pat Riehecky): added Tested-by: and (incorrect) From: Comments by Pat, original poster, for version 1: The following

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On Mon, 17 Jul 2017, Andi Kleen wrote: > > We need a tradeoff here IMHO. I'll check Daniel's work to understand how/if > > it's better than menu governor. > > I still would like to see how the fast path without the C1 heuristic works. > > Fast pathing is a different concept from a better

Re: [RFC PATCH v2] Bluetooth: btusb: Fix memory leak in play_deferred

Hi Oliver, > Currently we are calling usb_submit_urb directly to submit deferred tx > urbs after unanchor them. > > So the usb_giveback_urb_bh would failed to unref it in usb_unanchor_urb > and cause memory leak: > unreferenced object 0xffc0ce0fa400 (size 256): > ... > backtrace: >[]

Re: [PATCH 6/7] docs: Do not include from include/drm/drm_color_mgmt.h

On Mon, Jul 17, 2017 at 03:00:47PM -0600, Jonathan Corbet wrote: > Commit 8f2e045ec878 (drm/color: un-inline drm_color_lut_extract()) moved > the only kerneldoc comment out of include/drm/drm_color_mgmt.h, leading to > this warning: > > ./include/drm/drm_color_mgmt.h:1: warning: no structured

Re: [PATCH v1] staging: rts5208: Change fixed function names with "%s: ", __func__

On Mon, Jul 17, 2017 at 08:19:45PM +0530, Gaurav Pathak wrote: > staging: rts5208: Fix coding style issue caught by checkpatch.pl related to > function name in debug print and shorten few lines over 80 char No, only do one-type-of-thing per patch. It would make sense to maybe fix an 80 char line

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On 2017/7/18 14:43, Thomas Gleixner wrote: > On Mon, 17 Jul 2017, Andi Kleen wrote: > >>> We need a tradeoff here IMHO. I'll check Daniel's work to understand how/if >>> it's better than menu governor. >> >> I still would like to see how the fast path without the C1 heuristic works. >> >> Fast

[PATCH 0/5] earlycon hang under some conditions

I was testing earlycon with 8250 dw serial console. And it hangs in these cases: 1/ kernel hang when calling early write function after free_initmem: a) the earlycon not disabled after the init code(due to keep_bootcon or not specify a real console to switch to) b) the early write func is

Re: [RFC][PATCH] drm: kirin: Restrict modes to known good mode clocks

On Mon, Jul 17, 2017 at 04:20:23PM -0700, John Stultz wrote: > On Tue, Jul 11, 2017 at 9:27 AM, Daniel Vetter wrote: > > On Tue, Jul 11, 2017 at 5:44 PM, John Stultz wrote: > >> On Tue, Jul 11, 2017 at 8:12 AM, Daniel Vetter wrote: > >>>

Re: [PATCH] kthread: Fix race condition between kthread_parkme() and kthread_unpark()

On Mon, 17 Jul 2017, Junaid Shahid wrote: > Hi, > > Has anyone been able to take a look at this? Yes. It's in my pile of stuff to look at.

[PATCH v3] Bluetooth: btusb: Fix memory leak in play_deferred

Currently we are calling usb_submit_urb directly to submit deferred tx urbs after unanchor them. So the usb_giveback_urb_bh would failed to unref it in usb_unanchor_urb and cause memory leak: unreferenced object 0xffc0ce0fa400 (size 256): ... backtrace: [] __save_stack_trace+0x48/0x6c

Re: WARN_ON_ONCE(work > weight) in napi_poll()

On 07/11/2017 06:19 PM, Igor Mitsyanko wrote: > On 07/11/2017 10:28 AM, Andrey Ryabinin wrote: >> >> It gave me this: >> >> [118648.825347] #1 quota too big 72 64 16 >> [118648.825351] #2 quota too big 72 64 16 >> [118648.825471] [ cut here ] >> [118648.825484] WARNING:

Re: [PATCH v7 1/1] f2fs: dax: implement direct access

On 2017/7/18 11:45, sunqiuyang wrote: > From: Qiuyang Sun > > This patch implements Direct Access (DAX) in F2FS, including: > - a mount option to choose whether to enable DAX or not > - read/write and mmap of regular files in the DAX way > - zero-out of unaligned partial

Re: [PATCH V3 1/5] drivers/fmc: remove unused variable

On Tue, Jul 18, 2017 at 08:32:42AM +0200, Alessandro Rubini wrote: > From: Federico Vaga > > Signed-off-by: Federico Vaga > Tested-by: Pat Riehecky > Acked-by: Alessandro Rubini > --- Again, I do not like to

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Mon, Jul 17, 2017 at 03:59:12PM -0600, Toshi Kani wrote: > The ghes_edac driver was introduced in 2013 [1], but it has not > been enabled by any distro yet. This driver obtains error info > from firmware interfaces, which are not properly implemented on > many platforms, as the driver always

[PATCH v5 3/3] dt-bindings: cpufreq: enhance MediaTek cpufreq dt-binding document

From: Sean Wang Update binding document with adding operating-points-v2 as the required property and the cooling level as the optional properties and adding more examples guiding people how to use MediaTek cpufreq driver for MediaTek SoCs. Signed-off-by: Sean Wang

[PATCH v5 2/3] dt-bindings: cpufreq: move MediaTek cpufreq dt-bindings document to proper place

From: Sean Wang The old place is Documentation/devicetree/bindings/clock/ that would let people hard to find how to use MediaTek cpufreq driver, so moving it to the appropriate place as other cpufreq drivers done would be better. Signed-off-by: Sean Wang

[PATCH v5 1/3] cpufreq: mediatek: Add support of cpufreq to MT2701/MT7623 SoC

From: Sean Wang MT2701/MT7623 is a 32-bit ARMv7 based quad-core (4 * Cortex-A7) with single cluster and this hardware is also compatible with the existing driver through enabling CPU frequency feature with operating-points-v2 bindings. Also, this driver actually supports

Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add tracepoints for oom reaper-related events)

* Sebastian Reichel [170717 04:52]: > Hi, > > On Mon, Jul 17, 2017 at 01:17:13PM +0200, Sebastian Reichel wrote: > > [dropping people from Cc] > > > > Hi, > > > > On Mon, Jul 17, 2017 at 03:19:28AM -0700, Tony Lindgren wrote: > > > * Sebastian Reichel

RE: [PATCH] arm64: defconfig: enable CONFIG_UNIPHIER_WATCHDOG

Hello Yamada-san, > From: Masahiro Yamada [mailto:yamada.masah...@socionext.com] > Sent: Tuesday, July 18, 2017 2:51 PM > Subject: Re: [PATCH] arm64: defconfig: enable CONFIG_UNIPHIER_WATCHDOG > > 2017-07-18 14:24 GMT+09:00 Keiji Hayashibara > : > > Enable the

Re: [PATCH] Stagung: rtl8188eu: core: fixd comment coding style issue in rtw_xmit.c

On Mon, Jul 17, 2017 at 10:53:21PM +0200, ArminSchoenlieb wrote: > From: Armin Schoenlieb > > This is a patch to the rtw_xmit.c file that fixes up a comment/80 character > warning found by the checkpatch.pl tool It's ironic that your changelog violates this same issue :(

[PATCH V3 5/5] drivers/fmc: carrier can program FPGA on registration

From: Federico Vaga The initial FPGA may require programming before it is useful. Signed-off-by: Federico Vaga Tested-by: Pat Riehecky Acked-by: Alessandro Rubini --- V3 (Alessandro): fixed From line in

[PATCH V3 2/5] drivers/fmc: hide fmc operations behind helpers

From: Federico Vaga This gave us more freedom to change/add/remove operations without recompiling all device driver. Typically, Carrier board implement the fmc operations, so they will not use these helpers. Signed-off-by: Federico Vaga Tested-by:

[PATCH V3 3/5] drivers/fmc: The only way to dump the SDB is from debugfs

From: Federico Vaga Driver should not call fmc_sdb_dump() anymore. (actually they can but the operation is not supported, so it will print an error message) Signed-off-by: Federico Vaga Tested-by: Pat Riehecky Acked-by:

ping/icmp sockets: define "sane".

The title is from this comment in net/ipv4: /* * Sane defaults - nobody may create ping sockets. * Boot scripts should set this to distro-specific group. */ So in 2011 you added ICMP sockets, but made it so nobody could use them without root performing a magic incatation at boot time.

[PATCH V3 1/5] drivers/fmc: remove unused variable

From: Federico Vaga Signed-off-by: Federico Vaga Tested-by: Pat Riehecky Acked-by: Alessandro Rubini --- V3 (Alessandro): fixed From line in patch, added alessandro's acked-by V2 (Pat): added Tested-by and

Re: [PATCH v2 2/8] exec: Move security_bprm_secureexec() earlier

On Mon, Jul 10, 2017 at 7:07 PM, Kees Cook wrote: > On Mon, Jul 10, 2017 at 10:18 AM, Eric W. Biederman > wrote: >> Kees Cook writes: >> >>> On Mon, Jul 10, 2017 at 1:57 AM, Eric W. Biederman >>> wrote:

Re: [PATCH v2 1/2] staging: gs_fpgaboot: add buffer overflow checks

On Mon, Jul 17, 2017 at 08:47:25PM -0400, Jacob von Chorus wrote: > Four fields in struct fpgaimage are char arrays of length MAX_STR (256). > The amount of data read into these buffers is controlled by a length > field in the bitstream file read from userspace. If a corrupt or > malicious

[PATCH v5 0/3] some fixups for MediaTek cpufreq driver

From: Sean Wang Changes since v4: - add back the missing Acked-by from v3 Changes since v3: - remove the redundant line depends on ARM || ARM64 || COMPILE_TEST since the whole Kconfig.arm file depends on ARM || ARM64. - renaming from mtk-cpufreq.c to mediatek-cpufreq.c

[PATCH 4/5] serial: 8250_ingenic: Remove __init marking from early write

The earlycon would be alive outside the init code in these cases: 1/ we have keep_bootcon in cmdline. 2/ we don't have a real console to switch to. So remove the __init marking to avoid invalid memory access. Signed-off-by: Jeffy Chen ---

[PATCH 5/5] serial: 8250_early: Remove __init marking from early write

The earlycon would be alive outside the init code in these cases: 1/ we have keep_bootcon in cmdline. 2/ we don't have a real console to switch to. So remove the __init marking to avoid invalid memory access. Signed-off-by: Jeffy Chen ---

[PATCH 3/5] serial: xuartps: Remove __init marking from early write

The earlycon would be alive outside the init code in these cases: 1/ we have keep_bootcon in cmdline. 2/ we don't have a real console to switch to. So remove the __init marking to avoid invalid memory access. Signed-off-by: Jeffy Chen ---

[PATCH 2/5] serial: omap: Remove __init marking from early write

The earlycon would be alive outside the init code in these cases: 1/ we have keep_bootcon in cmdline. 2/ we don't have a real console to switch to. So remove the __init marking to avoid invalid memory access. Signed-off-by: Jeffy Chen ---

[PATCH 1/5] serial: arc: Remove __init marking from early write

The earlycon would be alive outside the init code in these cases: 1/ we have keep_bootcon in cmdline. 2/ we don't have a real console to switch to. So remove the __init marking to avoid invalid memory access. Signed-off-by: Jeffy Chen ---

Re: [PATCH v7 12/13] ACPI / init: Invoke early ACPI initialization earlier

Hi, Zheng At 07/18/2017 01:18 PM, Zheng, Lv wrote: Hi, Can the problem be fixed by invoking acpi_put_table() for mapped DMAR table? Invoking acpi_put_table() is my first choice. But it made the kernel *panic* when we try to get the table again in intel_iommu_init() in late stage. I am also

[PATCH] efifb: allow user to disable write combined mapping.

This patch allows the user to disable write combined mapping of the efifb framebuffer console using an nowc option. A customer noticed major slowdowns while logging to the console with write combining enabled, on other tasks running on the same CPU. (10x or greater slow down on all other cores on

Re: fscrypt request_module() deadlock

On Fri, Jun 30, 2017 at 05:27:34PM +0200, Richard Weinberger wrote: > Hi! > > David and I faced a deadlock with switch_root when fscrypt was in use. > When /sbin/modprobe is encrypted using fscrypt and no other kernel component > requested an AES cipher before, first access to an encrypted file

Re: [PATCH v2] drm/i915: Consistently use enum pipe for PCH transcoders

On Mon, Jul 17, 2017 at 11:14:03AM -0700, Matthias Kaehlcke wrote: > The current code uses in some instances enum transcoder for PCH > transcoders and enum pipe in others. This is error prone and clang > raises warnings like this: > > drivers/gpu/drm/i915/intel_dp.c:3546:51: warning: implicit

Re: [PATCH v2 1/8] exec: Correct comments about "point of no return"

On Mon, Jul 10, 2017 at 10:07 AM, Eric W. Biederman wrote: > Kees Cook writes: > >> On Mon, Jul 10, 2017 at 1:46 AM, Eric W. Biederman >> wrote: >>> >>> But you miss it. >>> >>> The "point of no return" is the call to

Re: [PATCH v5 2/5] tick: Add freeze timer events

On Mon, 17 Jul 2017, dbasehore . wrote: > On Mon, Jul 17, 2017 at 6:33 PM, Rafael J. Wysocki wrote: > I could make a patch to try it out. I would probably add a flag to rtc > timers to indicate whether it wakes the system (default true). We > would have to add a sync with the

Re: [PATCH v2] staging: unisys: visorbus: Constify attribute_group structures.

On Tue, Jul 18, 2017 at 10:54:21AM +0530, Arvind Yadav wrote: > attribute_group are not supposed to change at runtime. All functions > working with attribute_group provided by work > with const attribute_group. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On Tue, Jul 18, 2017 at 08:43:53AM +0200, Thomas Gleixner wrote: > On Mon, 17 Jul 2017, Andi Kleen wrote: > > > > We need a tradeoff here IMHO. I'll check Daniel's work to understand > > > how/if > > > it's better than menu governor. > > > > I still would like to see how the fast path without

Re: [PATCH] staging: wlan-ng: Fix endianness warnings

On Wed, Jul 12, 2017 at 09:38:50PM +0100, alfonsolimaas...@gmail.com wrote: > From: Alfonso Lima Astor > > These variables were set to u16 and u32 although they always hold a little > endian value. > > This patch fixes multiple sparse warnings like: >

Re: [PATCH v3 1/1] Staging: android/ion: declare function static

On Sat, Jul 15, 2017 at 11:43:05AM +, Joseph Wright wrote: > Declare private function static to fix sparse warning: > > ion_cma_heap.c:109:5: warning: symbol '__ion_add_cma_heaps' \ > was not declared. Should it be static? > > Signed-off-by: Joseph Wright >

Re: [RFC PATCH 1/5] serial: arc: Remove __init marking from early write

Hi Greg, On 07/18/2017 01:08 PM, Greg KH wrote: On Tue, Jul 18, 2017 at 12:29:59PM +0800, Jeffy Chen wrote: The earlycon would be alive outside the init code in these cases: 1/ we have keep_bootcon in cmdline. 2/ we don't have a real console to switch to. So remove the __init marking to avoid

Re: [PATCH] x86/microcode: Document the three loading methods

Thanks for the nice write-up! A few comments below: On Mon, Jul 17, 2017 at 11:43:28AM +0200, Borislav Petkov wrote: > new file mode 100644 > index ..6ab130c6ca45 > --- /dev/null > +++ b/Documentation/x86/microcode.txt > @@ -0,0 +1,133 @@ > + The Linux Microcode Loader > + >

[PATCH] audit: fix memleak in auditd_send_unicast_skb.

From: Shu Wang Found this issue by kmemleak report, auditd_send_unicast_skb did not free skb if rcu_dereference(auditd_conn) returns null. unreferenced object 0x88082568ce00 (size 256): comm "auditd", pid 1119, jiffies 4294708499 backtrace: [] kmemleak_alloc+0x4a/0xa0 []

[PATCH v2] arm64: defconfig: enable CONFIG_UNIPHIER_WATCHDOG

Enable the watchdog driver for UniPhier SoC Signed-off-by: Keiji Hayashibara --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 6c7d147..629c815 100644 ---

Re: [PATCH v3] Bluetooth: btusb: Fix memory leak in play_deferred

Hi Oliver, > Currently we are calling usb_submit_urb directly to submit deferred tx > urbs after unanchor them. > > So the usb_giveback_urb_bh would failed to unref it in usb_unanchor_urb > and cause memory leak: > unreferenced object 0xffc0ce0fa400 (size 256): > ... > backtrace: >[]

[PATCH v2] PCI: dwc: designware: test PCIE_ATU_ENABLE bit to check enabled or not

The ATU CTRL2 register is 32 bit, besides the enable bit, other bits may also be set. To check whether the ATU is enabled or not, we should test the enable bit. Signed-off-by: Jisheng Zhang Acked-by: Joao Pinto --- Since v1: - Add Joao's Ack - Fix

Re: [PATCH 2/5] drm: vmwgfx: constify pci_device_id.

Thanks. Queued. On Sat, Jul 15, 2017 at 12:44:53PM +0530, Arvind Yadav wrote: > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > File size before: >text

[PATCH v1 0/2] drm/bridge/synopsys: dsi: Various cleanups

Version 1: - Initial commit The purpose of this set of patches is to clean up the mipi dsi dw Synopsys drm bridge. Philippe CORNU (2): drm/bridge/synopsys: dsi: Constify funcs structures drm/bridge/synopsys: dsi: Register list clean up drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 79

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