Re: [RFC PATCH] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules

On 23.03.2016 23:58, Javier Martinez Canillas wrote: > There are a bunch of media platform drivers under drivers/media/platform/ > that are for Samsung SoCs but are not being built with exynos_defconfig. > > This patch enables them as a module to improve build coverage for these > drivers and

Re: [RFC PATCH] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules

On 23.03.2016 23:58, Javier Martinez Canillas wrote: > There are a bunch of media platform drivers under drivers/media/platform/ > that are for Samsung SoCs but are not being built with exynos_defconfig. > > This patch enables them as a module to improve build coverage for these > drivers and

[PATCH 1/2] compiler.h: add support for malloc attribute

gcc as far back as at least 3.04 documents the function attribute __malloc__. Add a shorthand for attaching that to a function declaration. This was also suggested by Andi Kleen way back in 2002 [1], but didn't get applied, perhaps because gcc at that time generated the exact same code with and

[PATCH 2/2] include/linux: apply __malloc attribute

Attach the malloc attribute to a few allocation functions. This helps gcc generate better code by telling it that the return value doesn't alias any existing pointers (which is even more valuable given the pessimizations implied by -fno-strict-aliasing). A simple example of what this allows gcc

[PATCH 1/2] compiler.h: add support for malloc attribute

gcc as far back as at least 3.04 documents the function attribute __malloc__. Add a shorthand for attaching that to a function declaration. This was also suggested by Andi Kleen way back in 2002 [1], but didn't get applied, perhaps because gcc at that time generated the exact same code with and

[PATCH 2/2] include/linux: apply __malloc attribute

Attach the malloc attribute to a few allocation functions. This helps gcc generate better code by telling it that the return value doesn't alias any existing pointers (which is even more valuable given the pessimizations implied by -fno-strict-aliasing). A simple example of what this allows gcc

Re: [PATCH 1/3] sched/fair: Fix asym packing to select correct cpu

On Wed, 2016-03-23 at 17:04 +0530, Srikar Dronamraju wrote: > If asymmetric packing is used when target cpu is busy, > update_sd_pick_busiest(), can select a lightly loaded cpu. > find_busiest_group() has checks to ensure asym packing is only used > when target cpu is not busy. However it may not

Re: [PATCH 1/3] sched/fair: Fix asym packing to select correct cpu

On Wed, 2016-03-23 at 17:04 +0530, Srikar Dronamraju wrote: > If asymmetric packing is used when target cpu is busy, > update_sd_pick_busiest(), can select a lightly loaded cpu. > find_busiest_group() has checks to ensure asym packing is only used > when target cpu is not busy. However it may not

Dear Truly God Chosen

(Dear Truly God Chosen) Please excuse this humble email if it offends your sensibilities, but I have no other means to contact you. I cannot talk on the telephone, so I did a search for your email address, which I found on the international directorate email data search. I am Mrs. Nicole Benoite

Dear Truly God Chosen

(Dear Truly God Chosen) Please excuse this humble email if it offends your sensibilities, but I have no other means to contact you. I cannot talk on the telephone, so I did a search for your email address, which I found on the international directorate email data search. I am Mrs. Nicole Benoite

Re: linux-next: manual merge of the rdma tree with the net-next tree

On Wed, Mar 23, 2016 at 4:04 PM, Or Gerlitz wrote: > > I know there's history here, and in the 4.5 cycle things were much > worse, but I still wanted to put things in their more precise place, > if you don't mind. We'll see how things shape up in the future. Once bitten,

Re: linux-next: manual merge of the rdma tree with the net-next tree

On Wed, Mar 23, 2016 at 4:04 PM, Or Gerlitz wrote: > > I know there's history here, and in the 4.5 cycle things were much > worse, but I still wanted to put things in their more precise place, > if you don't mind. We'll see how things shape up in the future. Once bitten, twice shy, as they say.

[PATCH 7/7] Drivers: hv: vmbus: Implement APIs to support "in place" consumption of vmbus packets

