From: Lee Jones <lee.jones@linaro.org>
To: Adrian Pop <pop.adrian61@gmail.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] arm: dt-bindings: mfd: stm32f-rcc: Add missing DSI clock
Date: Mon, 27 Apr 2020 07:49:10 +0100 [thread overview]
Message-ID: <20200427064910.GC3559@dell> (raw)
In-Reply-To: <20200424181642.32084-1-pop.adrian61@gmail.com>
On Fri, 24 Apr 2020, Adrian Pop wrote:
> Add missing clock.
>
> Signed-off-by: Adrian Pop <pop.adrian61@gmail.com>
> ---
> include/dt-bindings/mfd/stm32f7-rcc.h | 1 +
> 1 file changed, 1 insertion(+)
I assume patch 2 depends on this?
If so, where is it? Why isn't it in my inbox?
> diff --git a/include/dt-bindings/mfd/stm32f7-rcc.h b/include/dt-bindings/mfd/stm32f7-rcc.h
> index a90f3613c584..ba5cb7456ee4 100644
> --- a/include/dt-bindings/mfd/stm32f7-rcc.h
> +++ b/include/dt-bindings/mfd/stm32f7-rcc.h
> @@ -107,6 +107,7 @@
> #define STM32F7_RCC_APB2_SAI1 22
> #define STM32F7_RCC_APB2_SAI2 23
> #define STM32F7_RCC_APB2_LTDC 26
> +#define STM32F7_RCC_APB2_DSI 27
>
> #define STM32F7_APB2_RESET(bit) (STM32F7_RCC_APB2_##bit + (0x24 * 8))
> #define STM32F7_APB2_CLOCK(bit) (STM32F7_RCC_APB2_##bit + 0xA0)
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-04-27 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 18:16 [PATCH 1/2] arm: dt-bindings: mfd: stm32f-rcc: Add missing DSI clock Adrian Pop
2020-04-27 6:49 ` Lee Jones [this message]
2020-04-27 18:59 ` Adrian Pop
2020-04-28 7:03 ` Lee Jones
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=20200427064910.GC3559@dell \
--to=lee.jones@linaro.org \
--cc=alexandre.torgue@st.com \
--cc=devicetree@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=mcoquelin.stm32@gmail.com \
--cc=pop.adrian61@gmail.com \
--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 NNTP newsgroup(s).