From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-arm-kernel@lists.infradead.org, suzuki.poulose@arm.com
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>,
coresight@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: [RFC RESEND 0/7] coresight: Move remaining AMBA ACPI devices into platform driver
Date: Thu, 21 Sep 2023 09:50:33 +0530 [thread overview]
Message-ID: <20230921042040.1334641-1-anshuman.khandual@arm.com> (raw)
This moves remaining AMBA ACPI devices into respective platform drivers for
enabling ACPI based power management support. This might still require some
further changes but presented here just for some initial review & feedback.
This series applies on coresight/next coresight/for-next/queue and has been
built tested. This series has also been boot tested on a DT based coresight
device latform. Although it still requires testing on ACPI platforms.
Cc: Suzuki Poulose <suzuki.poulose@arm.com>
Cc: James Clark <james.clark@arm.com>
Cc: Mike Leach <mike.leach@linaro.org>
Cc: coresight@lists.linaro.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Anshuman Khandual (7):
coresight: replicator: Move ACPI support from AMBA driver to platform driver
coresight: funnel: Move ACPI support from AMBA driver to platform driver
coresight: catu: Move ACPI support from AMBA driver to platform driver
coresight: tpiu: Move ACPI support from AMBA driver to platform driver
coresight: tmc: Move ACPI support from AMBA driver to platform driver
coresight: stm: Move ACPI support from AMBA driver to platform driver
coresight: debug: Move ACPI support from AMBA driver to platform driver
drivers/acpi/arm64/amba.c | 8 --
drivers/hwtracing/coresight/coresight-catu.c | 136 ++++++++++++++++--
drivers/hwtracing/coresight/coresight-catu.h | 1 +
.../hwtracing/coresight/coresight-cpu-debug.c | 130 +++++++++++++++--
.../hwtracing/coresight/coresight-funnel.c | 49 ++++---
.../coresight/coresight-replicator.c | 44 +++---
drivers/hwtracing/coresight/coresight-stm.c | 80 +++++++++--
.../hwtracing/coresight/coresight-tmc-core.c | 127 ++++++++++++++--
drivers/hwtracing/coresight/coresight-tmc.h | 1 +
drivers/hwtracing/coresight/coresight-tpiu.c | 76 +++++++++-
10 files changed, 549 insertions(+), 103 deletions(-)
--
2.25.1
next reply other threads:[~2023-09-21 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 4:20 Anshuman Khandual [this message]
2023-09-21 4:20 ` [RFC RESEND 1/7] coresight: replicator: Move ACPI support from AMBA driver to " Anshuman Khandual
2023-09-21 11:10 ` Suzuki K Poulose
2023-09-22 4:10 ` Anshuman Khandual
2023-09-21 4:20 ` [RFC RESEND 2/7] coresight: funnel: " Anshuman Khandual
2023-09-21 4:20 ` [RFC RESEND 3/7] coresight: catu: " Anshuman Khandual
2023-09-21 4:20 ` [RFC RESEND 4/7] coresight: tpiu: " Anshuman Khandual
2023-09-21 4:20 ` [RFC RESEND 5/7] coresight: tmc: " Anshuman Khandual
2023-09-21 4:20 ` [RFC RESEND 6/7] coresight: stm: " Anshuman Khandual
2023-09-21 4:20 ` [RFC RESEND 7/7] coresight: debug: " Anshuman Khandual
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=20230921042040.1334641-1-anshuman.khandual@arm.com \
--to=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.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®