Implement APIs for in-place consumption of vmbus packets. Currently, each packet is copied and processed one at a time and as part of processing each packet we potentially may signal the host (if it is waiting for room to produce a packet). These APIs help batched in-place processing of vmbus

[PATCH 2/7] Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile

Use the READ_ONCE macro to access variabes that can change asynchronously. Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c |7 --- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c index

[PATCH 7/7] Drivers: hv: vmbus: Implement APIs to support "in place" consumption of vmbus packets

Implement APIs for in-place consumption of vmbus packets. Currently, each packet is copied and processed one at a time and as part of processing each packet we potentially may signal the host (if it is waiting for room to produce a packet). These APIs help batched in-place processing of vmbus

[PATCH 2/7] Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile

Use the READ_ONCE macro to access variabes that can change asynchronously. Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c |7 --- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c index 902375b..2919395

[PATCH 3/7] Drivers: hv: vmbus: Fix a bug in hv_need_to_signal_on_read()

We need to issue a full memory barrier prior making a signalling decision. Signed-off-by: K. Y. Srinivasan Cc: sta...@vger.kernel.org --- drivers/hv/ring_buffer.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/hv/ring_buffer.c

[PATCH 6/7] Drivers: hv: vmbus: Move some ring buffer functions to hyperv.h

In preparation for implementing APIs for in-place consumption of VMBUS packets, movve some ring buffer functionality into hyperv.h Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 42 -- include/linux/hyperv.h | 42

[PATCH 3/7] Drivers: hv: vmbus: Fix a bug in hv_need_to_signal_on_read()

We need to issue a full memory barrier prior making a signalling decision. Signed-off-by: K. Y. Srinivasan Cc: sta...@vger.kernel.org --- drivers/hv/ring_buffer.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c index

[PATCH 6/7] Drivers: hv: vmbus: Move some ring buffer functions to hyperv.h

In preparation for implementing APIs for in-place consumption of VMBUS packets, movve some ring buffer functionality into hyperv.h Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 42 -- include/linux/hyperv.h | 42

[PATCH 5/7] Drivers: hv: vmbus: Export the vmbus_set_event() API

In preparation for moving some ring buffer functionality out of the vmbus driver, export the API for signaling the host. Signed-off-by: K. Y. Srinivasan --- drivers/hv/connection.c |1 + drivers/hv/hyperv_vmbus.h |2 -- include/linux/hyperv.h|1 + 3 files

[PATCH 1/7] Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer

Introduce separate functions for estimating how much can be read from and written to the ring buffer. Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 24 include/linux/hyperv.h | 27 +++ 2 files changed,

[PATCH 4/7] Drivers: hv: vmbus: Use the new virt_xx barrier code

Use the virt_xx barriers that have been defined for use in virtual machines. Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 14 +++--- 1 files changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c

[PATCH 5/7] Drivers: hv: vmbus: Export the vmbus_set_event() API

In preparation for moving some ring buffer functionality out of the vmbus driver, export the API for signaling the host. Signed-off-by: K. Y. Srinivasan --- drivers/hv/connection.c |1 + drivers/hv/hyperv_vmbus.h |2 -- include/linux/hyperv.h|1 + 3 files changed, 2

[PATCH 1/7] Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer

Introduce separate functions for estimating how much can be read from and written to the ring buffer. Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 24 include/linux/hyperv.h | 27 +++ 2 files changed, 31 insertions(+), 20

[PATCH 4/7] Drivers: hv: vmbus: Use the new virt_xx barrier code

Use the virt_xx barriers that have been defined for use in virtual machines. Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 14 +++--- 1 files changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c index

[PATCH 0/7] Drivers: hv: vmbus: Cleanup the ring buffer code

Cleanup and fix a bug in the ring buffer code. Also implement APIs for in place consumption of received packets. K. Y. Srinivasan (7): Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile

[PATCH 0/7] Drivers: hv: vmbus: Cleanup the ring buffer code

Cleanup and fix a bug in the ring buffer code. Also implement APIs for in place consumption of received packets. K. Y. Srinivasan (7): Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile

Re: [Patch V2 2/2] iommu: remove sysfs_link to device in iommu_group/devices when failed

