[PATCH 0/3] serial: 8250_uniphier: bug fix and suspend/resume support

2017-08-08 Thread Masahiro Yamada
1/3 is a bug-fix (the driver may unregister a different port) 2/3 and 3/3 add suspend/resume support. Masahiro Yamada (3): serial: 8250_uniphier: fix serial port index in private data serial: 8250_uniphier: use CHAR register for canary to detect power-off serial: 8250_uniphier: add

[PATCH 2/3] serial: 8250_uniphier: use CHAR register for canary to detect power-off

2017-08-08 Thread Masahiro Yamada
The 8250 core uses the SCR as a canary to discover if the console has been powered-off. This hardware does not have SCR at offset 7, but an unused register CHAR at a different offset. As long as the character interrupt is disabled, the register access has no impact, so it is useful as an

[PATCH 3/3] serial: 8250_uniphier: add suspend/resume support

2017-08-08 Thread Masahiro Yamada
Add suspend/resume support for UniPhier serial driver. Signed-off-by: Masahiro Yamada --- drivers/tty/serial/8250/8250_uniphier.c | 35 + 1 file changed, 35 insertions(+) diff --git a/drivers/tty/serial/8250/8250_uniphier.c

[PATCH 3/3] serial: 8250_uniphier: add suspend/resume support

2017-08-08 Thread Masahiro Yamada
Add suspend/resume support for UniPhier serial driver. Signed-off-by: Masahiro Yamada --- drivers/tty/serial/8250/8250_uniphier.c | 35 + 1 file changed, 35 insertions(+) diff --git a/drivers/tty/serial/8250/8250_uniphier.c

[PATCH 1/3] serial: 8250_uniphier: fix serial port index in private data

