public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: hotran <hotran@apm.com>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	Robert Moore <robert.moore@intel.com>,
	Lv Zheng <lv.zheng@intel.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	devel@acpica.org, Sudeep Holla <sudeep.holla@arm.com>,
	lho@apm.com, dhdang@apm.com
Subject: Re: [PATCH] mailbox: pcc: Support HW-Reduced Communication Subspace Type 2
Date: Fri, 8 Apr 2016 13:58:00 +0100	[thread overview]
Message-ID: <5707AAD8.9070306@arm.com> (raw)
In-Reply-To: <1459894447-15400-1-git-send-email-hotran@apm.com>

Hi,

On 05/04/16 23:14, hotran wrote:
> ACPI 6.1 has a HW-Reduced Communication Subspace Type 2 intended for
> use on HW-Reduce ACPI Platform, which requires read-modify-write sequence
> to acknowledge doorbell interrupt. This patch provides the implementation
> for the Communication Subspace Type 2.
>
> Signed-off-by: Hoan Tran <hotran@apm.com>
> ---
>   drivers/mailbox/pcc.c | 384 +++++++++++++++++++++++++++++++++++++-------------

>   include/acpi/actbl3.h |   8 +-

This(2nd) file is generally imported from ACPICA directly.

So you need to work with acpica-devel list(you can cc Robert Moore) to
get that alone integrated in acpica projected so that iasl tool and
other related components also gain support for this first.

If the ACPI tables are generated by UEFI, it would be good to add the
support in tianocore project. IIRC tianocore has some PCC reference in
Acpi60.h header.

It would help if the above two are done before we start looking into
Linux changes(pcc.c). To summarize this patch needs to be split.

-- 
Regards,
Sudeep

  reply	other threads:[~2016-04-08 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 22:14 [PATCH] mailbox: pcc: Support HW-Reduced Communication Subspace Type 2 hotran
2016-04-08 12:58 ` Sudeep Holla [this message]
2016-04-08 19:33   ` Moore, Robert
2016-04-19 19:02 ` Alexey Klimov
2016-04-19 20:40   ` Hoan Tran

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=5707AAD8.9070306@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=devel@acpica.org \
    --cc=dhdang@apm.com \
    --cc=hotran@apm.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=lenb@kernel.org \
    --cc=lho@apm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=robert.moore@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