From: nicolas.ferre@atmel•com (Nicolas Ferre)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] ARM: at91/dt: define RTT nodes
Date: Wed, 19 Nov 2014 14:26:04 +0100 [thread overview]
Message-ID: <546C9A6C.4070907@atmel.com> (raw)
In-Reply-To: <1415959732-13591-1-git-send-email-boris.brezillon@free-electrons.com>
On 14/11/2014 11:08, Boris Brezillon :
> Hello,
>
> This patch series define RTT and GPBR devices on all at91 SoCs
> embedding those blocks and enable them on the at91sam9g20ek and
> at91sam9m10g45ek boards (which are the boards I tested on).
>
> Best Regards,
>
> Boris
>
> Boris Brezillon (4):
> ARM: at91/dt: add RTT nodes to at91 dtsis
> ARM: at91/dt: add GPBR nodes
> ARM: at91/dt: enable the RTT block on the sam9g20ek board
> ARM: at91/dt: enable the RTT block on the at91sam9m10g45ek board
On the whole series:
Acked-by: Nicolas Ferre <nicolas.ferre@atmel•com>
and stacked up on top of at91-3.19-dt2
Bye,
> arch/arm/boot/dts/at91sam9260.dtsi | 14 ++++++++++++++
> arch/arm/boot/dts/at91sam9261.dtsi | 14 ++++++++++++++
> arch/arm/boot/dts/at91sam9263.dtsi | 21 +++++++++++++++++++++
> arch/arm/boot/dts/at91sam9g20ek_common.dtsi | 14 ++++++++++++++
> arch/arm/boot/dts/at91sam9g45.dtsi | 14 ++++++++++++++
> arch/arm/boot/dts/at91sam9m10g45ek.dts | 9 +++++++++
> arch/arm/boot/dts/at91sam9rl.dtsi | 14 ++++++++++++++
> 7 files changed, 100 insertions(+)
>
--
Nicolas Ferre
prev parent reply other threads:[~2014-11-19 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 10:08 [PATCH 0/4] ARM: at91/dt: define RTT nodes Boris Brezillon
2014-11-14 10:08 ` [PATCH 1/4] ARM: at91/dt: add RTT nodes to at91 dtsis Boris Brezillon
2014-11-14 10:08 ` [PATCH 2/4] ARM: at91/dt: add GPBR nodes Boris Brezillon
2014-11-14 10:08 ` [PATCH 3/4] ARM: at91/dt: enable the RTT block on the sam9g20ek board Boris Brezillon
2014-11-14 10:08 ` [PATCH 4/4] ARM: at91/dt: enable the RTT block on the at91sam9m10g45ek board Boris Brezillon
2014-11-19 13:26 ` Nicolas Ferre [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=546C9A6C.4070907@atmel.com \
--to=nicolas.ferre@atmel$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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