On Wed, 23 Mar 2016 22:25:11 + Wei Yang wrote: > The original code forgets to remove the sysfs_link to a device in > iommu_group/devices directory, when the creation fails or conflicts on the > name. > > This patch tries to remove the sysfs_link on the failure. >

Re: [Patch V2 2/2] iommu: remove sysfs_link to device in iommu_group/devices when failed

On Wed, 23 Mar 2016 22:25:11 + Wei Yang wrote: > The original code forgets to remove the sysfs_link to a device in > iommu_group/devices directory, when the creation fails or conflicts on the > name. > > This patch tries to remove the sysfs_link on the failure. > > Signed-off-by: Wei Yang

Re: linux-next: manual merge of the rdma tree with the net-next tree

On Wed, Mar 16, 2016 at 7:44 PM, Linus Torvalds wrote: > On Wed, Mar 16, 2016 at 10:35 AM, Doug Ledford wrote: >> On 3/16/2016 1:18 PM, Linus Torvalds wrote: >>> On Tue, Mar 15, 2016 at 5:58 PM, Stephen Rothwell >>>

Re: linux-next: manual merge of the rdma tree with the net-next tree

On Wed, Mar 16, 2016 at 7:44 PM, Linus Torvalds wrote: > On Wed, Mar 16, 2016 at 10:35 AM, Doug Ledford wrote: >> On 3/16/2016 1:18 PM, Linus Torvalds wrote: >>> On Tue, Mar 15, 2016 at 5:58 PM, Stephen Rothwell >>> wrote: I fixed it up (see below) and can carry the fix as necessary (no

[PATCH] staging: xgifb: remove extra braces from if stmt (single branch)

Remove braces from one branch of if statement where both branches only have a single line of code, as suggested in Documentation/CodingStyle Signed-off-by: Nicholas Sim --- drivers/staging/xgifb/vb_setmode.c | 8 1 file changed, 4 insertions(+), 4 deletions(-)

[PATCH] staging: xgifb: remove extra braces from if stmt (single branch)

Remove braces from one branch of if statement where both branches only have a single line of code, as suggested in Documentation/CodingStyle Signed-off-by: Nicholas Sim --- drivers/staging/xgifb/vb_setmode.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH] staging: xgifb: ensure braces on all arms of if stmt

Added braces on else arm of if statement where if arm already has braces as suggested for clarity in Documentation/CodingStyle Signed-off-by: Nicholas Sim --- drivers/staging/xgifb/vb_setmode.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH] staging: xgifb: ensure braces on all arms of if stmt

Added braces on else arm of if statement where if arm already has braces as suggested for clarity in Documentation/CodingStyle Signed-off-by: Nicholas Sim --- drivers/staging/xgifb/vb_setmode.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH] gpio / ACPI: ignore GpioInt() GPIOs when requesting GPIO_OUT_*

From: Dmitry Torokhov When firmware does not use _DSD properties that allow properly name GPIO resources, the kernel falls back on parsing _CRS resources, and will return entries described as GpioInt() as general purpose GPIOs even though they are meant to be used simply as

[PATCH] gpio / ACPI: ignore GpioInt() GPIOs when requesting GPIO_OUT_*

From: Dmitry Torokhov When firmware does not use _DSD properties that allow properly name GPIO resources, the kernel falls back on parsing _CRS resources, and will return entries described as GpioInt() as general purpose GPIOs even though they are meant to be used simply as interrupt sources for

Proposal for Anti-Keystroke Fingerprinting at the Input Driver Level

== Attack Description == Keystroke fingerprinting works by measuring how long keys are pressed and the time between presses. Its very high accuracy poses a serious threat to anonymous users.[1] This tracking technology has been deployed by major advertisers (Google, Facebook), banks and

Proposal for Anti-Keystroke Fingerprinting at the Input Driver Level

== Attack Description == Keystroke fingerprinting works by measuring how long keys are pressed and the time between presses. Its very high accuracy poses a serious threat to anonymous users.[1] This tracking technology has been deployed by major advertisers (Google, Facebook), banks and

