All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Luciano Coelho <coelho@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] WLAN support for omap4 when booted with devicetree
Date: Fri, 26 Apr 2013 09:04:01 -0700	[thread overview]
Message-ID: <20130426160400.GD29360@atomide.com> (raw)
In-Reply-To: <1366957908.4029.15.camel@cumari.coelho.fi>

* Luciano Coelho <coelho@ti.com> [130425 23:38]:
> On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
> > Hi all,
> 
> Hi Tony,
> 
> 
> > Here are some patches against linux next to make WLAN to work with
> > device tree. Note that we still are initializing wl12xx with pdata,
> > but so far it looks like only minimal binding for it is needed.
> 
> Thanks for doing this! I've been out on vacation for the past 3 weeks,
> so I didn't manage to finish the wl12xx DT stuff in time for 3.10. :(

OK I was wondering what happened.. 
 
> > There are various fixes pending posted recently, but at least the
> > fix "[PATCH] mmc: omap_hsmmc: Fix the DT pbias workaround for MMC
> > controllers 2 to 5" is needed.
> 
> I managed to apply the OMAP2+ and the blaze patches.  There were
> conflicts with the panda patch, so I skipped it for now.  I'll come back
> to it a bit later.

OK 
 
> > Please test on blaze/sdp if you have a chance, I don't have the
> > connectivity card on mine.
> 
> I tested this on Blaze and it seems to work fine! The driver gets probed
> and I can power the chip on and off (by putting the interface up and
> down) without any problems. :)

OK great thanks! It took me few hours of debugging to figure out that
it does not work on my blaze as I did not have the wl12xx card in it :)

Also can you fill in the missing GPIO lines for blaze from the schematics?
 
> BTW, did you (or anyone else) manage to get ethernet to work on Blaze
> (or Panda) with DT?

Yes that needs the two GPIO fixes posted by Jon Hunter last week.
One for patching in the GPIO trigger type to both omap4-sdp.dts, and
the other one is "gpio/omap: ensure gpio context is initialised".

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] WLAN support for omap4 when booted with devicetree
Date: Fri, 26 Apr 2013 09:04:01 -0700	[thread overview]
Message-ID: <20130426160400.GD29360@atomide.com> (raw)
In-Reply-To: <1366957908.4029.15.camel@cumari.coelho.fi>

* Luciano Coelho <coelho@ti.com> [130425 23:38]:
> On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
> > Hi all,
> 
> Hi Tony,
> 
> 
> > Here are some patches against linux next to make WLAN to work with
> > device tree. Note that we still are initializing wl12xx with pdata,
> > but so far it looks like only minimal binding for it is needed.
> 
> Thanks for doing this! I've been out on vacation for the past 3 weeks,
> so I didn't manage to finish the wl12xx DT stuff in time for 3.10. :(

OK I was wondering what happened.. 
 
> > There are various fixes pending posted recently, but at least the
> > fix "[PATCH] mmc: omap_hsmmc: Fix the DT pbias workaround for MMC
> > controllers 2 to 5" is needed.
> 
> I managed to apply the OMAP2+ and the blaze patches.  There were
> conflicts with the panda patch, so I skipped it for now.  I'll come back
> to it a bit later.

OK 
 
> > Please test on blaze/sdp if you have a chance, I don't have the
> > connectivity card on mine.
> 
> I tested this on Blaze and it seems to work fine! The driver gets probed
> and I can power the chip on and off (by putting the interface up and
> down) without any problems. :)

OK great thanks! It took me few hours of debugging to figure out that
it does not work on my blaze as I did not have the wl12xx card in it :)

Also can you fill in the missing GPIO lines for blaze from the schematics?
 
> BTW, did you (or anyone else) manage to get ethernet to work on Blaze
> (or Panda) with DT?

Yes that needs the two GPIO fixes posted by Jon Hunter last week.
One for patching in the GPIO trigger type to both omap4-sdp.dts, and
the other one is "gpio/omap: ensure gpio context is initialised".

Regards,

Tony

  reply	other threads:[~2013-04-26 16:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26  3:52 [PATCH 0/3] WLAN support for omap4 when booted with devicetree Tony Lindgren
2013-04-26  3:52 ` Tony Lindgren
2013-04-26  3:52 ` [PATCH 1/3] ARM: OMAP2+: Legacy support for wl12xx " Tony Lindgren
2013-04-26  3:52   ` Tony Lindgren
2013-04-26  6:32   ` Luciano Coelho
2013-04-26  6:32     ` Luciano Coelho
2013-04-26  9:33   ` Koen Kooi
2013-04-26  9:33     ` Koen Kooi
2013-04-26 11:00     ` Luciano Coelho
2013-04-26 11:00       ` Luciano Coelho
2013-04-26 11:16       ` Luciano Coelho
2013-04-26 11:16         ` Luciano Coelho
2013-04-26 15:51     ` Tony Lindgren
2013-04-26 15:51       ` Tony Lindgren
2013-04-26  3:52 ` [PATCH 2/3] ARM: dts: Add muxing for wl12xx on the SDIO bus for pandaboard Tony Lindgren
2013-04-26  3:52   ` Tony Lindgren
2013-04-26 13:23   ` Luciano Coelho
2013-04-26 13:23     ` Luciano Coelho
2013-04-26 15:58     ` Tony Lindgren
2013-04-26 15:58       ` Tony Lindgren
2013-04-26  3:52 ` [PATCH 3/3] ARM: dts: Add muxing for wl12xx on the SDIO bus for blaze Tony Lindgren
2013-04-26  3:52   ` Tony Lindgren
2013-04-26  6:32   ` Luciano Coelho
2013-04-26  6:32     ` Luciano Coelho
2013-04-26  6:31 ` [PATCH 0/3] WLAN support for omap4 when booted with devicetree Luciano Coelho
2013-04-26  6:31   ` Luciano Coelho
2013-04-26 16:04   ` Tony Lindgren [this message]
2013-04-26 16:04     ` Tony Lindgren

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=20130426160400.GD29360@atomide.com \
    --to=tony@atomide.com \
    --cc=coelho@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    /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.