linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 6/8] wlcore: sdio: add wilink clock providers
Date: Tue, 30 Jul 2013 15:35:35 -0700	[thread overview]
Message-ID: <20130730223535.5270.39864@quantum> (raw)
In-Reply-To: <1375189476-21557-7-git-send-email-coelho@ti.com>

Quoting Luciano Coelho (2013-07-30 06:04:34)
> +static const struct of_device_id wlcore_sdio_of_clk_match_table[] = {
> +       { .compatible = "ti,wilink-clock" },
> +};
> +
>  static struct wl12xx_platform_data *wlcore_get_pdata_from_of(struct device *dev)
>  {
>         struct wl12xx_platform_data *pdata;
>         struct device_node *np = dev->of_node;
> +       struct device_node *clock_node;
>  
>         if (!np) {
>                 np = of_find_matching_node(NULL, dev->driver->of_match_table);
> @@ -241,6 +247,9 @@ static struct wl12xx_platform_data *wlcore_get_pdata_from_of(struct device *dev)
>                 goto out_free;
>         }
>  
> +       for_each_matching_node(clock_node, wlcore_sdio_of_clk_match_table)
> +               of_fixed_clk_setup(clock_node);

Hi Luciano,

Any reason for establishing your own compatible string if you just plan
to use the fixed rate clock? You could just use "fixed-clock" compatible
in your DTS.

I will be posting patches this week which makes the fixed-rate clock a
proper driver and matches that compatible string to instantiate those
clocks. That means that your driver could probably remove the clock
setup code completely.

Regards,
Mike

> +
>         goto out;
>  
>  out_free:
> -- 
> 1.8.3.2

  reply	other threads:[~2013-07-30 22:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 13:04 [PATCH v4 0/8] wilink: add device tree support Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 1/8] wl1251: split wl251 platform data to a separate structure Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 2/8] wlcore: set irq_flags in the board files instead of hiding behind a quirk Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 3/8] wlcore: remove pwr_in_suspend from platform data Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 4/8] wl12xx: use frequency instead of enumerations for pdata clocks Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 5/8] wlcore: add initial device tree support to the sdio module Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 6/8] wlcore: sdio: add wilink clock providers Luciano Coelho
2013-07-30 22:35   ` Mike Turquette [this message]
2013-07-30 23:04     ` Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 7/8] wlcore: sdio: get clocks from device tree Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 8/8] wlcore/wl12xx: check if we got correct clock data from DT Luciano Coelho
2014-02-28  7:26 ` [PATCH v4 0/8] wilink: add device tree support Yegor Yefremov
2014-02-28  9:22   ` Alexandre Belloni
2014-03-06 10:51     ` Yegor Yefremov
2014-02-28 12:29   ` Luca Coelho
2014-02-28 14:12     ` Luca Coelho

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=20130730223535.5270.39864@quantum \
    --to=mturquette@linaro.org \
    --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).