Re: [tip:perf/urgent] perf/x86/cqm: Fix CQM handling of grouping events into a cache_group

On Wed, 23 Mar 2016, Matt Fleming wrote: On Mon, 21 Mar, at 11:14:37AM, Vikas Shivappa wrote: Before MBM , the below condition was never hit because we had only one event ? - if (a->hw.target == b->hw.target) + if (a->hw.target == b->hw.target) { +

Re: [tip:perf/urgent] perf/x86/cqm: Fix CQM handling of grouping events into a cache_group

On Wed, 23 Mar 2016, Matt Fleming wrote: On Mon, 21 Mar, at 11:14:37AM, Vikas Shivappa wrote: Before MBM , the below condition was never hit because we had only one event ? - if (a->hw.target == b->hw.target) + if (a->hw.target == b->hw.target) { +

Re: [PATCH 08/17] watchdog: qcom: configure BARK time in addition to BITE time

On 03/23, Matthew McClintock wrote: > For certain parts and some versions of TZ, TZ will reset the chip > when a BARK is triggered even though it was not configured here. So > by default let's configure this BARK time as well. > Why isn't TZ configuring the bark time to what it wants? I'm lost

Re: [PATCH 08/17] watchdog: qcom: configure BARK time in addition to BITE time

On 03/23, Matthew McClintock wrote: > For certain parts and some versions of TZ, TZ will reset the chip > when a BARK is triggered even though it was not configured here. So > by default let's configure this BARK time as well. > Why isn't TZ configuring the bark time to what it wants? I'm lost

Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support

On Tue, Mar 22, 2016 at 1:25 PM, Kees Cook wrote: > On Tue, Mar 22, 2016 at 12:31 AM, Baoquan He wrote: >> ***Background: >> Previously a bug is reported that kdump didn't work when kaslr is enabled. >> During >> discussing that bug fix, we found current

Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support

On Tue, Mar 22, 2016 at 1:25 PM, Kees Cook wrote: > On Tue, Mar 22, 2016 at 12:31 AM, Baoquan He wrote: >> ***Background: >> Previously a bug is reported that kdump didn't work when kaslr is enabled. >> During >> discussing that bug fix, we found current kaslr has a limilation that it can >>

Re: [PATCH 07/17] watchdog: qcom: add option for standalone watchdog not in timer block

On 03/23, Matthew McClintock wrote: > @@ -202,13 +238,6 @@ static int qcom_wdt_remove(struct platform_device *pdev) > return 0; > } > > -static const struct of_device_id qcom_wdt_of_table[] = { > - { .compatible = "qcom,kpss-timer" }, > - { .compatible = "qcom,scss-timer" }, > -

Re: [PATCH 07/17] watchdog: qcom: add option for standalone watchdog not in timer block

On 03/23, Matthew McClintock wrote: > @@ -202,13 +238,6 @@ static int qcom_wdt_remove(struct platform_device *pdev) > return 0; > } > > -static const struct of_device_id qcom_wdt_of_table[] = { > - { .compatible = "qcom,kpss-timer" }, > - { .compatible = "qcom,scss-timer" }, > -

[PATCH v3] sparc/PCI: Fix for panic while enabling SR-IOV

We noticed this panic while enabling SR-IOV in sparc. mlx4_core: Mellanox ConnectX core driver v2.2-1 (Jan 1 2015) mlx4_core: Initializing 0007:01:00.0 mlx4_core 0007:01:00.0: Enabling SR-IOV with 5 VFs mlx4_core: Initializing 0007:01:00.1 Unable to handle kernel NULL pointer dereference

[PATCH v3] sparc/PCI: Fix for panic while enabling SR-IOV

We noticed this panic while enabling SR-IOV in sparc. mlx4_core: Mellanox ConnectX core driver v2.2-1 (Jan 1 2015) mlx4_core: Initializing 0007:01:00.0 mlx4_core 0007:01:00.0: Enabling SR-IOV with 5 VFs mlx4_core: Initializing 0007:01:00.1 Unable to handle kernel NULL pointer dereference

[PATCH] staging: rtl8188eu: remove return at end of void function call

Remove unnecessary return statements from last lines of void function call (several) Signed-off-by: Nicholas Sim --- drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 17 - 1 file changed, 17 deletions(-) diff --git

[PATCH] staging: rtl8188eu: remove return at end of void function call

Remove unnecessary return statements from last lines of void function call (several) Signed-off-by: Nicholas Sim --- drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 17 - 1 file changed, 17 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c

Re: [PATCH 15/17] qcom: ipq4019: add cpu operating points for cpufreq support

On 03/23/2016 03:05 PM, Matthew McClintock wrote: > This adds some operating points for cpu frequeny scaling > > Signed-off-by: Matthew McClintock > --- Can you use the v2 OPP bindings instead? I imagine uV could be left out then because there isn't any regulator

Re: [PATCH 15/17] qcom: ipq4019: add cpu operating points for cpufreq support

On 03/23/2016 03:05 PM, Matthew McClintock wrote: > This adds some operating points for cpu frequeny scaling > > Signed-off-by: Matthew McClintock > --- Can you use the v2 OPP bindings instead? I imagine uV could be left out then because there isn't any regulator control? -- Qualcomm

Re: [RFT PATCH] [media] exynos4-is: Fix fimc_is_parse_sensor_config() nodes handling

Hi Javier, Am 23.03.2016 um 17:15 schrieb Javier Martinez Canillas: > The same struct device_node * is used for looking up the I2C sensor, OF > graph endpoint and port. So the reference count is incremented but not > decremented for the endpoint and port nodes. > > Fix this by having separate

Re: [RFT PATCH] [media] exynos4-is: Fix fimc_is_parse_sensor_config() nodes handling

Hi Javier, Am 23.03.2016 um 17:15 schrieb Javier Martinez Canillas: > The same struct device_node * is used for looking up the I2C sensor, OF > graph endpoint and port. So the reference count is incremented but not > decremented for the endpoint and port nodes. > > Fix this by having separate

Re: [PATCH 06/17] watchdog: qcom: update device tree bindings

On 03/23/2016 03:05 PM, Matthew McClintock wrote: > Update the compatible string to align with driver > > CC: linux-watch...@vger.kernel.org > Signed-off-by: Matthew McClintock I had a patch similar to this before

Re: [PATCH 06/17] watchdog: qcom: update device tree bindings

On 03/23/2016 03:05 PM, Matthew McClintock wrote: > Update the compatible string to align with driver > > CC: linux-watch...@vger.kernel.org > Signed-off-by: Matthew McClintock I had a patch similar to this before http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/325235.html

Re: [PATCH] iommu: remove the iommu_callback_data

Obsolete this one, V2 is sent. On Sun, Mar 20, 2016 at 01:57:52AM +, Wei Yang wrote: >According to the code path, iommu_callback_data is passed in >iommu_bus_init() and just used in {add/remove}_iommu_group, by when the >bus->iommu_ops is already set up properly. > >This patch removes the

Re: [PATCH] iommu: remove the iommu_callback_data

Obsolete this one, V2 is sent. On Sun, Mar 20, 2016 at 01:57:52AM +, Wei Yang wrote: >According to the code path, iommu_callback_data is passed in >iommu_bus_init() and just used in {add/remove}_iommu_group, by when the >bus->iommu_ops is already set up properly. > >This patch removes the

[Patch V2 2/2] iommu: remove sysfs_link to device in iommu_group/devices when failed

The original code forgets to remove the sysfs_link to a device in iommu_group/devices directory, when the creation fails or conflicts on the name. This patch tries to remove the sysfs_link on the failure. Signed-off-by: Wei Yang --- drivers/iommu/iommu.c |1 + 1

[Patch V2 0/2] Cleanup on IOMMU

This two patches tries to do some cleanup in iommu. V2: * add patch 2 Wei Yang (2): iommu: remove the iommu_callback_data iommu: remove sysfs_link to device in iommu_group/devices when failed drivers/iommu/iommu.c | 22 +++--- 1 file changed, 7 insertions(+), 15

[Patch V2 2/2] iommu: remove sysfs_link to device in iommu_group/devices when failed

The original code forgets to remove the sysfs_link to a device in iommu_group/devices directory, when the creation fails or conflicts on the name. This patch tries to remove the sysfs_link on the failure. Signed-off-by: Wei Yang --- drivers/iommu/iommu.c |1 + 1 file changed, 1

[Patch V2 0/2] Cleanup on IOMMU

This two patches tries to do some cleanup in iommu. V2: * add patch 2 Wei Yang (2): iommu: remove the iommu_callback_data iommu: remove sysfs_link to device in iommu_group/devices when failed drivers/iommu/iommu.c | 22 +++--- 1 file changed, 7 insertions(+), 15

[Patch V2 1/2] iommu: remove the iommu_callback_data

According to the code path, iommu_callback_data is passed in iommu_bus_init() and just used in {add/remove}_iommu_group, by when the bus->iommu_ops is already set up properly. This patch removes the iommu_callback_data by retrieving iommu_ops from bus->iommu_ops directly. Signed-off-by: Wei

[Patch V2 1/2] iommu: remove the iommu_callback_data

According to the code path, iommu_callback_data is passed in iommu_bus_init() and just used in {add/remove}_iommu_group, by when the bus->iommu_ops is already set up properly. This patch removes the iommu_callback_data by retrieving iommu_ops from bus->iommu_ops directly. Signed-off-by: Wei

[PATCH 4/4] arm64: dts: marvell: Rename armada-ap806 XOR nodes

Petazzoni <thomas.petazz...@free-electrons.com> Signed-off-by: Andreas Färber <afaer...@suse.de> --- "marvell,mv-xor-v2" is not yet referenced from any driver in next-20160323. arch/arm64/boot/dts/marvell/armada-ap806.dtsi | 8 1 file changed, 4 insertions(+), 4 delet

[PATCH 1/4] arm64: dts: marvell: Clean up armada-3720-db

Instead of duplicating the SoC's node hierarchy, including a bus node named "internal-regs", reference the actually desired nodes by label, like Berlin already does. Add labels where necessary. Drop an inconsistent white line while at it. Fixes: adbc3695d9e4 ("arm64: dts: add the Marvell Armada

[PATCH 2/4] arm64: dts: marvell: Rename armada-37xx USB node

No need to reflect the USB version in the node name. Fixes: adbc3695d9e4 ("arm64: dts: add the Marvell Armada 3700 family and a development board") Cc: Gregory CLEMENT Signed-off-by: Andreas Färber ---

[PATCH 4/4] arm64: dts: marvell: Rename armada-ap806 XOR nodes

Petazzoni Signed-off-by: Andreas Färber --- "marvell,mv-xor-v2" is not yet referenced from any driver in next-20160323. arch/arm64/boot/dts/marvell/armada-ap806.dtsi | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm64/boot/dts/marvell/armada-ap806.dts

[PATCH 1/4] arm64: dts: marvell: Clean up armada-3720-db

Instead of duplicating the SoC's node hierarchy, including a bus node named "internal-regs", reference the actually desired nodes by label, like Berlin already does. Add labels where necessary. Drop an inconsistent white line while at it. Fixes: adbc3695d9e4 ("arm64: dts: add the Marvell Armada

[PATCH 2/4] arm64: dts: marvell: Rename armada-37xx USB node

No need to reflect the USB version in the node name. Fixes: adbc3695d9e4 ("arm64: dts: add the Marvell Armada 3700 family and a development board") Cc: Gregory CLEMENT Signed-off-by: Andreas Färber --- arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 3/4] arm64: dts: marvell: Clean up armada-7040-db

Instead of duplicating the node hierarchy, reference the nodes by label, adding labels where necessary. Drop some trailing or inconsistent white lines while at it. Fixes: ec7e5a569bce ("arm64: dts: marvell: add Device Tree files for Armada 7K/8K") Cc: Thomas Petazzoni

[PATCH 3/4] arm64: dts: marvell: Clean up armada-7040-db

Instead of duplicating the node hierarchy, reference the nodes by label, adding labels where necessary. Drop some trailing or inconsistent white lines while at it. Fixes: ec7e5a569bce ("arm64: dts: marvell: add Device Tree files for Armada 7K/8K") Cc: Thomas Petazzoni Signed-off-by: Andreas

[PATCH 04/17] clk: qcom: ipq4019: switch remaining defines to enums

When this was added not all the remaining defines were switched over to use enums, so let's complete that process here Reported-by: Stephen Boyd Signed-off-by: Matthew McClintock --- drivers/clk/qcom/gcc-ipq4019.c | 60

[PATCH 04/17] clk: qcom: ipq4019: switch remaining defines to enums

When this was added not all the remaining defines were switched over to use enums, so let's complete that process here Reported-by: Stephen Boyd Signed-off-by: Matthew McClintock --- drivers/clk/qcom/gcc-ipq4019.c | 60 ++ 1 file changed, 25

[PATCH 11/17] qcom: ipq4019: add support for reset via qcom,ps-hold

This will allow these types of boards to be rebooted. Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi b/arch/arm/boot/dts/qcom-ipq4019.dtsi index

[PATCH 11/17] qcom: ipq4019: add support for reset via qcom,ps-hold

This will allow these types of boards to be rebooted. Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi b/arch/arm/boot/dts/qcom-ipq4019.dtsi index 00a5e9e..acb851d 100644 ---

[PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding

Update the compatible string to add new device tree binding CC: linux-watch...@vger.kernel.org Signed-off-by: Matthew McClintock --- Documentation/devicetree/bindings/watchdog/qcom-wdt.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 06/17] watchdog: qcom: update device tree bindings

Update the compatible string to align with driver CC: linux-watch...@vger.kernel.org Signed-off-by: Matthew McClintock --- Documentation/devicetree/bindings/watchdog/qcom-wdt.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding

Update the compatible string to add new device tree binding CC: linux-watch...@vger.kernel.org Signed-off-by: Matthew McClintock --- Documentation/devicetree/bindings/watchdog/qcom-wdt.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 06/17] watchdog: qcom: update device tree bindings

