DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=pacbell.net;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
  b=ntxB4ZUi0lU2NLgSo80/D3XU98L4hBZVjYxqot91qUPSJ5DmIh/IrMixlCHi5uy19iR6EnN+Rlbo9MSV68H9KUdUJ0FPcO6V97P+2auQ3TkGDn1dMfQXLxVmHmHsIXvx8PcIqnZwJfz67RX50gJVasUbbfB4DhnMQTUELMUD4t0=;
Message-ID: <94320.67137.qm@web180312.mail.gq1.yahoo.com>
Date: Fri, 23 Jul 2010 02:53:30 -0700 (PDT)
From: David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH] musb: move usb_add_hcd to the core init code from gadget code
To: felipe.balbi@nokia.com, linux-usb@vger.kernel.org,
        Bryan Wu <bryan.wu@canonical.com>
Cc: kernel-team@lists.ubuntu.com, linux-kernel@vger.kernel.org,
        ricardo.salveti@canonical.com
In-Reply-To: <1279877769-5210-1-git-send-email-bryan.wu@canonical.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 649
Lines: 18

Are you sure this doesn't break the hardware
initialization sequencing on some chips?

I distinctly call losing over a month of development
time on this issue, because the hardware has some
undocumented constraints in this area.  The entire
reeason the host init is so "late" is that doing
it earlier (at more logically sensible moments, (in
terms of USB specs vs Mentor silicon) broke things.

- Dave


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/