From: Hanjun Guo <guohanjun@huawei.com>
To: Yang Shunyong <shunyong.yang@hxt-semitech.com>, <rjw@rjwysocki.net>
Cc: <lenb@kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Joey Zheng <yu.zheng@hxt-semitech.com>,
"Wang Dongsheng" <dongsheng.wang@hxt-semitech.com>,
Jiang Yutang <yutang2.jiang@hxt-semitech.com>
Subject: Re: [PATCH v3] ACPI / tables: Add IORT to injectable table list
Date: Fri, 2 Feb 2018 19:54:24 +0800 [thread overview]
Message-ID: <68362a1f-cc0c-42f9-97da-bdf379c4f5a1@huawei.com> (raw)
In-Reply-To: <1517567138-27283-1-git-send-email-shunyong.yang@hxt-semitech.com>
On 2018/2/2 18:25, Yang Shunyong wrote:
> Loading IORT table from initrd is used to fix firmware IORT defects.
I don't think this fix "firmware defects", it just for debug purpose,
we will not use that for production purpose, right? I think above line
can be removed.
> Moreover, it is very useful to debug SMMU node/device probe, MSI
> allocation, stream id translation and IORT table from firmware. It
> is also very useful to enable SMMU and devices behind SMMU before
> firmware is ready.
>
> This patch adds ACPI_SIG_IORT to the table, which enables IORT
> from initrd to override which from firmware.
>
> Signed-off-by: Yang Shunyong <shunyong.yang@hxt-semitech.com>
> Cc: Joey Zheng <yu.zheng@hxt-semitech.com>
> Cc: Wang Dongsheng <dongsheng.wang@hxt-semitech.com>
> Cc: Jiang Yutang <yutang2.jiang@hxt-semitech.com>
> Cc: Hanjun Guo <guohanjun@huawei.com>
With that updated,
Acked-by: Hanjun Guo <hanjun.guo@linaro.org>
Thanks
Hanjun
next prev parent reply other threads:[~2018-02-02 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 10:25 Yang Shunyong
2018-02-02 11:54 ` Hanjun Guo [this message]
2018-02-02 12:12 ` Wang, Dongsheng
2018-02-19 19:13 ` Jon Masters
2018-02-20 2:52 ` Yang, Shunyong
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=68362a1f-cc0c-42f9-97da-bdf379c4f5a1@huawei.com \
--to=guohanjun@huawei.com \
--cc=dongsheng.wang@hxt-semitech.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shunyong.yang@hxt-semitech.com \
--cc=yu.zheng@hxt-semitech.com \
--cc=yutang2.jiang@hxt-semitech.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
all inboxes | Powered by JetHome®