From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: Jonas Jensen <jonas.jensen@gmail.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<arm@kernel.org>, <linux@arm.linux.org.uk>, <arnd@arndb.de>,
<olof@lixom.net>, <peter.crosthwaite@xilinx.com>,
<linux@roeck-us.net>
Subject: Re: [PATCH v6 0/2] ARM: mach-moxart: add MOXA ART SoC support
Date: Wed, 18 Dec 2013 09:26:10 -0800 [thread overview]
Message-ID: <0e3d482f-0b7c-4654-bb75-d6aa3e209fd7@CH1EHSMHS008.ehs.local> (raw)
In-Reply-To: <1387371526-15309-1-git-send-email-jonas.jensen@gmail.com>
Hi Jonas,
On Wed, Dec 18, 2013 at 01:58:44PM +0100, Jonas Jensen wrote:
> Thanks for the replies!
>
> This should tick the boxes on feedback except for one detail
> on the fixed rate clock:
>
> Moving fixed-clock "ref12" from .dtsi to .dts proved problematic
> for other clocks, this is why ref12 is still in SoC.
>
> My assertion is that "fixed-clock" clocks are probed later when
> placed in .dts (see diff and boot log below).
> of_clk_get() from clk_pll in .dtsi fails, i.e. fixed-clock ref12
> is not added as a provider in time before clk_pll loads.
I haven't looked into the details, but is of_clk_get_parent_name() an
alternative? That function does purely rely on DT data to obtain a name
of a clock which may enable to register your PLL? Then probing oder
wouldn't matter anymore.
Sören
next prev parent reply other threads:[~2013-12-18 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 12:58 Jonas Jensen
2013-12-18 12:58 ` [PATCH v6 1/2] ARM: mach-moxart: add MOXA ART SoC platform files Jonas Jensen
2013-12-18 12:58 ` [PATCH v6 2/2] ARM: mach-moxart: add MOXA ART SoC device tree files Jonas Jensen
2013-12-18 23:41 ` Peter Crosthwaite
2013-12-19 10:58 ` Jonas Jensen
2013-12-18 17:26 ` Sören Brinkmann [this message]
2013-12-22 19:56 ` [PATCH v6 0/2] ARM: mach-moxart: add MOXA ART SoC support Olof Johansson
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=0e3d482f-0b7c-4654-bb75-d6aa3e209fd7@CH1EHSMHS008.ehs.local \
--to=soren.brinkmann@xilinx.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=jonas.jensen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@roeck-us.net \
--cc=olof@lixom.net \
--cc=peter.crosthwaite@xilinx.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
all inboxes | Powered by JetHome®