From: Stephen Boyd <sboyd@codeaurora.org>
To: Paul Osmialowski <newchief@king.net.pl>
Cc: Michael Turquette <mturquette@baylibre.com>,
Russell King <linux@arm.linux.org.uk>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Osmialowski <pawelo@king.net.pl>
Subject: Re: [PATCH 0/1] add devm_of_clk_get() and devm_of_clk_get_by_name() functions
Date: Mon, 28 Sep 2015 16:05:23 -0700 [thread overview]
Message-ID: <20150928230523.GR23081@codeaurora.org> (raw)
In-Reply-To: <1443081808-19688-1-git-send-email-newchief@king.net.pl>
On 09/24, Paul Osmialowski wrote:
> From: Paul Osmialowski <pawelo@king.net.pl>
>
> While working on my pinctrl driver I've found lack of devres compatible
> equivalent for of_clk_get() function. I'd like to use it for the following
> (incomplete) piece of device tree configuration:
>
> pinctrl: pinctrl {
> compatible = "fsl,kinetis-pinctrl";
> #address-cells = <1>;
> #size-cells = <1>;
> ranges;
>
> port_a@40049000 {
> compatible = "fsl,kinetis-pin-bank";
> reg = <0x40049000 0x1000>;
> clocks = <&sim SIM_CLK_SCGC5_PORTA>;
> };
>
> port_b@4004a000 {
> compatible = "fsl,kinetis-pin-bank";
> reg = <0x4004a000 0x1000>;
> clocks = <&sim SIM_CLK_SCGC5_PORTB>;
> };
> ...
> };
>
> In my pinconf-generic compatible fsl,kinetis-pinctrl driver, I'm iterating
> over fsl,kinetis-pin-bank nodes using for_each_child_of_node(dev->of_node,
> child) along with of_match_node() in order to grab resources (I/O base
> address, clock gate).
>
> Normally, I'd have to use of_clk_get() on each pin bank device_node and
> then worry about proper resource release myself.
>
I'd say your binding is wrong. Either the container node
"pinctrl" is a software concept that contains the two devices for
port_a and port_b or there's only one pinctrl device that happens
to span some number of 0x1000 size banks. The former would be
written as so
pinctrl {
compatible = "fsl,kenetis-pinctrl";
reg = <0x40049000 0x2000>;
clocks = <&sim SIM_CLK_SCGC5_PORTA>, <&sim SIM_CLK_SCGC5_PORTB>;
};
and the latter would drop the container node and have two nodes
that probed the same driver instance twice.
port_a@40049000 {
compatible = "fsl,kinetis-pin-bank";
reg = <0x40049000 0x1000>;
clocks = <&sim SIM_CLK_SCGC5_PORTA>;
};
port_b@4004a000 {
compatible = "fsl,kinetis-pin-bank";
reg = <0x4004a000 0x1000>;
clocks = <&sim SIM_CLK_SCGC5_PORTB>;
};
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-09-28 23:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 8:03 [PATCH 0/1] add devm_of_clk_get() and devm_of_clk_get_by_name() functions Paul Osmialowski
2015-09-24 8:03 ` [PATCH 1/1] clk: " Paul Osmialowski
2015-09-28 23:13 ` Stephen Boyd
2015-09-28 23:05 ` Stephen Boyd [this message]
2015-09-29 4:45 ` [PATCH 0/1] " Paul Osmialowski
2015-09-30 22:04 ` Stephen Boyd
2015-10-01 7:52 ` Paul Osmialowski
2015-10-01 18:03 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2015-09-30 7:46 Paul Osmialowski
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=20150928230523.GR23081@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@baylibre.com \
--cc=newchief@king.net.pl \
--cc=pawelo@king.net.pl \
/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).