From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: prima2: enable dt-binding clkdev mapping
Date: Tue, 15 Jan 2013 16:32:39 -0800 [thread overview]
Message-ID: <20130116003239.8920.65687@quantum> (raw)
In-Reply-To: <CAGsJ_4wMsFk2EKuXtH5=+PJUSJrcg-tPJFU2bvbYvH_J8BEHJQ@mail.gmail.com>
Quoting Barry Song (2013-01-14 17:43:45)
> Hi Mike,
>
> 2013/1/15 Mike Turquette <mturquette@linaro.org>:
> > Quoting Barry Song (2012-12-20 00:51:31)
> >> From: Barry Song <Baohua.Song@csr.com>
> >>
> >> this patche deletes hard code that registers clkdev by things like:
> >> clk_register_clkdev(clk, NULL, "b0030000.nand");
> >> clk_register_clkdev(clk, NULL, "b0040000.audio");
> >> clk_register_clkdev(clk, NULL, "b0080000.usp");
> >> prima2 clock controller becomes a clock provider and every dt node
> >> just declares its clock sources by dt prop.
> >>
> >> it also makes us easier to extend this driver to support both prima2
> >> and marco as marco has different address mapping with prima2.
> >>
> >> Signed-off-by: Barry Song <Baohua.Song@csr.com>
> >
> > Barry,
> >
> > The changes to clk-prima2.c look OK to me. Did you want me to take this
> > patch through clk-next?
>
> yes. since it has no conflict with what i am handling in my machine codes.
>
Taken into clk-next.
Thanks,
Mike
> >
> > Thanks,
> > Mike
> >
> >> ---
> >> .../devicetree/bindings/clock/prima2-clock.txt | 73 +++++++
> >> arch/arm/boot/dts/prima2.dtsi | 31 +++-
> >> drivers/clk/clk-prima2.c | 205 ++++++++------------
> >> 3 files changed, 183 insertions(+), 126 deletions(-)
> >> create mode 100644 Documentation/devicetree/bindings/clock/prima2-clock.txt
>
> -barry
prev parent reply other threads:[~2013-01-16 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 8:51 [PATCH] clk: prima2: enable dt-binding clkdev mapping Barry Song
2013-01-14 21:52 ` Mike Turquette
2013-01-15 1:43 ` Barry Song
2013-01-16 0:32 ` Mike Turquette [this message]
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=20130116003239.8920.65687@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).