From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: dts: stm32f7: add stm32f769I & stm32f746 discovery board support
Date: Mon, 12 Jun 2017 13:56:50 +0200 [thread overview]
Message-ID: <ca91f3d2-8758-b46b-dc2c-8081d32f40ab@st.com> (raw)
In-Reply-To: <1492043225-22424-1-git-send-email-vikas.manocha@st.com>
Hi Vikas
On 04/13/2017 02:27 AM, Vikas Manocha wrote:
> Stm32f769I & stm32f746 are MCUs of stm32f7 family. Here are the major
> specs of the two boards:
>
> stm32f769I discovery board:
> - Cortex-M7 core @216MHz
> - 2MB mcu internal flash
> - 512KB internal sram
> - 16MB sdram memory
> - 64MB qspi flash memory
> - 4 inch wvga LCD-TFT Display
>
> stm32f746 discovery board:
> - Cortex-M7 core @216MHz
> - 1MB mcu internal flash
> - 320KB internal sram
> - 8MB sdram memory
> - 16MB qspi flash memory
> - 4.3 inch 480x272 LCD-TFT display
>
> Signed-off-by: Vikas Manocha <vikas.manocha@st.com>
> ---
> Changed in v3:
> - fixed usart pin muxing for stm32f746 board, correct one is usart1_pins_pa9_pb7.
> - Added patch version in the patch title, was missed in v2.
>
> Changed in v2:
> - moved pin muxing from board dts file to soc dtsi
>
> arch/arm/boot/dts/Makefile | 2 +
> arch/arm/boot/dts/stm32f746-disco.dts | 74 +++++++++++++++++++++++++++++++++++
> arch/arm/boot/dts/stm32f746.dtsi | 12 ++++++
> arch/arm/boot/dts/stm32f769-disco.dts | 74 +++++++++++++++++++++++++++++++++++
> 4 files changed, 162 insertions(+)
> create mode 100644 arch/arm/boot/dts/stm32f746-disco.dts
> create mode 100644 arch/arm/boot/dts/stm32f769-disco.dts
>
...
Applied on stm32-dt-for-v4.13.
Regards
Alex
prev parent reply other threads:[~2017-06-12 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 0:27 [PATCH v3] ARM: dts: stm32f7: add stm32f769I & stm32f746 discovery board support Vikas Manocha
2017-06-12 11:56 ` Alexandre Torgue [this message]
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=ca91f3d2-8758-b46b-dc2c-8081d32f40ab@st.com \
--to=alexandre.torgue@st.com \
--cc=linux-arm-kernel@lists.infradead.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).