[PATCH v12 PATCH 4/5] Documentation: bindings: add dt documentation for cdn DP controller

This patch adds a binding that describes the cdn DP controller for rk3399. Signed-off-by: Chris Zhong Acked-by: Rob Herring --- Changes in v12: None Changes in v11: - refer dp phy Changes in v10: - add pclk_vio_grf clock Changes in v9: - modify the reference phy = < 0>, < 0>; Changes in

[PATCH v12 PATCH 3/5] arm64: dts: rockchip: add Type-C phy for RK3399

There are 2 Type-C phy on RK3399, they are almost same, except the address of register. They support USB3.0 Type-C and DisplayPort1.3 Alt Mode on USB Type-C. Register a phy, supply it to USB3 controller and DP controller. Signed-off-by: Chris Zhong Reviewed-by: Guenter Roeck --- Changes in

Re: [PATCH] iio: adc: rockchip_saradc: Explicitly disable ADC on probe

Hi Jonathan, On Mon, Aug 15, 2016 at 07:04:31PM +0100, Jonathan Cameron wrote: > On 26/07/16 04:22, Guenter Roeck wrote: > > On 07/25/2016 07:51 PM, Caesar Wang wrote: > >> Hi Guenter, > >> > >> Thanks for fixing it. > >> > >> On 2016年07月26日 03:39, Guenter Roeck wrote: > >>> If the ADC is read

Re: [PATCH] iio: adc: rockchip_saradc: Explicitly disable ADC on probe

Hi Jonathan, On Mon, Aug 15, 2016 at 07:04:31PM +0100, Jonathan Cameron wrote: > On 26/07/16 04:22, Guenter Roeck wrote: > > On 07/25/2016 07:51 PM, Caesar Wang wrote: > >> Hi Guenter, > >> > >> Thanks for fixing it. > >> > >> On 2016年07月26日 03:39, Guenter Roeck wrote: > >>> If the ADC is read

Re: [PATCH v2] perf symbols: Fix annotation of objects with debuginfo files

Em Mon, Aug 15, 2016 at 03:13:47PM +0800, Wangnan (F) escreveu: > > > On 2016/8/13 9:55, Anton Blanchard wrote: > > From: Anton Blanchard > > > > Commit 73cdf0c6ea9c ("perf symbols: Record text offset in dso > > to calculate objdump address") started storing the offset of > >

Re: [PATCH v2] perf symbols: Fix annotation of objects with debuginfo files

Em Mon, Aug 15, 2016 at 03:13:47PM +0800, Wangnan (F) escreveu: > > > On 2016/8/13 9:55, Anton Blanchard wrote: > > From: Anton Blanchard > > > > Commit 73cdf0c6ea9c ("perf symbols: Record text offset in dso > > to calculate objdump address") started storing the offset of > > the text section

[PATCH v2 1/3] radix-tree: 'slot' can be NULL in radix_tree_next_slot()

There are four cases I can see where we could end up with a NULL 'slot' in radix_tree_next_slot(). Yet radix_tree_next_slot() never actually checks whether 'slot' is NULL. It just happens that for the cases where 'slot' is NULL, some other combination of factors prevents us from dereferencing

Re: [PATCH V4 1/1] iio: as6200: add AS6200 temperature sensor driver from ams AG

On Mon, Aug 15, 2016 at 06:25:44PM +0100, Jonathan Cameron wrote: > On 04/08/16 09:35, Florian Lobmaier wrote: > > Hello Peter, > > > > Thanks again for your valuable feedback. We use now IIO_EV_THRESH to > > set high and low limits for temperature. Also removed all the custom > > ABI as this are

Re: [PATCH V4 1/1] iio: as6200: add AS6200 temperature sensor driver from ams AG

On Mon, Aug 15, 2016 at 06:25:44PM +0100, Jonathan Cameron wrote: > On 04/08/16 09:35, Florian Lobmaier wrote: > > Hello Peter, > > > > Thanks again for your valuable feedback. We use now IIO_EV_THRESH to > > set high and low limits for temperature. Also removed all the custom > > ABI as this are

[PATCH v2 1/3] radix-tree: 'slot' can be NULL in radix_tree_next_slot()

