From: "Arend van Spriel" <arend@broadcom.com>
To: "Tony Lindgren" <tony@atomide.com>
Cc: linux-omap@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Roger Quadros" <rogerq@ti.com>
Subject: Re: Regression 3.11-rc1: omap4panda: no usb and consequently no ethernet
Date: Thu, 18 Jul 2013 12:18:09 +0200 [thread overview]
Message-ID: <51E7C0E1.5090705@broadcom.com> (raw)
In-Reply-To: <20130718085951.GT7656@atomide.com>
On 07/18/2013 10:59 AM, Tony Lindgren wrote:
> * Arend van Spriel <arend@broadcom.com> [130718 01:47]:
>> So my first step was to follow the recipe given in that commit.
>> Beside that I noticed a thread about USB issue on LKML so I also
>> applied the following commit:
>>
>> commit 352f573e59050c7a604c35c58b4bbfc51edebbee
>> Author: Roger Quadros <rogerq@ti.com>
>> Date: Tue Jun 18 19:04:47 2013 +0300
>>
>> ARM: OMAP2+: Provide alias to USB PHY clock
>>
>> The attached kernel log seems to suggest that the device tree is
>> picked up by the kernel, but the USB does not seem very active. No
>> ethernet connectivity. This does seem a regression to me. Is there
>> some other patch that I need to get it going again?
>
> There are few .dts related patches missing for USB. Roger can
> point you to the current versions that Benoit should be queueing
> for the -rc series.
Hope Roger or Benoit will chime in.
> Then for the SDIO with device tree, take a look at the following
> patches:
>
> [PATCH 0/3] WLAN support for omap4 when booted with devicetree
> http://comments.gmane.org/gmane.linux.ports.arm.omap/97522#
>
> The wl12xx .dts changes for pandaboard are still missing too.
>
> Then I'll be updating these soonish:
> [PATCH 0/4] Updated omap_hsmmc SDIO and remuxing patches
>
> Those are needed for the SDIO interrupt, SDIO will work also
> without those.
Thanks for the pointers,
Arend
next prev parent reply other threads:[~2013-07-18 10:18 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 [this message]
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
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=51E7C0E1.5090705@broadcom.com \
--to=arend@broadcom.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).