or future AMD UART
> controller
>
> Add device HID AMDI0020 to match the AMD ACPI Vendor ID (AMDI) as
> registered in http://www.uefi.org/acpi_id_list, and the UART controller on
> future AMD paltform will use the HID instead of AMD0020.
>
> Signed-off-by: Wang Hongcheng <an
> From: Wang Hongcheng [mailto:annie.w...@amd.com]
> Sent: Friday, March 11, 2016 5:28 PM
> To: Rafael J. Wysocki; Len Brown; linux-a...@vger.kernel.org; linux-
> ker...@vger.kernel.org; SPG_Linux_Kernel
> Cc: Wang, Annie
> Subject: [PATCH V2] ACPI: APD: Add device HID for future AMD UART
>
ontroller
>
> Add device HID AMDI0030 to match the AMD ACPI Vendor ID (AMDI) as
> registered in http://www.uefi.org/acpi_id_list, and the GPIO controller on
> future AMD paltform will use the HID instead of AMD0030.
>
> Signed-off-by: Wang Hongcheng <annie.w...@amd.com>
>
> From: Wang Hongcheng [mailto:annie.w...@amd.com]
> Sent: Friday, March 11, 2016 10:59 AM
> To: Linus Walleij; linux-g...@vger.kernel.org; linux-kernel@vger.kernel.org;
> SPG_Linux_Kernel
> Cc: Wang, Annie
> Subject: [PATCH] pinctrl: amd:Add device HID for future AMD GPIO controller
>
> Add
On 四, 2015-09-10 at 10:23 +0800, Ken Xue wrote:
Can someone help to apply this patch series? Thanks.
http://marc.info/?l=linux-scsi=144185206825609=2
http://marc.info/?l=linux-scsi=144185208525611=2
> Revert "SCSI: Fix NULL pointer dereference in runtime PM"
>
> This reverts commit
n sr device goes to runtime suspend,
> blk_{pre|post}_runtime_suspend will be called since sr device defined
> pm->runtime_suspend. But blk_{pre|post}_runtime_resume will not be
> called
> since sr device doesn't have pm->runtime_resume. Then sr device can
> not
> resume correctly anym
nding? And
try thoughts about acpi_soc, if there were more common features.
Regards,
Ken
-Original Message-
From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
Sent: Friday, January 23, 2015 6:57 AM
To: Xue, Ken
Cc: andy.shevche...@gmail.com; mika.westerb...@linux.intel.com;
linux-a...
acpi_soc, if there were more common features.
Regards,
Ken
-Original Message-
From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
Sent: Friday, January 23, 2015 6:57 AM
To: Xue, Ken
Cc: andy.shevche...@gmail.com; mika.westerb...@linux.intel.com;
linux-a...@vger.kernel.org; linux-kernel
On Tuesday, November 18, 2014 01:58:11 PM Ken Xue wrote:
> This new feature is to interpret AMD specific ACPI device to platform
> device such as I2C, UART found on AMD CZ and later chipsets. It is
> based on example INTEL LPSS. Now, it can support AMD I2C & UART.
>
> Signed-off-by: Ken Xue
>
On Tuesday, November 18, 2014 01:58:11 PM Ken Xue wrote:
This new feature is to interpret AMD specific ACPI device to platform
device such as I2C, UART found on AMD CZ and later chipsets. It is
based on example INTEL LPSS. Now, it can support AMD I2C UART.
Signed-off-by: Ken Xue ken
ger.kernel.org; linux-kernel@vger.kernel.org; Xue, Ken; Wu, Jeff
Subject: [PATCH] acpi:apd:add AMD ACPI2Platform device support for x86 system.
This new feature is to interpret AMD specific ACPI device to platform device
such as I2C, UART found on AMD CZ and later chipsets. It is based on example
I
-kernel@vger.kernel.org; Xue, Ken; Wu, Jeff
Subject: [PATCH] acpi:apd:add AMD ACPI2Platform device support for x86 system.
This new feature is to interpret AMD specific ACPI device to platform device
such as I2C, UART found on AMD CZ and later chipsets. It is based on example
INTEL LPSS. Now
12 matches
Mail list logo
