From: Benjamin GAIGNARD <benjamin.gaignard@st.com>
To: Hugues FRUCHET <hugues.fruchet@st.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"valentin.schneider@arm.com" <valentin.schneider@arm.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Subject: Re: [PATCH v6 1/3] dt-bindings: media: stm32-dcmi: Add DCMI min frequency property
Date: Tue, 23 Jun 2020 11:48:28 +0000 [thread overview]
Message-ID: <459a0e53-c8d7-b79b-3004-f0114c99cff5@st.com> (raw)
In-Reply-To: <20200610122500.4304-2-benjamin.gaignard@st.com>
On 6/10/20 2:24 PM, Benjamin Gaignard wrote:
> Document st,stm32-dcmi-min-frequency property which is used to
> request CPUs minimum frequency when streaming frames.
Gentle for reviewers on this bindings.
Thanks,
Benjamin
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml b/Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml
> index 3fe778cb5cc3..05ca85a2411a 100644
> --- a/Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml
> +++ b/Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml
> @@ -44,6 +44,13 @@ properties:
> bindings defined in
> Documentation/devicetree/bindings/media/video-interfaces.txt.
>
> + st,stm32-dcmi-min-frequency:
> + description: DCMI minimum CPUs frequency requirement (in KHz).
> + allOf:
> + - $ref: /schemas/types.yaml#/definitions/uint32
> + - minimum: 0
> + - default: 0
> +
> required:
> - compatible
> - reg
> @@ -71,6 +78,7 @@ examples:
> clock-names = "mclk";
> dmas = <&dmamux1 75 0x400 0x0d>;
> dma-names = "tx";
> + st,stm32-dcmi-min-frequency = <650000>;
>
> port {
> dcmi_0: endpoint {
next prev parent reply other threads:[~2020-06-23 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 12:24 [PATCH v6 0/3] DCMI set minimum cpufreq requirement Benjamin Gaignard
2020-06-10 12:24 ` [PATCH v6 1/3] dt-bindings: media: stm32-dcmi: Add DCMI min frequency property Benjamin Gaignard
2020-06-23 11:48 ` Benjamin GAIGNARD [this message]
2020-06-10 12:24 ` [PATCH v6 2/3] media: stm32-dcmi: Set minimum cpufreq requirement Benjamin Gaignard
2020-06-10 17:16 ` Valentin Schneider
2020-06-24 9:24 ` Hugues FRUCHET
2020-06-24 11:27 ` Benjamin GAIGNARD
2020-06-10 12:25 ` [PATCH v6 3/3] ARM: dts: stm32: Set DCMI frequency requirement for stm32mp15x Benjamin Gaignard
2020-07-01 12:59 [PATCH v6 0/3] DCMI set minimum cpufreq requirement Benjamin Gaignard
2020-07-01 12:59 ` [PATCH v6 1/3] dt-bindings: media: stm32-dcmi: Add DCMI min frequency property Benjamin Gaignard
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=459a0e53-c8d7-b79b-3004-f0114c99cff5@st.com \
--to=benjamin.gaignard@st.com \
--cc=alexandre.torgue@st.com \
--cc=hugues.fruchet@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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 NNTP newsgroup(s).