[GIT pull] x86 fixes for 4.11

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus A set of small fixes for x86: - Fix locking in RDT to prevent memory leaks and freeing in use memory - Prevent setting invalid values for

[PATCH 3/7] PCI: call pcie_flr from reset_chelsio_generic_dev

Instead of copy & pasting and old version of the code. Signed-off-by: Christoph Hellwig Acked-by: Bjorn Helgaas --- drivers/pci/quirks.c | 15 +-- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/drivers/pci/quirks.c

[GIT pull] x86 fixes for 4.11

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus A set of small fixes for x86: - Fix locking in RDT to prevent memory leaks and freeing in use memory - Prevent setting invalid values for

[PATCH 3/7] PCI: call pcie_flr from reset_chelsio_generic_dev

Instead of copy & pasting and old version of the code. Signed-off-by: Christoph Hellwig Acked-by: Bjorn Helgaas --- drivers/pci/quirks.c | 15 +-- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index

Re: [PATCH] clockevents/tcb_clksrc: implement suspend/resume

On 11/04/2017 17:48, Alexandre Belloni wrote: > On sama5d2, power to the core may be cut while entering suspend mode. It is > necessary to save and restore the TCB registers. > > Signed-off-by: Alexandre Belloni > --- > drivers/clocksource/tcb_clksrc.c | 46

Re: [PATCH] clockevents/tcb_clksrc: implement suspend/resume

On 11/04/2017 17:48, Alexandre Belloni wrote: > On sama5d2, power to the core may be cut while entering suspend mode. It is > necessary to save and restore the TCB registers. > > Signed-off-by: Alexandre Belloni > --- > drivers/clocksource/tcb_clksrc.c | 46 >

[PATCH 6/7] crypto: qat: use pcie_flr instead of duplicating it

Signed-off-by: Christoph Hellwig --- drivers/crypto/qat/qat_common/adf_aer.c | 15 +-- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/drivers/crypto/qat/qat_common/adf_aer.c b/drivers/crypto/qat/qat_common/adf_aer.c index 2839fccdd84b..d3e25c37dc33 100644

[PATCH 6/7] crypto: qat: use pcie_flr instead of duplicating it

Signed-off-by: Christoph Hellwig --- drivers/crypto/qat/qat_common/adf_aer.c | 15 +-- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/drivers/crypto/qat/qat_common/adf_aer.c b/drivers/crypto/qat/qat_common/adf_aer.c index 2839fccdd84b..d3e25c37dc33 100644 ---

[PATCH 4/7] ixgbe: use pcie_flr instead of duplicating it

Signed-off-by: Christoph Hellwig --- drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 16 ++-- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c index

[PATCH 4/7] ixgbe: use pcie_flr instead of duplicating it

Signed-off-by: Christoph Hellwig --- drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 16 ++-- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c index a7a430a7be2c..543ddde5f8e2

Re: [PATCH V8 4/5] PCI/ASPM: save power on values during bridge init

Bjorn, On 4/12/2017 3:19 PM, Rajat Jain wrote: > On Fri, Apr 7, 2017 at 9:55 PM, Sinan Kaya wrote: >> Now that we added a hook to be called from device_add, save the >> default values from the HW registers early in the boot for further >> reuse during hot device add/remove

[PATCH 7/7] liquidio: use pcie_flr instead of duplicating it

Signed-off-by: Christoph Hellwig --- drivers/net/ethernet/cavium/liquidio/lio_vf_main.c | 15 +-- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/drivers/net/ethernet/cavium/liquidio/lio_vf_main.c b/drivers/net/ethernet/cavium/liquidio/lio_vf_main.c index

Re: [PATCH V8 4/5] PCI/ASPM: save power on values during bridge init

Bjorn, On 4/12/2017 3:19 PM, Rajat Jain wrote: > On Fri, Apr 7, 2017 at 9:55 PM, Sinan Kaya wrote: >> Now that we added a hook to be called from device_add, save the >> default values from the HW registers early in the boot for further >> reuse during hot device add/remove operations. >> >> If

[PATCH 7/7] liquidio: use pcie_flr instead of duplicating it

