From: Stephen Boyd <sboyd@kernel.org>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Conor Dooley <conor+dt@kernel.org>,
Gabriel Fernandez <gabriel.fernandez@foss.st.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: clocks: stm32mp25: add access-controllers description
Date: Tue, 07 May 2024 14:59:23 -0700 [thread overview]
Message-ID: <dab1901cc1de2688977340734c252e98.sboyd@kernel.org> (raw)
In-Reply-To: <20240419152723.570159-2-gabriel.fernandez@foss.st.com>
Quoting gabriel.fernandez@foss.st.com (2024-04-19 08:27:20)
> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
>
> access-controllers is an optional property that allows to refer to
> domain access controller.
> The RCC driver will be able to check if we are allowed to register
> clocks for a peripheral.
>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2024-05-07 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 15:27 [PATCH 0/4] Use STM32 access controller for STM32MP25 clocks gabriel.fernandez
2024-04-19 15:27 ` [PATCH 1/4] dt-bindings: clocks: stm32mp25: add access-controllers description gabriel.fernandez
2024-04-22 14:34 ` Rob Herring
2024-05-07 21:59 ` Stephen Boyd [this message]
2024-04-19 15:27 ` [PATCH 2/4] clk: stm32mp2: use of STM32 access controller gabriel.fernandez
2024-05-07 22:02 ` Stephen Boyd
2024-05-15 6:41 ` Gabriel FERNANDEZ
2024-05-17 0:34 ` Stephen Boyd
2024-04-19 15:27 ` [PATCH 3/4] clk: stm32mp25: add security clocks gabriel.fernandez
2024-04-19 15:27 ` [PATCH 4/4] arm64: dts: st: add rcc support for STM32MP25 gabriel.fernandez
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=dab1901cc1de2688977340734c252e98.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@foss.st.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).