linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: Joel Fernandes <joelf@ti.com>
Cc: Roger Quadros <rogerq@ti.com>,
	tony@atomide.com, linux-omap@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regression 3.11-rc1: omap4panda: no usb and consequently no ethernet
Date: Fri, 26 Jul 2013 09:25:49 +0200	[thread overview]
Message-ID: <51F2247D.2000805@broadcom.com> (raw)
In-Reply-To: <51F1E65B.4020005@ti.com>

On 07/26/2013 05:00 AM, Joel Fernandes wrote:
> On 07/25/2013 09:49 PM, Joel Fernandes wrote:
>
> [..]
>
>>> Can I get back on this topic. When USB and ethernet was working for me
>>> as stated above, I was not doing tftpboot. When I use tftpboot the
>>> images are obtained from the tftp server, but after kernel has started
>>> there is nothing in /sys/bus/usb/devices/.
>>
>> I quickly tried 3.11-rc2 + Roger's USB PHY clock patch on omap4-panda-es
>> and enabled following USB options:
>>
>> CONFIG_USB_MUSB_HDRC=y
>> CONFIG_USB_PHY=y
>> CONFIG_OMAP_USB2=y
>> CONFIG_OMAP_CONTROL_USB=y
>> CONFIG_USB_MUSB_OMAP2PLUS=y
>> CONFIG_MFD_OMAP_USB_HOST=y
>> CONFIG_USB_EHCI_HCD=y
>> CONFIG_USB_OHCI_HCD=y
>> CONFIG_USB_EHCI_HCD_OMAP=y
>
> Sorry I missed saying I also set had to set CONFIG_NOP_USB_XCEIV=y
>

I will compare this with my .config. At first glance it looks like I am 
missing some of these.

Gr. AvS

  reply	other threads:[~2013-07-26  7:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  8:41 Regression 3.11-rc1: omap4panda: no usb and consequently no ethernet Arend van Spriel
2013-07-18  8:59 ` Tony Lindgren
2013-07-18 10:18   ` Arend van Spriel
2013-07-19 10:36   ` Arend van Spriel
2013-07-19 10:49     ` Roger Quadros
2013-07-19 10:57       ` Arend van Spriel
2013-10-01  8:05         ` using mmc2 on panda [was: Regression 3.11-rc1: omap4panda: no usb and consequently no ethernet] Arend van Spriel
2013-10-01  9:49           ` Roger Quadros
2013-10-01  9:53             ` Roger Quadros
2013-10-01 10:53               ` Arend van Spriel
2013-10-01 11:29                 ` Luca Coelho
2013-10-02 10:20                   ` Arend van Spriel
2013-10-02 10:48                     ` Luca Coelho
2013-10-01 12:17                 ` Roger Quadros
2013-10-01 13:19                   ` Balaji T K
2013-10-02  9:03                     ` Arend van Spriel
2013-07-19 10:53     ` Regression 3.11-rc1: omap4panda: no usb and consequently no ethernet Tony Lindgren
2013-07-20  7:38   ` Luciano Coelho
2013-07-18 11:18 ` Roger Quadros
2013-07-18 11:24   ` Arend van Spriel
2013-07-18 11:30     ` Roger Quadros
2013-07-18 12:38       ` Arend van Spriel
2013-07-18 12:42         ` Roger Quadros
2013-07-25 13:06           ` Arend van Spriel
2013-07-26  2:49             ` Joel Fernandes
2013-07-26  3:00               ` Joel Fernandes
2013-07-26  7:25                 ` Arend van Spriel [this message]
2013-07-26 10:13                 ` Arend van Spriel
2013-07-26 10:15                   ` Arend van Spriel
2013-07-26 10:23                     ` Arend van Spriel
2013-07-26 10:37                       ` Roger Quadros
2013-07-26 10:40                         ` Arend van Spriel

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=51F2247D.2000805@broadcom.com \
    --to=arend@broadcom.com \
    --cc=joelf@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rogerq@ti.com \
    --cc=tony@atomide.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 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).