Update the compatible string to align with driver CC: linux-watch...@vger.kernel.org Signed-off-by: Matthew McClintock --- Documentation/devicetree/bindings/watchdog/qcom-wdt.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 07/17] watchdog: qcom: add option for standalone watchdog not in timer block

Commit 0dfd582e026a ("watchdog: qcom: use timer devicetree binding") moved to use the watchdog as a subset timer register block. Some devices have the watchdog completely standalone with slightly different register offsets as well so let's account for the differences here. Signed-off-by: Matthew

[PATCH 13/17] qcom: ipq4019: add i2c node to ipq4019 SoC and DK01 device tree

This will allow boards to enable the I2C bus CC: Sricharan R Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 13 + 1 file changed, 13 insertions(+) diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi

[PATCH 07/17] watchdog: qcom: add option for standalone watchdog not in timer block

Commit 0dfd582e026a ("watchdog: qcom: use timer devicetree binding") moved to use the watchdog as a subset timer register block. Some devices have the watchdog completely standalone with slightly different register offsets as well so let's account for the differences here. Signed-off-by: Matthew

[PATCH 13/17] qcom: ipq4019: add i2c node to ipq4019 SoC and DK01 device tree

This will allow boards to enable the I2C bus CC: Sricharan R Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 13 + 1 file changed, 13 insertions(+) diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi b/arch/arm/boot/dts/qcom-ipq4019.dtsi index

