Re: [PATCH 0/6] {sched_,}find_first{_zero}_bit optimizations

Ping? On Tue, May 23, 2017 at 09:43:15PM +0300, Yury Norov wrote: > The series is the result of this discussion: > https://lkml.org/lkml/2017/5/12/665 > plus this patch: https://lkml.org/lkml/2017/5/13/137 > (I'd like to have it together with others.) > > Patch 1 remove useless

Re: [PATCH 0/6] {sched_,}find_first{_zero}_bit optimizations

Ping? On Tue, May 23, 2017 at 09:43:15PM +0300, Yury Norov wrote: > The series is the result of this discussion: > https://lkml.org/lkml/2017/5/12/665 > plus this patch: https://lkml.org/lkml/2017/5/13/137 > (I'd like to have it together with others.) > > Patch 1 remove useless

Re: [PATCH 4.4 075/103] [media] dvb-frontends/cxd2841er: define symbol_rate_min/max in T/C fe-ops

On Tue, 2017-05-23 at 22:09 +0200, Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Daniel Scheller > > commit 158f0328af86a99d64073851967a02694bff987d upstream. > > Fixes "w_scan -f c"

Re: [PATCH 4.4 075/103] [media] dvb-frontends/cxd2841er: define symbol_rate_min/max in T/C fe-ops

On Tue, 2017-05-23 at 22:09 +0200, Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Daniel Scheller > > commit 158f0328af86a99d64073851967a02694bff987d upstream. > > Fixes "w_scan -f c" complaining with >

[PATCH] qla2xxx: remove writeq/readq function definitions

Instead of rewriting write/readq, use linux/io-64-nonatomic-lo-hi.h which already have them. Signed-off-by: Corentin Labbe --- drivers/scsi/qla2xxx/qla_nx.h | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git

[PATCH] qla2xxx: remove writeq/readq function definitions

Instead of rewriting write/readq, use linux/io-64-nonatomic-lo-hi.h which already have them. Signed-off-by: Corentin Labbe --- drivers/scsi/qla2xxx/qla_nx.h | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git a/drivers/scsi/qla2xxx/qla_nx.h

Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()

On Fri, Jun 2, 2017 at 1:18 PM, Yan, Zheng wrote: > On Fri, Jun 2, 2017 at 6:51 PM, Arnd Bergmann wrote: >> On Fri, Jun 2, 2017 at 12:10 PM, Yan, Zheng wrote: >>> On Fri, Jun 2, 2017 at 5:45 PM, Arnd Bergmann wrote: On

Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()

On Fri, Jun 2, 2017 at 1:18 PM, Yan, Zheng wrote: > On Fri, Jun 2, 2017 at 6:51 PM, Arnd Bergmann wrote: >> On Fri, Jun 2, 2017 at 12:10 PM, Yan, Zheng wrote: >>> On Fri, Jun 2, 2017 at 5:45 PM, Arnd Bergmann wrote: On Fri, Jun 2, 2017 at 4:09 AM, Yan, Zheng wrote: > On Fri, Jun 2,

[PATCH] pinctrl: sunxi: constify irq_domain_ops

struct irq_domain_ops is not modified, so it can be made const. Suggested-by: Marc Zyngier Signed-off-by: Tobias Klauser --- drivers/pinctrl/sunxi/pinctrl-sunxi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] pinctrl: sunxi: constify irq_domain_ops

struct irq_domain_ops is not modified, so it can be made const. Suggested-by: Marc Zyngier Signed-off-by: Tobias Klauser --- drivers/pinctrl/sunxi/pinctrl-sunxi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pinctrl/sunxi/pinctrl-sunxi.c

[PATCH] cpufreq: Find transition latency dynamically

