From: Anshuman Khandual <anshuman.khandual@arm.com>
To: James Clark <james.clark@arm.com>, Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Mike Leach <mike.leach@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
coresight@lists.linaro.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH V2 1/7] coresight: replicator: Move ACPI support from AMBA driver to platform driver
Date: Mon, 4 Dec 2023 17:07:30 +0530 [thread overview]
Message-ID: <dbcd6fa5-1385-41d7-905e-d77b536c5d33@arm.com> (raw)
In-Reply-To: <2aec13e9-4ae3-676f-1ba8-c9e9a9241063@arm.com>
On 12/4/23 15:27, James Clark wrote:
>
> On 04/12/2023 04:48, Anshuman Khandual wrote:
>>
>> On 12/4/23 09:56, Anshuman Khandual wrote:
>>>
>>> On 12/1/23 18:05, Sudeep Holla wrote:
>>>> On Fri, Dec 01, 2023 at 11:50:47AM +0530, Anshuman Khandual wrote:
>>>>> Add support for the dynamic replicator device in the platform driver, which
>>>>> can then be used on ACPI based platforms. This change would now allow
>>>>> runtime power management for repliacator devices on ACPI based systems.
>>>>>
>>>>> The driver would try to enable the APB clock if available. Also, rename the
>>>>> code to reflect the fact that it now handles both static and dynamic
>>>>> replicators.
>>>>>
>>>>> Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>
>>>>> Cc: Sudeep Holla <sudeep.holla@arm.com>
>>>> Except the minor nit below which may apply also for few other patches
>>>> in the series
>>>>
>>>> Acked-by: Sudeep Holla <sudeep.holla@arm.com> # For ACPI related changes
>>>> Tested-by: Sudeep Holla <sudeep.holla@arm.com> # Boot and driver probe only
>>>>
>>>> [...]
>>>>
>>>>> diff --git a/drivers/hwtracing/coresight/coresight-replicator.c b/drivers/hwtracing/coresight/coresight-replicator.c
>>>>> index b6be73034996..64de0bee02ec 100644
>>>>> --- a/drivers/hwtracing/coresight/coresight-replicator.c
>>>>> +++ b/drivers/hwtracing/coresight/coresight-replicator.c
>>>>> @@ -38,6 +38,7 @@ DEFINE_CORESIGHT_DEVLIST(replicator_devs, "replicator");
>>>>> struct replicator_drvdata {
>>>>> void __iomem *base;
>>>>> struct clk *atclk;
>>>>> + struct clk *pclk;
>>>> [minor nit] Perhaps can be documented as well ?
>>> Sure, will add the following comment above the structure.
>>>
>>> @pclk: optional clock for the core parts of the replicator.
>> My bad, this will be the following instead.
>>
>> diff --git a/drivers/hwtracing/coresight/coresight-replicator.c b/drivers/hwtracing/coresight/coresight-replicator.c
>> index 64de0bee02ec..44b9a77ec8aa 100644
>> --- a/drivers/hwtracing/coresight/coresight-replicator.c
>> +++ b/drivers/hwtracing/coresight/coresight-replicator.c
>> @@ -31,6 +31,7 @@ DEFINE_CORESIGHT_DEVLIST(replicator_devs, "replicator");
>> * @base: memory mapped base address for this component. Also indicates
>> * whether this one is programmable or not.
>> * @atclk: optional clock for the core parts of the replicator.
>> + * @pclk: APB clock if present, otherwise NULL
>> * @csdev: component vitals needed by the framework
>> * @spinlock: serialize enable/disable operations.
>> * @check_idfilter_val: check if the context is lost upon clock removal.
>>
>> I will update replicator, tpiu, tmc, and stm devices.
>>
> funnel is missing it as well. If you build with W=1 it shows up.
Updated, done.
next prev parent reply other threads:[~2023-12-04 11:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 6:20 [PATCH V2 0/7] coresight: Move remaining AMBA ACPI devices into platform driver Anshuman Khandual
2023-12-01 6:20 ` [PATCH V2 1/7] coresight: replicator: Move ACPI support from AMBA driver to " Anshuman Khandual
2023-12-01 12:35 ` Sudeep Holla
2023-12-04 4:26 ` Anshuman Khandual
2023-12-04 4:48 ` Anshuman Khandual
2023-12-04 9:57 ` James Clark
2023-12-04 11:37 ` Anshuman Khandual [this message]
2023-12-01 6:20 ` [PATCH V2 2/7] coresight: funnel: " Anshuman Khandual
2023-12-01 12:35 ` Sudeep Holla
2023-12-01 6:20 ` [PATCH V2 3/7] coresight: catu: " Anshuman Khandual
2023-12-01 12:35 ` Sudeep Holla
2023-12-01 13:41 ` Suzuki K Poulose
2023-12-04 6:48 ` Anshuman Khandual
2023-12-01 6:20 ` [PATCH V2 4/7] coresight: tpiu: " Anshuman Khandual
2023-12-01 12:36 ` Sudeep Holla
2023-12-01 6:20 ` [PATCH V2 5/7] coresight: tmc: " Anshuman Khandual
2023-12-01 12:36 ` Sudeep Holla
2023-12-04 10:42 ` James Clark
2023-12-04 10:50 ` Suzuki K Poulose
2023-12-04 10:54 ` James Clark
2023-12-04 11:40 ` Sudeep Holla
2023-12-05 3:56 ` Anshuman Khandual
2023-12-01 6:20 ` [PATCH V2 6/7] coresight: stm: " Anshuman Khandual
2023-12-01 12:36 ` Sudeep Holla
2023-12-04 10:23 ` James Clark
2023-12-04 11:50 ` Anshuman Khandual
2023-12-04 13:17 ` James Clark
2023-12-05 5:20 ` Anshuman Khandual
2023-12-05 9:35 ` Sudeep Holla
2023-12-05 10:18 ` Suzuki K Poulose
2023-12-04 11:58 ` Sudeep Holla
2023-12-01 6:20 ` [PATCH V2 7/7] coresight: debug: " Anshuman Khandual
2023-12-01 12:37 ` Sudeep Holla
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=dbcd6fa5-1385-41d7-905e-d77b536c5d33@arm.com \
--to=anshuman.khandual@arm.com \
--cc=alexandre.torgue@foss.st.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lpieralisi@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mike.leach@linaro.org \
--cc=sudeep.holla@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