2017-08-08 Thread Masahiro Yamada
serial8250_register_8250_port() may allocate a different port index than requested. The driver needs to remember the returned value of serial8250_register_8250_port() for later use. Otherwise, the .remove hook may unregister a different port. Fixes: 1a8d2903cb6a ("serial: 8250_uniphier: add

[PATCH 1/3] serial: 8250_uniphier: fix serial port index in private data

2017-08-08 Thread Masahiro Yamada
serial8250_register_8250_port() may allocate a different port index than requested. The driver needs to remember the returned value of serial8250_register_8250_port() for later use. Otherwise, the .remove hook may unregister a different port. Fixes: 1a8d2903cb6a ("serial: 8250_uniphier: add

[PATCHv2] bluetooth: document config options

2017-08-08 Thread Pavel Machek
Kernel config options should include useful help text; I had to look up the terms on wikipedia. Signed-off-by: Pavel Machek --- > are you planning to send a patch with updated wording for this? Sorry for the delay, it is above. I added word "wifi" to 802.11 description.

[PATCHv2] bluetooth: document config options

2017-08-08 Thread Pavel Machek
Kernel config options should include useful help text; I had to look up the terms on wikipedia. Signed-off-by: Pavel Machek --- > are you planning to send a patch with updated wording for this? Sorry for the delay, it is above. I added word "wifi" to 802.11 description.

Re: [PATCH v4] printk: Add monotonic, boottime, and realtime timestamps

2017-08-08 Thread Prarit Bhargava
On 08/07/2017 08:19 PM, Sergey Senozhatsky wrote: > On (08/07/17 11:52), Prarit Bhargava wrote: > [..] >> +if (strlen(param) == 1) { >> +/* Preserve legacy boolean settings */ >> +if (!strcmp("0", param) || !strcmp("n", param) || >> +!strcmp("N",

Re: [PATCH v4] printk: Add monotonic, boottime, and realtime timestamps

2017-08-08 Thread Prarit Bhargava
On 08/07/2017 08:19 PM, Sergey Senozhatsky wrote: > On (08/07/17 11:52), Prarit Bhargava wrote: > [..] >> +if (strlen(param) == 1) { >> +/* Preserve legacy boolean settings */ >> +if (!strcmp("0", param) || !strcmp("n", param) || >> +!strcmp("N",

Re: [PATCH 0/4] constify thermal_zone_of_device_ops structures

2017-08-08 Thread Julia Lawall
On Tue, 8 Aug 2017, Zhang Rui wrote: > On Sat, 2017-08-05 at 22:37 +0200, Julia Lawall wrote: > > The thermal_zone_of_device_ops structures are only passed as the > > fourth > > argument to thermal_zone_of_sensor_register, which is declared as > > const. > > Thus the thermal_zone_of_device_ops

Re: [PATCH 0/4] constify thermal_zone_of_device_ops structures

2017-08-08 Thread Julia Lawall
On Tue, 8 Aug 2017, Zhang Rui wrote: > On Sat, 2017-08-05 at 22:37 +0200, Julia Lawall wrote: > > The thermal_zone_of_device_ops structures are only passed as the > > fourth > > argument to thermal_zone_of_sensor_register, which is declared as > > const. > > Thus the thermal_zone_of_device_ops

Re: [PATCH v4 06/19] crypto: move algif to generic async completion

2017-08-08 Thread Gilad Ben-Yossef
On Tue, Aug 8, 2017 at 4:10 PM, Stephan Mueller wrote: > Am Dienstag, 8. August 2017, 14:03:37 CEST schrieb Gilad Ben-Yossef: > > Hi Gilad, > >> algif starts several async crypto ops and waits for their completion. >> Move it over to generic code doing the same. > > Just FYI:

Re: [PATCH v4 06/19] crypto: move algif to generic async completion

2017-08-08 Thread Gilad Ben-Yossef
On Tue, Aug 8, 2017 at 4:10 PM, Stephan Mueller wrote: > Am Dienstag, 8. August 2017, 14:03:37 CEST schrieb Gilad Ben-Yossef: > > Hi Gilad, > >> algif starts several async crypto ops and waits for their completion. >> Move it over to generic code doing the same. > > Just FYI: your patch set and

Re: [PATCH 0/4] constify thermal_zone_of_device_ops structures

2017-08-08 Thread Zhang Rui
On Sat, 2017-08-05 at 22:37 +0200, Julia Lawall wrote: > The thermal_zone_of_device_ops structures are only passed as the > fourth > argument to thermal_zone_of_sensor_register, which is declared as > const. > Thus the thermal_zone_of_device_ops structures themselves can be > const. > > Done with

Re: [PATCH 0/4] constify thermal_zone_of_device_ops structures

2017-08-08 Thread Zhang Rui
On Sat, 2017-08-05 at 22:37 +0200, Julia Lawall wrote: > The thermal_zone_of_device_ops structures are only passed as the > fourth > argument to thermal_zone_of_sensor_register, which is declared as > const. > Thus the thermal_zone_of_device_ops structures themselves can be > const. > > Done with

Re: [PATCH] MAINTAINERS: greybus: Fix typo s/LOOBACK/LOOPBACK

2017-08-08 Thread Sedat Dilek
On Tue, Jul 25, 2017 at 2:53 PM, Sedat Dilek wrote: > From: Sedat Dilek > > Fixes: f47e07bc5f1a5c48 ("Fix up MAINTAINERS file problems") > Cc: Joe Perches > Cc: Linus Torvalds > Cc:

[PATCH] f2fs: introduce cur_reserved_blocks in sysfs

2017-08-08 Thread Yunlong Song
In this patch, we add a new sysfs interface, we can use it to gradually achieve the reserved_blocks finally, even when reserved_blocks is initially set over user_block_count - total_valid_block_count. This is very useful, especially when we upgrade kernel with new reserved_blocks value, but old

[PATCH] f2fs: introduce cur_reserved_blocks in sysfs

2017-08-08 Thread Yunlong Song
In this patch, we add a new sysfs interface, we can use it to gradually achieve the reserved_blocks finally, even when reserved_blocks is initially set over user_block_count - total_valid_block_count. This is very useful, especially when we upgrade kernel with new reserved_blocks value, but old

Re: [PATCH] MAINTAINERS: greybus: Fix typo s/LOOBACK/LOOPBACK

2017-08-08 Thread Sedat Dilek
On Tue, Jul 25, 2017 at 2:53 PM, Sedat Dilek wrote: > From: Sedat Dilek > > Fixes: f47e07bc5f1a5c48 ("Fix up MAINTAINERS file problems") > Cc: Joe Perches > Cc: Linus Torvalds > Cc: linux-kernel@vger.kernel.org > Signed-off-by: Sedat Dilek > --- > [ dileks: v2: CC LKML (Thanks Joe Perches) ]

crypto: ccp: use dma_mapping_error to check map error

2017-08-08 Thread Pan Bian
The return value of dma_map_single() should be checked by dma_mapping_error(). However, in function ccp_init_dm_workarea(), its return value is checked against NULL, which could result in failures. Signed-off-by: Pan Bian --- drivers/crypto/ccp/ccp-ops.c | 2 +- 1 file

crypto: ccp: use dma_mapping_error to check map error

2017-08-08 Thread Pan Bian
The return value of dma_map_single() should be checked by dma_mapping_error(). However, in function ccp_init_dm_workarea(), its return value is checked against NULL, which could result in failures. Signed-off-by: Pan Bian --- drivers/crypto/ccp/ccp-ops.c | 2 +- 1 file changed, 1 insertion(+),

Re: [PATCH] kbuild: Update example for ccflags-y usage

2017-08-08 Thread Jonathan Corbet
On Tue, 8 Aug 2017 14:36:02 +0200 Sedat Dilek wrote: > Will this go to Linux v4.13 or v4.14? It's queued for 4.14. jon

Re: [PATCH] kbuild: Update example for ccflags-y usage

2017-08-08 Thread Jonathan Corbet
On Tue, 8 Aug 2017 14:36:02 +0200 Sedat Dilek wrote: > Will this go to Linux v4.13 or v4.14? It's queued for 4.14. jon

[PATCH v4 04/21] doc: media/v4l-drivers: Add Qualcomm Camera Subsystem driver document

2017-08-08 Thread Todor Tomov
Add a document to describe Qualcomm Camera Subsystem driver. Signed-off-by: Todor Tomov --- Documentation/media/v4l-drivers/qcom_camss.rst | 124 + 1 file changed, 124 insertions(+) create mode 100644

[PATCH v4 04/21] doc: media/v4l-drivers: Add Qualcomm Camera Subsystem driver document

2017-08-08 Thread Todor Tomov
Add a document to describe Qualcomm Camera Subsystem driver. Signed-off-by: Todor Tomov --- Documentation/media/v4l-drivers/qcom_camss.rst | 124 + 1 file changed, 124 insertions(+) create mode 100644 Documentation/media/v4l-drivers/qcom_camss.rst diff --git

[PATCH v4 00/21] Qualcomm 8x16 Camera Subsystem driver

2017-08-08 Thread Todor Tomov
This patchset adds basic support for the Qualcomm Camera Subsystem found on Qualcomm MSM8916 and APQ8016 processors. The driver implements V4L2, Media controller and V4L2 subdev interfaces. Camera sensor using V4L2 subdev interface in the kernel is supported. The driver is implemented using as a

[PATCH v4 00/21] Qualcomm 8x16 Camera Subsystem driver

2017-08-08 Thread Todor Tomov
This patchset adds basic support for the Qualcomm Camera Subsystem found on Qualcomm MSM8916 and APQ8016 processors. The driver implements V4L2, Media controller and V4L2 subdev interfaces. Camera sensor using V4L2 subdev interface in the kernel is supported. The driver is implemented using as a

[PATCH v4 07/21] media: camss: Add ISPIF files

2017-08-08 Thread Todor Tomov
These files control the ISPIF module which handles the routing of the data streams from the CSIDs to the inputs of the VFE. Signed-off-by: Todor Tomov --- .../media/platform/qcom/camss-8x16/camss-ispif.c | 1164

[PATCH v4 07/21] media: camss: Add ISPIF files

2017-08-08 Thread Todor Tomov
These files control the ISPIF module which handles the routing of the data streams from the CSIDs to the inputs of the VFE. Signed-off-by: Todor Tomov --- .../media/platform/qcom/camss-8x16/camss-ispif.c | 1164 .../media/platform/qcom/camss-8x16/camss-ispif.h | 85 ++

[PATCH v4 05/21] media: camss: Add CSIPHY files

2017-08-08 Thread Todor Tomov
These files control the CSIPHY modules which are responsible for the physical layer of the CSI2 receivers. Signed-off-by: Todor Tomov --- .../media/platform/qcom/camss-8x16/camss-csiphy.c | 823 + .../media/platform/qcom/camss-8x16/camss-csiphy.h |

[PATCH v4 05/21] media: camss: Add CSIPHY files

2017-08-08 Thread Todor Tomov
These files control the CSIPHY modules which are responsible for the physical layer of the CSI2 receivers. Signed-off-by: Todor Tomov --- .../media/platform/qcom/camss-8x16/camss-csiphy.c | 823 + .../media/platform/qcom/camss-8x16/camss-csiphy.h | 77 ++ 2 files changed,

[PATCH v4 06/21] media: camss: Add CSID files

2017-08-08 Thread Todor Tomov
These files control the CSID modules which handle the protocol and application layer of the CSI2 receivers. Signed-off-by: Todor Tomov --- .../media/platform/qcom/camss-8x16/camss-csid.c| 1003 .../media/platform/qcom/camss-8x16/camss-csid.h|

[PATCH v4 06/21] media: camss: Add CSID files

2017-08-08 Thread Todor Tomov
These files control the CSID modules which handle the protocol and application layer of the CSI2 receivers. Signed-off-by: Todor Tomov --- .../media/platform/qcom/camss-8x16/camss-csid.c| 1003 .../media/platform/qcom/camss-8x16/camss-csid.h| 82 ++ 2 files

[PATCH v4 03/21] MAINTAINERS: Add Qualcomm Camera subsystem driver

2017-08-08 Thread Todor Tomov
Add an entry for Qualcomm Camera subsystem driver. Signed-off-by: Todor Tomov --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index bdde944..87d0c7f 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10996,6 +10996,14 @@

[PATCH v4 03/21] MAINTAINERS: Add Qualcomm Camera subsystem driver

2017-08-08 Thread Todor Tomov
Add an entry for Qualcomm Camera subsystem driver. Signed-off-by: Todor Tomov --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index bdde944..87d0c7f 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10996,6 +10996,14 @@ W:

[PATCH v4 08/21] media: camss: Add VFE files

2017-08-08 Thread Todor Tomov
These files control the VFE module. The VFE has different input interfaces. The PIX input interface feeds the input data to an image processing pipeline. Three RDI input interfaces bypass the image processing pipeline. The VFE also contains the AXI bus interface which writes the output data to

[PATCH v4 08/21] media: camss: Add VFE files

2017-08-08 Thread Todor Tomov
These files control the VFE module. The VFE has different input interfaces. The PIX input interface feeds the input data to an image processing pipeline. Three RDI input interfaces bypass the image processing pipeline. The VFE also contains the AXI bus interface which writes the output data to

[PATCH v4 10/21] media: camms: Add core files

2017-08-08 Thread Todor Tomov
These files implement the platform driver code. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss.c | 699 + drivers/media/platform/qcom/camss-8x16/camss.h | 97 2 files changed, 796 insertions(+) create mode

[PATCH v4 10/21] media: camms: Add core files

2017-08-08 Thread Todor Tomov
These files implement the platform driver code. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss.c | 699 + drivers/media/platform/qcom/camss-8x16/camss.h | 97 2 files changed, 796 insertions(+) create mode 100644

[PATCH v4 09/21] media: camss: Add files which handle the video device nodes

2017-08-08 Thread Todor Tomov
These files handle the video device nodes of the camss driver. Signed-off-by: Todor Tomov --- .../media/platform/qcom/camss-8x16/camss-video.c | 681 + .../media/platform/qcom/camss-8x16/camss-video.h | 64 ++ 2 files changed, 745 insertions(+)

[PATCH v4 09/21] media: camss: Add files which handle the video device nodes

2017-08-08 Thread Todor Tomov
These files handle the video device nodes of the camss driver. Signed-off-by: Todor Tomov --- .../media/platform/qcom/camss-8x16/camss-video.c | 681 + .../media/platform/qcom/camss-8x16/camss-video.h | 64 ++ 2 files changed, 745 insertions(+) create mode 100644

Re: [v6 11/15] arm64/kasan: explicitly zero kasan shadow memory

2017-08-08 Thread Pasha Tatashin
On 2017-08-08 09:15, David Laight wrote: From: Pasha Tatashin Sent: 08 August 2017 12:49 Thank you for looking at this change. What you described was in my previous iterations of this project. See for example here: https://lkml.org/lkml/2017/5/5/369 I was asked to remove that flag, and only

Re: [PATCH v8 00/20] ILP32 for ARM64

2017-08-08 Thread Catalin Marinas
On Mon, Jul 24, 2017 at 02:26:24PM +0300, Yury Norov wrote: > This is the 4.12 and linux-next - based kernel patches: > https://github.com/norov/linux/tree/ilp32-4.12 > https://github.com/norov/linux/tree/ilp32-20170724 I published the 4.12 branch here:

Re: [v6 11/15] arm64/kasan: explicitly zero kasan shadow memory

2017-08-08 Thread Pasha Tatashin
On 2017-08-08 09:15, David Laight wrote: From: Pasha Tatashin Sent: 08 August 2017 12:49 Thank you for looking at this change. What you described was in my previous iterations of this project. See for example here: https://lkml.org/lkml/2017/5/5/369 I was asked to remove that flag, and only

Re: [PATCH v8 00/20] ILP32 for ARM64

2017-08-08 Thread Catalin Marinas
On Mon, Jul 24, 2017 at 02:26:24PM +0300, Yury Norov wrote: > This is the 4.12 and linux-next - based kernel patches: > https://github.com/norov/linux/tree/ilp32-4.12 > https://github.com/norov/linux/tree/ilp32-20170724 I published the 4.12 branch here:

Re: [RFC v5 05/11] mm: fix lock dependency against mapping->i_mmap_rwsem

2017-08-08 Thread Laurent Dufour
On 08/08/2017 15:15, Peter Zijlstra wrote: > On Tue, Aug 08, 2017 at 02:20:23PM +0200, Laurent Dufour wrote: >> This is an option, but the previous one was signed by Peter, and I'd prefer >> to keep his unchanged and add this new one to fix that. >> Again this is to ease the review. > > You can

Re: [RFC v5 05/11] mm: fix lock dependency against mapping->i_mmap_rwsem

2017-08-08 Thread Laurent Dufour
On 08/08/2017 15:15, Peter Zijlstra wrote: > On Tue, Aug 08, 2017 at 02:20:23PM +0200, Laurent Dufour wrote: >> This is an option, but the previous one was signed by Peter, and I'd prefer >> to keep his unchanged and add this new one to fix that. >> Again this is to ease the review. > > You can

Re: suspicious __GFP_NOMEMALLOC in selinux

2017-08-08 Thread Paul Moore
On Mon, Aug 7, 2017 at 2:58 AM, Michal Hocko wrote: > On Fri 04-08-17 13:12:04, Paul Moore wrote: >> On Fri, Aug 4, 2017 at 3:56 AM, Michal Hocko wrote: > [...] >> > Btw. Should I resend the patch or somebody will take it from this email >> > thread? >> >>

Re: suspicious __GFP_NOMEMALLOC in selinux

2017-08-08 Thread Paul Moore
On Mon, Aug 7, 2017 at 2:58 AM, Michal Hocko wrote: > On Fri 04-08-17 13:12:04, Paul Moore wrote: >> On Fri, Aug 4, 2017 at 3:56 AM, Michal Hocko wrote: > [...] >> > Btw. Should I resend the patch or somebody will take it from this email >> > thread? >> >> No, unless your mailer mangled the

[PATCH v4 12/21] camss: vfe: Format conversion support using PIX interface

2017-08-08 Thread Todor Tomov
Use VFE PIX input interface and do format conversion in VFE. Supported input format is UYVY (single plane YUV 4:2:2) and its different sample order variations. Supported output formats are: - NV12/NV21 (two plane YUV 4:2:0) - NV16/NV61 (two plane YUV 4:2:2) Signed-off-by: Todor Tomov

[PATCH v4 12/21] camss: vfe: Format conversion support using PIX interface

2017-08-08 Thread Todor Tomov
Use VFE PIX input interface and do format conversion in VFE. Supported input format is UYVY (single plane YUV 4:2:2) and its different sample order variations. Supported output formats are: - NV12/NV21 (two plane YUV 4:2:0) - NV16/NV61 (two plane YUV 4:2:2) Signed-off-by: Todor Tomov ---

[PATCH v4 13/21] doc: media/v4l-drivers: Qualcomm Camera Subsystem - PIX Interface

2017-08-08 Thread Todor Tomov
Update Qualcomm Camera Subsystem driver document for the PIX interface and format conversion support. Signed-off-by: Todor Tomov --- Documentation/media/v4l-drivers/qcom_camss.rst | 46 -- 1 file changed, 36 insertions(+), 10 deletions(-) diff

[PATCH v4 13/21] doc: media/v4l-drivers: Qualcomm Camera Subsystem - PIX Interface

2017-08-08 Thread Todor Tomov
Update Qualcomm Camera Subsystem driver document for the PIX interface and format conversion support. Signed-off-by: Todor Tomov --- Documentation/media/v4l-drivers/qcom_camss.rst | 46 -- 1 file changed, 36 insertions(+), 10 deletions(-) diff --git

[PATCH v4 11/21] media: camss: Enable building

2017-08-08 Thread Todor Tomov
Add Makefile and update platform/Kconfig and platform/Makefile to enable building of the QCom CAMSS driver. Signed-off-by: Todor Tomov --- drivers/media/platform/Kconfig | 7 +++ drivers/media/platform/Makefile | 2 ++

[PATCH v4 11/21] media: camss: Enable building

2017-08-08 Thread Todor Tomov
Add Makefile and update platform/Kconfig and platform/Makefile to enable building of the QCom CAMSS driver. Signed-off-by: Todor Tomov --- drivers/media/platform/Kconfig | 7 +++ drivers/media/platform/Makefile | 2 ++

[PATCH v4 01/21] v4l: Add packed Bayer raw12 pixel formats

2017-08-08 Thread Todor Tomov
From: Sakari Ailus These formats are compressed 12-bit raw bayer formats with four different pixel orders. They are similar to 10-bit variants. The formats added by this patch are V4L2_PIX_FMT_SBGGR12P V4L2_PIX_FMT_SGBRG12P

[PATCH v4 01/21] v4l: Add packed Bayer raw12 pixel formats

2017-08-08 Thread Todor Tomov
From: Sakari Ailus These formats are compressed 12-bit raw bayer formats with four different pixel orders. They are similar to 10-bit variants. The formats added by this patch are V4L2_PIX_FMT_SBGGR12P V4L2_PIX_FMT_SGBRG12P V4L2_PIX_FMT_SGRBG12P

[PATCH v4 15/21] camss: vfe: Add interface for scaling

2017-08-08 Thread Todor Tomov
Add compose selection ioctls to handle scaling configuration. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 184 - drivers/media/platform/qcom/camss-8x16/camss-vfe.h | 1 + 2 files changed, 183 insertions(+), 2

[PATCH v4 15/21] camss: vfe: Add interface for scaling

2017-08-08 Thread Todor Tomov
Add compose selection ioctls to handle scaling configuration. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 184 - drivers/media/platform/qcom/camss-8x16/camss-vfe.h | 1 + 2 files changed, 183 insertions(+), 2 deletions(-) diff --git

[PATCH v4 14/21] camss: vfe: Support for frame padding

2017-08-08 Thread Todor Tomov
Add support for horizontal and vertical frame padding. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 85 +- .../media/platform/qcom/camss-8x16/camss-video.c | 53 ++

[PATCH v4 14/21] camss: vfe: Support for frame padding

2017-08-08 Thread Todor Tomov
Add support for horizontal and vertical frame padding. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 85 +- .../media/platform/qcom/camss-8x16/camss-video.c | 53 ++ .../media/platform/qcom/camss-8x16/camss-video.h | 2 +

[PATCH v4 17/21] camss: vfe: Add interface for cropping

2017-08-08 Thread Todor Tomov
Extend selection ioctls to handle cropping configuration. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 191 - drivers/media/platform/qcom/camss-8x16/camss-vfe.h | 1 + 2 files changed, 150 insertions(+), 42

[PATCH v4 17/21] camss: vfe: Add interface for cropping

2017-08-08 Thread Todor Tomov
Extend selection ioctls to handle cropping configuration. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 191 - drivers/media/platform/qcom/camss-8x16/camss-vfe.h | 1 + 2 files changed, 150 insertions(+), 42 deletions(-) diff --git

[PATCH v4 16/21] camss: vfe: Configure scaler module in VFE

2017-08-08 Thread Todor Tomov
Add scaler module configuration support to be able to apply scaling. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 59 +- 1 file changed, 46 insertions(+), 13 deletions(-) diff --git

[PATCH v4 16/21] camss: vfe: Configure scaler module in VFE

2017-08-08 Thread Todor Tomov
Add scaler module configuration support to be able to apply scaling. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 59 +- 1 file changed, 46 insertions(+), 13 deletions(-) diff --git a/drivers/media/platform/qcom/camss-8x16/camss-vfe.c

[PATCH v4 19/21] doc: media/v4l-drivers: Qualcomm Camera Subsystem - Scale and crop

2017-08-08 Thread Todor Tomov
Update the Qualcomm Camera Subsystem driver document for VFE scale and crop modules support. Signed-off-by: Todor Tomov --- Documentation/media/v4l-drivers/qcom_camss.rst | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git

[PATCH v4 19/21] doc: media/v4l-drivers: Qualcomm Camera Subsystem - Scale and crop

2017-08-08 Thread Todor Tomov
Update the Qualcomm Camera Subsystem driver document for VFE scale and crop modules support. Signed-off-by: Todor Tomov --- Documentation/media/v4l-drivers/qcom_camss.rst | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git

[PATCH v4 18/21] camss: vfe: Configure crop module in VFE

2017-08-08 Thread Todor Tomov
Add crop module configuration support to be able to apply cropping. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 41 +- 1 file changed, 40 insertions(+), 1 deletion(-) diff --git

[PATCH v4 18/21] camss: vfe: Configure crop module in VFE

2017-08-08 Thread Todor Tomov
Add crop module configuration support to be able to apply cropping. Signed-off-by: Todor Tomov --- drivers/media/platform/qcom/camss-8x16/camss-vfe.c | 41 +- 1 file changed, 40 insertions(+), 1 deletion(-) diff --git a/drivers/media/platform/qcom/camss-8x16/camss-vfe.c

[PATCH v4 20/21] camss: Use optimal clock frequency rates

2017-08-08 Thread Todor Tomov
Use standard V4L2 control to get pixel clock rate from a sensor linked in the media controller pipeline. Then calculate clock rates on CSIPHY, CSID and VFE to use the lowest possible. If the currnet pixel clock rate of the sensor cannot be read then use the highest possible. This case covers also

[PATCH v4 02/21] dt-bindings: media: Binding document for Qualcomm Camera subsystem driver

2017-08-08 Thread Todor Tomov
Add DT binding document for Qualcomm Camera subsystem driver. CC: Rob Herring CC: devicet...@vger.kernel.org Signed-off-by: Todor Tomov Acked-by: Rob Herring --- .../devicetree/bindings/media/qcom,camss.txt | 197

[PATCH v4 20/21] camss: Use optimal clock frequency rates

2017-08-08 Thread Todor Tomov
Use standard V4L2 control to get pixel clock rate from a sensor linked in the media controller pipeline. Then calculate clock rates on CSIPHY, CSID and VFE to use the lowest possible. If the currnet pixel clock rate of the sensor cannot be read then use the highest possible. This case covers also

[PATCH v4 02/21] dt-bindings: media: Binding document for Qualcomm Camera subsystem driver

2017-08-08 Thread Todor Tomov
Add DT binding document for Qualcomm Camera subsystem driver. CC: Rob Herring CC: devicet...@vger.kernel.org Signed-off-by: Todor Tomov Acked-by: Rob Herring --- .../devicetree/bindings/media/qcom,camss.txt | 197 + 1 file changed, 197 insertions(+) create mode

[PATCH v4 21/21] doc: media/v4l-drivers: Qualcomm Camera Subsystem - Media graph

2017-08-08 Thread Todor Tomov
Update the Qualcomm Camera Subsystem driver document with a media controller pipeline graph diagram. Signed-off-by: Todor Tomov --- Documentation/media/v4l-drivers/qcom_camss.rst | 27 ++ .../media/v4l-drivers/qcom_camss_graph.dot | 41

[PATCH v4 21/21] doc: media/v4l-drivers: Qualcomm Camera Subsystem - Media graph

2017-08-08 Thread Todor Tomov
Update the Qualcomm Camera Subsystem driver document with a media controller pipeline graph diagram. Signed-off-by: Todor Tomov --- Documentation/media/v4l-drivers/qcom_camss.rst | 27 ++ .../media/v4l-drivers/qcom_camss_graph.dot | 41 ++ 2 files

Re: [PATCH] thermal/drivers/hisi: Remove confusing error message

2017-08-08 Thread Leo Yan
On Tue, Aug 08, 2017 at 08:48:51PM +0800, Zhang Rui wrote: [...] > > > > @@ -352,10 +353,9 @@ static int hisi_thermal_probe(struct > > > > platform_device *pdev) > > > >   ret = hisi_thermal_register_sensor(pdev, data, > > > >       > >

Re: [PATCH] thermal/drivers/hisi: Remove confusing error message

2017-08-08 Thread Leo Yan
On Tue, Aug 08, 2017 at 08:48:51PM +0800, Zhang Rui wrote: [...] > > > > @@ -352,10 +353,9 @@ static int hisi_thermal_probe(struct > > > > platform_device *pdev) > > > >   ret = hisi_thermal_register_sensor(pdev, data, > > > >       > >

Re: [PATCH v6 2/2] thermal: uniphier: add UniPhier thermal driver

2017-08-08 Thread Zhang Rui
On Tue, 2017-08-01 at 17:04 +0900, Kunihiko Hayashi wrote: > Add a thermal driver for on-chip PVT (Process, Voltage and > Temperature) > monitoring unit implemented on UniPhier SoCs. This driver supports > temperature monitoring and alert function. > > Signed-off-by: Kunihiko Hayashi

Re: [PATCH v6 2/2] thermal: uniphier: add UniPhier thermal driver

2017-08-08 Thread Zhang Rui
On Tue, 2017-08-01 at 17:04 +0900, Kunihiko Hayashi wrote: > Add a thermal driver for on-chip PVT (Process, Voltage and > Temperature) > monitoring unit implemented on UniPhier SoCs. This driver supports > temperature monitoring and alert function. > > Signed-off-by: Kunihiko Hayashi > --- >  

Re: [PATCH v1 2/6] fs: use on-stack-bio if backing device has BDI_CAP_SYNC capability

2017-08-08 Thread Matthew Wilcox
On Tue, Aug 08, 2017 at 05:49:59AM -0700, Matthew Wilcox wrote: > + struct bio sbio; > + struct bio_vec sbvec; ... this needs to be sbvec[nr_pages], of course. > - bio = mpage_alloc(bdev, blocks[0] << (blkbits - 9), > + if

Re: [PATCH v1 2/6] fs: use on-stack-bio if backing device has BDI_CAP_SYNC capability

2017-08-08 Thread Matthew Wilcox
On Tue, Aug 08, 2017 at 05:49:59AM -0700, Matthew Wilcox wrote: > + struct bio sbio; > + struct bio_vec sbvec; ... this needs to be sbvec[nr_pages], of course. > - bio = mpage_alloc(bdev, blocks[0] << (blkbits - 9), > + if

Re: [PATCH v1 2/2] [media] ov9655: fix missing mutex_destroy()

2017-08-08 Thread Sakari Ailus
On Fri, Jul 21, 2017 at 05:49:41PM +0200, Hugues Fruchet wrote: > Fix missing mutex_destroy() when probe fails and > when driver is removed. > > Signed-off-by: Hugues Fruchet Thanks, applied both, with the subject changed to reflect the driver file name (ov9550.c). --

Re: [PATCH v1 2/2] [media] ov9655: fix missing mutex_destroy()

2017-08-08 Thread Sakari Ailus
On Fri, Jul 21, 2017 at 05:49:41PM +0200, Hugues Fruchet wrote: > Fix missing mutex_destroy() when probe fails and > when driver is removed. > > Signed-off-by: Hugues Fruchet Thanks, applied both, with the subject changed to reflect the driver file name (ov9550.c). -- Sakari Ailus e-mail:

[PATCH] Add /proc/pid/smaps_rollup

2017-08-08 Thread Daniel Colascione
/proc/pid/smaps_rollup is a new proc file that improves the performance of user programs that determine aggregate memory statistics (e.g., total PSS) of a process. Anroid regularly "samples" the memory usage of various processes in order to blance its memory pool sizes. This sampling process

[PATCH] Add /proc/pid/smaps_rollup

2017-08-08 Thread Daniel Colascione
/proc/pid/smaps_rollup is a new proc file that improves the performance of user programs that determine aggregate memory statistics (e.g., total PSS) of a process. Anroid regularly "samples" the memory usage of various processes in order to blance its memory pool sizes. This sampling process

Re: [PATCH v2 0/4] ipmi: bt-i2c: added IPMI Block Transfer over I2C

2017-08-08 Thread Corey Minyard
On 08/07/2017 08:25 PM, Brendan Higgins wrote: On Sat, Aug 5, 2017 at 3:23 PM, Corey Minyard wrote: On 08/04/2017 08:18 PM, Brendan Higgins wrote: This patchset introduces IPMI Block Transfer over I2C (BT-I2C), which has the same semantics as IPMI Block Transfer except it

Re: [PATCH v2 0/4] ipmi: bt-i2c: added IPMI Block Transfer over I2C

2017-08-08 Thread Corey Minyard
On 08/07/2017 08:25 PM, Brendan Higgins wrote: On Sat, Aug 5, 2017 at 3:23 PM, Corey Minyard wrote: On 08/04/2017 08:18 PM, Brendan Higgins wrote: This patchset introduces IPMI Block Transfer over I2C (BT-I2C), which has the same semantics as IPMI Block Transfer except it done over I2C. For

Re: [PATCH v8 1/3] perf: cavium: Support memory controller PMU counters

2017-08-08 Thread Will Deacon
On Fri, Jul 28, 2017 at 04:12:33PM -0700, Greg KH wrote: > On Thu, Jul 27, 2017 at 03:15:15PM +0200, Borislav Petkov wrote: > > On Thu, Jul 27, 2017 at 11:08:56AM +0200, Jan Glauber wrote: > > > OK. As fixing the firmware will take quite some time I'll go for the > > > memory > > > controller

Re: [PATCH v8 1/3] perf: cavium: Support memory controller PMU counters

2017-08-08 Thread Will Deacon
On Fri, Jul 28, 2017 at 04:12:33PM -0700, Greg KH wrote: > On Thu, Jul 27, 2017 at 03:15:15PM +0200, Borislav Petkov wrote: > > On Thu, Jul 27, 2017 at 11:08:56AM +0200, Jan Glauber wrote: > > > OK. As fixing the firmware will take quite some time I'll go for the > > > memory > > > controller

xen/9pfs: check return value of xenbus_read correctly

2017-08-08 Thread Pan Bian
In function xen_9pfs_front_probe(), variable len is checked against 0 to to check the case that xenbus_read() fails. However, xenbus_read() may return an ERR_PTR pointer even aften assigning a non-zero value to len. As a result, the check of len cannot prevent from accessing bad memory.

xen/9pfs: check return value of xenbus_read correctly

2017-08-08 Thread Pan Bian
In function xen_9pfs_front_probe(), variable len is checked against 0 to to check the case that xenbus_read() fails. However, xenbus_read() may return an ERR_PTR pointer even aften assigning a non-zero value to len. As a result, the check of len cannot prevent from accessing bad memory.

Re: [Linux-ima-devel] [RFC PATCH 1/5] ima: extend clone() with IMA

2017-08-08 Thread Magalhaes, Guilherme (Brazil R)
Stefan, Still on the vTPM requirements, could you help answering the following questions? 1. Where will the boot measurements be stored? What is the integrity measurement domain for this vTPM? The current proposal is that the vTPM would be used for the container (or namespace) files/inodes.

Re: [Linux-ima-devel] [RFC PATCH 1/5] ima: extend clone() with IMA

2017-08-08 Thread Magalhaes, Guilherme (Brazil R)
Stefan, Still on the vTPM requirements, could you help answering the following questions? 1. Where will the boot measurements be stored? What is the integrity measurement domain for this vTPM? The current proposal is that the vTPM would be used for the container (or namespace) files/inodes.

Re: [PATCH net] rds: Reintroduce statistics counting

2017-08-08 Thread Shamir Rabinovitch
On Tue, Aug 08, 2017 at 11:13:32AM +0200, Håkon Bugge wrote: > In commit 7e3f2952eeb1 ("rds: don't let RDS shutdown a connection > while senders are present"), refilling the receive queue was removed > from rds_ib_recv(), along with the increment of > s_ib_rx_refill_from_thread. > > Commit

Re: [PATCH net] rds: Reintroduce statistics counting

2017-08-08 Thread Shamir Rabinovitch
On Tue, Aug 08, 2017 at 11:13:32AM +0200, Håkon Bugge wrote: > In commit 7e3f2952eeb1 ("rds: don't let RDS shutdown a connection > while senders are present"), refilling the receive queue was removed > from rds_ib_recv(), along with the increment of > s_ib_rx_refill_from_thread. > > Commit

Re: [PATCH] arm64: correct modules range of kernel virtual memory layout

2017-08-08 Thread Will Deacon
On Tue, Aug 08, 2017 at 01:27:25PM +0800, Miles Chen wrote: > On Tue, 2017-08-08 at 12:44 +0800, Miles Chen wrote: > > On Mon, 2017-08-07 at 15:01 +0100, Will Deacon wrote: > > > On Mon, Aug 07, 2017 at 02:18:00PM +0100, Ard Biesheuvel wrote: > > > > On 7 August 2017 at 14:16, Will Deacon

Re: [PATCH] arm64: correct modules range of kernel virtual memory layout

2017-08-08 Thread Will Deacon
On Tue, Aug 08, 2017 at 01:27:25PM +0800, Miles Chen wrote: > On Tue, 2017-08-08 at 12:44 +0800, Miles Chen wrote: > > On Mon, 2017-08-07 at 15:01 +0100, Will Deacon wrote: > > > On Mon, Aug 07, 2017 at 02:18:00PM +0100, Ard Biesheuvel wrote: > > > > On 7 August 2017 at 14:16, Will Deacon wrote:

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Thomas Meyer
On Tue, Aug 08, 2017 at 02:04:42PM +0200, Willy Tarreau wrote: > Hi Thomas, > > On Tue, Aug 08, 2017 at 01:46:25PM +0200, Thomas Meyer wrote: > > Hi, > > > > did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel > > build with an included ramdisk? > > > > As fas as I

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

2017-08-08 Thread Thomas Meyer
On Tue, Aug 08, 2017 at 02:04:42PM +0200, Willy Tarreau wrote: > Hi Thomas, > > On Tue, Aug 08, 2017 at 01:46:25PM +0200, Thomas Meyer wrote: > > Hi, > > > > did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel > > build with an included ramdisk? > > > > As fas as I

<    6   7   8   9   10   11   12   13   14   15   >