From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: "Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
Grazvydas Ignotas <notasas@gmail.com>,
Benoit Cousson <bcousson@baylibre.com>,
Sourav Poddar <sourav.poddar@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: Fix WLAN regression on omap5-uevm
Date: Fri, 18 Sep 2015 09:51:09 -0700 [thread overview]
Message-ID: <20150918165109.GB8020@atomide.com> (raw)
In-Reply-To: <CAOCHtYh3pDg6_mdX71G=L5Vz-mOmBnerwR5pjumq5jYQ-tN5Pw@mail.gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [150918 09:45]:
> On Fri, Sep 18, 2015 at 11:29 AM, Tony Lindgren <tony@atomide.com> wrote:
> > Commit 99f84cae43df ("ARM: dts: add wl12xx/wl18xx bindings") added
> > device tree bindings for the TI WLAN SDIO on many omap variants.
> >
> > I recall wondering how come omap5-uevm did not have the WLAN
> > added and this issue has been bugging me for a while now, and
> > I finally tracked it down to a bad pinmux regression, and a missing
> > deferred probe handling for the 32k clock from palmas that's
> > requested by twl6040.
> >
> > Basically 392adaf796b9 ("ARM: dts: omap5-evm: Add mcspi data")
> > added pin muxing for mcspi4 that conflicts with the onboard
> > WLAN. While the omap5-uevm docs say the WLAN is not populated,
> > this was probably only the case for initial prototypes. Both
> > omap5-uevm boards I have have WLAN populated.
>
> Production boards from svtronics don't populate the wlan..
>
> http://www.svtronics.com/EVM/OMAP5432/5432
>
> quote: "WiFi not available on this model"
>
> They have an option to order a version with a "COM8Q" connector to add wlan...
Oh OK interesting.
> http://www.svtronics.com/EVM/OMAP5432/5432C
>
> http://www.svtronics.com/EVM/OMAP5432/COM8Q
>
> I'm not sure who to bug from that era, but the wlan populated devices
> might have been prototype only.
Hmm OK. Well as it's a SDIO card, it seems safe to add for now.
We may want to have a minimal separate dts file if the wiring is
different with the COM8Q card.
Regards,
Tony
next prev parent reply other threads:[~2015-09-18 16:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 16:29 [PATCH 0/2] Fix omap5-uevm WLAN regressions Tony Lindgren
2015-09-18 16:29 ` [PATCH 1/2] mfd: twl6040: Fix deferred probe handling for clk32k Tony Lindgren
2015-09-18 16:40 ` Felipe Balbi
2015-09-19 9:57 ` Lee Jones
2015-09-21 9:55 ` Peter Ujfalusi
2015-09-21 13:59 ` Tony Lindgren
2015-09-18 16:29 ` [PATCH 2/2] ARM: dts: Fix WLAN regression on omap5-uevm Tony Lindgren
2015-09-18 16:40 ` Robert Nelson
2015-09-18 16:51 ` Tony Lindgren [this message]
2015-09-18 17:22 ` Tony Lindgren
2015-09-18 18:39 ` Robert Nelson
2015-09-19 21:12 ` Grazvydas Ignotas
2015-09-19 22:52 ` Tony Lindgren
2015-09-18 17:35 ` Javier Martinez Canillas
2015-09-18 17:48 ` Tony Lindgren
2015-09-18 20:27 ` Tony Lindgren
2015-09-18 20:35 ` Tony Lindgren
2015-09-21 9:13 ` Javier Martinez Canillas
2015-09-21 14:10 ` Tony Lindgren
2015-09-23 21:06 ` 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=20150918165109.GB8020@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=hns@goldelico.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=robertcnelson@gmail.com \
--cc=sourav.poddar@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 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).