All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Roger Quadros <rogerq@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-usb@vger.kernel.org, "Balbi, Felipe" <balbi@ti.com>
Cc: linux-next@vger.kernel.org
Subject: Re: regression(ti platforms): next-20140210 (ehci?)
Date: Mon, 10 Feb 2014 10:22:05 -0600	[thread overview]
Message-ID: <52F8FCAD.9080006@ti.com> (raw)
In-Reply-To: <52F8FA37.1020709@ti.com>

On 02/10/2014 10:11 AM, Roger Quadros wrote:
> On 02/10/2014 05:59 PM, Nishanth Menon wrote:
>> Hi,
>>
>> A quick note to report that I saw regression in today's next tag (logs
>> indicate around EHCI) boot on various TI platforms:
>>
>> Note: crane and sdp2430 are not expected to pass with
>> multi_v7_defconfig (note: omap2plus_defconfig boot seems to be sane
>> but USB is disabled there)
> 
> I'll take a look what's happening.
Thanks.

> Funny thing is that am335x doesn't even have an EHCI controller.

I dont think any of the am335x platforms fail - just OMAP3,4 platforms
which do fail.

Side note: all platforms are tested with device tree boot (not the
legacy boot).


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2014-02-10 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 15:59 regression(ti platforms): next-20140210 (ehci?) Nishanth Menon
2014-02-10 16:11 ` Roger Quadros
2014-02-10 16:22   ` Nishanth Menon [this message]
     [not found] ` <52F8F77B.70605-l0cyMroinI0@public.gmane.org>
2014-02-10 17:50   ` Roger Quadros
2014-02-10 18:02     ` Nishanth Menon
2014-02-10 18:16       ` Roger Quadros
2014-02-10 18:28     ` Kevin Hilman
2014-02-10 19:33       ` Nishanth Menon
2014-02-11  1:07         ` Kevin Hilman
2014-02-11 13:27           ` Nishanth Menon
     [not found]           ` <7h38jq8nk9.fsf-4poPxKt068f/PtFMR13I2A@public.gmane.org>
2014-02-11 15:21             ` Alan Stern

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=52F8FCAD.9080006@ti.com \
    --to=nm@ti.com \
    --cc=balbi@ti.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rogerq@ti.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.