Re: [PATCH 05/11] drm/vc4: Add support for feeding DSI encoders from the pixel valve.

On Wed, Dec 14, 2016 at 11:46:15AM -0800, Eric Anholt wrote: > We have to set a different pixel format, which tells the hardware to > use the pix_width field that's fed in sideband from the DSI encoder to > divide the "pixel" clock. > > Signed-off-by: Eric Anholt > --- > drivers/gpu/drm/vc4/vc4_

Re: [PATCH] mtd: spi-nor: cqspi: remove redundant dead code on error return check

On 01/31/2017 04:53 PM, Colin King wrote: > From: Colin Ian King > > Checking for ret < 0 is redundant because a previous check on ret > being non-zero already handles the ret < 0 case. Remove the redundant > code. Found by CoverityScan, CID#1398863, CID#1398864 > > Signed-off-by: Colin Ian King

Re: [PATCH] HID: add Asus macrokey support for Asus "Republic of Gamers" laptop

Hi Benjamin, On Tue, Dec 13, 2016 at 2:16 AM, Benjamin Tissoires wrote: > On Dec 12 2016 or thereabouts, Chris Chiu wrote: >> ROG means ASUS "Republic of Gamers" laptops. The input device info >> also represents itself as "ASASTeK COMPUTER INC. ROG MacroKey". It >> uses special HID_USAGE code for

Re: [PATCH 1/2] gpio: Rename devm_get_gpiod_from_child()

On Tue, 31 Jan 2017 10:39:36 -0800 Dmitry Torokhov wrote: > On Tue, Jan 31, 2017 at 10:24:24AM +0100, Boris Brezillon wrote: > > On Tue, 31 Jan 2017 01:11:55 -0800 > > Dmitry Torokhov wrote: > > > > > On Tue, Jan 31, 2017 at 10:07:21AM +0100, Boris Brezillon wrote: > > > > On Tue, 31 Jan 20

[PATCH] gpio: dwapb: Add support for next generation of X-Gene SoC

Next generation of X-Gene SoC's GPIO hardware register map is very similar to DW GPIO. It only differs by a few register addresses. This patch modifies DW GPIO driver to accommodate the difference in a few register addresses. Signed-off-by: Hoan Tran --- drivers/gpio/gpio-dwapb.c | 84 ++

Re: [PATCH 04/11] drm/vc4: Set up SCALER_DISPCTRL at boot.