There are four cases I can see where we could end up with a NULL 'slot' in radix_tree_next_slot(). Yet radix_tree_next_slot() never actually checks whether 'slot' is NULL. It just happens that for the cases where 'slot' is NULL, some other combination of factors prevents us from dereferencing

[PATCH v2 2/3] radix-tree tests: add iteration test

There are four cases I can see where we could end up with a NULL 'slot' in radix_tree_next_slot(). This unit test exercises all four of them, making sure that if in the future we have an unsafe path through radix_tree_next_slot(), we'll catch it. Here are details on the four cases: 1)

[PATCH v2 2/3] radix-tree tests: add iteration test

There are four cases I can see where we could end up with a NULL 'slot' in radix_tree_next_slot(). This unit test exercises all four of them, making sure that if in the future we have an unsafe path through radix_tree_next_slot(), we'll catch it. Here are details on the four cases: 1)

[PATCH v2 3/3] radix-tree tests: properly initialize mutex

The pthread_mutex_t in regression1.c wasn't being initialized properly. Signed-off-by: Ross Zwisler --- tools/testing/radix-tree/regression1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/radix-tree/regression1.c

[PATCH v2 0/3] 'slot' can be NULL in radix_tree_next_slot()

This adds comments above radix_tree_next_slot() documenting the combination of factors that prevent us from dereferencing a NULL 'slot' pointer. It also adds a radix tree unit test so that we can easily catch any unhandled NULL pointer issues with radix_tree_next_slot(). Changes from V1: -

[PATCH v2 3/3] radix-tree tests: properly initialize mutex

The pthread_mutex_t in regression1.c wasn't being initialized properly. Signed-off-by: Ross Zwisler --- tools/testing/radix-tree/regression1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/radix-tree/regression1.c b/tools/testing/radix-tree/regression1.c

[PATCH v2 0/3] 'slot' can be NULL in radix_tree_next_slot()

This adds comments above radix_tree_next_slot() documenting the combination of factors that prevent us from dereferencing a NULL 'slot' pointer. It also adds a radix tree unit test so that we can easily catch any unhandled NULL pointer issues with radix_tree_next_slot(). Changes from V1: -

[PATCH] usb: dwc3: gadget: don't rely on jiffies while holding spinlock

__dwc3_gadget_wakeup() is called while holding a spinlock, then depends on jiffies in order to timeout while polling the USB core for a link state update. In the case the wakeup failed, the timeout will never happen and will also cause the cpu to stall until rcu_preempt kicks in. This switches to

[PATCH] usb: dwc3: gadget: don't rely on jiffies while holding spinlock

__dwc3_gadget_wakeup() is called while holding a spinlock, then depends on jiffies in order to timeout while polling the USB core for a link state update. In the case the wakeup failed, the timeout will never happen and will also cause the cpu to stall until rcu_preempt kicks in. This switches to

Re: [PATCH] USB: core: of: Check device_node before parsing in usb_of_get_child_node()

On Mon, 15 Aug 2016, Greg KH wrote: > On Mon, Aug 15, 2016 at 11:31:10AM -0700, Vaibhav Hiremath wrote: > > In case of HUB devices connected to USB ports, we may not have DT > > node representing it inside USB, and when devices connected to hub > > gets enumerated, call to usb_of_get_child_node()

Re: [PATCH] USB: core: of: Check device_node before parsing in usb_of_get_child_node()

On Mon, 15 Aug 2016, Greg KH wrote: > On Mon, Aug 15, 2016 at 11:31:10AM -0700, Vaibhav Hiremath wrote: > > In case of HUB devices connected to USB ports, we may not have DT > > node representing it inside USB, and when devices connected to hub > > gets enumerated, call to usb_of_get_child_node()

[PATCH 2/2] staging: lustre: Remove .. paths from '#include "' uses

Make the include paths a bit easier to find and more compatible to a future move out of the staging tree. Signed-off-by: Joe Perches --- drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h | 6 +++--- drivers/staging/lustre/lnet/klnds/socklnd/socklnd.h | 8

[PATCH 2/2] staging: lustre: Remove .. paths from '#include "' uses

Make the include paths a bit easier to find and more compatible to a future move out of the staging tree. Signed-off-by: Joe Perches --- drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h | 6 +++--- drivers/staging/lustre/lnet/klnds/socklnd/socklnd.h | 8

[PATCH 0/2] staging: lustre: #include neatening

