linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eliad@wizery.com (Eliad Peller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 3/3] ARM: dts: igep00x0: add wl18xx bindings
Date: Tue, 10 Mar 2015 16:31:33 +0200	[thread overview]
Message-ID: <CAB3XZEftjwUGS_Kj2dCxYY1m82C+a1_=akbnG3_hLETCr+Dddg@mail.gmail.com> (raw)
In-Reply-To: <2223973.a64rBcZvaA@wuerfel>

On Tue, Mar 10, 2015 at 4:11 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Tuesday 10 March 2015 13:00:19 Eliad Peller wrote:
>> On Tue, Mar 10, 2015 at 12:49 AM, Tony Lindgren <tony@atomide.com> wrote:
>> >> > I was expecting you to remove all calls to legacy_init_wl12xx from this file,
>> >> > including the ones for wl12xx aside from the wl18xx ones you removed, but
>> >> > if that's enough to clean out the platform_data handling from the wlcore
>> >> > driver, it's good enough as a start.
>> >> not sure i'm following - can you elaborate?
>> >>
>> >> i'll summarize the way i see it. please correct me if i'm wrong.
>> >>
>> >> both wl18xx and wl12xx use the platform data to get the irq number.
>> >> wl12xx (only) also needs some additional clock definitions to be
>> >> passed. there's currently some issue with specifying some the of clock
>> >> sources, so i preferred starting only with (the simpler) wl18xx
>> >> bindings.
>> >>
>> >> for platforms with wl18xx, we can remove the pdata-quirk, as all the
>> >> data (i.e. irq) can be passed by the new DT bindings.
>> >> however, for platforms with wl12xx, we still need to pass the clock
>> >> definitions (along with the irq), so we have to keep
>> >> legacy_init_wl12xx for the time being (and that's also why we have to
>> >> currently keep the platform_data handling in the wlcore driver)
>> >>
>> >> do you have something else in mind?
>> >
>> > I think what Arnd is saying is we've now removed all the wl12xx using
>> > legacy platforms, so all of them can boot with just data from dts.
>
> Right, that was my idea.
>
>> I don't think that's the case (unless i'm missing something).
>> e.g. there's still pdata-quirk for "compulab,omap3-sbc-t3730" which
>> initializes wl12xx device.
>
> This one is just like the igep0030, as Tony was saying: the board
> boots from device tree already, so now that we have a binding for
> it, we can remove the wl12xx_set_platform_data() for it.
>
i think the wl12xx_set_platform_data() name created some confusion -
it is used to pass platform data for both wl12xx and wl18xx devices.
(this confusion is all around the wlcore driver as well, due to the
code evolution)

the binding i added is for wl18xx only (there is no wl12xx binding yet).
the remaining boards, AFAICT, have wl12xx (rather than wl18xx) cards.
so i don't see how we can remove these wl12xx_set_platform_data()
calls before we have wl12xx bindings in-place as well.

> Unfortunately, there is still one machine that uses a board file
> in combination with this wl12xx: da850-evm calls
> wl12xx_set_platform_data() from a legacy board file without DT.
>
ditto.

Eliad.

  parent reply	other threads:[~2015-03-10 14:31 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
2015-03-10 14:31             ` Eliad Peller [this message]
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='CAB3XZEftjwUGS_Kj2dCxYY1m82C+a1_=akbnG3_hLETCr+Dddg@mail.gmail.com' \
    --to=eliad@wizery.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).