linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver
Date: Fri, 19 Aug 2016 12:16:12 -0700	[thread overview]
Message-ID: <20160819191612.GU361@codeaurora.org> (raw)
In-Reply-To: <CAK7LNAQg-LcK-vsWVU-b0WsF=Y_NBNR_cWqNDJKyMqp7Svdvqg@mail.gmail.com>

On 08/20, Masahiro Yamada wrote:
> 2016-08-19 9:25 GMT+09:00 Stephen Boyd <sboyd@codeaurora.org>:
> >> +{
> >> +     struct device *dev = &pdev->dev;
> >> +     const struct of_device_id *match;
> >> +     struct clk_hw_onecell_data *hw_data;
> >> +     struct device_node *parent;
> >> +     struct regmap *regmap;
> >> +     const struct uniphier_clk_data *p;
> >> +     int clk_num = 0;
> >> +
> >> +     match = of_match_node(uniphier_clk_match, dev->of_node);
> >> +     if (!match)
> >> +             return -ENODEV;
> >
> > We can use of_driver_match_device() to make this simpler.
> 
> 
> I want to use the returned "match".
> The of_driver_match_device() just checks if it matches or not,
> so I do not think it can be the replacement.
> 
> I can use of_match_device() instead, if you like.

Sorry I meant of_device_get_match_data().

> 
> 
> 
> >> +
> >> +     parent = of_get_parent(dev->of_node); /* parent should be syscon node */
> >> +     regmap = syscon_node_to_regmap(parent);
> >> +     of_node_put(parent);
> >
> > devm_get_regmap(dev->parent) should work then? Why do we need to
> > use OF APIs?
> 
> "git grep devm_get_regmap" did not hit anything.
> 
> Where is it defined?
> 

Sorry I meant dev_get_regmap().

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-08-19 19:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  4:30 [PATCH v6 0/2] clk: uniphier: add clock drivers for UniPhier SoCs Masahiro Yamada
2016-08-02  4:30 ` [PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver Masahiro Yamada
2016-08-19  0:25   ` Stephen Boyd
2016-08-19 17:46     ` Masahiro Yamada
2016-08-19 19:16       ` Stephen Boyd [this message]
2016-08-29  2:21         ` Masahiro Yamada
2016-08-29 18:22           ` Stephen Boyd
2016-09-05  4:02             ` Masahiro Yamada
2016-09-07  0:32               ` Stephen Boyd
2016-09-16  7:41                 ` Masahiro Yamada
2016-08-02  4:30 ` [PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs Masahiro Yamada
2016-08-19  0:28   ` Stephen Boyd
2016-08-19 17:55     ` Masahiro Yamada
  -- strict thread matches above, loose matches on Subject: below --
2016-08-02  4:28 [PATCH v6 0/2] clk: uniphier: add clock drivers " Masahiro Yamada
2016-08-02  4:28 ` [PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver Masahiro Yamada

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=20160819191612.GU361@codeaurora.org \
    --to=sboyd@codeaurora.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).