Make it a bit easier to grep and help a future move out of staging. Joe Perches (2): staging: lustre: Add include path to Makefile staging: lustre: Remove .. paths from '#include "' uses drivers/staging/lustre/Makefile | 3 +++

[PATCH 0/2] staging: lustre: #include neatening

Make it a bit easier to grep and help a future move out of staging. Joe Perches (2): staging: lustre: Add include path to Makefile staging: lustre: Remove .. paths from '#include "' uses drivers/staging/lustre/Makefile | 3 +++

[PATCH 1/2] staging: lustre: Add include path to Makefile

Start to rationalize include paths in source code files. Signed-off-by: Joe Perches --- drivers/staging/lustre/Makefile | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/staging/lustre/Makefile b/drivers/staging/lustre/Makefile index 95ffe33..9d00237 100644 ---

[PATCH 1/2] staging: lustre: Add include path to Makefile

Start to rationalize include paths in source code files. Signed-off-by: Joe Perches --- drivers/staging/lustre/Makefile | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/staging/lustre/Makefile b/drivers/staging/lustre/Makefile index 95ffe33..9d00237 100644 ---

[PATCH v4 08/13] media: platform: pxa_camera: add buffer sequencing

Add sequence numbers to completed buffers. Signed-off-by: Robert Jarzmik --- Since v3: reset buffer sequence number in start_streaming() --- drivers/media/platform/soc_camera/pxa_camera.c | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH v4 09/13] media: platform: pxa_camera: remove set_crop

This is to be seen as a regression as the set_crop function is removed. This is a temporary situation in the v4l2 porting, and will have to be added later. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 76 -- 1

[PATCH v4 08/13] media: platform: pxa_camera: add buffer sequencing

Add sequence numbers to completed buffers. Signed-off-by: Robert Jarzmik --- Since v3: reset buffer sequence number in start_streaming() --- drivers/media/platform/soc_camera/pxa_camera.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/media/platform/soc_camera/pxa_camera.c

[PATCH v4 09/13] media: platform: pxa_camera: remove set_crop

This is to be seen as a regression as the set_crop function is removed. This is a temporary situation in the v4l2 porting, and will have to be added later. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 76 -- 1 file changed, 76

[PATCH v2] regulator: Add LTC3676 support

This patch adds support for the Linear Technology LTC3676 8-output I2C voltage regulator IC. Cc: Jaffer Kapasi Signed-off-by: Tim Harvey --- v2: - use kernel coding style for switch statements - change over-temp warning to dev_warn - explicitly

[PATCH v2] regulator: Add LTC3676 support

This patch adds support for the Linear Technology LTC3676 8-output I2C voltage regulator IC. Cc: Jaffer Kapasi Signed-off-by: Tim Harvey --- v2: - use kernel coding style for switch statements - change over-temp warning to dev_warn - explicitly handle all modes for suspend_mode - use the

sched: current instead rq->current

Hello, At the beginning of __schedule (kernel/sched/core.c), the current task is get with rq->curr. I try to to understand why not directly using current instead? Since a runqueue is specific to a CPU, it dosen't make sense to get the the current task of another CPU's runqueue. Yes? I try the

sched: current instead rq->current

Hello, At the beginning of __schedule (kernel/sched/core.c), the current task is get with rq->curr. I try to to understand why not directly using current instead? Since a runqueue is specific to a CPU, it dosen't make sense to get the the current task of another CPU's runqueue. Yes? I try the

Re: [PATCH] power:bq27xxx: 27000/10 read FLAGS register as single

Hi, On Mon, Jul 18, 2016 at 06:12:09PM +0200, H. Nikolaus Schaller wrote: > The bq27000 and bq27010 have a single byte FLAGS register. > Other gauges have 16 bit FLAGS registers. > > For reading the FLAGS register it is sufficient to read the single > register instead of reading RSOC at the next

Re: [PATCH] power:bq27xxx: 27000/10 read FLAGS register as single

Hi, On Mon, Jul 18, 2016 at 06:12:09PM +0200, H. Nikolaus Schaller wrote: > The bq27000 and bq27010 have a single byte FLAGS register. > Other gauges have 16 bit FLAGS registers. > > For reading the FLAGS register it is sufficient to read the single > register instead of reading RSOC at the next

