Re: [PATCH 00/13] various remoteproc/rpmsg trivial cleanups

On Fri 12 Aug 16:42 PDT 2016, Suman Anna wrote: > Hi Bjorn, > > Following are a bunch of trivial cleanups in remoteproc core, rpmsg > bus core and couple of cleanups in OMAP remoteproc driver. The patches > are baselined on 4.8-rc1 + your rproc-next branch. > > The only non-cleanup patches are

Re: [PATCH 00/13] various remoteproc/rpmsg trivial cleanups

On Fri 12 Aug 16:42 PDT 2016, Suman Anna wrote: > Hi Bjorn, > > Following are a bunch of trivial cleanups in remoteproc core, rpmsg > bus core and couple of cleanups in OMAP remoteproc driver. The patches > are baselined on 4.8-rc1 + your rproc-next branch. > > The only non-cleanup patches are

Re: [Documentation] State of CPU controller in cgroup v2

On Fri, 2016-08-12 at 18:17 -0400, Johannes Weiner wrote: > > > This argument that cgroup2 is not backward compatible is laughable. > > > > Fine, you're entitled to your sense of humor. I have one to, I find it > > laughable that threaded applications can only sit there like a lump of > > mud

Re: [Documentation] State of CPU controller in cgroup v2

On Fri, 2016-08-12 at 18:17 -0400, Johannes Weiner wrote: > > > This argument that cgroup2 is not backward compatible is laughable. > > > > Fine, you're entitled to your sense of humor. I have one to, I find it > > laughable that threaded applications can only sit there like a lump of > > mud

Re: [RFC linux-next] ARM: clps711x: update defconfig

Yes, the configuration has migrated to v4t_multi_defconfig, so this file could be removed. >Суббота, 13 августа 2016, 0:05 +03:00 от Fabian Frederick : > >sync defconfig to commit 4a56f46a7dc6 >("ARM: clps711x: Remove boards support") > >or maybe we could just remove it ? >

Re: [RFC linux-next] ARM: clps711x: update defconfig

Yes, the configuration has migrated to v4t_multi_defconfig, so this file could be removed. >Суббота, 13 августа 2016, 0:05 +03:00 от Fabian Frederick : > >sync defconfig to commit 4a56f46a7dc6 >("ARM: clps711x: Remove boards support") > >or maybe we could just remove it ? > >Signed-off-by:

[PATCH] drm/tegra: dpaux: Modify error handling