[PATCH 10/17] qcom: ipq4019: add watchdog node to ipq4019 SoC and DK01 device tree

This will allow boards to enable watchdog support Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi | 4 arch/arm/boot/dts/qcom-ipq4019.dtsi | 8 2 files changed, 12 insertions(+) diff --git

[PATCH 12/17] qcom: ipq4019: add spi node to ipq4019 SoC and DK01 device tree

This will allow boards to enable the SPI bus Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi | 37 +++ arch/arm/boot/dts/qcom-ipq4019.dtsi | 18 + 2 files changed, 55 insertions(+) diff

[PATCH 10/17] qcom: ipq4019: add watchdog node to ipq4019 SoC and DK01 device tree

This will allow boards to enable watchdog support Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi | 4 arch/arm/boot/dts/qcom-ipq4019.dtsi | 8 2 files changed, 12 insertions(+) diff --git

[PATCH 12/17] qcom: ipq4019: add spi node to ipq4019 SoC and DK01 device tree

This will allow boards to enable the SPI bus Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi | 37 +++ arch/arm/boot/dts/qcom-ipq4019.dtsi | 18 + 2 files changed, 55 insertions(+) diff --git

[PATCH 16/17] qcom: ipq4019: add crypto nodes to ipq4019 SoC and DK01 device tree

