From: Ken Xue <ken.xue@amd.com>
To: Loc Ho <lho@apm.com>
Cc: wsa@the-dreams.de, rjw@rjwysocki.net,
mika.westerberg@linux.intel.com, Len Brown <lenb@kernel.org>,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Jon Masters <jcm@redhat.com>, "patches@apm.com" <patches@apm.com>,
Annie.Wang@amd.com
Subject: Re: [PATCH 1/2] acpi:apd: Add APM X-Gene ACPI I2C device support
Date: Thu, 10 Dec 2015 15:19:10 +0800 [thread overview]
Message-ID: <1449731950.4557.24.camel@kxue-X58A-UD3R> (raw)
In-Reply-To: <CAPw-ZTnReGBAJWyj13=bov=A7WX5oZnrW8MDzUUVTjHkd3xkKg@mail.gmail.com>
On Wed, 2015-12-09 at 22:57 -0800, Loc Ho wrote:
> >> Sure you want this?
> > Yes. Even though it may look like too much macros for just several
> > devices now. But I think AMD and other ARM socs may also try to leverage
> > APD for more and more ACPI devices.
> > It is a good direction that 1)improve efficiency of matching ACPI
> > handler 2) split devices and potential hook routines into different
> > classes clearly
> >
> > It also will be more convenient to move ARM devices out of APD if there
> > is a new design for ARM ACPI device.
> >
>
> Okay... I will generate v2 when ready. One more question, does AMD
> ARM64 SoC need it later?
>
Thanks. I am not sure about driver design for AMD ARM64 SoC.
next prev parent reply other threads:[~2015-12-10 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 0:16 [PATCH 0/2] i2c:dw: Add APM X-Gene ACPI I2C device support Loc Ho
2015-12-08 0:16 ` [PATCH 1/2] acpi:apd: " Loc Ho
2015-12-08 2:49 ` Ken Xue
2015-12-09 22:03 ` Loc Ho
2015-12-10 6:14 ` Ken Xue
2015-12-10 6:57 ` Loc Ho
2015-12-10 7:19 ` Ken Xue [this message]
2015-12-08 0:16 ` [PATCH 2/2] i2c:dw: " Loc Ho
2015-12-08 11:36 ` Mika Westerberg
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=1449731950.4557.24.camel@kxue-X58A-UD3R \
--to=ken.xue@amd.com \
--cc=Annie.Wang@amd.com \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=lho@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=patches@apm.com \
--cc=rjw@rjwysocki.net \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).