All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Paul Walmsley <paul@pwsan.com>,
	arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org,
	Aida Mynzhasova <aida.mynzhasova@skitlab.ru>
Subject: Re: [GIT PULL] make mach-omap2 boot with device tree only for v3.14
Date: Tue, 10 Dec 2013 11:50:54 -0800	[thread overview]
Message-ID: <20131210195054.GS13171@atomide.com> (raw)
In-Reply-To: <201312102039.42933.arnd@arndb.de>

* Arnd Bergmann <arnd@arndb.de> [131210 11:41]:
> On Tuesday 10 December 2013, Tony Lindgren wrote:
> > board-ti8168evm.c
> > 
> > I doubt ti8168evm has even worked for a long time.. It's in pretty
> > sorry state unfortunately with missing clock support and missing
> > handle_irq entry in the board-ti8168evm.c.
> 
> Does that imply the entire ti81xx soc support is lacking, or just
> that board specifically? It seems to be the only board file that
> ever got merged.

It's an omap3 variant and it's still waiting for the clock patches 
that now unfortunately have a dependency to the the omap clock
move to drivers/clk. Aida Mynzhasova posted some patches few months
ago here:

http://www.spinics.net/lists/linux-omap/msg96341.html

Since it's an omap3 variant, we should be able to make it usable
quite easily, so no need to remove the whole support at least
yet. Plus it seems to be an active TI part, so people are still it.

But it's definitely not a show stopper for making omap3 to boot in
device tree only mode.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] make mach-omap2 boot with device tree only for v3.14
Date: Tue, 10 Dec 2013 11:50:54 -0800	[thread overview]
Message-ID: <20131210195054.GS13171@atomide.com> (raw)
In-Reply-To: <201312102039.42933.arnd@arndb.de>

* Arnd Bergmann <arnd@arndb.de> [131210 11:41]:
> On Tuesday 10 December 2013, Tony Lindgren wrote:
> > board-ti8168evm.c
> > 
> > I doubt ti8168evm has even worked for a long time.. It's in pretty
> > sorry state unfortunately with missing clock support and missing
> > handle_irq entry in the board-ti8168evm.c.
> 
> Does that imply the entire ti81xx soc support is lacking, or just
> that board specifically? It seems to be the only board file that
> ever got merged.

It's an omap3 variant and it's still waiting for the clock patches 
that now unfortunately have a dependency to the the omap clock
move to drivers/clk. Aida Mynzhasova posted some patches few months
ago here:

http://www.spinics.net/lists/linux-omap/msg96341.html

Since it's an omap3 variant, we should be able to make it usable
quite easily, so no need to remove the whole support at least
yet. Plus it seems to be an active TI part, so people are still it.

But it's definitely not a show stopper for making omap3 to boot in
device tree only mode.

Regards,

Tony

  parent reply	other threads:[~2013-12-10 19:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  2:42 [GIT PULL] make mach-omap2 boot with device tree only for v3.14 Tony Lindgren
2013-12-10 14:35 ` Russell King - ARM Linux
2013-12-10 14:35   ` Russell King - ARM Linux
2013-12-10 16:01   ` Tony Lindgren
2013-12-10 16:01     ` Tony Lindgren
2013-12-10 16:07     ` Russell King - ARM Linux
2013-12-10 16:07       ` Russell King - ARM Linux
2013-12-10 16:59       ` Tony Lindgren
2013-12-10 16:59         ` Tony Lindgren
2013-12-10 20:36         ` Tony Lindgren
2013-12-10 20:36           ` Tony Lindgren
2013-12-10 18:36     ` Arnd Bergmann
2013-12-10 18:36       ` Arnd Bergmann
2013-12-10 18:43       ` Tony Lindgren
2013-12-10 18:43         ` Tony Lindgren
2013-12-10 18:45 ` Paul Walmsley
2013-12-10 18:45   ` Paul Walmsley
2013-12-10 18:59   ` Tony Lindgren
2013-12-10 18:59     ` Tony Lindgren
2013-12-10 19:08     ` Tony Lindgren
2013-12-10 19:08       ` Tony Lindgren
2013-12-10 19:27     ` Tony Lindgren
2013-12-10 19:27       ` Tony Lindgren
2013-12-10 19:39       ` Arnd Bergmann
2013-12-10 19:39         ` Arnd Bergmann
2013-12-10 19:44         ` Paul Walmsley
2013-12-10 19:44           ` Paul Walmsley
2013-12-10 19:50         ` Tony Lindgren [this message]
2013-12-10 19:50           ` Tony Lindgren
2013-12-10 23:07       ` Tony Lindgren
2013-12-10 23:07         ` Tony Lindgren
2013-12-13 19:26         ` Tony Lindgren
2013-12-13 19:26           ` Tony Lindgren
2013-12-17  7:14           ` Paul Walmsley
2013-12-17  7:14             ` Paul Walmsley
2013-12-17 15:26             ` Tony Lindgren
2013-12-17 15:26               ` Tony Lindgren
2013-12-10 23:56     ` Paul Walmsley
2013-12-10 23:56       ` Paul Walmsley
  -- strict thread matches above, loose matches on Subject: below --
2013-12-10  2:42 Tony Lindgren
2013-12-10  2:42 Tony Lindgren

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=20131210195054.GS13171@atomide.com \
    --to=tony@atomide.com \
    --cc=aida.mynzhasova@skitlab.ru \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.