All of lore.kernel.org
 help / color / mirror / Atom feed
From: LW@KARO-electronics.de (Lothar Waßmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/7] ARM: mxs: convert tx28 board to device tree
Date: Mon, 16 Jul 2012 09:00:24 +0200	[thread overview]
Message-ID: <20483.48136.37651.182431@ipc1.ka-ro> (raw)
In-Reply-To: <20120715144935.GB2429@S2100-06.ap.freescale.net>

Hi,

Shawn Guo writes:
> On Fri, Jul 13, 2012 at 11:21:09AM +0200, Lothar Wa?mann wrote:
> > Shawn Guo writes:
> > > Hi Lothar,
> > > 
> > > On Mon, Jul 09, 2012 at 03:04:53PM +0200, Lothar Wa?mann wrote:
> > > > This doesn't work at least because the pins that are used for PHY
> > > > strap options need to be reconfigured for their FEC functionality
> > > > after releasing the PHY reset. But even after adding the missing
> > > > reconfiguration the ethernet PHY does not work.
> > > > 
> > > Can you please test the branch below to see if ethernet PHY works?
> > > 
> > No. See bootlog below.
> > 
> Thanks for testing, Lothar.  But from the boot log below, the kernel
> did a non-DT boot rather than a boot from device tree.  More on this
>
I compiled the kernel with DT support, but just the TX28 board
selected. When selecting an additional i.MX28 board, the kernel
doesn't boot at all any more. Does this mean in order to get a kernel
with DT support one has to select at least two different platforms?
Is this behaviour intended?

> below.  But does that mean ethernet PHY does not work even on non-DT
> kernel right now?
> 
Seems so.

> > The following patch is required for the kernel to build:
> 
> Yes, Marek has reported that.  But I'm not so fond of fixing it right
> away like that, since mxs_defconfig has it enabled with board file
> support and does not expose the problem.
> 
> Instead, I would really like to remove those board files with equivalent
> device tree support, and build in mach-mxs.c and ocotp.c all the time.
> 
OK.

> This line tells that the kernel is doing a traditional non-DT boot.
> If the kernel boots from device tree, you should see the following line
> instead.
> 
> Machine: Freescale i.MX28 (Device Tree), model: Ka-Ro electronics TX28 module
> 
> I'm not sure if you have your bootloader passes dtb to kernel or use
> append-dtb approach.  In the later case, here are the brief
> instructions.
> 
> - Enable CONFIG_ARM_APPENDED_DTB and CONFIG_ARM_ATAG_DTB_COMPAT
> - Build kernel
> - make ARCH=arm imx28-tx28.dtb
> - cat arch/arm/boot/zImage arch/arm/boot/imx28-tx28.dtb > arch/arm/boot/zImage_dtb
> - Boot zImage_dtb like you boot zImage as usual
> 
I'm using the appended DTB approach, and have done exactly this except
for using uImage rather than zImage.


Lothar Wa?mann
-- 
___________________________________________________________

Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996

www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________

  parent reply	other threads:[~2012-07-16  7:00 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 [this message]
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
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=20483.48136.37651.182431@ipc1.ka-ro \
    --to=lw@karo-electronics.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 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.