[PATCH] EDAC, mpc85xx: Fix PCIe error capture

According to the reference manual of MPC8572 and T4240, bit 31 of PEX_ERR_CAP_STAT is W1C (write 1 to clear). This patch adds the corresponding write to PEX_ERR_CAP_STAT in order to fix the PCIe error capture. Tested on a T4240 processor. Signed-off-by: Tillmann Heidsieck

[PATCH] EDAC, mpc85xx: Fix PCIe error capture

According to the reference manual of MPC8572 and T4240, bit 31 of PEX_ERR_CAP_STAT is W1C (write 1 to clear). This patch adds the corresponding write to PEX_ERR_CAP_STAT in order to fix the PCIe error capture. Tested on a T4240 processor. Signed-off-by: Tillmann Heidsieck ---

Re: [PATCH v3 16/51] x86/32: put real return address on stack in entry code

On 08/15/16 11:25, Josh Poimboeuf wrote: > On Mon, Aug 15, 2016 at 11:04:42AM -0700, H. Peter Anvin wrote: >> On 08/15/16 08:09, Josh Poimboeuf wrote: >>> On Sun, Aug 14, 2016 at 12:31:47AM -0700, Andy Lutomirski wrote: On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf

Re: [PATCH v3 16/51] x86/32: put real return address on stack in entry code

On 08/15/16 11:25, Josh Poimboeuf wrote: > On Mon, Aug 15, 2016 at 11:04:42AM -0700, H. Peter Anvin wrote: >> On 08/15/16 08:09, Josh Poimboeuf wrote: >>> On Sun, Aug 14, 2016 at 12:31:47AM -0700, Andy Lutomirski wrote: On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf wrote: > This

Re: [PATCH] USB: core: of: Check device_node before parsing in usb_of_get_child_node()

On Monday 15 August 2016 11:41 AM, Greg KH wrote: On Mon, Aug 15, 2016 at 11:31:10AM -0700, Vaibhav Hiremath wrote: In case of HUB devices connected to USB ports, we may not have DT node representing it inside USB, and when devices connected to hub gets enumerated, call to

Re: [PATCH] USB: core: of: Check device_node before parsing in usb_of_get_child_node()

On Monday 15 August 2016 11:41 AM, Greg KH wrote: On Mon, Aug 15, 2016 at 11:31:10AM -0700, Vaibhav Hiremath wrote: In case of HUB devices connected to USB ports, we may not have DT node representing it inside USB, and when devices connected to hub gets enumerated, call to

Re: [PATCH stable-4.4 1/3] mm: memcontrol: fix cgroup creation failure after many small jobs

On Mon, Aug 15, 2016 at 05:35:17PM +0200, Michal Hocko wrote: > Updated patch Thanks for this, and the updated patch series, I've now replaced the previous versions with this series. greg k-h

Re: [PATCH stable-4.4 1/3] mm: memcontrol: fix cgroup creation failure after many small jobs

On Mon, Aug 15, 2016 at 05:35:17PM +0200, Michal Hocko wrote: > Updated patch Thanks for this, and the updated patch series, I've now replaced the previous versions with this series. greg k-h

[PATCH v2 2/8] dt-bindings: i2c: add support for 'i2c-arb' subnode