The transition_latency_ns represents the maximum time it can take for the hardware to switch from/to any frequency for a CPU. The transition_latency_ns is used currently for two purposes: o To check if the hardware latency is over the maximum allowed for a governor (only for ondemand and

[PATCH] cpufreq: Find transition latency dynamically

The transition_latency_ns represents the maximum time it can take for the hardware to switch from/to any frequency for a CPU. The transition_latency_ns is used currently for two purposes: o To check if the hardware latency is over the maximum allowed for a governor (only for ondemand and

[PATCH] drm: remove writeq/readq function definitions

Instead of rewriting write/readq, use linux/io-64-nonatomic-lo-hi.h which already have them. Signed-off-by: Corentin Labbe --- include/drm/drm_os_linux.h | 14 +- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/include/drm/drm_os_linux.h

[PATCH] drm: remove writeq/readq function definitions

Instead of rewriting write/readq, use linux/io-64-nonatomic-lo-hi.h which already have them. Signed-off-by: Corentin Labbe --- include/drm/drm_os_linux.h | 14 +- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/include/drm/drm_os_linux.h b/include/drm/drm_os_linux.h

Re: [PATCH 0/7] irqchip: constify irq_domain_ops

On 2017-06-02 at 12:04:42 +0200, Marc Zyngier wrote: > On 02/06/17 09:20, Tobias Klauser wrote: > > Constify all remaining non-const instances of irq_domain_ops in the irqchip > > drivers. These can be made const as they are never modified. > > > > Tobias Klauser (7): > >

Re: [PATCH 0/7] irqchip: constify irq_domain_ops

On 2017-06-02 at 12:04:42 +0200, Marc Zyngier wrote: > On 02/06/17 09:20, Tobias Klauser wrote: > > Constify all remaining non-const instances of irq_domain_ops in the irqchip > > drivers. These can be made const as they are never modified. > > > > Tobias Klauser (7): > > irqchip/aspeed-vic:

Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()

On Fri, Jun 2, 2017 at 6:51 PM, Arnd Bergmann wrote: > On Fri, Jun 2, 2017 at 12:10 PM, Yan, Zheng wrote: >> On Fri, Jun 2, 2017 at 5:45 PM, Arnd Bergmann wrote: >>> On Fri, Jun 2, 2017 at 4:09 AM, Yan, Zheng wrote: On

Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()

On Fri, Jun 2, 2017 at 6:51 PM, Arnd Bergmann wrote: > On Fri, Jun 2, 2017 at 12:10 PM, Yan, Zheng wrote: >> On Fri, Jun 2, 2017 at 5:45 PM, Arnd Bergmann wrote: >>> On Fri, Jun 2, 2017 at 4:09 AM, Yan, Zheng wrote: On Fri, Jun 2, 2017 at 8:57 AM, Deepa Dinamani wrote: > On

[PATCH] net: phy: marvell: make two functions static

From: Colin Ian King functions m88e1510_get_temp_critical and m88e1510_get_temp_alarm can be made static as they not need to be in global scope. Cleans up sparse warnings: "symbol 'm88e1510_get_temp_alarm' was not declared. Should it be static?" "symbol

[PATCH] net: phy: marvell: make two functions static

From: Colin Ian King functions m88e1510_get_temp_critical and m88e1510_get_temp_alarm can be made static as they not need to be in global scope. Cleans up sparse warnings: "symbol 'm88e1510_get_temp_alarm' was not declared. Should it be static?" "symbol 'm88e1510_get_temp_critical' was not

arm64: segfaults on next-20170602 with LTP tests

4.12.0-rc3-next-20170602 #754 [ 1761.257324] Hardware name: linux,dummy-virt (DT) [ 1761.257434] task: 89036800 task.stack: 88fa4000 [ 1761.257542] PC is at 0xb7fb6f98 [ 1761.257613] LR is at 0xb7fb471c [ 1761.257678] pc : [<b7fb6f98&g

arm64: segfaults on next-20170602 with LTP tests

4.12.0-rc3-next-20170602 #754 [ 1761.257324] Hardware name: linux,dummy-virt (DT) [ 1761.257434] task: 89036800 task.stack: 88fa4000 [ 1761.257542] PC is at 0xb7fb6f98 [ 1761.257613] LR is at 0xb7fb471c [ 1761.257678] pc : [<b7fb6f98&g

[ANNOUNCE] util-linux v2.30

The util-linux release v2.30 is available at http://www.kernel.org/pub/linux/utils/util-linux/v2.30 Feedback and bug reports, as always, are welcomed. Karel Util-linux 2.30 Release Notes = The libblkid library has been improved for hybrid CDROM/DVD media by

[ANNOUNCE] util-linux v2.30

The util-linux release v2.30 is available at http://www.kernel.org/pub/linux/utils/util-linux/v2.30 Feedback and bug reports, as always, are welcomed. Karel Util-linux 2.30 Release Notes = The libblkid library has been improved for hybrid CDROM/DVD media by

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On 02.06.2017 09:02, Heiko Carstens wrote: > On Thu, Jun 01, 2017 at 12:46:51PM +0200, Martin Schwidefsky wrote: >>> Unfortunately, converting all page tables to 4k pgste page tables is >>> not possible without provoking various race conditions. >> >> That is one approach we tried and was found to

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On 02.06.2017 09:02, Heiko Carstens wrote: > On Thu, Jun 01, 2017 at 12:46:51PM +0200, Martin Schwidefsky wrote: >>> Unfortunately, converting all page tables to 4k pgste page tables is >>> not possible without provoking various race conditions. >> >> That is one approach we tried and was found to

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On Fri, 2 Jun 2017 12:19:19 +0200 Christian Borntraeger wrote: > On 06/02/2017 11:46 AM, Martin Schwidefsky wrote: > > On Fri, 2 Jun 2017 09:02:10 +0200 > > Heiko Carstens wrote: > > > >> On Thu, Jun 01, 2017 at 12:46:51PM +0200, Martin

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On Fri, 2 Jun 2017 12:19:19 +0200 Christian Borntraeger wrote: > On 06/02/2017 11:46 AM, Martin Schwidefsky wrote: > > On Fri, 2 Jun 2017 09:02:10 +0200 > > Heiko Carstens wrote: > > > >> On Thu, Jun 01, 2017 at 12:46:51PM +0200, Martin Schwidefsky wrote: > Unfortunately, converting

[PATCH v3 2/6] mfd: hi6421-pmic: add support for HiSilicon Hi6421v530

Add support for HiSilicon Hi6421v530 PMIC. Hi6421v530 communicates with main SoC via memory-mapped I/O. Hi6421v530 and Hi6421 are PMIC chips from the same vendor, HiSilicon, but at different revisions. They share the same memory-mapped I/O design. They differ in integrated devices, such as

[PATCH v3 2/6] mfd: hi6421-pmic: add support for HiSilicon Hi6421v530

Add support for HiSilicon Hi6421v530 PMIC. Hi6421v530 communicates with main SoC via memory-mapped I/O. Hi6421v530 and Hi6421 are PMIC chips from the same vendor, HiSilicon, but at different revisions. They share the same memory-mapped I/O design. They differ in integrated devices, such as

[PATCH v3 6/6] arm64: defconfig: enable support hi6421v530 PMIC

Enable configs for hi6421v530 mfd and regulator driver + CONFIG_MFD_HI6421_PMIC=y + CONFIG_REGULATOR_HI6421V530=y Signed-off-by: Guodong Xu --- arch/arm64/configs/defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/configs/defconfig

[PATCH v3 6/6] arm64: defconfig: enable support hi6421v530 PMIC

Enable configs for hi6421v530 mfd and regulator driver + CONFIG_MFD_HI6421_PMIC=y + CONFIG_REGULATOR_HI6421V530=y Signed-off-by: Guodong Xu --- arch/arm64/configs/defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index

[PATCH v3 5/6] arm64: dts: hikey960: add device node for pmic and regulators

From: Wang Xiaoyin add device node for hi6421 pmic core and hi6421v530 voltage regulator,include LDO(1,3,9,11,15,16) Signed-off-by: Wang Xiaoyin Signed-off-by: Guodong Xu ---

[PATCH v3 5/6] arm64: dts: hikey960: add device node for pmic and regulators

From: Wang Xiaoyin add device node for hi6421 pmic core and hi6421v530 voltage regulator,include LDO(1,3,9,11,15,16) Signed-off-by: Wang Xiaoyin Signed-off-by: Guodong Xu --- arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 46 +++ 1 file changed, 46 insertions(+)

[PATCH v3 1/6] dt-bindings: mfd: hi6421: Add hi6421v530 compatible string

Add compatible string for HiSilicon Hi6421v530 PMIC. Signed-off-by: Guodong Xu --- Documentation/devicetree/bindings/mfd/hi6421.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/mfd/hi6421.txt

[PATCH v3 1/6] dt-bindings: mfd: hi6421: Add hi6421v530 compatible string

Add compatible string for HiSilicon Hi6421v530 PMIC. Signed-off-by: Guodong Xu --- Documentation/devicetree/bindings/mfd/hi6421.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/mfd/hi6421.txt

[PATCH v3 4/6] regulator: hi6421: Describe consumed platform device

The hi6421-regulator driver consumes a similarly named platform device. Adding that to the module device table, allows modprobe to locate this driver once the device is created. Cc: Jeremy Linton Cc: Mark Brown Signed-off-by: Guodong Xu

[PATCH v3 4/6] regulator: hi6421: Describe consumed platform device

The hi6421-regulator driver consumes a similarly named platform device. Adding that to the module device table, allows modprobe to locate this driver once the device is created. Cc: Jeremy Linton Cc: Mark Brown Signed-off-by: Guodong Xu --- drivers/regulator/hi6421-regulator.c | 7 +++ 1

[PATCH v3 3/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator

From: Wang Xiaoyin add the driver for hi6421v530 voltage regulator Signed-off-by: Wang Xiaoyin Signed-off-by: Guodong Xu --- drivers/regulator/Kconfig| 10 ++ drivers/regulator/Makefile

[PATCH v3 3/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator

From: Wang Xiaoyin add the driver for hi6421v530 voltage regulator Signed-off-by: Wang Xiaoyin Signed-off-by: Guodong Xu --- drivers/regulator/Kconfig| 10 ++ drivers/regulator/Makefile | 1 + drivers/regulator/hi6421v530-regulator.c | 207

[PATCH v3 0/6] MFD: add driver for HiSilicon Hi6421v530 PMIC

This patchset adds driver for HiSilicon Hi6421v530 PMIC. Mainline kernel already has driver support to a similar chip, Hi6421. Hi6421 and Hi6421v530 are both from the same vendor, HiSilicon, but they are at different revisions. They both use the same Memory-mapped I/O method to communicate with

[PATCH v3 0/6] MFD: add driver for HiSilicon Hi6421v530 PMIC

This patchset adds driver for HiSilicon Hi6421v530 PMIC. Mainline kernel already has driver support to a similar chip, Hi6421. Hi6421 and Hi6421v530 are both from the same vendor, HiSilicon, but they are at different revisions. They both use the same Memory-mapped I/O method to communicate with

Re: [REGRESSION] [4.11/4.12-rc3] Hang on Suspend to RAM

Hello Hugh, Hugh Dickins - 01.06.17, 12:55: > On Thu, 1 Jun 2017, Martin Steigerwald wrote: > > Hello. […] > > Since 4.11 I have it quite often that a hang like this even happens on > > suspend to RAM (standby) as well. And even quite often about 1 time of of > > 2-3 suspend attempts. The hang

Re: [REGRESSION] [4.11/4.12-rc3] Hang on Suspend to RAM

Hello Hugh, Hugh Dickins - 01.06.17, 12:55: > On Thu, 1 Jun 2017, Martin Steigerwald wrote: > > Hello. […] > > Since 4.11 I have it quite often that a hang like this even happens on > > suspend to RAM (standby) as well. And even quite often about 1 time of of > > 2-3 suspend attempts. The hang

Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()

On Fri, Jun 2, 2017 at 12:10 PM, Yan, Zheng wrote: > On Fri, Jun 2, 2017 at 5:45 PM, Arnd Bergmann wrote: >> On Fri, Jun 2, 2017 at 4:09 AM, Yan, Zheng wrote: >>> On Fri, Jun 2, 2017 at 8:57 AM, Deepa Dinamani >>>

Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()

On Fri, Jun 2, 2017 at 12:10 PM, Yan, Zheng wrote: > On Fri, Jun 2, 2017 at 5:45 PM, Arnd Bergmann wrote: >> On Fri, Jun 2, 2017 at 4:09 AM, Yan, Zheng wrote: >>> On Fri, Jun 2, 2017 at 8:57 AM, Deepa Dinamani >>> wrote: On Thu, Jun 1, 2017 at 5:36 PM, John Stultz wrote: > On Thu,

Re: [PATCH 0/7] dra7: Fixes for MMC devicetree node

On 1 June 2017 at 16:33, Kishon Vijay Abraham I wrote: > There are the set of fixes that were sent initially as part > of [1]. > > These are mostly fixes w.r.t populating regulators in > mmc dt node. It was working before because the regulators > connecting to the IO lines are

Re: [PATCH 0/7] dra7: Fixes for MMC devicetree node

On 1 June 2017 at 16:33, Kishon Vijay Abraham I wrote: > There are the set of fixes that were sent initially as part > of [1]. > > These are mostly fixes w.r.t populating regulators in > mmc dt node. It was working before because the regulators > connecting to the IO lines are always on

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On Fri, 2 Jun 2017 12:28:48 +0200 Heiko Carstens wrote: > On Fri, Jun 02, 2017 at 11:46:47AM +0200, Martin Schwidefsky wrote: > > On Fri, 2 Jun 2017 09:02:10 +0200 > > Heiko Carstens wrote: > > > Maybe this is a bit over-simplified, but

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On Fri, 2 Jun 2017 12:28:48 +0200 Heiko Carstens wrote: > On Fri, Jun 02, 2017 at 11:46:47AM +0200, Martin Schwidefsky wrote: > > On Fri, 2 Jun 2017 09:02:10 +0200 > > Heiko Carstens wrote: > > > Maybe this is a bit over-simplified, but might work. > > This is not over-simplified at all,

Re: [PATCH v4 6/6] stmmac: pci: Remove setup handler indirection via stmmac_pci_info

On Fri, Jun 2, 2017 at 10:34 AM, Jan Kiszka wrote: > By now, stmmac_pci_info only contains a single entry. Register this > directly with the PCI device table, removing one indirection. Please, drop this patch from the next version. We can discuss it after the first 5

Re: [PATCH v4 6/6] stmmac: pci: Remove setup handler indirection via stmmac_pci_info

On Fri, Jun 2, 2017 at 10:34 AM, Jan Kiszka wrote: > By now, stmmac_pci_info only contains a single entry. Register this > directly with the PCI device table, removing one indirection. Please, drop this patch from the next version. We can discuss it after the first 5 will be in. -- With Best

Re: [PATCH v4 5/6] stmmac: pci: Use dmi_system_id table for retrieving PHY addresses

On Fri, Jun 2, 2017 at 10:34 AM, Jan Kiszka wrote: > Avoids reimplementation of DMI matching in stmmac_pci_find_phy_addr. > +static const struct stmmac_pci_func_data galileo_stmmac_func_data[] = { > { > .func = 6, > .phy_addr = 1, >

Re: [PATCH v4 5/6] stmmac: pci: Use dmi_system_id table for retrieving PHY addresses

On Fri, Jun 2, 2017 at 10:34 AM, Jan Kiszka wrote: > Avoids reimplementation of DMI matching in stmmac_pci_find_phy_addr. > +static const struct stmmac_pci_func_data galileo_stmmac_func_data[] = { > { > .func = 6, > .phy_addr = 1, > }, > + {

Re: [RFC PATCH 00/10] x86: undwarf unwinder

On Thu, Jun 01, 2017 at 04:08:25PM +0200, Jiri Slaby wrote: > Ccing Mel who did proper measurements and can hopefully comment on his > results. > > On 06/01/2017, 03:50 PM, Ingo Molnar wrote: > > That's not what I meant! The speedup comes from (hopefully) being able to > > disable > >

Re: [RFC PATCH 00/10] x86: undwarf unwinder

On Thu, Jun 01, 2017 at 04:08:25PM +0200, Jiri Slaby wrote: > Ccing Mel who did proper measurements and can hopefully comment on his > results. > > On 06/01/2017, 03:50 PM, Ingo Molnar wrote: > > That's not what I meant! The speedup comes from (hopefully) being able to > > disable > >

Re: [PATCH V2] ARM: cpuidle: Support asymmetric idle definition

On 02/06/2017 12:14, Sudeep Holla wrote: > > > On 02/06/17 11:06, Daniel Lezcano wrote: >> On 02/06/2017 11:39, Sudeep Holla wrote: >>> >>> >>> On 02/06/17 10:25, Daniel Lezcano wrote: On 02/06/2017 11:20, Sudeep Holla wrote: > > > On 01/06/17 12:39, Daniel Lezcano wrote: >>

Re: [PATCH V2] ARM: cpuidle: Support asymmetric idle definition

On 02/06/2017 12:14, Sudeep Holla wrote: > > > On 02/06/17 11:06, Daniel Lezcano wrote: >> On 02/06/2017 11:39, Sudeep Holla wrote: >>> >>> >>> On 02/06/17 10:25, Daniel Lezcano wrote: On 02/06/2017 11:20, Sudeep Holla wrote: > > > On 01/06/17 12:39, Daniel Lezcano wrote: >>

Re: [PATCH v5 10/11] gpio-exar/8250-exar: Make set of exported GPIOs configurable

On Fri, Jun 2, 2017 at 10:28 AM, Jan Kiszka wrote: > On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the > rest is required to operate the UART. To allow modeling this case, > expand the platform device data structure to specify a (consecutive) pin >

Re: [PATCH v5 10/11] gpio-exar/8250-exar: Make set of exported GPIOs configurable

On Fri, Jun 2, 2017 at 10:28 AM, Jan Kiszka wrote: > On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the > rest is required to operate the UART. To allow modeling this case, > expand the platform device data structure to specify a (consecutive) pin > subset for exporting by the

Re: [PATCH v6 2/3] phy:phy-bcm-ns2-usbdrd:Broadcom USB DRD Phy driver for Northstar2

Hi, On Wednesday 31 May 2017 03:42 PM, Raviteja Garimella wrote: > This is driver for USB DRD Phy used in Broadcom's Northstar2 > SoC. The phy can be configured to be in Device mode or Host > mode based on the type of cable connected to the port. The > driver registers to extcon framework to get

Re: [PATCH v6 2/3] phy:phy-bcm-ns2-usbdrd:Broadcom USB DRD Phy driver for Northstar2

Hi, On Wednesday 31 May 2017 03:42 PM, Raviteja Garimella wrote: > This is driver for USB DRD Phy used in Broadcom's Northstar2 > SoC. The phy can be configured to be in Device mode or Host > mode based on the type of cable connected to the port. The > driver registers to extcon framework to get

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On Fri, Jun 02, 2017 at 11:46:47AM +0200, Martin Schwidefsky wrote: > On Fri, 2 Jun 2017 09:02:10 +0200 > Heiko Carstens wrote: > > Maybe this is a bit over-simplified, but might work. > This is not over-simplified at all, that does work: Good! > +struct

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On Fri, Jun 02, 2017 at 11:46:47AM +0200, Martin Schwidefsky wrote: > On Fri, 2 Jun 2017 09:02:10 +0200 > Heiko Carstens wrote: > > Maybe this is a bit over-simplified, but might work. > This is not over-simplified at all, that does work: Good! > +struct arch_elf_state { > +}; > + > +#define

[PATCH v3 0/2] [PATCH v3 0/2] Lattice MachXO2 Slave SPI FPGA Manager support

Hi all, this series adds support for the Lattice MachXO2 FPGA chip, programmed over Slave SPI. Tested on my raspberry pi3 + bugblat's pif2 fpga hat. Changes from v1: * fixed all the warnings pointed out by 'checkpatch --strict' and Alan Tull Changes from v2: * convert to BIT() macro and

[PATCH v3 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support

This patch adds support to the FPGA manager for programming MachXO2 device’s internal flash memory, via slave SPI. Signed-off-by: Paolo Pisati --- drivers/fpga/Kconfig | 7 ++ drivers/fpga/Makefile | 1 + drivers/fpga/machxo2-spi.c | 277

[PATCH v3 0/2] [PATCH v3 0/2] Lattice MachXO2 Slave SPI FPGA Manager support

Hi all, this series adds support for the Lattice MachXO2 FPGA chip, programmed over Slave SPI. Tested on my raspberry pi3 + bugblat's pif2 fpga hat. Changes from v1: * fixed all the warnings pointed out by 'checkpatch --strict' and Alan Tull Changes from v2: * convert to BIT() macro and

[PATCH v3 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support

This patch adds support to the FPGA manager for programming MachXO2 device’s internal flash memory, via slave SPI. Signed-off-by: Paolo Pisati --- drivers/fpga/Kconfig | 7 ++ drivers/fpga/Makefile | 1 + drivers/fpga/machxo2-spi.c | 277

[PATCH v3 1/2] dt: bindings: fpga: add lattice machxo2 slave spi binding description

Add dt binding documentation details for Lattice MachXO2 FPGA configuration over Slave SPI interface. Signed-off-by: Paolo Pisati Acked-by: Rob Herring --- .../bindings/fpga/lattice-machxo2-spi.txt | 29 ++ 1 file changed, 29

[PATCH v3 1/2] dt: bindings: fpga: add lattice machxo2 slave spi binding description

Add dt binding documentation details for Lattice MachXO2 FPGA configuration over Slave SPI interface. Signed-off-by: Paolo Pisati Acked-by: Rob Herring --- .../bindings/fpga/lattice-machxo2-spi.txt | 29 ++ 1 file changed, 29 insertions(+) create mode 100644

Re: Ftrace Data Export

Hi, (sorry for the long delay, just back from vacations) Chunyan Zhang writes: > Hi Felipe, > > On 17 May 2017 at 16:08, Felipe Balbi wrote: >> >> Hi Chunyan, >> >> When you wrote your patchset to provide ftrace exports, why did you >>

Re: Ftrace Data Export

Hi, (sorry for the long delay, just back from vacations) Chunyan Zhang writes: > Hi Felipe, > > On 17 May 2017 at 16:08, Felipe Balbi wrote: >> >> Hi Chunyan, >> >> When you wrote your patchset to provide ftrace exports, why did you >> choose to export only function trace? Why not

[PATCH v2] kernel: trace: pass export pointer as argument to ->write()

That way, users don't need to keep a global static pointer and can rely on container_of() to fetch their own structure. Acked-by: Steven Rostedt (VMware) Reviewed-by: Chunyan Zhang Signed-off-by: Felipe Balbi ---

[PATCH v2] kernel: trace: pass export pointer as argument to ->write()

That way, users don't need to keep a global static pointer and can rely on container_of() to fetch their own structure. Acked-by: Steven Rostedt (VMware) Reviewed-by: Chunyan Zhang Signed-off-by: Felipe Balbi --- Changes since v1: - add missing & operator

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On 06/02/2017 11:46 AM, Martin Schwidefsky wrote: > On Fri, 2 Jun 2017 09:02:10 +0200 > Heiko Carstens wrote: > >> On Thu, Jun 01, 2017 at 12:46:51PM +0200, Martin Schwidefsky wrote: Unfortunately, converting all page tables to 4k pgste page tables is not

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On 06/02/2017 11:46 AM, Martin Schwidefsky wrote: > On Fri, 2 Jun 2017 09:02:10 +0200 > Heiko Carstens wrote: > >> On Thu, Jun 01, 2017 at 12:46:51PM +0200, Martin Schwidefsky wrote: Unfortunately, converting all page tables to 4k pgste page tables is not possible without provoking

Re: [PATCH v2 0/4] fix some issues for Rockchip usb2-phy and add rk3228 SoCs' support

On Friday 02 June 2017 08:50 AM, Frank Wang wrote: > These series of patches fix some issues for rockchip usb2-phy and amend > usb2-phy framework to support one phy which comprises with two host-ports. > > In addition, this change also add rk3228 usb2-phy support. merged, thanks! -Kishon > >

Re: [PATCH v2 0/4] fix some issues for Rockchip usb2-phy and add rk3228 SoCs' support

On Friday 02 June 2017 08:50 AM, Frank Wang wrote: > These series of patches fix some issues for rockchip usb2-phy and amend > usb2-phy framework to support one phy which comprises with two host-ports. > > In addition, this change also add rk3228 usb2-phy support. merged, thanks! -Kishon > >

Re: [PATCH] clk: Re-evaluate clock rate on min/max update

On Thu, Jun 01, 2017 at 02:12:51AM -0700, Stephen Boyd wrote: > On 04/13, Peter De Schrijver wrote: > > On Wed, Apr 12, 2017 at 09:46:05AM -0700, Stephen Boyd wrote: > > > On 03/21, Peter De Schrijver wrote: > > > > Whenever a user change its min or max rate limit of a clock, we need to > > > >

Re: [PATCH] clk: Re-evaluate clock rate on min/max update

On Thu, Jun 01, 2017 at 02:12:51AM -0700, Stephen Boyd wrote: > On 04/13, Peter De Schrijver wrote: > > On Wed, Apr 12, 2017 at 09:46:05AM -0700, Stephen Boyd wrote: > > > On 03/21, Peter De Schrijver wrote: > > > > Whenever a user change its min or max rate limit of a clock, we need to > > > >

Re: [PATCH] kernel: trace: pass export pointer as argument to ->write()

Hi, kbuild test robot writes: > Hi Felipe, > > [auto build test ERROR on tip/perf/core] > [also build test ERROR on v4.12-rc1 next-20170518] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [PATCH] kernel: trace: pass export pointer as argument to ->write()

Hi, kbuild test robot writes: > Hi Felipe, > > [auto build test ERROR on tip/perf/core] > [also build test ERROR on v4.12-rc1 next-20170518] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [RFC][PATCH 00/23] VFS: Introduce superblock configuration context [ver #4]

Hi Al, Here are some changes I've made, based on your comments plus a little more: (*) Get rid of the old vfs_new_sb_config() and rename __vfs_new_sb_config() to that. The callers then have to provide a file_system_type pointer and all the args. (*) Add a "struct net *s_net_ns" to

Re: [RFC][PATCH 00/23] VFS: Introduce superblock configuration context [ver #4]

Hi Al, Here are some changes I've made, based on your comments plus a little more: (*) Get rid of the old vfs_new_sb_config() and rename __vfs_new_sb_config() to that. The callers then have to provide a file_system_type pointer and all the args. (*) Add a "struct net *s_net_ns" to

Re: [PATCH V2] ARM: cpuidle: Support asymmetric idle definition

On 02/06/17 11:06, Daniel Lezcano wrote: > On 02/06/2017 11:39, Sudeep Holla wrote: >> >> >> On 02/06/17 10:25, Daniel Lezcano wrote: >>> On 02/06/2017 11:20, Sudeep Holla wrote: On 01/06/17 12:39, Daniel Lezcano wrote: > Some hardware have clusters with different idle states.

Re: [PATCH V2] ARM: cpuidle: Support asymmetric idle definition

On 02/06/17 11:06, Daniel Lezcano wrote: > On 02/06/2017 11:39, Sudeep Holla wrote: >> >> >> On 02/06/17 10:25, Daniel Lezcano wrote: >>> On 02/06/2017 11:20, Sudeep Holla wrote: On 01/06/17 12:39, Daniel Lezcano wrote: > Some hardware have clusters with different idle states.

Re: [PATCH v3 0/4] irqchip: armada-370-xp: remove IRQ_NOAUTOEN workaround

On 18/05/17 09:07, Thomas Petazzoni wrote: > Hello, > > This is the third version of a patch series initially posted in > October 2015, under the title: > > [PATCH 0/5] Fix regression introduced by set_irq_flags() removal > > at the time, the regression was worked around in commit >

Re: [PATCH v3 0/4] irqchip: armada-370-xp: remove IRQ_NOAUTOEN workaround

On 18/05/17 09:07, Thomas Petazzoni wrote: > Hello, > > This is the third version of a patch series initially posted in > October 2015, under the title: > > [PATCH 0/5] Fix regression introduced by set_irq_flags() removal > > at the time, the regression was worked around in commit >

Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2

On 02/06/2017 02:05, Olof Johansson wrote: [ ... ] >> For the story, this mmc/sdio is for the WiFi and this one was working for >> some >> version of the bootloader which initialized the clock and set the enable line >> for the chip. That is bad because the WiFi is working as a side effect from

Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2

On 02/06/2017 02:05, Olof Johansson wrote: [ ... ] >> For the story, this mmc/sdio is for the WiFi and this one was working for >> some >> version of the bootloader which initialized the clock and set the enable line >> for the chip. That is bad because the WiFi is working as a side effect from

Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()

On Fri, Jun 2, 2017 at 5:45 PM, Arnd Bergmann wrote: > On Fri, Jun 2, 2017 at 4:09 AM, Yan, Zheng wrote: >> On Fri, Jun 2, 2017 at 8:57 AM, Deepa Dinamani >> wrote: >>> On Thu, Jun 1, 2017 at 5:36 PM, John Stultz

Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()

On Fri, Jun 2, 2017 at 5:45 PM, Arnd Bergmann wrote: > On Fri, Jun 2, 2017 at 4:09 AM, Yan, Zheng wrote: >> On Fri, Jun 2, 2017 at 8:57 AM, Deepa Dinamani >> wrote: >>> On Thu, Jun 1, 2017 at 5:36 PM, John Stultz wrote: On Thu, Jun 1, 2017 at 5:26 PM, Yan, Zheng wrote: > On Thu, Jun

[GIT PULL v2] phy: for 4.12 -rc

Hi Greg, Please find the updated pull request for 4.12 -rc below. It includes only a couple of fixes in phy-qcom-qmp driver. The grouping of phy drivers to vendor specific directories will be sent for the next merge window. Consider merging it in this -rc cycle. Let me know If I have to make

[GIT PULL v2] phy: for 4.12 -rc

Hi Greg, Please find the updated pull request for 4.12 -rc below. It includes only a couple of fixes in phy-qcom-qmp driver. The grouping of phy drivers to vendor specific directories will be sent for the next merge window. Consider merging it in this -rc cycle. Let me know If I have to make

[PATCH v2 2/6] dt-bindings: interrupt-controller: add DT binding for the Marvell ICU

This commit adds the Device Tree binding documentation for the Marvell ICU interrupt controller, which collects wired interrupts from the devices located into the CP110 hardware block of Marvell Armada 7K/8K, and converts them into SPI interrupts in the GIC located in the AP hardware block, using

[PATCH v2 3/6] irqchip: irq-mvebu-gicp: new driver for Marvell GICP

This commit adds a simple driver for the Marvell GICP, a hardware unit that converts memory writes into GIC SPI interrupts. The driver provides a number of functions to the ICU driver to allocate GICP interrupts, and get the physical addresses that the ICUs should write to to set/clear interrupts.

[PATCH v2 2/6] dt-bindings: interrupt-controller: add DT binding for the Marvell ICU

This commit adds the Device Tree binding documentation for the Marvell ICU interrupt controller, which collects wired interrupts from the devices located into the CP110 hardware block of Marvell Armada 7K/8K, and converts them into SPI interrupts in the GIC located in the AP hardware block, using

[PATCH v2 3/6] irqchip: irq-mvebu-gicp: new driver for Marvell GICP

This commit adds a simple driver for the Marvell GICP, a hardware unit that converts memory writes into GIC SPI interrupts. The driver provides a number of functions to the ICU driver to allocate GICP interrupts, and get the physical addresses that the ICUs should write to to set/clear interrupts.

[PATCH v2 5/6] arm64: marvell: enable ICU and GICP drivers

This commit enables the newly introduced Marvell GICP and ICUs driver for the 64-bit Marvell EBU platforms. Signed-off-by: Thomas Petazzoni --- arch/arm64/Kconfig.platforms | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/Kconfig.platforms

[PATCH v2 5/6] arm64: marvell: enable ICU and GICP drivers

This commit enables the newly introduced Marvell GICP and ICUs driver for the 64-bit Marvell EBU platforms. Signed-off-by: Thomas Petazzoni --- arch/arm64/Kconfig.platforms | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms index

<    8   9   10   11   12   13   14   15   16   17   >