This adds the crypto nodes to the ipq4019 device tree, it also adds the BAM node used by crypto as well which the driver currently requires to operate properly The crypto driver itself depends on some other patches to qcom_bam_dma to function properly: https://lkml.org/lkml/2015/12/1/113 CC:

[PATCH 15/17] qcom: ipq4019: add cpu operating points for cpufreq support

This adds some operating points for cpu frequeny scaling Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi b/arch/arm/boot/dts/qcom-ipq4019.dtsi

[PATCH 15/17] qcom: ipq4019: add cpu operating points for cpufreq support

This adds some operating points for cpu frequeny scaling Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi b/arch/arm/boot/dts/qcom-ipq4019.dtsi index 1937edf..db48fd3 100644

[PATCH 16/17] qcom: ipq4019: add crypto nodes to ipq4019 SoC and DK01 device tree

This adds the crypto nodes to the ipq4019 device tree, it also adds the BAM node used by crypto as well which the driver currently requires to operate properly The crypto driver itself depends on some other patches to qcom_bam_dma to function properly: https://lkml.org/lkml/2015/12/1/113 CC:

[PATCH 14/17] cpufreq: ipq4019: add cpufreq driver

Add cpufreq driver for ipq4019 SoC. This driver simply instantiates cpufreq-dt. Signed-off-by: Matthew McClintock --- drivers/cpufreq/Kconfig.arm | 9 + drivers/cpufreq/Makefile | 1 + drivers/cpufreq/ipq4019-cpufreq.c | 35

