From: Alexandre Torgue <alexandre.torgue@st.com>
To: Arnd Bergmann <arnd@arndb.de>,
Kevin Hilman <khilman@baylibre.com>, arm-soc <arm@kernel.org>,
Olof Johansson <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
Subject: Re: [GIT PULL] STM32 DT changes for v4.21 #1
Date: Tue, 8 Jan 2019 08:29:00 +0100 [thread overview]
Message-ID: <6a490c72-c76a-51ef-7c5d-2178d2adcc83@st.com> (raw)
In-Reply-To: <3fb58758-a67f-3a0f-72d2-abbfd71b6ae0@st.com>
Hi guys
On 12/3/18 12:18 PM, Alexandre Torgue wrote:
> Hi Arnd, Olof and Kevin,
>
> Please consider this first round of STM32 DT updates for v4.21.
>
> Thanks.
> Alex
>
This PR has not been merged in 5.0-rc1. Is there an issue (except than
v4.21 doesn't exist :)) ?
If not, is it possible to get it in next 5.0 rc ?
Thanks in advance
Alex
> The following changes since commit
> 651022382c7f8da46cb4872a545ee1da6d097d2a:
>
> Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git
> stm32-dt-for-v4.21-1
>
> for you to fetch changes up to 8914b63bab3c43a529316ba2858137bc57b74fa1:
>
> ARM: dts: stm32: add thermal sensor support on STM32MP157c
> (2018-12-03 10:43:26 +0100)
>
> ----------------------------------------------------------------
> STM32 DT updates for v4.21, round 1
>
> Highlights:
> ----------
>
> -MPU STM32MP157 platform update:
> -Declare DMAs for timers
> -Add sleep support for CAN
> -Split CAN RAM mapping between the 2 FDCAN instances
> -Add support of thermal sensor (DTS)
>
> ----------------------------------------------------------------
> Bich HEMON (3):
> ARM: dts: stm32: change CAN RAM mapping on stm32mp157c
> ARM: dts: stm32: add can1 sleep pins muxing
> ARM: dts: stm32: add can1 sleep pins muxing on stm32mp157c-ev1 board
>
> David Hernandez Sanchez (1):
> ARM: dts: stm32: add thermal sensor support on STM32MP157c
>
> Fabrice Gasnier (3):
> ARM: dts: stm32: Add dmas to timer on stm32mp157c
> ARM: dts: stm32: don't use timers dmas on stm32mp157c-ed1
> ARM: dts: stm32: don't use timers dmas on stm32mp157c-ev1
>
> arch/arm/boot/dts/stm32mp157-pinctrl.dtsi | 7 +++
> arch/arm/boot/dts/stm32mp157c-ed1.dts | 3 +
> arch/arm/boot/dts/stm32mp157c-ev1.dts | 10 +++-
> arch/arm/boot/dts/stm32mp157c.dtsi | 97
> ++++++++++++++++++++++++++++++-
> 4 files changed, 114 insertions(+), 3 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-08 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 11:18 [GIT PULL] STM32 DT changes for v4.21 #1 Alexandre Torgue
2018-12-03 20:57 ` Olof Johansson
2019-01-08 7:29 ` Alexandre Torgue [this message]
2019-01-08 8:42 ` Alexandre Torgue
2019-01-30 16:29 ` Arnd Bergmann
2019-01-30 16:45 ` Alexandre Torgue
2019-01-30 21:01 ` Arnd Bergmann
2019-01-31 8:04 ` Alexandre Torgue
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=6a490c72-c76a-51ef-7c5d-2178d2adcc83@st.com \
--to=alexandre.torgue@st.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=olof@lixom.net \
/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