Dan Williams | 8 Feb 19:30 2016
Picon

[PATCH 0/3] ACPI 6.1 NFIT Compatibility

The latest NFIT specification clarifies that a memory device will have a
control region table per function interface.  Without the fix in [PATCH
1/3] Linux will miscount the number of DIMMs and fail to load the
driver.  The fix is tagged for -stable on the expectation that ACPI 6.1
compatible systems will overlap current -stable development branches.

The latter two patches in the series are verification tests that can be
integrated for 4.6.

---

Dan Williams (3):
      nfit: fix multi-interface dimm handling, acpi6.1 compatibility
      nfit, tools/testing/nvdimm: add format interface code definitions
      nfit, tools/testing/nvdimm: test multiple control regions per-dimm

 drivers/acpi/nfit.c              |   71 +++++++++++-----------
 drivers/acpi/nfit.h              |    6 ++
 tools/testing/nvdimm/test/nfit.c |  125 ++++++++++++++++++++++++++++++--------
 3 files changed, 141 insertions(+), 61 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Timur Tabi | 8 Feb 17:48 2016

platform_get_irq_byname() supported on ACPI?

Is there support for the platform_get_irq_byname() function on ACPI systems?

I'm working on adding ACPI support for a driver that currently only 
supports device tree.  This driver has code like this:

	ret = platform_get_irq_byname(pdev, "core0_irq");

This function works fine on device tree, but it fails on our ACPI system 
because our ACPI nodes don't appear to have any way to attach a name to 
an IRQ resource:

Method (_CRS, 0x0, Serialized) {
	Name (RBUF, ResourceTemplate() {
		[snip]
		Interrupt (ResourceConsumer, Level, ActiveHigh,
			Exclusive, , , )
			{0x120, 0x121, 0x122, 0x123}
	})
	Return (RBUF)
}

I would hate to have to do something like this:

ret = platform_get_irq_byname(pdev, "core0_irq");
if (ret)
	/* ACPI doesn't support named resources */
	ret = platform_get_irq(pdev, 0);

--

-- 
Qualcomm Innovation Center, Inc.
(Continue reading)

Gabriele Paoloni | 8 Feb 13:41 2016

[RFC PATCH v2 0/3] Add ACPI support for HiSilicon PCIe Host Controllers

From: gabriele paoloni <gabriele.paoloni <at> huawei.com>

This patchset adds ACPI support for the HiSilicon Hip05/Hip06 SoC PCIe controllers
The four patches respectively:
        - re-architect the current HiSilicon driver to make it scalable to the
          new ACPI quirks
        - rework the current HiSilicon driver to make it ECAM compliant
        - adds the HiSilicon ACPI specific quirks.

   This patchset  is based on
   https://github.com/semihalf-nowicki-tomasz/linux.git
   branch pci-acpi-v4

Changes v1 -> v2: removed the ACPI quirks dependency on Designware framework

gabriele paoloni (3):
  PCI: hisi: re-architect Hip05/Hip06 controllers driver to preapare for
    ACPI
  PCI: hisi: Make the HiSilicon PCIe host controller ECAM compliant
  PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers

 MAINTAINERS                         |   3 +
 drivers/pci/host/Kconfig            |   8 ++
 drivers/pci/host/Makefile           |   3 +-
 drivers/pci/host/pcie-designware.c  |   4 +-
 drivers/pci/host/pcie-designware.h  |   2 +
 drivers/pci/host/pcie-hisi-acpi.c   | 188 ++++++++++++++++++++++++++++++++++++
 drivers/pci/host/pcie-hisi-common.c |  73 ++++++++++++++
 drivers/pci/host/pcie-hisi.c        | 144 +++++++++++++--------------
 drivers/pci/host/pcie-hisi.h        |  25 +++++
(Continue reading)

Ms Ayala | 7 Feb 22:28 2016
Picon

Very Urgent,response needed.

Hi,

I am Ms. Ayala; I am getting in touch with you regarding an extremely
important and urgent matter.If you would oblige me the opportunity,I shall
provide you with details upon your response.Please respond to: msayalabrnaca101 <at> 163.com