Signed-off-by: Christoph Hellwig --- drivers/net/ethernet/cavium/liquidio/lio_vf_main.c | 15 +-- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/drivers/net/ethernet/cavium/liquidio/lio_vf_main.c b/drivers/net/ethernet/cavium/liquidio/lio_vf_main.c index

[PATCH 5/7] IB/hfi1: use pcie_flr instead of duplicating it

Signed-off-by: Christoph Hellwig --- drivers/infiniband/hw/hfi1/chip.c | 4 ++-- drivers/infiniband/hw/hfi1/hfi.h | 1 - drivers/infiniband/hw/hfi1/pcie.c | 30 -- 3 files changed, 2 insertions(+), 33 deletions(-) diff --git

[PATCH 5/7] IB/hfi1: use pcie_flr instead of duplicating it

Signed-off-by: Christoph Hellwig --- drivers/infiniband/hw/hfi1/chip.c | 4 ++-- drivers/infiniband/hw/hfi1/hfi.h | 1 - drivers/infiniband/hw/hfi1/pcie.c | 30 -- 3 files changed, 2 insertions(+), 33 deletions(-) diff --git a/drivers/infiniband/hw/hfi1/chip.c

[PATCH] orangefs: handle zero size write in debugfs

If we write zero bytes to this debugfs file, then it will cause an underflow when we do copy_from_user(buf, ubuf, count - 1). Debugfs can normally only be written to by root so the impact of this is low. Signed-off-by: Dan Carpenter diff --git

[PATCH] orangefs: handle zero size write in debugfs

If we write zero bytes to this debugfs file, then it will cause an underflow when we do copy_from_user(buf, ubuf, count - 1). Debugfs can normally only be written to by root so the impact of this is low. Signed-off-by: Dan Carpenter diff --git a/fs/orangefs/orangefs-debugfs.c

[PATCH 2/7] PCI: call pcie_flr from reset_intel_82599_sfp_virtfn

The 82599 quirk contained an outdated copy of the FLR code. Signed-off-by: Christoph Hellwig Acked-by: Bjorn Helgaas --- drivers/pci/quirks.c | 16 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/drivers/pci/quirks.c

[PATCH 2/7] PCI: call pcie_flr from reset_intel_82599_sfp_virtfn

The 82599 quirk contained an outdated copy of the FLR code. Signed-off-by: Christoph Hellwig Acked-by: Bjorn Helgaas --- drivers/pci/quirks.c | 16 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index

export pcie_flr and remove copies of it in drivers V2

Hi all, this exports the PCI layer pcie_flr helper, and removes various opencoded copies of it. Changes since V1: - rebase on top of the pci/virtualization branch - fixed the probe case in __pci_dev_reset - added ACKs from Bjorn

export pcie_flr and remove copies of it in drivers V2

Hi all, this exports the PCI layer pcie_flr helper, and removes various opencoded copies of it. Changes since V1: - rebase on top of the pci/virtualization branch - fixed the probe case in __pci_dev_reset - added ACKs from Bjorn

Re: [PATCH V8 1/5] PCI/ASPM: introduce pci_aspm_init() and add to pci_init_capabilities()

On 4/13/2017 4:51 PM, Bjorn Helgaas wrote: > I think these can go in drivers/pci/pci.h instead of the public > include/linux/pci.h. There's no ASPM section in drivers/pci/pci.h > yet, but I think we should add one. > > It looks like the following things from include/linux/pci-aspm.h could > be

Re: [PATCH V8 2/5] PCI/ASPM: split pci_aspm_init() into two

On 4/13/2017 2:25 PM, Bjorn Helgaas wrote: > I agree, and I made that change on my branch. I also renamed these to > pci_aspm_init_downstream_port() (for Root Ports and Switch Downstream > Ports) and pci_aspm_init_upstream_port() (for Switch Upstream Ports > and Endpoints) to try to match the

Re: [PATCH V8 1/5] PCI/ASPM: introduce pci_aspm_init() and add to pci_init_capabilities()

On 4/13/2017 4:51 PM, Bjorn Helgaas wrote: > I think these can go in drivers/pci/pci.h instead of the public > include/linux/pci.h. There's no ASPM section in drivers/pci/pci.h > yet, but I think we should add one. > > It looks like the following things from include/linux/pci-aspm.h could > be

