From: Alban <albeu@free.fr>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: Aban Bedel <albeu@free.fr>,
linux-mips@linux-mips.org,
Yegor Yefremov <yegorslists@googlemail.com>,
Gabor Juhos <juhosg@openwrt.org>,
devicetree@vger.kernel.org
Subject: Re: [RFC 1/4] WIP: MIPS: ath79: make ar933x clks more devicetree-friendly
Date: Thu, 21 Jan 2016 09:12:17 +0100 [thread overview]
Message-ID: <20160121091217.379b6239@tock> (raw)
In-Reply-To: <20160121031215.250b826347fd9c179b031288@gmail.com>
On Thu, 21 Jan 2016 03:12:15 +0300
Antony Pavlov <antonynpavlov@gmail.com> wrote:
> On Mon, 18 Jan 2016 20:57:25 +0100
> Alban <albeu@free.fr> wrote:
>
> > On Mon, 18 Jan 2016 02:56:24 +0300
> > Antony Pavlov <antonynpavlov@gmail.com> wrote:
> >
> > > At the moment ar933x of-enabled drivers use use clock names
> > > (e.g. "uart" or "ahb") to get clk descriptor.
> > > On the other hand
> > > Documentation/devicetree/bindings/clock/clock-bindings.txt states
> > > that the 'clocks' property is required for passing clk to clock
> > > consumers.
> >
> > This patch is not need, you should set the clock-names property in
> > the relevant device nodes instead.
>
> This patch is needed for AR9331!
>
> In ar933x_clocks_init() we have
>
> ath79_add_sys_clkdev("ref", ref_rate);
> clks[0] = ath79_add_sys_clkdev("cpu", cpu_rate);
> clks[1] = ath79_add_sys_clkdev("ddr", ddr_rate);
> clks[2] = ath79_add_sys_clkdev("ahb", ahb_rate);
>
> clk_add_alias("wdt", NULL, "ahb", NULL);
> clk_add_alias("uart", NULL, "ref", NULL);
>
> "uart" is an alias for "ref". But "ref" is not visible via device tree!
>
> I see this error message on ar933x-uart start:
>
> ERROR: could not get clock /ahb/apb/uart@18020000:uart(0)
The ref clock should be defined in the board DTS, I now see that it is
missing in yours. What you need to do is to define the clock-names
property in the Soc DTS, that allow the names lookup to work. Then in
the board DTS you can define the clock property to connect it to the
proper parent.
I'm also working on supporting the QCA9558 and the clock tree is similar.
See https://github.com/AlbanBedel/linux/commit/d6c8f8adfce08972c6
as example.
Alban
next prev parent reply other threads:[~2016-01-21 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1453074987-3356-1-git-send-email-antonynpavlov@gmail.com>
[not found] ` <1453074987-3356-1-git-send-email-antonynpavlov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-17 23:56 ` [RFC 1/4] WIP: MIPS: ath79: make ar933x clks more devicetree-friendly Antony Pavlov
[not found] ` <1453074987-3356-2-git-send-email-antonynpavlov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-18 19:57 ` Alban
2016-01-21 0:12 ` Antony Pavlov
2016-01-21 8:12 ` Alban [this message]
2016-01-21 10:17 ` Antony Pavlov
[not found] ` <20160121131711.a7315d3ca6233e50ec824544-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-21 11:03 ` Alban
2016-01-17 23:56 ` [RFC 2/4] MIPS: dts: qca: introduces AR9331 devicetree Antony Pavlov
2016-01-17 23:56 ` [RFC 3/4] MIPS: ath79: add initial support for TP-LINK MR3020 Antony Pavlov
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=20160121091217.379b6239@tock \
--to=albeu@free.fr \
--cc=antonynpavlov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=juhosg@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=yegorslists@googlemail.com \
/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).