Faithfully,
Ms. Ayala Bracha
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Rafael J. Wysocki | 6 Feb 00:52 2016

[GIT PULL] Power management and ACPI fixes for v4.5-rc3

Hi Linus,

Please pull from

 git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
 pm+acpi-4.5-rc3

to receive power management and ACPI fixes for v4.5-rc3 with top-most
commit 79e2f8dd522873614eb31001745af487451a10de

 Merge branches 'pm-core' and 'pm-domains'

on top of commit 36f90b0a2ddd60823fe193a85e60ff1906c2a9b3

 Linux 4.5-rc2

These are: a fix for a recently introduced false-positive
warnings about PM domain pointers being changed inappropriately
(harmless but annoying), an MCH size workaround quirk for one
more platform, a compiler warning fix (generic power domains
framework), an ACPI LPSS (Intel SoCs) driver fixup and a cleanup
of the ACPI CPPC core code.

Specifics:

 - PM core fix to avoid false-positive warnings generated when
   the pm_domain field is cleared for a device that appears to
   be bound to a driver (Rafael Wysocki).

 - New MCH size workaround quirk for Intel Haswell-ULT (Josh Boyer).
(Continue reading)

Heiner Kallweit | 6 Feb 00:00 2016
Picon

Problems since commit Recognize that Interrupt Line 255 means "not connected"

Since commit a44c386a361e "x86/PCI/ACPI: Recognize that Interrupt Line 255
means "not connected"" I get several "PCI INT not connected" warnings on
a Zotac CI321 and EHCI failes to load:

ehci-pci 0000:00:1d.0: PCI INT not connected
ehci-pci 0000:00:1d.0: EHCI Host Controller
ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 3
ehci-pci 0000:00:1d.0: debug port 2
ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
ehci-pci 0000:00:1d.0: request interrupt -2147483648 failed
ehci-pci 0000:00:1d.0: USB bus 3 deregistered
ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -107
ehci-pci: probe of 0000:00:1d.0 failed with error -107

XHCI brings the "PCI INT not connected" warning too but loads properly
(most likely because it uses a MSI interrupt).

Not sure whether this commit is to blame or a broken BIOS.
Just let me know in case you need additional information.

Regards, Heiner
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

qiujiang | 5 Feb 08:11 2016

[RFC PATCH] SPI/ACPI: DesignWare: Add ACPI support for Designware SPI driver

This patch added ACPI support for DesignWare SPI mmio driver. It
was based the corresponding DT driver and compatible for this two
way. This patch has been tested on Hisilicon D02 board. It relies
on the GPIO patchset.

Signed-off-by: qiujiang <qiujiang <at> huawei.com>
---
 drivers/spi/spi-dw-mmio.c | 26 +++++++++++++++++++++++---
 1 file changed, 23 insertions(+), 3 deletions(-)

diff --git a/drivers/spi/spi-dw-mmio.c b/drivers/spi/spi-dw-mmio.c
index a6d7029..de542f0 100644
--- a/drivers/spi/spi-dw-mmio.c
+++ b/drivers/spi/spi-dw-mmio.c
 <at>  <at>  -8,6 +8,7  <at>  <at> 
  * version 2, as published by the Free Software Foundation.
  */

+#include <linux/acpi.h>
 #include <linux/clk.h>
 #include <linux/err.h>
 #include <linux/interrupt.h>
 <at>  <at>  -36,7 +37,9  <at>  <at>  static int dw_spi_mmio_probe(struct platform_device *pdev)
 	struct dw_spi *dws;
 	struct resource *mem;
 	int ret;
-	int num_cs;
+	int num_cs, i;
+	struct gpio_desc *gpiod;
+	char propname[32];
(Continue reading)

Tomasz Nowicki | 4 Feb 18:28 2016

[PATCH V4 00/23] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI

From the functionality point of view this series might be split into the
following logic parts:
1. Make MMCONFIG code arch-agnostic which allows all architectures to collect
   PCI config regions and used when necessary.