devm_pinctrl_register returns an ERR_PTR in case of error and should have an IS_ERR check instead of a null check. The Coccinelle semantic patch used to make this change is as follows: @@ expression e; @@ e = devm_pinxtrl_register(...); if( -!e +IS_ERR(e) ) { <+... return -

Re: Applied "regulator: qcom_smd: Fix voltage ranges for pm8x41" to the regulator tree

On Fri 05 Aug 05:09 PDT 2016, Mark Brown wrote: > The patch > >regulator: qcom_smd: Fix voltage ranges for pm8x41 > Hi Mark, I have a boot regression with v4.8-rc1 on the Honami (msm8974): [1.796020] l24: Bringing 0uV into 3075000-3075000uV [1.796236] l24: unsupportable voltage

[PATCH] drm/tegra: dpaux: Modify error handling

devm_pinctrl_register returns an ERR_PTR in case of error and should have an IS_ERR check instead of a null check. The Coccinelle semantic patch used to make this change is as follows: @@ expression e; @@ e = devm_pinxtrl_register(...); if( -!e +IS_ERR(e) ) { <+... return -

Re: Applied "regulator: qcom_smd: Fix voltage ranges for pm8x41" to the regulator tree

On Fri 05 Aug 05:09 PDT 2016, Mark Brown wrote: > The patch > >regulator: qcom_smd: Fix voltage ranges for pm8x41 > Hi Mark, I have a boot regression with v4.8-rc1 on the Honami (msm8974): [1.796020] l24: Bringing 0uV into 3075000-3075000uV [1.796236] l24: unsupportable voltage

Re: [PATCH net 2/4] hv_netvsc: reset vf_inject on VF removal

From: Vitaly Kuznetsov Date: Thu, 11 Aug 2016 12:58:55 +0200 > We reset vf_inject on VF going down (netvsc_vf_down()) but we don't on > VF removal (netvsc_unregister_vf()) so vf_inject stays 'true' while > vf_netdev is already NULL and we're trying to inject packets into

Re: [PATCH net 2/4] hv_netvsc: reset vf_inject on VF removal

From: Vitaly Kuznetsov Date: Thu, 11 Aug 2016 12:58:55 +0200 > We reset vf_inject on VF going down (netvsc_vf_down()) but we don't on > VF removal (netvsc_unregister_vf()) so vf_inject stays 'true' while > vf_netdev is already NULL and we're trying to inject packets into NULL > net device in

[PATCH v2 5/6] kexec: Share logic to copy segment page contents.

Make kimage_load_normal_segment and kexec_update_segment share code which they currently duplicate. Signed-off-by: Thiago Jung Bauermann --- kernel/kexec_core.c | 159 +++- 1 file changed, 95 insertions(+), 64

[PATCH v2 6/6] IMA: Demonstration code for kexec buffer passing.

This patch is not intended to be committed. It shows how kernel code can use the kexec buffer passing mechanism to pass information to the next kernel. Signed-off-by: Thiago Jung Bauermann --- include/linux/ima.h | 11 + kernel/kexec_file.c

[PATCH v2 4/6] kexec_file: Add mechanism to update kexec segments.

kexec_update_segment allows a given segment in kexec_image to have its contents updated. This is useful if the current kernel wants to send information to the next kernel that is up-to-date at the time of reboot. Signed-off-by: Thiago Jung Bauermann ---

[PATCH v2 5/6] kexec: Share logic to copy segment page contents.

Make kimage_load_normal_segment and kexec_update_segment share code which they currently duplicate. Signed-off-by: Thiago Jung Bauermann --- kernel/kexec_core.c | 159 +++- 1 file changed, 95 insertions(+), 64 deletions(-) diff --git

[PATCH v2 6/6] IMA: Demonstration code for kexec buffer passing.

This patch is not intended to be committed. It shows how kernel code can use the kexec buffer passing mechanism to pass information to the next kernel. Signed-off-by: Thiago Jung Bauermann --- include/linux/ima.h | 11 + kernel/kexec_file.c | 4 ++

[PATCH v2 4/6] kexec_file: Add mechanism to update kexec segments.

kexec_update_segment allows a given segment in kexec_image to have its contents updated. This is useful if the current kernel wants to send information to the next kernel that is up-to-date at the time of reboot. Signed-off-by: Thiago Jung Bauermann --- include/linux/kexec.h | 2 ++

[PATCH v2 1/6] kexec_file: Add buffer hand-over support for the next kernel

The buffer hand-over mechanism allows the currently running kernel to pass data to kernel that will be kexec'd via a kexec segment. The second kernel can check whether the previous kernel sent data and retrieve it. This is the architecture-independent part of the feature. Signed-off-by: Thiago

[PATCH v2 1/6] kexec_file: Add buffer hand-over support for the next kernel

The buffer hand-over mechanism allows the currently running kernel to pass data to kernel that will be kexec'd via a kexec segment. The second kernel can check whether the previous kernel sent data and retrieve it. This is the architecture-independent part of the feature. Signed-off-by: Thiago

[PATCH v2 2/6] powerpc: kexec_file: Add buffer hand-over support for the next kernel

The buffer hand-over mechanism allows the currently running kernel to pass data to kernel that will be kexec'd via a kexec segment. The second kernel can check whether the previous kernel sent data and retrieve it. This is the architecture-specific part. Signed-off-by: Thiago Jung Bauermann

[PATCH v2 3/6] kexec_file: Allow skipping checksum calculation for some segments.

Adds checksum argument to kexec_add_buffer specifying whether the given segment should be part of the checksum calculation. The next patch will add a way to update segments after a kimage is loaded. Segments that will be updated in this way should not be checksummed, otherwise they will cause the

[PATCH v2 0/6] kexec_file: Add buffer hand-over for the next kernel

Hello, This patch series implements a mechanism which allows the kernel to pass on a buffer to the kernel that will be kexec'd. This buffer is passed as a segment which is added to the kimage when it is being prepared by kexec_file_load. How the second kernel is informed of this buffer is

[PATCH v2 2/6] powerpc: kexec_file: Add buffer hand-over support for the next kernel

The buffer hand-over mechanism allows the currently running kernel to pass data to kernel that will be kexec'd via a kexec segment. The second kernel can check whether the previous kernel sent data and retrieve it. This is the architecture-specific part. Signed-off-by: Thiago Jung Bauermann ---

[PATCH v2 3/6] kexec_file: Allow skipping checksum calculation for some segments.

Adds checksum argument to kexec_add_buffer specifying whether the given segment should be part of the checksum calculation. The next patch will add a way to update segments after a kimage is loaded. Segments that will be updated in this way should not be checksummed, otherwise they will cause the

[PATCH v2 0/6] kexec_file: Add buffer hand-over for the next kernel

Hello, This patch series implements a mechanism which allows the kernel to pass on a buffer to the kernel that will be kexec'd. This buffer is passed as a segment which is added to the kimage when it is being prepared by kexec_file_load. How the second kernel is informed of this buffer is

[RFC 2/7] tty: add support for "tty slave" devices

From: NeilBrown A "tty slave" is a device connected via UART. It may need a driver to, for example, power the device on when the tty is opened, and power it off when the tty is released. Signed-off-by: NeilBrown Signed-off-by: Sebastian Reichel

[RFC 2/7] tty: add support for "tty slave" devices

From: NeilBrown A "tty slave" is a device connected via UART. It may need a driver to, for example, power the device on when the tty is opened, and power it off when the tty is released. Signed-off-by: NeilBrown Signed-off-by: Sebastian Reichel ---

[RFC 5/7] Bluetooth: hci_nokia: Introduce new driver

This driver adds support for Nokia H4+ procotol used for example by Nokia's internet tablets (N770 - N950). --- drivers/bluetooth/Kconfig | 10 + drivers/bluetooth/Makefile| 1 + drivers/bluetooth/hci_ldisc.c | 6 + drivers/bluetooth/hci_nokia.c | 734

[RFC 4/7] Bluetooth: hci_uart: Add support for word alignment

This will be used by Nokia's H4+ protocol, which adds padding to packets to reach word alignment. --- drivers/bluetooth/hci_h4.c | 10 ++ drivers/bluetooth/hci_uart.h | 1 + 2 files changed, 11 insertions(+) diff --git a/drivers/bluetooth/hci_h4.c b/drivers/bluetooth/hci_h4.c index

[RFC 7/7] ARM: dts: OMAP3-N950: Add bluetooth

--- arch/arm/boot/dts/omap3-n950-n9.dtsi | 34 ++ 1 file changed, 34 insertions(+) diff --git a/arch/arm/boot/dts/omap3-n950-n9.dtsi b/arch/arm/boot/dts/omap3-n950-n9.dtsi index 927b17fc4ed8..7c0c53e2f679 100644 --- a/arch/arm/boot/dts/omap3-n950-n9.dtsi +++

[RFC 6/7] ARM: dts: OMAP3-N900: Add bluetooth

Add bcm2048 node and its system clock to the N900 device tree file. Apart from that a reference to the new clock has been added to wl1251 (which uses it, too). Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap3-n900.dts | 22 +- 1 file changed, 21

[RFC 4/7] Bluetooth: hci_uart: Add support for word alignment

This will be used by Nokia's H4+ protocol, which adds padding to packets to reach word alignment. --- drivers/bluetooth/hci_h4.c | 10 ++ drivers/bluetooth/hci_uart.h | 1 + 2 files changed, 11 insertions(+) diff --git a/drivers/bluetooth/hci_h4.c b/drivers/bluetooth/hci_h4.c index

[RFC 7/7] ARM: dts: OMAP3-N950: Add bluetooth

--- arch/arm/boot/dts/omap3-n950-n9.dtsi | 34 ++ 1 file changed, 34 insertions(+) diff --git a/arch/arm/boot/dts/omap3-n950-n9.dtsi b/arch/arm/boot/dts/omap3-n950-n9.dtsi index 927b17fc4ed8..7c0c53e2f679 100644 --- a/arch/arm/boot/dts/omap3-n950-n9.dtsi +++

[RFC 6/7] ARM: dts: OMAP3-N900: Add bluetooth

Add bcm2048 node and its system clock to the N900 device tree file. Apart from that a reference to the new clock has been added to wl1251 (which uses it, too). Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap3-n900.dts | 22 +- 1 file changed, 21 insertions(+), 1

[RFC 5/7] Bluetooth: hci_nokia: Introduce new driver

This driver adds support for Nokia H4+ procotol used for example by Nokia's internet tablets (N770 - N950). --- drivers/bluetooth/Kconfig | 10 + drivers/bluetooth/Makefile| 1 + drivers/bluetooth/hci_ldisc.c | 6 + drivers/bluetooth/hci_nokia.c | 734

[RFC 1/7] tty: serial: omap: add UPF_BOOT_AUTOCONF flag for DT init

--- drivers/tty/serial/omap-serial.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/tty/serial/omap-serial.c b/drivers/tty/serial/omap-serial.c index a2a529994ba5..7c2c77789c2c 100644 --- a/drivers/tty/serial/omap-serial.c +++ b/drivers/tty/serial/omap-serial.c @@ -1542,6 +1542,9

[RFC 3/7] dt: bindings: Add nokia-bluetooth

--- .../devicetree/bindings/net/nokia-bluetooth.txt| 43 ++ 1 file changed, 43 insertions(+) create mode 100644 Documentation/devicetree/bindings/net/nokia-bluetooth.txt diff --git a/Documentation/devicetree/bindings/net/nokia-bluetooth.txt

[RFC 1/7] tty: serial: omap: add UPF_BOOT_AUTOCONF flag for DT init

--- drivers/tty/serial/omap-serial.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/tty/serial/omap-serial.c b/drivers/tty/serial/omap-serial.c index a2a529994ba5..7c2c77789c2c 100644 --- a/drivers/tty/serial/omap-serial.c +++ b/drivers/tty/serial/omap-serial.c @@ -1542,6 +1542,9

[RFC 3/7] dt: bindings: Add nokia-bluetooth

--- .../devicetree/bindings/net/nokia-bluetooth.txt| 43 ++ 1 file changed, 43 insertions(+) create mode 100644 Documentation/devicetree/bindings/net/nokia-bluetooth.txt diff --git a/Documentation/devicetree/bindings/net/nokia-bluetooth.txt

[RFC 0/7] Nokia N9xx bluetooth driver

Hi, This series (based von 4.8-rc1) adds support for bluetooth on the Nokia N9xx devices. It has been tested on the Nokia N950, where it works correctly. On Nokia N900 it currently fails during negotiation (probably related to slightly incorrect serial settings/timings). The N900's bcm2048

[RFC 0/7] Nokia N9xx bluetooth driver

Hi, This series (based von 4.8-rc1) adds support for bluetooth on the Nokia N9xx devices. It has been tested on the Nokia N950, where it works correctly. On Nokia N900 it currently fails during negotiation (probably related to slightly incorrect serial settings/timings). The N900's bcm2048

[GIT PULL] Block fixes for 4.8-rc2

Hi Linus, A set of fixes for 4.8-rc2. This pull request contains: - A NVMe fix from Gabriel, fixing a suspend/resume issue on some setups. - Addition of a few missing entries in the block queue sysfs documentation, from Joe. - A fix for a sparse shadow warning for the bvec iterator, from

[GIT PULL] Block fixes for 4.8-rc2

Hi Linus, A set of fixes for 4.8-rc2. This pull request contains: - A NVMe fix from Gabriel, fixing a suspend/resume issue on some setups. - Addition of a few missing entries in the block queue sysfs documentation, from Joe. - A fix for a sparse shadow warning for the bvec iterator, from

Re: [PATCH v6] x86/hpet: Reduce HPET counter read contention

Hi Waiman, [auto build test ERROR on tip/auto-latest] [also build test ERROR on v4.8-rc1 next-20160812] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Waiman-Long/x86-hpet-Reduce-HPET-counter

Re: [PATCH v6] x86/hpet: Reduce HPET counter read contention

Hi Waiman, [auto build test ERROR on tip/auto-latest] [also build test ERROR on v4.8-rc1 next-20160812] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Waiman-Long/x86-hpet-Reduce-HPET-counter

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

From: Anton Blanchard Commit 73cdf0c6ea9c ("perf symbols: Record text offset in dso to calculate objdump address") started storing the offset of the text section for all DSOs: if (elf_section_by_name(elf, , , ".text", NULL)) dso->text_offset =

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

From: Anton Blanchard Commit 73cdf0c6ea9c ("perf symbols: Record text offset in dso to calculate objdump address") started storing the offset of the text section for all DSOs: if (elf_section_by_name(elf, , , ".text", NULL)) dso->text_offset = tshdr.sh_addr -

[PATCH 1/2] clk: fixed-factor: Remove export symbol on setup function

This function is marked __init, so it can't possibly need to be exported to modules. Remove the marking. Cc: Gregory CLEMENT Signed-off-by: Stephen Boyd --- drivers/clk/clk-fixed-factor.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH 2/2] clk: fixed-rate: Remove export symbol on setup function

This function is only called by builtin code, but we always exported it and had marked it as __init before commit e4eda8e0654c (clk: remove exported function from __init section, 2013-01-06) removed that marking. Given that it isn't used by modules, lets unexport it and add back __init. Cc: Denis

[PATCH 1/2] clk: fixed-factor: Remove export symbol on setup function

This function is marked __init, so it can't possibly need to be exported to modules. Remove the marking. Cc: Gregory CLEMENT Signed-off-by: Stephen Boyd --- drivers/clk/clk-fixed-factor.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/clk/clk-fixed-factor.c

[PATCH 2/2] clk: fixed-rate: Remove export symbol on setup function

This function is only called by builtin code, but we always exported it and had marked it as __init before commit e4eda8e0654c (clk: remove exported function from __init section, 2013-01-06) removed that marking. Given that it isn't used by modules, lets unexport it and add back __init. Cc: Denis

[RESEND][PATCH 1/2] phy: bcm-ns2-pcie: Get rid of struct ns2_pci_phy

By setting phy_set_drvdata(phy, mdiodev), struct ns2_pci_phy can be removed. Signed-off-by: Axel Lin --- I don't have this h/w. Appreciate if someone can test this patch serial. This was sent on http://www.spinics.net/lists/netdev/msg383513.html

[RESEND][PATCH 2/2] phy: bcm-ns2-pcie: Set missing .owner field in ns2_pci_phy_ops

Add missing .owner field in ns2_pci_phy_ops, which is used for refcounting. While at it, also makes ns2_pci_phy_ops const as it's never get modified. Signed-off-by: Axel Lin --- This was sent on http://www.spinics.net/lists/netdev/msg383514.html

[RESEND][PATCH 1/2] phy: bcm-ns2-pcie: Get rid of struct ns2_pci_phy

By setting phy_set_drvdata(phy, mdiodev), struct ns2_pci_phy can be removed. Signed-off-by: Axel Lin --- I don't have this h/w. Appreciate if someone can test this patch serial. This was sent on http://www.spinics.net/lists/netdev/msg383513.html drivers/phy/phy-bcm-ns2-pcie.c | 25

[RESEND][PATCH 2/2] phy: bcm-ns2-pcie: Set missing .owner field in ns2_pci_phy_ops

Add missing .owner field in ns2_pci_phy_ops, which is used for refcounting. While at it, also makes ns2_pci_phy_ops const as it's never get modified. Signed-off-by: Axel Lin --- This was sent on http://www.spinics.net/lists/netdev/msg383514.html drivers/phy/phy-bcm-ns2-pcie.c | 3 ++- 1 file

Re: [PATCH v2] locking/percpu-rwsem: Optimize readers and reduce global impact

Thank you Dimtry for sharing the patches. Update from my tests: Use-case: Android application launches. I tested the patches on android N build, i see max latency ~7ms. In my tests, the wait is due to: copy_process(fork.c) blocks all threads in __cgroup_procs_write including threads which are

Re: [PATCH v2] locking/percpu-rwsem: Optimize readers and reduce global impact

Thank you Dimtry for sharing the patches. Update from my tests: Use-case: Android application launches. I tested the patches on android N build, i see max latency ~7ms. In my tests, the wait is due to: copy_process(fork.c) blocks all threads in __cgroup_procs_write including threads which are

Re: [PATCH 02/12] pinctrl: Add core pinctrl support for Aspeed SoCs

On Fri, 2016-08-12 at 15:18 +0200, Linus Walleij wrote: > I would probably prefer that option (introduce another field) > but you should make the overall decision, it's no strong opinion > from my side. > > > Would it be acceptable to document that requirement? It might make it a bit less nasty

Re: [PATCH 02/12] pinctrl: Add core pinctrl support for Aspeed SoCs

On Fri, 2016-08-12 at 15:18 +0200, Linus Walleij wrote: > I would probably prefer that option (introduce another field) > but you should make the overall decision, it's no strong opinion > from my side. > > > Would it be acceptable to document that requirement? It might make it a bit less nasty

Re: [PATCH 1/3] clk: meson: Add GXBB AO Clock and Reset controller driver

On 08/09, Neil Armstrong wrote: > diff --git a/drivers/clk/meson/gxbb-aoclk.c b/drivers/clk/meson/gxbb-aoclk.c > new file mode 100644 > index 000..56a9186 > --- /dev/null > +++ b/drivers/clk/meson/gxbb-aoclk.c > @@ -0,0 +1,203 @@ > +/* > + * This file is provided under a dual BSD/GPLv2

Re: [RFC PATCH v7 7/7] Restartable sequences: self-tests

On Fri, Aug 12, 2016 at 06:11:45PM +, Mathieu Desnoyers wrote: > - On Aug 12, 2016, at 12:35 PM, Boqun Feng boqun.f...@gmail.com wrote: > > > On Fri, Aug 12, 2016 at 01:30:15PM +0800, Boqun Feng wrote: > > [snip] > >> > > Besides, do we allow userspace programs do read-only access to the

Re: [PATCH 1/3] clk: meson: Add GXBB AO Clock and Reset controller driver

On 08/09, Neil Armstrong wrote: > diff --git a/drivers/clk/meson/gxbb-aoclk.c b/drivers/clk/meson/gxbb-aoclk.c > new file mode 100644 > index 000..56a9186 > --- /dev/null > +++ b/drivers/clk/meson/gxbb-aoclk.c > @@ -0,0 +1,203 @@ > +/* > + * This file is provided under a dual BSD/GPLv2

Re: [RFC PATCH v7 7/7] Restartable sequences: self-tests

On Fri, Aug 12, 2016 at 06:11:45PM +, Mathieu Desnoyers wrote: > - On Aug 12, 2016, at 12:35 PM, Boqun Feng boqun.f...@gmail.com wrote: > > > On Fri, Aug 12, 2016 at 01:30:15PM +0800, Boqun Feng wrote: > > [snip] > >> > > Besides, do we allow userspace programs do read-only access to the

Re: [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

Hi Boris, On Fri, Aug 12, 2016 at 09:15:03PM +0200, Boris Brezillon wrote: > Hi Kyle, > > On Fri, 12 Aug 2016 12:54:49 -0500 > Kyle Roeschley wrote: > > > From: Boris Brezillon > > > > This clarifies the write_bbt() by removing the

Re: [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()

Hi Boris, On Fri, Aug 12, 2016 at 09:15:03PM +0200, Boris Brezillon wrote: > Hi Kyle, > > On Fri, 12 Aug 2016 12:54:49 -0500 > Kyle Roeschley wrote: > > > From: Boris Brezillon > > > > This clarifies the write_bbt() by removing the write label and clarifying > > the error/exit path. > > > >

Re: [PATCH] clk: mvebu: armada-39x: add clk description for supported interfaces

On 07/21, Grzegorz Jaszczyk wrote: > Both SATA and second USB3.0 interface are supported in Armada-39x SoC > family. Add necessary clk description, so both xhci and sata drivers > can be correctly initialized. > > The binding documentation has also been updated accordingly. > > Signed-off-by:

Re: [PATCH] clk: mvebu: armada-39x: add clk description for supported interfaces

On 07/21, Grzegorz Jaszczyk wrote: > Both SATA and second USB3.0 interface are supported in Armada-39x SoC > family. Add necessary clk description, so both xhci and sata drivers > can be correctly initialized. > > The binding documentation has also been updated accordingly. > > Signed-off-by:

[PATCH v4 2/2] remoteproc: qcom: Introduce WCNSS peripheral image loader

From: Bjorn Andersson This introduces the peripheral image loader, for loading WCNSS firmware and boot the core on e.g. MSM8974. The firmware is verified and booted with the help of the Peripheral Authentication System (PAS) in TrustZone. Tested-by: John Stultz

[PATCH v4 1/2] dt-binding: remoteproc: Introduce Qualcomm WCNSS loader binding

From: Bjorn Andersson The document defines the binding for a component that loads firmware for and boots the Qualcomm WCNSS core. Acked-by: Rob Herring Signed-off-by: Bjorn Andersson Signed-off-by: Bjorn

[PATCH v4 2/2] remoteproc: qcom: Introduce WCNSS peripheral image loader

From: Bjorn Andersson This introduces the peripheral image loader, for loading WCNSS firmware and boot the core on e.g. MSM8974. The firmware is verified and booted with the help of the Peripheral Authentication System (PAS) in TrustZone. Tested-by: John Stultz Signed-off-by: Bjorn Andersson

[PATCH v4 1/2] dt-binding: remoteproc: Introduce Qualcomm WCNSS loader binding

From: Bjorn Andersson The document defines the binding for a component that loads firmware for and boots the Qualcomm WCNSS core. Acked-by: Rob Herring Signed-off-by: Bjorn Andersson Signed-off-by: Bjorn Andersson --- Changes since v3: - None Changes since v2: - None

Re: [PATCH v5 8/8] clk: fixed-rate: Convert into a module platform driver

On 07/05, Ricardo Ribalda Delgado wrote: > Adds support for fixed-rate clock providers which have not been > enabled via of_clk_init(). > > This is required by Device trees overlays that introduce clocks > providers. > > Signed-off-by: Ricardo Ribalda Delgado > ---

Re: [PATCH v5 5/8] clk: sunxi: apb0: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via sun8i_a23_apb0_setup > and then continues the initialization on sun8i_a23_apb0_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado

Re: [PATCH v5 7/8] clk: fixed-factor: Convert into a module platform driver

On 07/05, Ricardo Ribalda Delgado wrote: > Adds support for fixed-factor clock providers which have not been > enabled via of_clk_init(). > > This is required by Device trees overlays that introduce clocks > providers. > > Signed-off-by: Ricardo Ribalda Delgado > ---

Re: [PATCH v5 5/8] clk: sunxi: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via sun8i_a23_apb0_setup > and then continues the initialization on sun8i_a23_apb0_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado

Re: [PATCH] clk: use ERR_CAST() for __clk_create_clk()

On 07/19, Masahiro Yamada wrote: > This code is clear enough, but the intention will be even clearer > with this. > > Signed-off-by: Masahiro Yamada > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux

Re: [PATCH v5 8/8] clk: fixed-rate: Convert into a module platform driver

On 07/05, Ricardo Ribalda Delgado wrote: > Adds support for fixed-rate clock providers which have not been > enabled via of_clk_init(). > > This is required by Device trees overlays that introduce clocks > providers. > > Signed-off-by: Ricardo Ribalda Delgado > --- Applied to clk-next --

Re: [PATCH v5 5/8] clk: sunxi: apb0: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via sun8i_a23_apb0_setup > and then continues the initialization on sun8i_a23_apb0_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado >

Re: [PATCH v5 7/8] clk: fixed-factor: Convert into a module platform driver

On 07/05, Ricardo Ribalda Delgado wrote: > Adds support for fixed-factor clock providers which have not been > enabled via of_clk_init(). > > This is required by Device trees overlays that introduce clocks > providers. > > Signed-off-by: Ricardo Ribalda Delgado > --- Applied to clk-next --

Re: [PATCH v5 5/8] clk: sunxi: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via sun8i_a23_apb0_setup > and then continues the initialization on sun8i_a23_apb0_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado >

Re: [PATCH] clk: use ERR_CAST() for __clk_create_clk()

On 07/19, Masahiro Yamada wrote: > This code is clear enough, but the intention will be even clearer > with this. > > Signed-off-by: Masahiro Yamada > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH v5 4/8] clk: sunxi: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via sun4i_a10_mod0_setup > and then continues the initialization on sun4i_a10_mod0_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado

Re: [PATCH v5 4/8] clk: sunxi: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via sun4i_a10_mod0_setup > and then continues the initialization on sun4i_a10_mod0_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado >

Re: [PATCH v5 6/8] clk: core: Avoid double initialization of clocks

On 07/05, Ricardo Ribalda Delgado wrote: > Some clock providers can be initialized via of_clk_init() and also via > platform device probe. > > Avoid double initialization of them by setting the OF_POPULATED flag. > > Signed-off-by: Ricardo Ribalda Delgado > ---

Re: [PATCH v5 4/8] clk: sunxi: mod0: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via sun4i_a10_mod0_setup > and then continues the initialization on sun4i_a10_mod0_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado

Re: [PATCH v5 6/8] clk: core: Avoid double initialization of clocks

On 07/05, Ricardo Ribalda Delgado wrote: > Some clock providers can be initialized via of_clk_init() and also via > platform device probe. > > Avoid double initialization of them by setting the OF_POPULATED flag. > > Signed-off-by: Ricardo Ribalda Delgado > --- Applied to clk-next --

Re: [PATCH v5 4/8] clk: sunxi: mod0: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via sun4i_a10_mod0_setup > and then continues the initialization on sun4i_a10_mod0_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado >

Re: [PATCH v5 3/8] clk: npx: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via lpc18xx_creg_clk_init > and then continues the initialization on lpc18xx_creg_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado

Re: [PATCH v5 2/8] clk: axis: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via of_artpec6_clkctrl_setup > and then continues the initialization on artpec6_clkctrl_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado

Re: [PATCH v5 3/8] clk: npx: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via lpc18xx_creg_clk_init > and then continues the initialization on lpc18xx_creg_clk_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado >

Re: [PATCH v5 2/8] clk: axis: Use new macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This driver initializes a clock provider via of_artpec6_clkctrl_setup > and then continues the initialization on artpec6_clkctrl_probe. > > Use the new macro to notify the clk subsystem about this behaviour. > > Signed-off-by: Ricardo Ribalda Delgado >

Re: [PATCH v5 1/8] clk: core: New macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This will be used by drivers that requires initialization at > of_clk_init() time and also during platform device probing. > > Signed-off-by: Ricardo Ribalda Delgado > --- Applied to clk-next -- Qualcomm Innovation Center,

Re: [PATCH v5 1/8] clk: core: New macro CLK_OF_DECLARE_DRIVER

On 07/05, Ricardo Ribalda Delgado wrote: > This will be used by drivers that requires initialization at > of_clk_init() time and also during platform device probing. > > Signed-off-by: Ricardo Ribalda Delgado > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code

[PATCH v2 4/6] lib/raid6: Add AVX512 optimized xor_syndrome functions

Optimize RAID6 xor_syndrome functions to take advantage of the 512-bit ZMM integer instructions introduced in AVX512. AVX512 optimized xor_syndrome functions, which is simply based on sse2.c written by hpa. The patch was tested and benchmarked before submission on a hardware that has AVX512

[PATCH v2 2/6] lib/raid6: Add AVX512 optimized recovery functions

Optimize RAID6 recovery functions to take advantage of the 512-bit ZMM integer instructions introduced in AVX512. AVX512 optimized recovery functions, which is simply based on recov_avx2.c written by Jim Kukunas This patch was tested and benchmarked before submission on a hardware that has

[PATCH v2 4/6] lib/raid6: Add AVX512 optimized xor_syndrome functions

Optimize RAID6 xor_syndrome functions to take advantage of the 512-bit ZMM integer instructions introduced in AVX512. AVX512 optimized xor_syndrome functions, which is simply based on sse2.c written by hpa. The patch was tested and benchmarked before submission on a hardware that has AVX512

[PATCH v2 2/6] lib/raid6: Add AVX512 optimized recovery functions

Optimize RAID6 recovery functions to take advantage of the 512-bit ZMM integer instructions introduced in AVX512. AVX512 optimized recovery functions, which is simply based on recov_avx2.c written by Jim Kukunas This patch was tested and benchmarked before submission on a hardware that has

[PATCH v2 1/6] lib/raid6: Add AVX512 optimized gen_syndrome functions

Optimize RAID6 gen_syndrom functions to take advantage of the 512-bit ZMM integer instructions introduced in AVX512. AVX512 optimized gen_syndrom functions, which is simply based on avx2.c written by Yuanhan Liu and sse2.c written by hpa. The patch was tested and benchmarked before submission on

[PATCH v2 1/6] lib/raid6: Add AVX512 optimized gen_syndrome functions

Optimize RAID6 gen_syndrom functions to take advantage of the 512-bit ZMM integer instructions introduced in AVX512. AVX512 optimized gen_syndrom functions, which is simply based on avx2.c written by Yuanhan Liu and sse2.c written by hpa. The patch was tested and benchmarked before submission on

  1   2   3   4   5   6   7   8   9   10   >