On Wed, Dec 14, 2016 at 11:46:14AM -0800, Eric Anholt wrote: > We want the HVS on, obviously, and we also want DSP3 (PV1's source) to > be muxed from HVS channel 2 like we expect in vc4_crtc.c. The > firmware wasn't setting the DSP3 mux up when both the LCD and HDMI > were disabled. > > Signed-of

[PATCH V2] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT

When the operating system is booted with the default ASPM policy (POLICY_DEFAULT), the current code is determining the ASPM policy set up by the BIOS by querying the enable/disable states from ASPM registers. In the case of hotplug removal, the ASPM registers get cleared by calling the pcie_aspm_e

[PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

I've been maintaining the bcm2835 branches here for a year or so. Signed-off-by: Eric Anholt --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 844835563ef8..64b281a7ff09 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2624,7 +2624,

Re: [PATCH] r8152: Allocate interrupt buffer as part of struct r8152

On Tue, 2017-01-31 at 11:06 -0800, Guenter Roeck wrote: > When unloading the r8152 driver using the 'unbind' sysfs attribute > in a system with KASAN enabled, the following error message is seen > on a regular basis. > > static int alloc_all_mem(struct r8152 *tp) > @@ -1423,10 +1420,6 @@ static

Re: [PATCH 05/11] drm/vc4: Add support for feeding DSI encoders from the pixel valve.

Daniel Vetter writes: > On Wed, Dec 14, 2016 at 11:46:15AM -0800, Eric Anholt wrote: >> We have to set a different pixel format, which tells the hardware to >> use the pix_width field that's fed in sideband from the DSI encoder to >> divide the "pixel" clock. >> >> Signed-off-by: Eric Anholt >>

Re: [PATCH] r8152: Allocate interrupt buffer as part of struct r8152

On Tue, 31 Jan 2017, Guenter Roeck wrote: > When unloading the r8152 driver using the 'unbind' sysfs attribute > in a system with KASAN enabled, the following error message is seen > on a regular basis. ... > The two-byte allocation in conjunction with code analysis suggests that > the interrupt

Re: [PATCH 07/11] drm/vc4: Add DSI driver

On Wed, Dec 14, 2016 at 11:46:17AM -0800, Eric Anholt wrote: > The DSI0 and DSI1 blocks on the 2835 are related hardware blocks. > Some registers move around, and the featureset is slightly different, > as DSI1 (the 4-lane DSI) is a later version of the hardware block. > This driver doesn't yet ena

[PATCH 1/1] Updated typo in help section

From: James Garcia --- drivers/rtc/Kconfig |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig index 5dc673d..2d94f81 100644 --- a/drivers/rtc/Kconfig +++ b/drivers/rtc/Kconfig @@ -1557,7 +1557,7 @@ config RTC_DRV_JZ4740 I

Applied "ASoC: davinci - Fix possible NULL derefrence." to the asoc tree

The patch ASoC: davinci - Fix possible NULL derefrence. has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to L

Applied "spi: When no dma_chan map buffers with spi_master's parent" to the spi tree

The patch spi: When no dma_chan map buffers with spi_master's parent has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Tue, 2017-01-31 at 14:28 -0500, Ken Goldman wrote: > On 1/30/2017 11:04 AM, James Bottomley wrote: > > > > This depends what your threat model is. For ssh keys, you worry > > that someone might be watching, so you use HMAC authority even for > > a local TPM. > > If someone can "watch" my loc

[PATCH] net: ethernet: ti: cpsw: fix NULL pointer dereference in switch mode

In switch mode on struct cpsw_slave->ndev field will be initialized with proper value only for the one cpsw slave port, as result cpsw_get_usage_count() will generate "Unable to handle kernel NULL pointer dereference" exception when first ethernet interface is opening cpsw_ndo_open(). This issue ca

Re: [PATCH 5/5] iio: stx104: Add GPIO set_multiple callback function support

On Sun, Jan 22, 2017 at 01:23:07PM +, Jonathan Cameron wrote: >On 19/01/17 15:06, William Breathitt Gray wrote: >> The Apex Embedded Systems STX104 series provides a digital output >> register where 4 lines may be set at a time. This patch add support for >> the set_multiple callback function,

Applied "regulator: s2mpa01: reduce stack size for probe function" to the regulator tree

The patch regulator: s2mpa01: reduce stack size for probe function has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "spi: mediatek: Only do dma for 4-byte aligned buffers" to the spi tree

The patch spi: mediatek: Only do dma for 4-byte aligned buffers has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

[PATCH 1/2] ARM: dts: i.MX25: add AIPS control registers

The i.MX25 contains two AHB to IP bridges (AIPS), each of which has a set of control registers. Add the memory regions for the control registers to the Device Tree. All the registers from the i.MX53 AIPSTZ are present on the i.MX25 as well. Indicate that we are compatible to fsl,imx53-aipstz. Howe

Re: [PATCH v3 1/7] drm: Add DRM support for tiny LCD displays

On Tue, Jan 31, 2017 at 07:01:10PM +0100, Noralf Trønnes wrote: > > Den 31.01.2017 17.23, skrev Daniel Vetter: > > On Tue, Jan 31, 2017 at 05:03:13PM +0100, Noralf Trønnes wrote: > > > tinydrm provides helpers for very simple displays that can use > > > CMA backed framebuffers and need flushing on

Re: [PATCH] Documentation/gpu: drm-mm.rst: fix formatting for struct vm_operations_struct

On Tue, Jan 31, 2017 at 05:41:09PM +, Liviu Dudau wrote: > drm-mm.rst contains some unformatted dump of the vm_operations_struct > structure. Add some C formatting around it and some context for the > dump. While there, update the structure to resemble the new signature > for the fault handler

Re: [PATCH v2 00/12] mm: page migration enhancement for thp

I am also doing some tests on THP migration and discover that there are some corner cases not handled in this patchset. For example, in handle_mm_fault, without taking pmd_lock, the kernel may see pmd_none(*pmd) during THP migrations, which leads to handle_pte_fault or even deeper in the code path

Re: [RFC] [PATCH] audit: log module name on init_module

On 2017-01-31 11:07, Paul Moore wrote: > On Tue, Jan 31, 2017 at 7:36 AM, Richard Guy Briggs wrote: > > On 2017-01-31 06:59, Paul Moore wrote: > >> On Thu, Jan 26, 2017 at 4:21 PM, Richard Guy Briggs > >> wrote: > >> > This adds a new auxiliary record MODULE_INIT to the SYSCALL event. > >> > > >

Re: [RFC 0/6]mm: add new LRU list for MADV_FREE pages

On Tue, Jan 31, 2017 at 01:59:49PM -0500, Johannes Weiner wrote: > Hi Shaohua, > > On Sun, Jan 29, 2017 at 09:51:17PM -0800, Shaohua Li wrote: > > We are trying to use MADV_FREE in jemalloc. Several issues are found. > > Without > > solving the issues, jemalloc can't use the MADV_FREE feature. >

Re: [PATCH 4.9 00/66] 4.9.7-stable review

On Tue, Jan 31, 2017 at 09:21:57AM -0800, Guenter Roeck wrote: > On Tue, Jan 31, 2017 at 06:36:04AM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.7 release. > > There are 66 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH v3 3/3] spi: acpi: Initialize modalias from of_compatible

On Mon, Jan 30, 2017 at 10:41:33AM +0100, Rafael J. Wysocki wrote: > On Mon, Jan 23, 2017 at 5:08 PM, Dan O'Donovan wrote: > Mark, any objections here? I've not looked yet, please allow a reasonable time for review (there still seemed to be ongoing discussion at the ACPI level). I continue to b

[PATCH 1/2] ACPI/IORT: add iort_get_memory_address_limit function

The memory_address_limit field present in IORT named component nodes describes the effective number of address bits that a device can use when accessing memory. Because this information has value when creating or validating device dma_masks, the aforementioned accessor function is introduced. Sign

[PATCH 2/2] arm64/dma-mapping: validate dma_masks against IORT defined limits

Some drivers set the dma_mask of client devices based solely on values read from capability registers which may not account for platform specific bus address width limitations. Fortunately, the ACPI IORT table provides a way to report the effective number of address bits a device can use to access

[PATCH v5 0/4] Introduce the initify gcc plugin

This is a continuation of Emese Revfy's initify plugin upstreaming, updated with various fixes from her github tree. Additionally, I split off the printf attribute fixes and sent those separately. This is the initify gcc plugin. The kernel already has a mechanism to free up code and data memory th

Re: [PATCH] PCI: ACPI: Fix ThunderX PEM initialization

On Tue, Jan 31, 2017 at 06:57:20AM -0800, Vadim Lomovtsev wrote: > On Tue, Jan 31, 2017 at 08:25:25AM -0600, Bjorn Helgaas wrote: > > On Tue, Jan 31, 2017 at 02:28:30AM -0800, Vadim Lomovtsev wrote: > > > Hi Bjorn, > > > > > > On Mon, Jan 30, 2017 at 03:12:37PM -0600, Bjorn Helgaas wrote: > > > >

[PATCH v5 3/4] initify: Mark functions with the __nocapture attribute

From: Emese Revfy The nocapture gcc attribute can be on functions only. The attribute takes zero or more signed integer constants as parameters that specify the function parameters to initify when the passed arguments are of const char* type. A negative attribute parameter value means that the c

[PATCH v5 4/4] initify: Mark functions with the __unverified_nocapture attribute

From: Emese Revfy The initify plugin attempts to analyze function arguments that have been marked correctly with the __nocapture attribute. However, due to code complexity, this is not always possible to verify. As a result, some __nocapture attributes need to be marked as excluded from the autom

[PATCH v5 1/4] gcc-plugins: Add the initify gcc plugin

From: Emese Revfy The kernel already has a mechanism to free up code and data memory that is only used during kernel or module initialization. This plugin will teach the compiler to find more such code and data that can be freed after initialization. The plugin runs in two passes. The first one

Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

On Tue, 2017-01-31 at 11:48 -0800, Eric Anholt wrote: > I've been maintaining the bcm2835 branches here for a year or so. > > Signed-off-by: Eric Anholt > --- >  MAINTAINERS | 2 +- >  1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 844835563ef8..6

kernel 4.10-rcx iio helper question

Hi, I find the latest kernel introduces new iio sys attributes. https://patchwork.kernel.org/patch/9391771/ https://patchwork.kernel.org/patch/9391259/ Is there anyone has some ideas about how the new iio sys attribute - in_pressure_scale_available works? I'm not sure if it's the regression iss

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On Tue, Jan 31, 2017 at 07:46:59PM +0200, Jarkko Sakkinen wrote: > On Mon, Jan 30, 2017 at 03:08:42PM +0530, Nayna wrote: > > > > > From: "Ken Goldman" > > > > > > Date: 26-Jan-2017 2:53 AM > > > Subject: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs > > >

Re: [PATCH v3 20/24] media: imx: Add Camera Interface subdev driver

On Tue, Jan 31, 2017 at 10:21:26AM -0800, Steve Longerbeam wrote: > On 01/31/2017 05:42 AM, Russell King - ARM Linux wrote: > >On Fri, Jan 20, 2017 at 03:38:28PM +0100, Hans Verkuil wrote: > >>Should be set to something like 'platform:imx-media-camif'. v4l2-compliance > >>should complain about this

Re: [PATCH 2/3] mmc: host: omap_hsmmc: use generic_cmd6_time to program timeout value for CMD6

On Tuesday 31 January 2017 03:42 PM, Ulf Hansson wrote: On 30 January 2017 at 11:11, Ravikumar Kattekola wrote: From: Kishon Vijay Abraham I commit e2bf08d643a244ccb ("omap_hsmmc: set a large data timeout for commands with busy signal") sets an arbitrary timeout value (100ms) for commands l

Re: [PATCH] tpm: fix a sparse error in tpm-sysfs.c

On Tue, Jan 31, 2017 at 01:43:59PM -0500, Stefan Berger wrote: > drivers/char/tpm/tpm-sysfs.c:161:25: warning: expression using sizeof bool > > Fixes: c659af78eb7b ("tpm: Check size of response before accessing data") > Signed-off-by: Stefan Berger > --- > drivers/char/tpm/tpm.h | 2 +- > 1 file

[PATCH/RESEND v3 0/5] z3fold: optimizations and fixes

This is a new take on z3fold optimizations/fixes consolidation, revised after comments from Dan ([1] - [6]). The coming patches are to be applied on top of the following commit: Author: zhong jiang Date: Tue Dec 20 11:53:40 2016 +1100 mm/z3fold.c: limit first_num to the actual range of p

[PATCH/RESEND v3 1/5] z3fold: make pages_nr atomic

This patch converts pages_nr per-pool counter to atomic64_t. Signed-off-by: Vitaly Wool --- mm/z3fold.c | 20 +--- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/mm/z3fold.c b/mm/z3fold.c index 207e5dd..2273789 100644 --- a/mm/z3fold.c +++ b/mm/z3fold.c @@ -80,7 +

[PATCH/RESEND v3 2/5] z3fold: fix header size related issues

Currently the whole kernel build will be stopped if the size of struct z3fold_header is greater than the size of one chunk, which is 64 bytes by default. This patch instead defines the offset for z3fold objects as the size of the z3fold header in chunks. Fixed also are the calculation of num_free_

[PATCH/RESEND v3 4/5] z3fold: use per-page spinlock

Most of z3fold operations are in-page, such as modifying z3fold page header or moving z3fold objects within a page. Taking per-pool spinlock to protect per-page objects is therefore suboptimal, and the idea of having a per-page spinlock (or rwlock) has been around for some time. This patch implem

Re: [PATCH] regulator: fixed: constify regulator_ops structure

On Sat, Jan 28, 2017 at 07:36:09PM +0530, Bhumika Goyal wrote: > Declare regulator_ops structure as const as it is only stored in the ops > field of a regulator_desc structure. This field is of type const, so > regulator_ops structures having this property can be made const too. Sorry, it's *this*

Re: [PATCH 1/1] MicroSemi Switchtec management interface driver

Hi Logan, NOTE: Please take my comments with a healthy pinch of salt. I'd imagine that core/more experienced developers have more thorough feedback, so I'll mention a few things on the less common part - robust/compat UABI. Above all, please read through the in-tree documentation on the topic [1]

[PATCH v5 2/4] util: Move type casts into is_kernel_rodata

From: Emese Revfy This moves type casts into the is_kernel_rodata() function itself so that parameters can be marked as "nocapture" in the coming initify gcc plugin. Signed-off-by: Emese Revfy [kees: expanded commit message] Signed-off-by: Kees Cook --- mm/util.c | 10 +- 1 file chang

[PATCH/RESEND v3 3/5] z3fold: extend compaction function

z3fold_compact_page() currently only handles the situation when there's a single middle chunk within the z3fold page. However it may be worth it to move middle chunk closer to either first or last chunk, whichever is there, if the gap between them is big enough. This patch adds the relevant code,

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On Wed, Feb 01, 2017 at 12:14:12AM +0530, Nayna wrote: > > I already sent my pull request to 4.11 and even today I found something > > fishy. You declared a function local array by using a variable in "tpm: > > enhance TPM 2.0 PCR extend to support multiple banks" (max_active_banks > > or something

[PATCH 1/3] auxdisplay: ht16k33: do not try to free fbdev

'fbdev' is allocated as part of larger ht16k33_priv structure; trying to free it will cause troubles. Signed-off-by: Dmitry Torokhov --- Note that the patches have not been tried on a real hardware. I am pretty confident in #1 and #3, but #2 is larger and it would be great if someone with hardw

[PATCH 3/3] auxdisplay: ht16k33: remove private workqueue

There is no need for the driver to user private workqueue, standard system workqueue should suffice as they going to use the same worker pool anyway. Signed-off-by: Dmitry Torokhov --- drivers/auxdisplay/ht16k33.c | 20 +--- 1 file changed, 5 insertions(+), 15 deletions(-) diff

[PATCH 2/3] auxdisplay: ht16k33: rework input device initialization

This patch fixes following issues in input device (keypad) handling: - requesting IRQ before allocating and initializing parts of the device that can be referenced from IRQ handler is racy, even if we try to disable interrupt after requesting it. Let's move allocations around so that everyth

Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

On 01/31/2017 12:32 PM, Michael Zoran wrote: > On Tue, 2017-01-31 at 11:48 -0800, Eric Anholt wrote: >> I've been maintaining the bcm2835 branches here for a year or so. >> >> Signed-off-by: Eric Anholt >> --- >> MAINTAINERS | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --gi

Re: [tpmdd-devel] [PATCH] tpm: fix a sparse error in tpm-interface.c

On Tue, Jan 31, 2017 at 11:10:41AM -0800, James Bottomley wrote: > On Tue, 2017-01-31 at 20:07 +0200, Jarkko Sakkinen wrote: > > drivers/char/tpm//tpm-interface.c:492:42: warning: bad assignment ( > > -=) > > to restricted __be32 > > > > Fixes: 0883743825e3 ("TPM: sysfs functions consolidation") >

[PATCH/RESEND v3 5/5] z3fold: add kref refcounting

With both coming and already present locking optimizations, introducing kref to reference-count z3fold objects is the right thing to do. Moreover, it makes buddied list no longer necessary, and allows for a simpler handling of headless pages. Signed-off-by: Vitaly Wool --- mm/z3fold.c | 151

Re: [PATCH 01/14] locking/atomic: import atomic_dec_not_zero()

> On 31 January 2017 at 20:17 Peter Zijlstra wrote: > > > On Tue, Jan 31, 2017 at 06:41:28PM +0100, Fabian Frederick wrote: > > > > > > > On 31 January 2017 at 11:41 Peter Zijlstra wrote: > > > > > > > > > On Mon, Jan 30, 2017 at 07:39:38PM +0100, Fabian Frederick wrote: > > > > complementary d

Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

On Tue, Jan 31, 2017 at 12:32:59PM -0800, Michael Zoran wrote: > On Tue, 2017-01-31 at 11:48 -0800, Eric Anholt wrote: > > diff --git a/MAINTAINERS b/MAINTAINERS > > index 844835563ef8..64b281a7ff09 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -2624,7 +2624,7 @@ M:Lee Jones > >  M

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On 01/31/2017 11:16 PM, Jarkko Sakkinen wrote: On Mon, Jan 30, 2017 at 03:08:42PM +0530, Nayna wrote: From: "Ken Goldman" mailto:kg...@linux.vnet.ibm.com>> Date: 26-Jan-2017 2:53 AM Subject: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log To: mailt

Re: [PATCH] regulator: palmas-regulator: constify regulator_ops structure

On Sat, Jan 28, 2017 at 08:23:55PM +0530, Bhumika Goyal wrote: > Declare regulator_ops structure as const as it is only stored in the ops > field of a regulator_desc structure. This field is of type const, so > regulator_ops structures having this property can be made const too. Please submit patc

Re: [PATCH] rtc: bq32000: add support to enable disable the trickle charge FET bypass.

On 27/01/2017 at 18:43:46 +0100, Enric Balletbo i Serra wrote: > The bq32000 includes a trickle charge circuit to maintain the charge of the > backup supply when a super capacitor is used. > > You can enable the charging circuit by setting 'trickle-resistor-ohms', > additionally you can set TCFE t

Re: [PATCH] [RFC] fs: Possible filp_open race experiment

On 01/31/2017 02:17 PM, Greg Kroah-Hartman wrote: > On Tue, Jan 31, 2017 at 01:58:14PM +0100, Christoph Hellwig wrote: >> On Tue, Jan 31, 2017 at 11:21:02AM +0100, Greg Kroah-Hartman wrote: >>> >>> -next isn't Linus's tree, sometimes stuff sits in there for years :) >>> >>> Anyway, if this is a con

Re: kernel 4.10-rcx iio helper question

On Tue, Jan 31, 2017 at 8:19 PM, Ken.Lin wrote: > Hi, > > I find the latest kernel introduces new iio sys attributes. > https://patchwork.kernel.org/patch/9391771/ > https://patchwork.kernel.org/patch/9391259/ > > Is there anyone has some ideas about how the new iio sys attribute - > in_pressure_

Re: kernel 4.10-rcx iio helper question

On 31 January 2017 18:19:12 GMT+00:00, "Ken.Lin" wrote: >Hi, > >I find the latest kernel introduces new iio sys attributes. >https://patchwork.kernel.org/patch/9391771/ >https://patchwork.kernel.org/patch/9391259/ > >Is there anyone has some ideas about how the new iio sys attribute - >in_press

[PATCH v2] iio: 104-quad-8: Add IRQ support for the ACCES 104-QUAD-8

The LSI/CSI LS7266R1 chip provides programmable output via the FLG pins. When interrupts are enabled on the ACCES 104-QUAD-8, they occur whenever FLG1 is active. Four functions are available for the FLG1 signal: /Carry, /Compare, /Carry/Borrow, and Index. /Carry: Interrupt

Re: remove the cmd_type field from struct request

On 01/31/2017 07:57 AM, Christoph Hellwig wrote: > Hi Jens, > > this series gets rid of the cmd_type field in struct request and > instead folds it into the REQ_OP* space. This reduces the size of > struct request, and leads to a single op namespace that drivers > can easily switch on. Except fo

Re: [PATCH 09/11] drm/panel: Add support for the Raspberry Pi 7" Touchscreen.

On Wed, Dec 14, 2016 at 11:46:19AM -0800, Eric Anholt wrote: [...] > diff --git a/drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c > b/drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c [...] > +/** > + * DOC: Raspberry Pi 7" touchscreen panel driver. > + * > + * The 7" touchscreen consist

Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

On Tue, 2017-01-31 at 12:55 -0800, Florian Fainelli wrote: > On 01/31/2017 12:32 PM, Michael Zoran wrote: > > On Tue, 2017-01-31 at 11:48 -0800, Eric Anholt wrote: > > > I've been maintaining the bcm2835 branches here for a year or so. > > > > > > Signed-off-by: Eric Anholt > > > --- > > >  MAINT

Re: remove the cmd_type field from struct request

On 01/31/2017 10:58 AM, Sergei Shtylyov wrote: > On 01/31/2017 09:51 PM, James Bottomley wrote: > [1] which were a pain in the ass to untangle and debug during development, it's really time for it to die.. >>> >>> Outside of the patch series in question, how to we expedite the >>> euthan

Re: [PATCH] rtc: sun6i: Fix compatibility with old DT binding

On 29/01/2017 at 18:13:43 +0800, Chen-Yu Tsai wrote: > Commit 847b8bf62eb4 ("rtc: sun6i: Expose the 32kHz oscillator") adds > a new clock for the rtc block with a 2 step probe mechanism. To share > the register region between both the clock and rtc instance, a static > pointer is used to keep the r

Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

> Eric Anholt hat am 31. Januar 2017 um 20:48 geschrieben: > > > I've been maintaining the bcm2835 branches here for a year or so. > > Signed-off-by: Eric Anholt FWIW Acked-by: Stefan Wahren

Applied "regulator: pcap-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: pcap-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "regulator: pcf50633-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: pcf50633-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the n

Applied "regulator: ltc3589: constify regulator_ops structure" to the regulator tree

The patch regulator: ltc3589: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hour

Applied "regulator: hi655x-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: hi655x-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the nex

Applied "regulator: arizona-micsupp: constify regulator_ops structure" to the regulator tree

The patch regulator: arizona-micsupp: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "regulator: max77686-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: max77686-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the n

Applied "regulator: lp8755: constify regulator_ops structure" to the regulator tree

The patch regulator: lp8755: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours

Applied "regulator: ad5398: constify regulator_ops structure" to the regulator tree

The patch regulator: ad5398: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours

Applied "regulator: aat2870-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: aat2870-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the ne

Applied "spi: fix device-node leaks" to the spi tree

The patch spi: fix device-node leaks has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next m

Applied "regulator: anatop-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: anatop-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the nex

Applied "regulator: arizona-ldo1: constify regulator_ops structure" to the regulator tree

The patch regulator: arizona-ldo1: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: 88pm800: constify regulator_ops structures" to the regulator tree

The patch regulator: 88pm800: constify regulator_ops structures has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hou

Applied "regulator: 88pm8607: constify regulator_ops structure" to the regulator tree

The patch regulator: 88pm8607: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hou

Applied "regulator: act8945a-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: act8945a-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the n

Applied "regulator: as3711-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: as3711-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the nex

Re: [PATCH 09/11] drm/panel: Add support for the Raspberry Pi 7" Touchscreen.

On Tue, Jan 31, 2017 at 10:07:19PM +0100, Thierry Reding wrote: > On Wed, Dec 14, 2016 at 11:46:19AM -0800, Eric Anholt wrote: > > +static int rpi_touchscreen_dsi_remove(struct mipi_dsi_device *dsi) > > +{ > > + struct device *dev = &dsi->dev; > > + struct rpi_touchscreen *ts = dev_get_drvdata(

Applied "regulator: fan53555: constify regulator_ops structure" to the regulator tree

The patch regulator: fan53555: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hou

Applied "regulator: bcm590xx-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: bcm590xx-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the n

Applied "regulator: axp20x-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: axp20x-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the nex

Applied "regulator: ltc3676: constify regulator_ops structure" to the regulator tree

The patch regulator: ltc3676: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hour

Re: [PATCH v6 5/5] leds: lm3533: Support initialization from Device Tree

Hi Bjorn, Thanks for the patch. On 01/30/2017 10:17 PM, Bjorn Andersson wrote: > From: Bjorn Andersson > > Implement support for initialization of the lm3533 LED driver from > Device Tree. > > Signed-off-by: Bjorn Andersson > Signed-off-by: Bjorn Andersson > --- > > Note that this patch can

Re: [PATCH v8 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On Tue, Jan 31, 2017 at 10:49:51AM -0500, Sean Paul wrote: > On Tue, Jan 31, 2017 at 04:02:26PM +0100, Thierry Reding wrote: > > On Tue, Jan 31, 2017 at 09:38:53AM -0500, Sean Paul wrote: > > > On Tue, Jan 31, 2017 at 09:54:49AM +0100, Thierry Reding wrote: > > > > On Tue, Jan 31, 2017 at 09:01:07A

Applied "regulator: max14577-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: max14577-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the n

Applied "regulator: max77620-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: max77620-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the n

Applied "regulator: rc5t583-regulator: constify regulator_ops structure" to the regulator tree

The patch regulator: rc5t583-regulator: constify regulator_ops structure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the ne

FYI, The cause of the remaining lost wakeups

Hello, Peter, So I mentioned a few months ago that I was still seeing lost wakeups. I found the cause, which was of course my own stupidity. If call_rcu() is invoked with interrupts disabled on a callback-offloaded (NOCB) CPU, the wakeup of the corresponding rcuo kthread must be deferred, because

Re: [PATCH] regulator: gpio-regulator: constify regulator_ops structure

On Sat, Jan 28, 2017 at 07:38:55PM +0530, Bhumika Goyal wrote: > Declare regulator_ops structure as const as it is only stored in the ops > field of a regulator_desc structure. This field is of type const, so > regulator_ops structures having this property can be made const too. This still doesn't

Re: [PATCH 14/14] ASoC: sunxi: simplify optional reset handling

On Mon, Jan 30, 2017 at 12:41:16PM +0100, Philipp Zabel wrote: > As of commit bb475230b8e5 ("reset: make optional functions really > optional"), the reset framework API calls use NULL pointers to describe > optional, non-present reset controls. Acked-by: Mark Brown signature.asc Description: PG

<    2   3   4   5   6   7   8   9   >