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: Mon, 18 Jan 2016 20:57:25 +0100 [thread overview]
Message-ID: <20160118205725.0a16be8e@tock> (raw)
In-Reply-To: <1453074987-3356-2-git-send-email-antonynpavlov@gmail.com>
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.
Alban
next prev parent reply other threads:[~2016-01-18 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 23:56 [RFC 0/4] MIPS: ath79: introduce AR9331 devicetree support Antony Pavlov
2016-01-17 23:56 ` [RFC 1/4] WIP: MIPS: ath79: make ar933x clks more devicetree-friendly Antony Pavlov
2016-01-18 19:57 ` Alban [this message]
2016-01-21 0:12 ` Antony Pavlov
2016-01-21 8:12 ` Alban
2016-01-21 10:17 ` Antony Pavlov
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
2016-01-17 23:56 ` [RFC 4/4] WIP: MIPS: add tl-mr3020-dt-raw_defconfig 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=20160118205725.0a16be8e@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