Re: [PATCH V8 2/5] PCI/ASPM: split pci_aspm_init() into two

On 4/13/2017 2:25 PM, Bjorn Helgaas wrote: > I agree, and I made that change on my branch. I also renamed these to > pci_aspm_init_downstream_port() (for Root Ports and Switch Downstream > Ports) and pci_aspm_init_upstream_port() (for Switch Upstream Ports > and Endpoints) to try to match the

[PATCH] arm64: dts: allwinner: pine64: Add remaining UART aliases

Enabling uart2 node currently leads to a /dev/ttyS1 device, with ttyS0..4 always present, causing confusion on the user's part. dtc cannot resolve an overlay's reference for strings, only for phandles, so it would need to hardcode the full node path. Avoid this and enforce reliable numbering by

[GIT pull] perf fixes for 4.11

Linus, please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus Two small fixes for perf: - The move to support cross arch annotation introduced per arch initialization requirements, fullfill them for

[PATCH] arm64: dts: allwinner: pine64: Add remaining UART aliases

Enabling uart2 node currently leads to a /dev/ttyS1 device, with ttyS0..4 always present, causing confusion on the user's part. dtc cannot resolve an overlay's reference for strings, only for phandles, so it would need to hardcode the full node path. Avoid this and enforce reliable numbering by

[GIT pull] perf fixes for 4.11

Linus, please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus Two small fixes for perf: - The move to support cross arch annotation introduced per arch initialization requirements, fullfill them for

[GIT pull] irq fixes for 4.11

Linus, please pull the latest irq-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-for-linus The irq department provides: - Two fixes for the CPU affinity spread infrastructure to prevent unbalanced spreading in corner cases

[GIT pull] irq fixes for 4.11

Linus, please pull the latest irq-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-for-linus The irq department provides: - Two fixes for the CPU affinity spread infrastructure to prevent unbalanced spreading in corner cases

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

On Fri, Apr 14, 2017 at 11:30:14AM -0600, Logan Gunthorpe wrote: > On 14/04/17 05:37 AM, Benjamin Herrenschmidt wrote: > > I object to designing a subsystem that by design cannot work on whole > > categories of architectures out there. > > Hardly. That's extreme. We'd design a subsystem that

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

On Fri, Apr 14, 2017 at 11:30:14AM -0600, Logan Gunthorpe wrote: > On 14/04/17 05:37 AM, Benjamin Herrenschmidt wrote: > > I object to designing a subsystem that by design cannot work on whole > > categories of architectures out there. > > Hardly. That's extreme. We'd design a subsystem that

RE: RFC: WMI Enhancements

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Friday, April 14, 2017 1:28 PM > To: Limonciello, Mario > Cc: pali.ro...@gmail.com; r...@rjwysocki.net; len.br...@intel.com; > corentin.ch...@gmail.com; l...@kernel.org;

RE: RFC: WMI Enhancements

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Friday, April 14, 2017 1:28 PM > To: Limonciello, Mario > Cc: pali.ro...@gmail.com; r...@rjwysocki.net; len.br...@intel.com; > corentin.ch...@gmail.com; l...@kernel.org; andriy.shevche...@linux.intel.com; >

[GIT pull] efi fixes for 4.11

Linus, please pull the latest efi-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus Three fixes from EFI land: - Prevent accessing a Graphic Output Device (GOP) which the kernel does not know to handle - Prevent PCI

[GIT pull] efi fixes for 4.11

Linus, please pull the latest efi-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus Three fixes from EFI land: - Prevent accessing a Graphic Output Device (GOP) which the kernel does not know to handle - Prevent PCI

Re: [PATCH] regulator: vctrl: Fix out of bounds array access for vctrl->vtable

El Fri, Apr 14, 2017 at 10:11:37AM -0700 Matthias Kaehlcke ha dit: > Hi Axel, > > El Fri, Apr 14, 2017 at 10:50:43AM +0800 Axel Lin ha dit: > > > Current code only allocates rdesc->n_voltages entries for vctrl->vtable. > > Thus use rdesc->n_voltages instead of n_voltages in the for loop. > >

