From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Xue, Ken" <Ken.Xue@amd.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wu, Jeff" <Jeff.Wu@amd.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andriy Shevchenko <andriy.shevchenko@intel.com>
Subject: Re: [PATCH] acpi:apd:add AMD ACPI2Platform device support for x86 system.
Date: Mon, 24 Nov 2014 02:47:32 +0100 [thread overview]
Message-ID: <2267517.glgofXUn7B@vostro.rjw.lan> (raw)
In-Reply-To: <4AC89B18A26BAB43B540DB1C94E2802C05A48D06@scybexdag03.amd.com>
On Monday, November 24, 2014 01:02:30 AM Xue, Ken wrote:
>
> 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@amd.com>
> > Signed-off-by: Jeff Wu <Jeff.Wu@amd.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?
I'd prefer the common code to reside in one file (or one .c file and one header
file), and the driver-specific code to stay in separate per-driver files.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-11-24 1:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 5:58 [PATCH] acpi:apd:add AMD ACPI2Platform device support for x86 system Ken Xue
2014-11-21 5:15 ` Xue, Ken
2014-11-21 14:58 ` Rafael J. Wysocki
2014-11-24 1:15 ` Rafael J. Wysocki
2014-11-24 1:02 ` Xue, Ken
2014-11-24 1:47 ` Rafael J. Wysocki [this message]
2014-11-26 10:31 ` Ken Xue
2014-11-27 11:46 ` Mika Westerberg
2014-11-27 17:06 ` Rafael J. Wysocki
2014-11-27 16:48 ` Mika Westerberg
2014-11-28 1:33 ` Ken Xue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2267517.glgofXUn7B@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=Jeff.Wu@amd.com \
--cc=Ken.Xue@amd.com \
--cc=andriy.shevchenko@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox