From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: AM3517 fails to boot 3.16-rc5 device tree kernel Date: Mon, 21 Jul 2014 23:20:50 -0700 Message-ID: <20140722062050.GE18374@atomide.com> References: <20140717234037.GA9660@sysresccd> <20140718063806.GK18374@atomide.com> <20140721070913.GN18374@atomide.com> <20140721163838.GB14362@sysresccd> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:15930 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751139AbaGVGWP (ORCPT ); Tue, 22 Jul 2014 02:22:15 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Michael Welling Cc: linux-omap@vger.kernel.org, Benoit Cousson , paul@pwsan.com * Michael Welling [140721 17:17]: > On Mon, Jul 21, 2014 at 11:38 AM, Michael Welling wrote: > > On Mon, Jul 21, 2014 at 12:09:13AM -0700, Tony Lindgren wrote: > >> * Michael Welling [140718 07:42]: > >> > On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren wrote: > >> > > > >> > > Hmm maybe double check your're booting device tree based kernel > >> > > instead of legacy machine ID based kernel? The legacy booting should > >> > > still work just fine and no changes has been made to it, but it will > >> > > get removed shortly. > >> > > >> > I downloaded the version from the test results and it did boot. > >> > >> OK that's good to hear. > >> > >> > These are combining the uImage and dtb. How do you accomplish this? > >> > >> You need to make sure you have the appended DTB support enabled like > >> we do in omap2plus_defconfig: > >> > >> CONFIG_ARM_APPENDED_DTB=y > >> CONFIG_ARM_ATAG_DTB_COMPAT=y > >> CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y > >> > >> Then just cat zImage board.dtb > /tmp/zImage-dtba and run > >> mkimage to convert it to a uImage: > >> > >> $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \ > >> -n "Linux" -d /tmp/zImage-dtba /tmp/uImage > >> > > > > I actually discovered this and got LCD video working. Now USB host is > > not working. The only thing that registers is the OHCI/EHCI hosts. > > > > root@som3517:~# lsusb > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > > > Not sure what the problem is. The USB devices that are plugged in are > > powered but never detected. > > > > Any hints? > > So I got the USB host to work on boot with additional entries in the devicetree. > Documentation/devicetree/bindings/omap-usb-host.txt > > Though the devices work if plugged in at boot, any time a device is > hotplugged then > the device is not detected. It is powered very briefly and then off > without any kernel messages. > > So hints from this point would be good. Sorry no idea on that, maybe send a separate email about that with the USB and PHY people in Cc. Regards, Tony