[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AC89B18A26BAB43B540DB1C94E2802C05A48D06@scybexdag03.amd.com>
Date: Mon, 24 Nov 2014 01:02:30 +0000
From: "Xue, Ken" <Ken.Xue@....com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
CC: "lenb@...nel.org" <lenb@...nel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Wu, Jeff" <Jeff.Wu@....com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Andriy Shevchenko <andriy.shevchenko@...el.com>
Subject: RE: [PATCH] acpi:apd:add AMD ACPI2Platform device support for x86
system.
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.Xue@....com>
> Signed-off-by: Jeff Wu <Jeff.Wu@....com>
Generally speaking, this seems to duplicate much code from acpi_lpss which should be re-used instead. What about moving the code that will be common between acpi_lpss and the new driver into a new file (say acpi_soc.c)?
Also, you need to avoid automatic creation of platform devices when !X86_AMD_PLATFORM_DEVICE in analogy with what acpi_lpss does, or bad things will happen.
[ken] sounds fair enough. Let me take action to merge drivers to acpi_soc.c ? or you have other plan?
[...]
Powered by blists - more mailing lists