Re: [PATCH] regulator: vctrl: Fix out of bounds array access for vctrl->vtable

El Fri, Apr 14, 2017 at 10:11:37AM -0700 Matthias Kaehlcke ha dit: > Hi Axel, > > El Fri, Apr 14, 2017 at 10:50:43AM +0800 Axel Lin ha dit: > > > Current code only allocates rdesc->n_voltages entries for vctrl->vtable. > > Thus use rdesc->n_voltages instead of n_voltages in the for loop. > >

[tip:irq/core] genirq: Use cpumask_available() for check of cpumask variable

Commit-ID: d170fe7dd992b313d4851ae5ab77ee7a51ed8c72 Gitweb: http://git.kernel.org/tip/d170fe7dd992b313d4851ae5ab77ee7a51ed8c72 Author: Matthias Kaehlcke AuthorDate: Wed, 12 Apr 2017 11:20:30 -0700 Committer: Thomas Gleixner CommitDate: Fri, 14 Apr

[tip:irq/core] genirq: Use cpumask_available() for check of cpumask variable

Commit-ID: d170fe7dd992b313d4851ae5ab77ee7a51ed8c72 Gitweb: http://git.kernel.org/tip/d170fe7dd992b313d4851ae5ab77ee7a51ed8c72 Author: Matthias Kaehlcke AuthorDate: Wed, 12 Apr 2017 11:20:30 -0700 Committer: Thomas Gleixner CommitDate: Fri, 14 Apr 2017 20:49:27 +0200 genirq: Use

Re: [PATCH v3] sched: Have do_idle() call __schedule() without enabling preemption

On Fri, 14 Apr 2017, Steven Rostedt wrote: > > Acked-by: "Paul E. McKenney" > Signed-off-by: Steven Rostedt (VMware) Reviewed-by: Thomas Gleixner

Re: [PATCH v3] sched: Have do_idle() call __schedule() without enabling preemption

On Fri, 14 Apr 2017, Steven Rostedt wrote: > > Acked-by: "Paul E. McKenney" > Signed-off-by: Steven Rostedt (VMware) Reviewed-by: Thomas Gleixner

[RFC][PATCH 0/3] add EXTCON_CHG_USB_* cables to MSM USB phy

This patchset adds a way for the MSM USB phy to notify a power supply when the charging state changes. It achieves that using the extcon subsystem. The first patch makes sure msm_otg_notify_charger is called after the charger attributes have been set. The second one makes sure that function is

[RFC][PATCH 0/3] add EXTCON_CHG_USB_* cables to MSM USB phy

This patchset adds a way for the MSM USB phy to notify a power supply when the charging state changes. It achieves that using the extcon subsystem. The first patch makes sure msm_otg_notify_charger is called after the charger attributes have been set. The second one makes sure that function is

[RFC][PATCH 2/3] usb: phy: msm: notify charger when power supply is unplugged

With the current code, msm_otg_notify_charger doesn't get called when a power supply identified as a DCP is unplugged. To work around that, update charger info and call the notify function when switching from idle to host. Signed-off-by: Damien Riegel ---

[RFC][PATCH 2/3] usb: phy: msm: notify charger when power supply is unplugged

With the current code, msm_otg_notify_charger doesn't get called when a power supply identified as a DCP is unplugged. To work around that, update charger info and call the notify function when switching from idle to host. Signed-off-by: Damien Riegel --- drivers/usb/phy/phy-msm-usb.c | 3 +++

[RFC][PATCH 3/3] usb: phy: msm: use extcon to notify charger

Phy already keeps track of the USB charger mode it is in, that information could be useful to a power supply to let it know how much current it can draw. So in this case when DCP or CDP is set maximum current available is 1500mA, and 100mA when SDP is set. This is a bit peculiar in that this

[RFC][PATCH 3/3] usb: phy: msm: use extcon to notify charger

Phy already keeps track of the USB charger mode it is in, that information could be useful to a power supply to let it know how much current it can draw. So in this case when DCP or CDP is set maximum current available is 1500mA, and 100mA when SDP is set. This is a bit peculiar in that this

[RFC][PATCH 1/3] usb: phy: msm: notify charger after setting charger info