2. Move non-arch specific bits to the core code.
3. Use MMCONFIG code and implement generic ACPI based PCI host controller driver.
4. Enable above driver on ARM64

Patches has been built on top of 4.5-rc1 and can be found here:
git <at> github.com:semihalf-nowicki-tomasz/linux.git (pci-acpi-v4)

NOTE, this patch set depends on Lorenzo's fixes:
https://patchwork.ozlabs.org/patch/576450/
which can be found in pci-acpi-v4 branch.

This has been tested on Cavium ThunderX server, JunoR2, HP RX2660 IA64, x86,
Hip05, X-Gene and QEMU-aarch64. Any help in reviewing and testing is very appreciated.

v3 -> v4
- dropped Jiang's fix http://lkml.iu.edu/hypermail/linux/kernel/1601.1/04318.html
- added Lorenzo's fix patch 19/24
- ACPI PCI bus domain number assigning cleanup
- changed resource management, we now claim and reassign resources
- improvements for applying quirks
- dropped Matthew's http://www.spinics.net/lists/linux-pci/msg45950.html dependency
- rebased to 4.5-rc1

v2 -> v3
- fix legacy IRQ assigning and IO ports registration
- remove reference to arch specific companion device for ia64
(Continue reading)

Dmitry Sutyagin | 3 Feb 17:04 2016
Picon

Powerbutton not detected/handled on Dell Venue 11 Pro (7140)

Dear all,

I am writing to ask for the attached patch to be reviewed and merged
into linux kernel (preferably starting from 3.18 but at least for 4.4
and up).
The patch was created by Jan-Michael Brummer, I took it from here -
https://bugzilla.kernel.org/show_bug.cgi?id=102281

Please let me know if I can help in any way.
Chen Yu | 3 Feb 12:04 2016
Picon

[PATCH] ACPI / button: Avoid using broken _LID on Surface tablet

Some platforms such as Surface 3, Surface Pro 1 have broken _LID
that, either _LID returns 'closed' during bootup, or _LID fails
to return the up-to-date lid state to OSPM. This is because
that, on these platforms _LID is implemented by returning a
local variable, which can only be updated by lid events:

Device (LID)
{
	Name (LIDB, Zero)
	Method (_LID, 0, NotSerialized)
	{
		Return (LIDB)
	}
}

Method (_E4C, 0, Serialized)
{
	If ((HELD == One))
	{
		^^LID.LIDB = One
	}
	Else
	{
		^^LID.LIDB = Zero
		Notify (LID, 0x80)
	}
}

After the lid is closed, _E4C updates the LIDB to zero, then system
falls asleep, however when lid is opened, there would be no interrupt
(Continue reading)

Sinan Kaya | 2 Feb 15:38 2016

platform: Do not detach from PM domains on shutdown

Hi Rafael,Ulf;

Following up to these patches on linux 4.5-rc1, 

commit 2d30bb0b3889adf09b342722b2ce596c0763bc93
Author: Rafael J. Wysocki <rafael.j.wysocki <at> intel.com>
Date:   Tue Jan 12 00:12:19 2016 +0100

    platform: Do not detach from PM domains on shutdown

    Shutdown is carried out when the driver is still bound to the
    device, so it is incorrect to detach it from a PM domain (if any)
    at this point.

    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki <at> intel.com>
    Reported-and-tested-by: Fabio Estevam <fabio.estevam <at> nxp.com>
    Acked-by: Ulf Hansson <ulf.hansson <at> linaro.org>

From Tomeu Vizoso <> 
Subject [PATCH v11 2/4] PM / Domains: add setter for dev.pm_domain 
Date Tue, 27 Oct 2015 15:38:49 +0100 

I'm seeing a problem with HIDMA driver during
unbind. I recognize that you fixed the issue for shutdown but the issue seems to be still there for
the remove case.

I'm wondering if you need to remove this too.

static int platform_drv_remove(struct device *_dev)
{
(Continue reading)


Gmane