From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Eliad Peller <eliad@wizery.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Sekhar Nori <nsekhar@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH v5 3/3] ARM: dts: igep00x0: add wl18xx bindings
Date: Tue, 10 Mar 2015 08:55:30 -0700 [thread overview]
Message-ID: <20150310155529.GP5264@atomide.com> (raw)
In-Reply-To: <2300824.dcEMS7aYJa@wuerfel>
* Arnd Bergmann <arnd@arndb.de> [150310 08:48]:
> On Tuesday 10 March 2015 07:28:05 Tony Lindgren wrote:
> >
> > Oops I forgot about the omap3-sbc-t3730, so yes we have to keep the
> > platform data a little bit longer. But nothing stopping us moving
> > all the other ones to use a proper device tree based configuration.
> >
>
> For all I can tell, the t3730 board file does not support wl12xx
> at the moment, only the dts file does.
Hmm strange, it seems to configure the wlan_rst pin. Maybe there
are variants with different WLAN module. But yeah, seems to be
unused.
That still leaves configuring all the dts users of the
pdata-quirks.c legacy_init_wl12xx() with proper dts before
removing it:
$ git grep legacy_init_wl12xx pdata-quirks.c
pdata-quirks.c:static void __init __used legacy_init_wl12xx(unsigned ref_clock,
pdata-quirks.c:static inline void legacy_init_wl12xx(unsigned ref_clock,
pdata-quirks.c: legacy_init_wl12xx(WL12XX_REFCLOCK_38, 0, 136);
pdata-quirks.c: legacy_init_wl12xx(0, 0, 177);
pdata-quirks.c: legacy_init_wl12xx(0, 0, 136);
pdata-quirks.c: legacy_init_wl12xx(WL12XX_REFCLOCK_38, 0, 149);
pdata-quirks.c: legacy_init_wl12xx(WL12XX_REFCLOCK_26, 0, 162);
pdata-quirks.c: legacy_init_wl12xx(WL12XX_REFCLOCK_38, 0, 145);
pdata-quirks.c: legacy_init_wl12xx(WL12XX_REFCLOCK_26,
pdata-quirks.c: legacy_init_wl12xx(WL12XX_REFCLOCK_38, 0, 53);
pdata-quirks.c: legacy_init_wl12xx(WL12XX_REFCLOCK_38, 0, 41);
pdata-quirks.c: legacy_init_wl12xx(WL12XX_REFCLOCK_38, 0, 31);
> If we do what Sekhar suggested and drop wl12xx support from
> the DA850 EVM board file, we can fix all wlcore users.
I guess Sekhar knows the da850 evm status the best. So up to
you guys if wl12xx is not being used on legacy da850.
Regards,
Tony
next prev parent reply other threads:[~2015-03-10 16:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 15:36 [PATCH v5 1/3] dt: bindings: add wl18xx wireless device Eliad Peller
2015-03-09 15:36 ` [PATCH v5 2/3] wl18xx: add basic device-tree support Eliad Peller
2015-03-09 19:47 ` Arnd Bergmann
2015-03-11 0:34 ` Javier Martinez Canillas
2015-03-11 9:51 ` Arnd Bergmann
2015-03-11 10:05 ` Javier Martinez Canillas
2015-03-11 10:32 ` Arnd Bergmann
2015-03-11 11:50 ` Eliad Peller
2015-03-09 15:36 ` [PATCH v5 3/3] ARM: dts: igep00x0: add wl18xx bindings Eliad Peller
2015-03-09 19:50 ` Arnd Bergmann
2015-03-09 21:03 ` Eliad Peller
2015-03-09 22:49 ` Tony Lindgren
2015-03-10 11:00 ` Eliad Peller
2015-03-10 14:11 ` Arnd Bergmann
2015-03-10 14:28 ` Tony Lindgren
2015-03-10 15:48 ` Arnd Bergmann
2015-03-10 15:55 ` Tony Lindgren [this message]
2015-03-10 14:31 ` Eliad Peller
2015-03-10 15:52 ` Arnd Bergmann
2015-03-10 16:11 ` Eliad Peller
2015-03-10 16:18 ` Tony Lindgren
2015-03-10 17:01 ` Eliad Peller
2015-03-10 17:35 ` Tony Lindgren
2015-03-10 19:49 ` Arnd Bergmann
2015-03-11 1:00 ` Javier Martinez Canillas
2015-03-11 9:53 ` Arnd Bergmann
2015-03-11 11:34 ` Javier Martinez Canillas
2015-03-11 12:12 ` Eliad Peller
2015-03-11 13:13 ` Arnd Bergmann
2015-03-11 12:40 ` Arnd Bergmann
2015-03-11 13:07 ` Javier Martinez Canillas
2015-03-11 13:17 ` Arnd Bergmann
2015-03-11 13:21 ` Javier Martinez Canillas
2015-03-11 13:38 ` Eliad Peller
2015-03-11 15:11 ` Tony Lindgren
2015-03-10 14:34 ` Sekhar Nori
2015-03-10 15:54 ` Arnd Bergmann
2015-03-11 0:28 ` Javier Martinez Canillas
2015-03-11 1:19 ` Javier Martinez Canillas
2015-03-11 11:59 ` Eliad Peller
2015-03-11 12:07 ` Javier Martinez Canillas
2015-03-11 11:54 ` Eliad Peller
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=20150310155529.GP5264@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=eliad@wizery.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nsekhar@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).