[PATCH 08/17] watchdog: qcom: configure BARK time in addition to BITE time

For certain parts and some versions of TZ, TZ will reset the chip when a BARK is triggered even though it was not configured here. So by default let's configure this BARK time as well. Signed-off-by: Matthew McClintock --- drivers/watchdog/qcom-wdt.c | 5 + 1 file

[PATCH 14/17] cpufreq: ipq4019: add cpufreq driver

Add cpufreq driver for ipq4019 SoC. This driver simply instantiates cpufreq-dt. Signed-off-by: Matthew McClintock --- drivers/cpufreq/Kconfig.arm | 9 + drivers/cpufreq/Makefile | 1 + drivers/cpufreq/ipq4019-cpufreq.c | 35 +++ 3 files

[PATCH 08/17] watchdog: qcom: configure BARK time in addition to BITE time

For certain parts and some versions of TZ, TZ will reset the chip when a BARK is triggered even though it was not configured here. So by default let's configure this BARK time as well. Signed-off-by: Matthew McClintock --- drivers/watchdog/qcom-wdt.c | 5 + 1 file changed, 5 insertions(+)

[PATCH 05/17] clk: qcom: ipq4019: add some fixed clocks for ddrppl and fepll

Drivers for these don't exist yet so we will add them as fixed clocks so we don't BUG() if we change clocks that reference these clocks. Signed-off-by: Matthew McClintock --- drivers/clk/qcom/gcc-ipq4019.c | 10 ++ 1 file changed, 10 insertions(+) diff --git

[PATCH 17/17] qcom: ipq4019: add DMA nodes to ipq4019 SoC and DK01 device tree

This adds the blsp_dma node to the device tree and the required properties for using DMA with serial Signed-off-by: Matthew McClintock --- arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi | 4 arch/arm/boot/dts/qcom-ipq4019.dtsi | 15 +++ 2

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