From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 1/2] dt-bindings: arm: coresight: Add 'power-domains' property
Date: Fri, 22 Jul 2022 09:35:20 +0100 [thread overview]
Message-ID: <20220722083520.coovqsa2pv7mnifp@bogus> (raw)
In-Reply-To: <20220721212718.1980905-1-robh@kernel.org>
On Thu, Jul 21, 2022 at 03:27:14PM -0600, Rob Herring wrote:
> Coresight components may be in a power domain which is the case for the Arm
> Juno board. Allow a single 'power-domains' entry for Coresight components.
>
I assume the maxItems can be changed in case if some platforms have multiple
power domains especially for some per CPU coresight ETR/debug components.
But for now, it looks good.
Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
--
Regards,
Sudeep
next prev parent reply other threads:[~2022-07-22 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 21:27 [PATCH 1/2] dt-bindings: arm: coresight: Add 'power-domains' property Rob Herring
2022-07-21 21:27 ` [PATCH 2/2] dt-bindings: arm: coresight-tmc: Add 'iommu' property Rob Herring
2022-07-22 8:35 ` Sudeep Holla [this message]
2022-08-24 19:04 ` [PATCH 1/2] dt-bindings: arm: coresight: Add 'power-domains' property Rob Herring
2022-08-25 16:32 ` Mathieu Poirier
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=20220722083520.coovqsa2pv7mnifp@bogus \
--to=sudeep.holla@arm.com \
--cc=alexandre.torgue@foss.st.com \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mathieu.poirier@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mike.leach@linaro.org \
--cc=robh@kernel.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