linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
Date: Wed, 12 Jun 2013 15:39:05 -0700	[thread overview]
Message-ID: <87mwqvar92.fsf@linaro.org> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83ECAF76E@DBDE04.ent.ti.com> (Vaibhav Hiremath's message of "Wed, 12 Jun 2013 06:00:12 +0000")

Hi Vaibhav,

"Hiremath, Vaibhav" <hvaibhav@ti.com> writes:

[...]

> Paul/Kevin/Santosh,
>
> AM335x is booting up from Mainline, starting from v3.7, that?s where HWMOD data got merged to
> Mainline.
>
> We have discussed on this in the past as well, let me explain the issue here in detail
> again for everybody -

Thanks for the detail.

In my case, after more debug, it appears that where I was putting the
DTB in memory from u-boot was not working.   Using the addresses you
used gets things working again.  Thanks.

u-boot mainline (v2013.04) for BeagleBone has defaults that don't work
appear together:

U-Boot# printenv loadaddr
loadaddr=0x80200000
U-Boot# printenv fdtaddr
fdtaddr=0x80F80000

Changing fdtaddr around got things working again.  It's probably a good
idea to change the u-boot defaults to values that work, since that's a
likely starting point for people.

I'm now back to mainline booting well on both my original BeagleBone and
my BeagleBone black.

Thanks,

Kevin

> In case of Am335x we have only two possible options, as AM335x only boots up
> With DTB (Tested in BBB) -
>
> 1. Mainline u-boot + mainline Kernel:
> =====================================
>
> 1.a. Appended DTB method
> ------------------------
>
> Here you __must__ enabled below config options in order to get kernel booting,
>
> CONFIG_ARM_APPENDED_DTB=y
> CONFIG_ARM_ATAG_DTB_COMPAT=y
> CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
>
> And, I have used below command to append DTB to kernel image
>
> # cat arch/arm/boot/zImage arch/arm/boot/dts/am335x-bone.dtb >
> zImage-append && mkimage -A arm -O linux -T kernel -C none -a
> 0x80008000 -e 0x80008000 -n "Linux" -d zImage-append uImage-append
>
>
> I have attached complete log here with this mail for reference
> http://pastebin.com/82duFh78
>
>
> 1.b. Discrete DTB and uImage method:
> ------------------------------------
>
> Here you don?t need to enable any extra config options. Plain omap2plus_defconfig
> Should work without any issues.
>
> I have attached complete log here with this mail for reference
> http://pastebin.com/Nqr0PiwW
>
>
> 2. Older U-Boot (without DTB) + Mainline Kernel:
> ================================================
>
> This is same as #OPTION-1.a above.
>
>
> Thanks,
> Vaibhav

  reply	other threads:[~2013-06-12 22:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 16:38 [PATCH 00/14] ARM: OMAP5: hwmod, prm/cm data files and updates for 3.11 Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 01/14] ARM: OMAP4+: PRM: Move function prototypes to common header for re-use Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 03/14] ARM: OMAP4+: CM: " Santosh Shilimkar
2013-06-08 17:44   ` Paul Walmsley
2013-05-29 16:38 ` [PATCH 05/14] ARM: OMAP4+: PRCM MPU: " Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 06/14] ARM: OMAP5: PRCM: Add OMAP54XX local MPU PRCM registers Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 07/14] ARM: OMAP5: SCRM: Add OMAP54XX header file Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 08/14] ARM: OMAP5: clockdomain data: Add OMAP54XX data and update the header Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 09/14] ARM: OMAP5: powerdomain " Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 10/14] ARM: OMAP5: hwmod data: Create initial OMAP5 SOC hwmod data Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 11/14] ARM: OMAP5: voltagedomain data: Add OMAP5 voltage domain data Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 12/14] ARM: OMAP5: Enable build and frameowrk initialisations Santosh Shilimkar
2013-05-29 16:38 ` [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up Santosh Shilimkar
2013-06-06  4:00   ` Paul Walmsley
2013-06-06 22:27     ` Kevin Hilman
2013-06-07 17:01       ` Santosh Shilimkar
2013-06-10  8:35       ` Lokesh Vutla
2013-06-10 12:43         ` Lokesh Vutla
2013-06-10 17:03         ` Kevin Hilman
2013-06-11  4:14           ` Lokesh Vutla
2013-06-12  6:00             ` Hiremath, Vaibhav
2013-06-12 22:39               ` Kevin Hilman [this message]
2013-06-13  4:46                 ` Hiremath, Vaibhav
2013-06-12  6:04       ` Hiremath, Vaibhav
2013-06-12  6:26         ` Hiremath, Vaibhav
2013-06-07 16:13     ` Tony Lindgren
2013-05-29 16:38 ` [PATCH 14/14] ARM: OMAP4: hwmod data: Clean up the data file Santosh Shilimkar
2013-06-06 17:57   ` Paul Walmsley
2013-06-06 18:30     ` Santosh Shilimkar
2013-06-07  5:55       ` Sricharan R
2013-06-07  7:52         ` Paul Walmsley
2013-06-07  9:01           ` Sricharan R
2013-06-07  9:46             ` Tero Kristo
2013-06-07  9:50               ` Paul Walmsley
2013-06-07  9:53                 ` Sricharan R
2013-05-30  0:13 ` [PATCH 00/14] ARM: OMAP5: hwmod, prm/cm data files and updates for 3.11 Tony Lindgren
2013-05-30  0:24   ` Tony Lindgren
     [not found] ` <1369845494-30231-5-git-send-email-santosh.shilimkar@ti.com>
2013-06-08 17:54   ` [PATCH 04/14] ARM: OMAP5: CM: Add OMAP54XX register and bitfield files Paul Walmsley

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=87mwqvar92.fsf@linaro.org \
    --to=khilman@linaro.org \
    --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).