From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Besar Wicaksono <bwicaksono@nvidia.com>,
rafael@kernel.org, lenb@kernel.org, catalin.marinas@arm.com,
will@kernel.org, lorenzo.pieralisi@arm.com, guohanjun@huawei.com,
linux-tegra@vger.kernel.org, treding@nvidia.com,
jonathanh@nvidia.com, vsethi@nvidia.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ACPI: ARM Performance Monitoring Unit Table (APMT) initial support
Date: Fri, 14 Oct 2022 16:15:01 +0200 [thread overview]
Message-ID: <Y0lu5Vqs8pVeAfwR@lpieralisi> (raw)
In-Reply-To: <20221014105938.fyy6jns5fsu5xd7q@bogus>
[Please Besar update my email address according to MAINTAINERS - I missed
this thread]
On Fri, Oct 14, 2022 at 11:59:38AM +0100, Sudeep Holla wrote:
> Hi Besar,
>
> On Wed, Sep 28, 2022 at 07:28:34PM -0500, Besar Wicaksono wrote:
> > ARM Performance Monitoring Unit Table describes the properties of PMU
> > support in ARM-based system. The APMT table contains a list of nodes,
> > each represents a PMU in the system that conforms to ARM CoreSight PMU
> > architecture. The properties of each node include information required
> > to access the PMU (e.g. MMIO base address, interrupt number) and also
> > identification. For more detailed information, please refer to the
> > specification below:
> > * APMT: https://developer.arm.com/documentation/den0117/latest
> > * ARM Coresight PMU:
> > https://developer.arm.com/documentation/ihi0091/latest
> >
> > The initial support adds the detection of APMT table and generic
> > infrastructure to create platform devices for ARM CoreSight PMUs.
> > Similar to IORT the root pointer of APMT is preserved during runtime
> > and each PMU platform device is given a pointer to the corresponding
> > APMT node.
> >
>
> This looks good to me know.
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
>
> Hi Lorenzo,
>
> Not sure if there are any other arm specific ACPI changes in the queue
> for v6.2. Can you please add this too ?
We should just ask Catalin/Will to pick it up for the next kernel cycle,
if there is no need to repost we can just remind them in a couple
of weeks.
This also requires Rafael's review - at least to acknowledge the
change.
Thanks,
Lorenzo
WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Besar Wicaksono <bwicaksono@nvidia.com>,
rafael@kernel.org, lenb@kernel.org, catalin.marinas@arm.com,
will@kernel.org, lorenzo.pieralisi@arm.com, guohanjun@huawei.com,
linux-tegra@vger.kernel.org, treding@nvidia.com,
jonathanh@nvidia.com, vsethi@nvidia.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ACPI: ARM Performance Monitoring Unit Table (APMT) initial support
Date: Fri, 14 Oct 2022 16:15:01 +0200 [thread overview]
Message-ID: <Y0lu5Vqs8pVeAfwR@lpieralisi> (raw)
In-Reply-To: <20221014105938.fyy6jns5fsu5xd7q@bogus>
[Please Besar update my email address according to MAINTAINERS - I missed
this thread]
On Fri, Oct 14, 2022 at 11:59:38AM +0100, Sudeep Holla wrote:
> Hi Besar,
>
> On Wed, Sep 28, 2022 at 07:28:34PM -0500, Besar Wicaksono wrote:
> > ARM Performance Monitoring Unit Table describes the properties of PMU
> > support in ARM-based system. The APMT table contains a list of nodes,
> > each represents a PMU in the system that conforms to ARM CoreSight PMU
> > architecture. The properties of each node include information required
> > to access the PMU (e.g. MMIO base address, interrupt number) and also
> > identification. For more detailed information, please refer to the
> > specification below:
> > * APMT: https://developer.arm.com/documentation/den0117/latest
> > * ARM Coresight PMU:
> > https://developer.arm.com/documentation/ihi0091/latest
> >
> > The initial support adds the detection of APMT table and generic
> > infrastructure to create platform devices for ARM CoreSight PMUs.
> > Similar to IORT the root pointer of APMT is preserved during runtime
> > and each PMU platform device is given a pointer to the corresponding
> > APMT node.
> >
>
> This looks good to me know.
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
>
> Hi Lorenzo,
>
> Not sure if there are any other arm specific ACPI changes in the queue
> for v6.2. Can you please add this too ?
We should just ask Catalin/Will to pick it up for the next kernel cycle,
if there is no need to repost we can just remind them in a couple
of weeks.
This also requires Rafael's review - at least to acknowledge the
change.
Thanks,
Lorenzo
_______________________________________________
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-10-14 14:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 0:28 [PATCH v2] ACPI: ARM Performance Monitoring Unit Table (APMT) initial support Besar Wicaksono
2022-09-29 0:28 ` Besar Wicaksono
2022-09-30 17:46 ` Rafael J. Wysocki
2022-09-30 17:46 ` Rafael J. Wysocki
2022-10-07 16:49 ` Besar Wicaksono
2022-10-07 16:49 ` Besar Wicaksono
2022-10-14 10:55 ` Sudeep Holla
2022-10-14 10:55 ` Sudeep Holla
2022-10-14 10:59 ` Sudeep Holla
2022-10-14 10:59 ` Sudeep Holla
2022-10-14 14:15 ` Lorenzo Pieralisi [this message]
2022-10-14 14:15 ` Lorenzo Pieralisi
2022-10-14 14:17 ` Lorenzo Pieralisi
2022-10-14 14:17 ` Lorenzo Pieralisi
2022-11-02 9:31 ` Lorenzo Pieralisi
2022-11-02 9:31 ` Lorenzo Pieralisi
2022-11-07 19:08 ` Will Deacon
2022-11-07 19:08 ` Will Deacon
2022-11-07 19:10 ` Will Deacon
2022-11-07 19:10 ` Will Deacon
2022-11-11 23:54 ` Besar Wicaksono
2022-11-11 23:54 ` Besar Wicaksono
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=Y0lu5Vqs8pVeAfwR@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=bwicaksono@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=jonathanh@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=treding@nvidia.com \
--cc=vsethi@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.