From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: add acpi support for the arm
Date: Wed, 20 Nov 2019 15:43:45 +0200 [thread overview]
Message-ID: <20191120134345.GO32742@smile.fi.intel.com> (raw)
In-Reply-To: <HK0PR03MB395381E10D367C6229CCF8B6FF4F0@HK0PR03MB3953.apcprd03.prod.outlook.com>
On Wed, Nov 20, 2019 at 01:15:25PM +0000, Steven Hao wrote:
> Hi Bin：
>
> There are a little difference about acpi specification between the arm and x86，so the arm-acpi-support is needed.
Nobody disputes against it. The point is that ACPI table generation here and
there is fundamentally the same, the contents may be differ. Moreover, for some
tables I don't believe, for instance SPCR, has anything new in ARM vs. x86.
> One generic comment, could you please check whether the existing x86
> ACPI support can be reused/refactored to support ARM?
>
> Regards,
> Bin
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2019-11-20 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 7:38 [U-Boot] [PATCH] arm: add acpi support for the arm Steven Hao
2019-11-20 10:21 ` Bin Meng
2019-11-20 10:56 ` Andy Shevchenko
2019-11-20 13:15 ` Steven Hao
2019-11-20 13:43 ` Andy Shevchenko [this message]
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=20191120134345.GO32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=u-boot@lists.denx.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