From: dev@lynxeye.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra board file deprecation schedule
Date: Sat, 28 Apr 2012 23:26:21 +0200 [thread overview]
Message-ID: <1335648381.13148.4.camel@antimon> (raw)
In-Reply-To: <4F9B0E7C.1060408@wwwdotorg.org>
Am Freitag, den 27.04.2012, 15:24 -0600 schrieb Stephen Warren:
> Eventually, Tegra support will become device tree only in the mainline
> kernel; arch/arm/mach-tegra/board* will be deleted.
>
> I propose the following policy towards this goal: I'd like to maintain
> the board files until the relevant device tree file has the same level
> of functionality. Once that is achieved, and a Linus kernel is release
> with full support for the board via device tree, the board files can be
> deleted from the next kernel release.
>
> Does anyone have any issues with this?
Do we have any way to describe the clocks in the device tree? I'm
planning to add support for the Toradex Colibri T20 processor module,
which uses a 13MHz external OSC, so the generic clock init in the
current dt code definitely won't work for this board.
Thanks,
Lucas
next prev parent reply other threads:[~2012-04-28 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 21:24 Tegra board file deprecation schedule Stephen Warren
2012-04-27 21:39 ` Olof Johansson
2012-04-27 21:53 ` Stephen Warren
2012-04-27 22:00 ` Fabio Estevam
2012-04-27 22:20 ` Stephen Warren
2012-04-28 16:09 ` Marc Dietrich
2012-04-28 21:34 ` Russell King - ARM Linux
2012-04-29 18:11 ` Marc Dietrich
2012-04-29 18:56 ` Russell King - ARM Linux
2012-04-29 19:16 ` Stephen Warren
2012-04-30 8:58 ` Marc Dietrich
2012-04-30 15:58 ` Stephen Warren
2012-04-30 16:51 ` Marc Dietrich
2012-04-29 19:21 ` Stephen Warren
2012-04-30 9:00 ` Marc Dietrich
2012-04-28 21:26 ` Lucas Stach [this message]
2012-04-29 19:25 ` Stephen Warren
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=1335648381.13148.4.camel@antimon \
--to=dev@lynxeye.de \
--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).