From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-next 2/4] arm: boot: dts: am4372: add ARM timers and SCU nodes
Date: Thu, 13 Aug 2015 10:01:14 -0500 [thread overview]
Message-ID: <20150813150114.GH27560@saruman.tx.rr.com> (raw)
In-Reply-To: <20150813083215.GY4215@atomide.com>
On Thu, Aug 13, 2015 at 01:32:15AM -0700, Tony Lindgren wrote:
> * Felipe Balbi <balbi@ti.com> [150812 13:00]:
> > AM437x devices sport SCU, TWD and Global timers,
> > let's add them to DTS so they have a chance to
> > probe and be used by Linux.
>
> Applying this one into omap-for-v4.3/dt-v2. Not sure
> if it will get merged as we're getting close to the
> merge window. The rest we can patch once Russell has
> reverted the bogus SMP dependency.
I'm just waiting for Russell's "it's okay to post on patch system".
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150813/a9e68a66/attachment-0001.sig>
next prev parent reply other threads:[~2015-08-13 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 19:56 [PATCH-next 0/4] arm: am437x: use TWD/Global timers Felipe Balbi
2015-08-12 19:56 ` [PATCH-next 1/4] Revert "ARM: 7655/1: smp_twd: make twd_local_timer_of_register() no-op for nosmp" Felipe Balbi
2015-08-13 15:37 ` Russell King - ARM Linux
2015-08-13 15:47 ` Felipe Balbi
2015-08-12 19:56 ` [PATCH-next 2/4] arm: boot: dts: am4372: add ARM timers and SCU nodes Felipe Balbi
2015-08-13 8:32 ` Tony Lindgren
2015-08-13 15:01 ` Felipe Balbi [this message]
2015-08-12 19:56 ` [PATCH-next 3/4] arm: omap2: Kconfig: select TWD and global timer on AM43xx devices Felipe Balbi
2015-08-12 19:56 ` [PATCH-next 4/4] arm: omap2: board-generic: use omap4_local_timer_init for AM437x Felipe Balbi
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=20150813150114.GH27560@saruman.tx.rr.com \
--to=balbi@ti.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).