This gets rid of the need for a pointless 'reg' property for i2c arbitrators. I.e. this new and more compact style some-arbitrator { i2c-arb { #address-cells = <1>; #size-cells = <0>;

[PATCH v2 2/8] dt-bindings: i2c: add support for 'i2c-arb' subnode

This gets rid of the need for a pointless 'reg' property for i2c arbitrators. I.e. this new and more compact style some-arbitrator { i2c-arb { #address-cells = <1>; #size-cells = <0>;

[PATCH v2 1/8] dt-bindings: i2c: add support for 'i2c-mux' subnode

Similar to the new optional 'i2c-bus' subnode from Jon Hunter, this adds an optional 'i2c-mux' subnode, for similar reasons. I.e. it is bad of the i2c mux core to assume that any subnode of an i2c mux device is a potential (when the 'reg' property matches) i2c-mux child bus, given that i2c mux

[PATCH v2 1/8] dt-bindings: i2c: add support for 'i2c-mux' subnode

Similar to the new optional 'i2c-bus' subnode from Jon Hunter, this adds an optional 'i2c-mux' subnode, for similar reasons. I.e. it is bad of the i2c mux core to assume that any subnode of an i2c mux device is a potential (when the 'reg' property matches) i2c-mux child bus, given that i2c mux

[PATCH 2/7] ext4: tell DAX the size of allocation holes

When DAX calls _ext4_get_block() and the file offset points to a hole we currently don't set bh->b_size. When we re-enable PMD faults DAX will need bh->b_size to tell it the size of the hole so it can decide whether to fault in a 4 KiB zero page or a 2 MiB zero page. _ext4_get_block() has the

[PATCH 2/7] ext4: tell DAX the size of allocation holes

When DAX calls _ext4_get_block() and the file offset points to a hole we currently don't set bh->b_size. When we re-enable PMD faults DAX will need bh->b_size to tell it the size of the hole so it can decide whether to fault in a 4 KiB zero page or a 2 MiB zero page. _ext4_get_block() has the

[PATCH 7/7] dax: remove "depends on BROKEN" from FS_DAX_PMD

Now that DAX PMD faults are once again working and are now participating in DAX's radix tree locking scheme, allow their config option to be enabled. Signed-off-by: Ross Zwisler --- fs/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/Kconfig

Re: [PATCH v3] block: make sure big bio is splitted into at most 256 bvecs

On Mon, Aug 15, 2016 at 11:23:28AM -0700, Christoph Hellwig wrote: > On Mon, Aug 15, 2016 at 11:11:22PM +0800, Ming Lei wrote: > > After arbitrary bio size is supported, the incoming bio may > > be very big. We have to split the bio into small bios so that > > each holds at most BIO_MAX_PAGES

[PATCH 7/7] dax: remove "depends on BROKEN" from FS_DAX_PMD

Now that DAX PMD faults are once again working and are now participating in DAX's radix tree locking scheme, allow their config option to be enabled. Signed-off-by: Ross Zwisler --- fs/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/Kconfig b/fs/Kconfig index 2bc7ad7..b6f0fce

Re: [PATCH v3] block: make sure big bio is splitted into at most 256 bvecs

On Mon, Aug 15, 2016 at 11:23:28AM -0700, Christoph Hellwig wrote: > On Mon, Aug 15, 2016 at 11:11:22PM +0800, Ming Lei wrote: > > After arbitrary bio size is supported, the incoming bio may > > be very big. We have to split the bio into small bios so that > > each holds at most BIO_MAX_PAGES

Re: commit 444d13ff10f introduced boot failure on s390x

+++ Jessica Yu [10/08/16 18:58 -0400]: +++ Eryu Guan [10/08/16 23:21 +0800]: Hi, I hit boot failure on s390x host starting from 4.8-rc1 kernel, 4.7 kernel works fine. And I bisected to this commit 444d13ff10fb commit 444d13ff10fb13bc3e64859c3cf9ce43dcfeb075 Author: Jessica Yu

[PATCH 5/7] dax: lock based on slot instead of [mapping, index]

DAX radix tree locking currently locks entries based on the unique combination of the 'mapping' pointer and the pgoff_t 'index' for the entry. This works for PTEs, but as we move to PMDs we will need to have all the offsets within the range covered by the PMD to map to the same bit lock. To

Re: commit 444d13ff10f introduced boot failure on s390x

+++ Jessica Yu [10/08/16 18:58 -0400]: +++ Eryu Guan [10/08/16 23:21 +0800]: Hi, I hit boot failure on s390x host starting from 4.8-rc1 kernel, 4.7 kernel works fine. And I bisected to this commit 444d13ff10fb commit 444d13ff10fb13bc3e64859c3cf9ce43dcfeb075 Author: Jessica Yu Date:

[PATCH 5/7] dax: lock based on slot instead of [mapping, index]

DAX radix tree locking currently locks entries based on the unique combination of the 'mapping' pointer and the pgoff_t 'index' for the entry. This works for PTEs, but as we move to PMDs we will need to have all the offsets within the range covered by the PMD to map to the same bit lock. To

[PATCH 1/7] ext2: tell DAX the size of allocation holes

When DAX calls ext2_get_block() and the file offset points to a hole we currently don't set bh_result->b_size. When we re-enable PMD faults DAX will need bh_result->b_size to tell it the size of the hole so it can decide whether to fault in a 4 KiB zero page or a 2 MiB zero page. For ext2 we

[PATCH 1/7] ext2: tell DAX the size of allocation holes

When DAX calls ext2_get_block() and the file offset points to a hole we currently don't set bh_result->b_size. When we re-enable PMD faults DAX will need bh_result->b_size to tell it the size of the hole so it can decide whether to fault in a 4 KiB zero page or a 2 MiB zero page. For ext2 we

[PATCH v4 06/13] media: platform: pxa_camera: introduce sensor_call

Introduce sensor_call(), which will be used for all sensor invocations. This is a preparation move to v4l2 device conversion, ie. soc_camera adherence removal. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 27

[PATCH v4 06/13] media: platform: pxa_camera: introduce sensor_call

Introduce sensor_call(), which will be used for all sensor invocations. This is a preparation move to v4l2 device conversion, ie. soc_camera adherence removal. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 27 ++ 1 file changed, 15

[PATCH 6/7] dax: re-enable DAX PMD support

DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based locking. This patch allows DAX PMDs to participate in the DAX radix tree based locking scheme so that they can be re-enabled. There are currently three types of DAX 4k entries: 4k zero pages, 4k DAX mappings that have an

[PATCH 6/7] dax: re-enable DAX PMD support

DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based locking. This patch allows DAX PMDs to participate in the DAX radix tree based locking scheme so that they can be re-enabled. There are currently three types of DAX 4k entries: 4k zero pages, 4k DAX mappings that have an

[PATCH 4/7] dax: rename 'ret' to 'entry' in grab_mapping_entry

No functional change. Everywhere else that we get entries via get_unlocked_mapping_entry(), we save it in 'entry' variables. Just change this to be more descriptive. Signed-off-by: Ross Zwisler --- fs/dax.c | 20 ++-- 1 file changed, 10

Re: [PATCH v1 01/14] clk: twl6040: Correct clk_ops

On 05/30, Peter Ujfalusi wrote: > Since the drover only supports prepare callbacks, the use of is_enabled is > not correct, it should be handling is_prepared. > > Signed-off-by: Peter Ujfalusi > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of

Re: [PATCH v1 03/14] clk: twl6040: Rename the driver and use consistent names in the code

On 05/30, Peter Ujfalusi wrote: > The driver is to provide the functional clock to OMAP4/5 McPDM. The clock > is named as pdmclk in the documentations so change the function names, > structure names and variables to align with this. > At the same time rename the driver from "twl6040-clk" to

[PATCH 0/7] re-enable DAX PMD support

DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based locking. This series allows DAX PMDs to participate in the DAX radix tree based locking scheme so that they can be re-enabled. This series restores DAX PMD functionality back to what it was before it was disabled. There

Re: [PATCH v1 03/14] clk: twl6040: Rename the driver and use consistent names in the code

On 05/30, Peter Ujfalusi wrote: > The driver is to provide the functional clock to OMAP4/5 McPDM. The clock > is named as pdmclk in the documentations so change the function names, > structure names and variables to align with this. > At the same time rename the driver from "twl6040-clk" to

[PATCH 0/7] re-enable DAX PMD support

DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based locking. This series allows DAX PMDs to participate in the DAX radix tree based locking scheme so that they can be re-enabled. This series restores DAX PMD functionality back to what it was before it was disabled. There

[PATCH 4/7] dax: rename 'ret' to 'entry' in grab_mapping_entry

No functional change. Everywhere else that we get entries via get_unlocked_mapping_entry(), we save it in 'entry' variables. Just change this to be more descriptive. Signed-off-by: Ross Zwisler --- fs/dax.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff

Re: [PATCH v1 01/14] clk: twl6040: Correct clk_ops

On 05/30, Peter Ujfalusi wrote: > Since the drover only supports prepare callbacks, the use of is_enabled is > not correct, it should be handling is_prepared. > > Signed-off-by: Peter Ujfalusi > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a

[PATCH 3/7] dax: remove buffer_size_valid()

Now that all our supported filesystems (ext2, ext4 and XFS) all properly set bh.b_size when we call get_block() for a hole, rely on that value and remove the buffer_size_valid() sanity check. Signed-off-by: Ross Zwisler --- fs/dax.c | 22 +- 1

[PATCH 3/7] dax: remove buffer_size_valid()

Now that all our supported filesystems (ext2, ext4 and XFS) all properly set bh.b_size when we call get_block() for a hole, rely on that value and remove the buffer_size_valid() sanity check. Signed-off-by: Ross Zwisler --- fs/dax.c | 22 +- 1 file changed, 1 insertion(+),

Re: [PATCH v1 02/14] clk: twl6040: Register the clock as of_clk_provider

On 05/30, Peter Ujfalusi wrote: > In order ot be able to use the pdmclk clock via DT it need to be registered > as of_clk_provide. > Since the twl6040 clock driver does not have it's own DT node, use the > parent's node for registering. > > Signed-off-by: Peter Ujfalusi >

Re: [PATCH v1 02/14] clk: twl6040: Register the clock as of_clk_provider

On 05/30, Peter Ujfalusi wrote: > In order ot be able to use the pdmclk clock via DT it need to be registered > as of_clk_provide. > Since the twl6040 clock driver does not have it's own DT node, use the > parent's node for registering. > > Signed-off-by: Peter Ujfalusi > --- Applied to

[PATCH v4 01/13] media: mt9m111: make a standalone v4l2 subdevice

Remove the soc_camera adherence. Mostly the change removes the power manipulation provided by soc_camera, and instead : - powers on the sensor when the s_power control is activated - powers on the sensor in initial probe - enables and disables the MCLK provided to it in power on/off

[PATCH v4 04/13] media: platform: pxa_camera: convert to vb2

Convert pxa_camera from videobuf to videobuf2. As the soc_camera was already compatible with videobuf2, the port is quite straightforward. The special case of this code in which the vb2 to prepare is "too big" in terms of size for the new capture format, the pxa_camera will fail. Signed-off-by:

[PATCH v4 01/13] media: mt9m111: make a standalone v4l2 subdevice

Remove the soc_camera adherence. Mostly the change removes the power manipulation provided by soc_camera, and instead : - powers on the sensor when the s_power control is activated - powers on the sensor in initial probe - enables and disables the MCLK provided to it in power on/off

[PATCH v4 04/13] media: platform: pxa_camera: convert to vb2

Convert pxa_camera from videobuf to videobuf2. As the soc_camera was already compatible with videobuf2, the port is quite straightforward. The special case of this code in which the vb2 to prepare is "too big" in terms of size for the new capture format, the pxa_camera will fail. Signed-off-by:

[PATCH v4 00/13] pxa_camera transition to v4l2 standalone device

Hi Hans, Now only your comments have been taken between v3 and v4, the buffer sequence number reset, and the rebase on top of v4.8-rc1, which makes the diffstat with the former submission : drivers/media/i2c/mt9m111.c | 14 ++ drivers/media/platform/pxa_camera.c |

[PATCH v4 03/13] media: mt9m111: move mt9m111 out of soc_camera

As the mt9m111 is now working as a standalone v4l2 subdevice sensor, move it out of soc_camera directory and severe its dependency on soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/Kconfig |7 + drivers/media/i2c/Makefile |

[PATCH v4 00/13] pxa_camera transition to v4l2 standalone device

Hi Hans, Now only your comments have been taken between v3 and v4, the buffer sequence number reset, and the rebase on top of v4.8-rc1, which makes the diffstat with the former submission : drivers/media/i2c/mt9m111.c | 14 ++ drivers/media/platform/pxa_camera.c |

[PATCH v4 03/13] media: mt9m111: move mt9m111 out of soc_camera

As the mt9m111 is now working as a standalone v4l2 subdevice sensor, move it out of soc_camera directory and severe its dependency on soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/Kconfig |7 + drivers/media/i2c/Makefile |1 +

[PATCH v4 05/13] media: platform: pxa_camera: trivial move of functions

Move the functions in the file to be regrouped into meaningful blocks : 1. pxa camera core handling functions, manipulating the herdware 2. videobuf2 functions, dealing with video buffers 3. video ioctl (vidioc) related functions 4. driver probing, removal, suspend and resume This patch

[PATCH v4 05/13] media: platform: pxa_camera: trivial move of functions

Move the functions in the file to be regrouped into meaningful blocks : 1. pxa camera core handling functions, manipulating the herdware 2. videobuf2 functions, dealing with video buffers 3. video ioctl (vidioc) related functions 4. driver probing, removal, suspend and resume This patch

[PATCH v4 10/13] media: platform: pxa_camera: make a standalone v4l2 device

This patch removes the soc_camera API dependency from pxa_camera. In the current status : - all previously captures are working the same on pxa270 - the s_crop() call was removed, judged not working (see what happens soc_camera_s_crop() when get_crop() == NULL) - if the pixel clock is

[PATCH v4 10/13] media: platform: pxa_camera: make a standalone v4l2 device

This patch removes the soc_camera API dependency from pxa_camera. In the current status : - all previously captures are working the same on pxa270 - the s_crop() call was removed, judged not working (see what happens soc_camera_s_crop() when get_crop() == NULL) - if the pixel clock is

[PATCH v4 07/13] media: platform: pxa_camera: make printk consistent

Make all print consistent by always using : - dev_xxx(pcdev_to_dev(pcdev), ) This prepares the soc_camera adherence removal by making these call rely on only pcdev, and not the soc_camera icd structure. Signed-off-by: Robert Jarzmik ---

[PATCH v4 07/13] media: platform: pxa_camera: make printk consistent

Make all print consistent by always using : - dev_xxx(pcdev_to_dev(pcdev), ) This prepares the soc_camera adherence removal by making these call rely on only pcdev, and not the soc_camera icd structure. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 70

[PATCH v4 11/13] media: platform: pxa_camera: add debug register access

Add pxa_camera registers access through advanced video debugging. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 32 ++ 1 file changed, 32 insertions(+) diff --git

[PATCH v4 13/13] media: platform: pxa_camera: move pxa_camera out of soc_camera

As the conversion to a v4l2 standalone device is finished, move pxa_camera one directory up and finish severing any dependency to soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/platform/Kconfig |8 + drivers/media/platform/Makefile

[PATCH v4 11/13] media: platform: pxa_camera: add debug register access

Add pxa_camera registers access through advanced video debugging. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 32 ++ 1 file changed, 32 insertions(+) diff --git a/drivers/media/platform/soc_camera/pxa_camera.c

[PATCH v4 13/13] media: platform: pxa_camera: move pxa_camera out of soc_camera

As the conversion to a v4l2 standalone device is finished, move pxa_camera one directory up and finish severing any dependency to soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/platform/Kconfig |8 + drivers/media/platform/Makefile|1 +

[PATCH v4 02/13] media: mt9m111: use only the SRGB colorspace

mt9m111 being a camera sensor, its colorspace should always be SRGB, for both RGB based formats or YCbCr based ones. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/soc_camera/mt9m111.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v4 12/13] media: platform: pxa_camera: change stop_streaming semantics

Instead of the legacy behavior where it was required to wait for all video buffers to be finished by the hardware, use a cancel like strategy : as soon as the stop_streaming() call is done, abort all DMA transfers, report the already buffers as failed and return. This makes stop_streaming() more

[PATCH v4 02/13] media: mt9m111: use only the SRGB colorspace

mt9m111 being a camera sensor, its colorspace should always be SRGB, for both RGB based formats or YCbCr based ones. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/soc_camera/mt9m111.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v4 12/13] media: platform: pxa_camera: change stop_streaming semantics

Instead of the legacy behavior where it was required to wait for all video buffers to be finished by the hardware, use a cancel like strategy : as soon as the stop_streaming() call is done, abort all DMA transfers, report the already buffers as failed and return. This makes stop_streaming() more

Re: BUG and WARN kernel log levels

On Mon, 2016-08-15 at 11:53 -0700, Kees Cook wrote: > Hi, > > So, I noticed that asm-gemeric/bug.h defines BUG() without a log level: > > #ifndef HAVE_ARCH_BUG > #define BUG() do { \ >    printk("BUG: failure at %s:%d/%s()!\n", __FILE__, __LINE__, __func__); > \ > > Seems like it should

Re: BUG and WARN kernel log levels

On Mon, 2016-08-15 at 11:53 -0700, Kees Cook wrote: > Hi, > > So, I noticed that asm-gemeric/bug.h defines BUG() without a log level: > > #ifndef HAVE_ARCH_BUG > #define BUG() do { \ >    printk("BUG: failure at %s:%d/%s()!\n", __FILE__, __LINE__, __func__); > \ > > Seems like it should

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