Move calls to msm_otg_notify_charger after attributes chg_state and chg_type have been set. That way the function can use them and not rely only on the "mA" parameter. Signed-off-by: Damien Riegel --- drivers/usb/phy/phy-msm-usb.c | 6 +++--- 1 file changed,

[RFC][PATCH 1/3] usb: phy: msm: notify charger after setting charger info

Move calls to msm_otg_notify_charger after attributes chg_state and chg_type have been set. That way the function can use them and not rely only on the "mA" parameter. Signed-off-by: Damien Riegel --- drivers/usb/phy/phy-msm-usb.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

Re: [PATCH 1/3] rtmutex: comments update

On Fri, 14 Apr 2017 16:52:11 +0800 Alex Shi wrote: > >> -Plist > >> -- > >> - > >> -Before I go further and talk about how the PI chain is stored through > >> lists > >> -on both mutexes and processes, I'll explain the plist. This is similar to > >> -the struct

[PATCH v24 10/11] clocksource: arm_arch_timer: add GTDT support for memory-mapped timer

From: Fu Wei The patch add memory-mapped timer register support by using the information provided by the new GTDT driver of ACPI. Signed-off-by: Fu Wei Reviewed-by: Hanjun Guo [Mark: verify CNTFRQ, only register the first frame]

Re: [PATCH 1/3] rtmutex: comments update

On Fri, 14 Apr 2017 16:52:11 +0800 Alex Shi wrote: > >> -Plist > >> -- > >> - > >> -Before I go further and talk about how the PI chain is stored through > >> lists > >> -on both mutexes and processes, I'll explain the plist. This is similar to > >> -the struct list_head functionality that

[PATCH v24 10/11] clocksource: arm_arch_timer: add GTDT support for memory-mapped timer

From: Fu Wei The patch add memory-mapped timer register support by using the information provided by the new GTDT driver of ACPI. Signed-off-by: Fu Wei Reviewed-by: Hanjun Guo [Mark: verify CNTFRQ, only register the first frame] Signed-off-by: Mark Rutland ---

[PATCH v24 11/11] acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver

From: Fu Wei This driver adds support for parsing SBSA Generic Watchdog timer in GTDT, parse all info in SBSA Generic Watchdog Structure in GTDT, and creating a platform device with that information. This allows the operating system to obtain device data from the resource of

[PATCH v24 11/11] acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver

From: Fu Wei This driver adds support for parsing SBSA Generic Watchdog timer in GTDT, parse all info in SBSA Generic Watchdog Structure in GTDT, and creating a platform device with that information. This allows the operating system to obtain device data from the resource of platform device.

Re: [PATCH] orangefs: free superblock when mount fails

ACK. I tried to mount orangefs with a nonsense option and got: [96967.205842] [96967.206439] [ BUG: lock held when returning to user space! ] [96967.207046] 4.10.0-8-g554ce8b #2 Not tainted [96967.207531]

Re: [PATCH] orangefs: free superblock when mount fails

ACK. I tried to mount orangefs with a nonsense option and got: [96967.205842] [96967.206439] [ BUG: lock held when returning to user space! ] [96967.207046] 4.10.0-8-g554ce8b #2 Not tainted [96967.207531]

[PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

From: Fu Wei On platforms booting with ACPI, architected memory-mapped timers' configuration data is provided by firmware through the ACPI GTDT static table. The clocksource architected timer kernel driver requires a firmware interface to collect timer configuration and

[PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

From: Fu Wei On platforms booting with ACPI, architected memory-mapped timers' configuration data is provided by firmware through the ACPI GTDT static table. The clocksource architected timer kernel driver requires a firmware interface to collect timer configuration and configure its driver.

[PATCH v24 08/11] acpi: Introduce acpi_unregister_irq function

From: Fu Wei This patch introduces acpi_unregister_irq function to free a linux IRQ number<->GSI mapping by a given linux IRQ number. Even we have successfully registered the GSI, when some error occurs, we may need to unmap it for freeing the IRQ resource. But in some cases,

[PATCH v24 08/11] acpi: Introduce acpi_unregister_irq function

From: Fu Wei This patch introduces acpi_unregister_irq function to free a linux IRQ number<->GSI mapping by a given linux IRQ number. Even we have successfully registered the GSI, when some error occurs, we may need to unmap it for freeing the IRQ resource. But in some cases, we only have IRQ,

[PATCH v24 05/11] clocksource: arm_arch_timer: split MMIO timer probing.

From: Fu Wei Currently the code to probe MMIO architected timers mixes DT parsing with actual poking of hardware. This makes the code harder than necessary to understand, and makes it difficult to add support for probing via ACPI. This patch splits the DT parsing from HW

[PATCH v24 07/11] clocksource: arm_arch_timer: simplify ACPI support code.

From: Fu Wei The patch update arm_arch_timer driver to use the function provided by the new GTDT driver of ACPI. By this way, arm_arch_timer.c can be simplified, and separate all the ACPI GTDT knowledge from this timer driver. Signed-off-by: Fu Wei

[PATCH v24 06/11] acpi/arm64: Add GTDT table parse driver

From: Fu Wei This patch adds support for parsing arch timer info in GTDT, provides some kernel APIs to parse all the PPIs and always-on info in GTDT and export them. By this driver, we can simplify arm_arch_timer drivers, and separate the ACPI GTDT knowledge from it.

[PATCH v24 05/11] clocksource: arm_arch_timer: split MMIO timer probing.

From: Fu Wei Currently the code to probe MMIO architected timers mixes DT parsing with actual poking of hardware. This makes the code harder than necessary to understand, and makes it difficult to add support for probing via ACPI. This patch splits the DT parsing from HW probing. The DT parsing

[PATCH v24 07/11] clocksource: arm_arch_timer: simplify ACPI support code.

From: Fu Wei The patch update arm_arch_timer driver to use the function provided by the new GTDT driver of ACPI. By this way, arm_arch_timer.c can be simplified, and separate all the ACPI GTDT knowledge from this timer driver. Signed-off-by: Fu Wei Signed-off-by: Hanjun Guo Tested-by:

[PATCH v24 06/11] acpi/arm64: Add GTDT table parse driver

From: Fu Wei This patch adds support for parsing arch timer info in GTDT, provides some kernel APIs to parse all the PPIs and always-on info in GTDT and export them. By this driver, we can simplify arm_arch_timer drivers, and separate the ACPI GTDT knowledge from it. Signed-off-by: Fu Wei

[PATCH v24 03/11] clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call

From: Fu Wei To cleanly split code paths specific to ACPI or DT at a higher level, this patch removes arch_timer_init(), folding the relevant parts of its logic into existing callers. This paths the way for further rework, and saves a few lines. Signed-off-by: Fu Wei

[PATCH v24 04/11] clocksource: arm_arch_timer: add structs to describe MMIO timer

From: Fu Wei In preparation for ACPI GTDT support, this patch adds structs to describe the MMIO timers indepedent of the firmware interface. Subsequent patches will use these to split the FW/HW probing logic, so that the HW probing logic can be shared by ACPI and DT.

[PATCH v24 03/11] clocksource: arm_arch_timer: move arch_timer_needs_of_probing into DT init call

From: Fu Wei To cleanly split code paths specific to ACPI or DT at a higher level, this patch removes arch_timer_init(), folding the relevant parts of its logic into existing callers. This paths the way for further rework, and saves a few lines. Signed-off-by: Fu Wei Reviewed-by: Hanjun Guo

[PATCH v24 04/11] clocksource: arm_arch_timer: add structs to describe MMIO timer

From: Fu Wei In preparation for ACPI GTDT support, this patch adds structs to describe the MMIO timers indepedent of the firmware interface. Subsequent patches will use these to split the FW/HW probing logic, so that the HW probing logic can be shared by ACPI and DT. Signed-off-by: Fu Wei

[PATCH v24 02/11] clocksource: arm_arch_timer: refactor arch_timer_needs_probing

From: Fu Wei When booting with DT, it's possible for timer nodes to be probed in any order. Some common initialisation needs to occur after all nodes have been probed, and arch_timer_common_init() has code to detect when this has happened. This logic is DT-specific, and it

[PATCH v24 02/11] clocksource: arm_arch_timer: refactor arch_timer_needs_probing

From: Fu Wei When booting with DT, it's possible for timer nodes to be probed in any order. Some common initialisation needs to occur after all nodes have been probed, and arch_timer_common_init() has code to detect when this has happened. This logic is DT-specific, and it would be best to

[PATCH v24 01/11] clocksource: arm_arch_timer: split dt-only rate handling

From: Fu Wei For historical reasons, rate detection when probing via DT is somewhat convoluted. We tried to package this up in arch_timer_detect_rate(), but with the addition of ACPI worse, and gets in the way of stringent rate checking when ACPI is used. This patch makes

[PATCH v24 01/11] clocksource: arm_arch_timer: split dt-only rate handling

From: Fu Wei For historical reasons, rate detection when probing via DT is somewhat convoluted. We tried to package this up in arch_timer_detect_rate(), but with the addition of ACPI worse, and gets in the way of stringent rate checking when ACPI is used. This patch makes

[PATCH v24 00/11] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

From: Fu Wei This patchset: (1)Preparation for adding GTDT support in arm_arch_timer: 1. Introduce a MMIO CNTFRQ helper. 2. separate out device-tree code from arch_timer_detect_rate 3. replace arch_timer_detect_rate with arch_timer_of_configure_rate

[PATCH v24 00/11] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

From: Fu Wei This patchset: (1)Preparation for adding GTDT support in arm_arch_timer: 1. Introduce a MMIO CNTFRQ helper. 2. separate out device-tree code from arch_timer_detect_rate 3. replace arch_timer_detect_rate with arch_timer_of_configure_rate 4.

[PATCH] ide: don't call memcpy with the same source and destination

The parisc architecture recently reimplemented the memcpy function and their reimplementation crashed when source and destination overlapped. The crash happened in the function ide_complete_cmd where memcpy is called with the same source and destination pointer. According to the C specification,

[PATCH] ide: don't call memcpy with the same source and destination

The parisc architecture recently reimplemented the memcpy function and their reimplementation crashed when source and destination overlapped. The crash happened in the function ide_complete_cmd where memcpy is called with the same source and destination pointer. According to the C specification,

Re: [PATCH 14/24] x86: Restrict MSR access when the kernel is locked down

On Wed, 5 Apr 2017, David Howells wrote: Can you please change the subsys in $subject to 'x86/msr:' ? > From: Matthew Garrett > > Writing to MSRs should not be allowed if the kernel is locked down, since > it could lead to execution of arbitrary code in kernel mode.

Re: [PATCH 14/24] x86: Restrict MSR access when the kernel is locked down

On Wed, 5 Apr 2017, David Howells wrote: Can you please change the subsys in $subject to 'x86/msr:' ? > From: Matthew Garrett > > Writing to MSRs should not be allowed if the kernel is locked down, since > it could lead to execution of arbitrary code in kernel mode. Based on a > patch by Kees

[GIT PULL] Btrfs

Hi Linus Dave Sterba collected a few more fixes for the last rc: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 These aren't marked for stable, but I'm putting them in with a batch were testing/sending by hand for this release. Liu Bo (3) commits

[GIT PULL] Btrfs

Hi Linus Dave Sterba collected a few more fixes for the last rc: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 These aren't marked for stable, but I'm putting them in with a batch were testing/sending by hand for this release. Liu Bo (3) commits

Re: [PATCH 13/24] x86: Lock down IO port access when the kernel is locked down

On Wed, 5 Apr 2017, David Howells wrote: > From: Matthew Garrett > > IO port access would permit users to gain access to PCI configuration > registers, which in turn (on a lot of hardware) give access to MMIO > register space. This would potentially permit root to

Re: [PATCH 13/24] x86: Lock down IO port access when the kernel is locked down

On Wed, 5 Apr 2017, David Howells wrote: > From: Matthew Garrett > > IO port access would permit users to gain access to PCI configuration > registers, which in turn (on a lot of hardware) give access to MMIO > register space. This would potentially permit root to trigger arbitrary > DMA, so

Re: [PATCH 3/4] net: macb: Add hardware PTP support

On Thu, Apr 13, 2017 at 02:39:23PM +0100, Rafal Ozieblo wrote: > This patch is based on original Harini's patch and Andrei's patch, > implemented in a separate file to ease the review/maintanance > and integration with other platforms. Please see if you can break this patch into 2 parts: 1.

Re: [PATCH 3/4] net: macb: Add hardware PTP support

On Thu, Apr 13, 2017 at 02:39:23PM +0100, Rafal Ozieblo wrote: > This patch is based on original Harini's patch and Andrei's patch, > implemented in a separate file to ease the review/maintanance > and integration with other platforms. Please see if you can break this patch into 2 parts: 1.

Re: RFC: WMI Enhancements

On Fri, Apr 14, 2017 at 05:42:03PM +, mario.limoncie...@dell.com wrote: > > > > -Original Message- > > From: Darren Hart [mailto:dvh...@infradead.org] > > Sent: Thursday, April 13, 2017 6:51 PM > > To: Limonciello, Mario > > Cc: pali.ro...@gmail.com;

Re: RFC: WMI Enhancements

On Fri, Apr 14, 2017 at 05:42:03PM +, mario.limoncie...@dell.com wrote: > > > > -Original Message- > > From: Darren Hart [mailto:dvh...@infradead.org] > > Sent: Thursday, April 13, 2017 6:51 PM > > To: Limonciello, Mario > > Cc: pali.ro...@gmail.com; r...@rjwysocki.net;

[PATCH v3 3/3] drivers:power:twl4030-charger: remove nonstandard max_current sysfs attribute

Signed-off-by: H. Nikolaus Schaller --- drivers/power/supply/twl4030_charger.c | 63 -- 1 file changed, 63 deletions(-) diff --git a/drivers/power/supply/twl4030_charger.c b/drivers/power/supply/twl4030_charger.c index e70c4ed..e02e150 100644

[PATCH v3 3/3] drivers:power:twl4030-charger: remove nonstandard max_current sysfs attribute

Signed-off-by: H. Nikolaus Schaller --- drivers/power/supply/twl4030_charger.c | 63 -- 1 file changed, 63 deletions(-) diff --git a/drivers/power/supply/twl4030_charger.c b/drivers/power/supply/twl4030_charger.c index e70c4ed..e02e150 100644 ---

[PATCH v3 1/3] drivers:power:twl4030-charger: don't check if battery is present

We can't assume that the battery is or stays present after probing on devices with replaceable battery. On some devices (e.g. GTA04 or OpenPanodra) it can be removed and even be hot swapped by the user while device continues to operate through external AC or USB power (as long as system power

[PATCH v3 1/3] drivers:power:twl4030-charger: don't check if battery is present

We can't assume that the battery is or stays present after probing on devices with replaceable battery. On some devices (e.g. GTA04 or OpenPanodra) it can be removed and even be hot swapped by the user while device continues to operate through external AC or USB power (as long as system power

[PATCH v3 2/3] drivers:power:twl4030-charger: add INPUT_CURRENT_LIMIT property and make it writeable

Currently, the twl4030 charger defines its own max_current by directly creating sysfs nodes. It should use the input_current_limit property which is e.g. used by the bq24257 driver. This patch adds the input_current_property with the same semantics as the max_current property. The code to manage

[PATCH v3 2/3] drivers:power:twl4030-charger: add INPUT_CURRENT_LIMIT property and make it writeable

Currently, the twl4030 charger defines its own max_current by directly creating sysfs nodes. It should use the input_current_limit property which is e.g. used by the bq24257 driver. This patch adds the input_current_property with the same semantics as the max_current property. The code to manage

[PATCH v3 0/3] Fixes for twl4030 charger

Changes V3: * worked in comments by Sebsatian Reichel * clarifications of some commit messages * rebased on v4.11rc-6 It took a while (18 months) until we propose an updated patch for upstream... 2015-11-02 12:27:39: Changes V2: * worked in comments by Nishanth Menon * added

[PATCH v3 0/3] Fixes for twl4030 charger

Changes V3: * worked in comments by Sebsatian Reichel * clarifications of some commit messages * rebased on v4.11rc-6 It took a while (18 months) until we propose an updated patch for upstream... 2015-11-02 12:27:39: Changes V2: * worked in comments by Nishanth Menon * added another patch which

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