From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 1/3] ACPICA: Add support for FFH Opregion special context data
Date: Wed, 22 Jun 2022 15:00:42 +0100 [thread overview]
Message-ID: <20220622140042.bjg72oxjo43l2rwo@bogus> (raw)
In-Reply-To: <CAJZ5v0j0Ayb3KGpfxuuXH9CHUrt8rupVg5OK=r6hqZQEYm3jFA@mail.gmail.com>
On Wed, Jun 22, 2022 at 02:50:08PM +0200, Rafael J. Wysocki wrote:
> On Thu, Jun 16, 2022 at 11:01 AM Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > FFH(Fixed Function Hardware) Opregion is approved to be added in ACPIC 6.5 via
>
> s/ACPIC/ACPI/
>
Fixed and pushed in ACPICA PR.
> > code first approach[1]. It requires special context data similar to GPIO and
> > Generic Serial Bus as it needs to know platform specific offset and length.
> >
> > Add support for the special context data needed by FFH Opregion.
> >
> > FFH OpRegion enables advanced use of FFH on some architectures. For example,
> > it could be used to easily proxy AML code to architecture-specific behavior
> > (to ensure it is OS initiated)
> >
> > Actual behavior of FFH is ofcourse architecture specific and depends on
> > the FFH bindings. The offset and length could have arch specific meaning
> > or usage.
> >
> > [1] https://bugzilla.tianocore.org/show_bug.cgi?id=3598
> >
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>
> This looks reasonable to me and I see that you've already submitted a
> pull request to the upstream ACPICA.
I assume you would prefer me to post the other 2 patches once this lands
in your -next. Worst case I would like to get the generic patch in along
with ACPICA changes, I can then route the arm64 specific next cycle if it
gets too late for v5.20
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-22 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 9:01 [PATCH 0/3] ACPI: Implement FFH OpRegion support Sudeep Holla
2022-06-16 9:01 ` [PATCH 1/3] ACPICA: Add support for FFH Opregion special context data Sudeep Holla
2022-06-22 12:50 ` Rafael J. Wysocki
2022-06-22 14:00 ` Sudeep Holla [this message]
2022-06-22 14:10 ` Rafael J. Wysocki
2022-06-16 9:01 ` [PATCH 2/3] ACPI: Implement a generic FFH Opregion handler Sudeep Holla
2022-06-16 9:01 ` [PATCH 3/3] arm64: Add architecture specific ACPI FFH Opregion callbacks Sudeep Holla
2022-06-30 13:35 ` Catalin Marinas
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=20220622140042.bjg72oxjo43l2rwo@bogus \
--to=sudeep.holla@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=will@kernel.org \
/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