linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] ARM: mxs: convert m28evk board to device tree
Date: Mon, 9 Jul 2012 11:50:10 +0200	[thread overview]
Message-ID: <201207091150.10910.marex@denx.de> (raw)
In-Reply-To: <20120709090239.GH11635@S2101-09.ap.freescale.net>

Dear Shawn Guo,

> On Mon, Jul 09, 2012 at 10:46:36AM +0200, Marek Vasut wrote:
> > Well ... the support for that board that's in current mainline is pretty
> > deprecated. And I wasn't really able to update it due to all the DT hype,
> > you know the rest of the story more then well etc. etc.
> 
> Let's remove it then :)

Yea.

> > To start the enet_out clock.
> 
> Will take care of it in m28evk_init().

But almost every board needs that hack ... won't it be easier to make it into 
default behavior? Or can we not somehow configure this via DT itself?

Best regards,
Marek Vasut

  reply	other threads:[~2012-07-09  9:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  6:14 [PATCH 0/7] Convert mxs board files to device tree Shawn Guo
2012-07-09  6:14 ` [PATCH 1/7] ARM: dts: imx28: move extra gpmi-nand pins into board dts Shawn Guo
2012-07-09  6:14 ` [PATCH 2/7] ARM: dts: imx28: move lcdif control " Shawn Guo
2012-07-09  6:14 ` [PATCH 3/7] ARM: mxs: convert m28evk board to device tree Shawn Guo
2012-07-09  7:10   ` Marek Vasut
2012-07-09  7:27     ` Shawn Guo
2012-07-09  7:32       ` Marek Vasut
2012-07-09  7:42         ` Shawn Guo
2012-07-09  6:14 ` [PATCH 4/7] ARM: mxs: convert apx4devkit " Shawn Guo
2012-07-09 15:15   ` Lauri Hintsala
2012-07-10  4:01     ` Shawn Guo
2012-07-10  7:10       ` Lauri Hintsala
2012-07-09  6:14 ` [PATCH 5/7] ARM: mxs: convert tx28 " Shawn Guo
2012-07-09 13:04   ` Lothar Waßmann
2012-07-09 14:18     ` Shawn Guo
2012-07-13  7:14     ` Shawn Guo
2012-07-13  9:21       ` Lothar Waßmann
2012-07-15 14:49         ` Shawn Guo
2012-07-15 15:00           ` Shawn Guo
2012-07-16  7:03             ` Lothar Waßmann
2012-07-18 13:36               ` Shawn Guo
2012-07-19  5:58                 ` Lothar Waßmann
2012-07-19  6:05                   ` Shawn Guo
2012-07-16  7:00           ` Lothar Waßmann
2012-07-18 13:39             ` Shawn Guo
2012-07-19  6:13               ` Lothar Waßmann
2012-07-19  6:22                 ` Shawn Guo
2012-07-09  6:14 ` [PATCH 6/7] ARM: mxs: convert stmp378x_devb " Shawn Guo
2012-07-09  6:14 ` [PATCH 7/7] ARM: mxs: add dtb-y target into Makefile.boot Shawn Guo
2012-07-09  7:04 ` [PATCH 0/7] Convert mxs board files to device tree Marek Vasut
2012-07-09  7:13   ` Shawn Guo
2012-07-09  7:33     ` Marek Vasut
2012-07-09  7:33       ` Marek Vasut
2012-07-09  8:06 ` [PATCH 3/7] ARM: mxs: convert m28evk board " Shawn Guo
2012-07-09  8:18   ` Marek Vasut
2012-07-09  8:40     ` Shawn Guo
2012-07-09  8:46       ` Marek Vasut
2012-07-09  9:02         ` Shawn Guo
2012-07-09  9:50           ` Marek Vasut [this message]
2012-07-09 14:23             ` Shawn Guo
2012-07-09  8:50       ` Marek Vasut
2012-07-09  9:00         ` Shawn Guo
2012-07-09  8:07 ` [PATCH 6/7] ARM: mxs: convert stmp378x_devb " Shawn Guo

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=201207091150.10910.marex@denx.de \
    --to=marex@denx.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).