From: jonas@microbit.se (Jonas Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: imx53 cspi clock problem
Date: Thu, 23 May 2013 10:08:59 +0200 [thread overview]
Message-ID: <519DCE9B.2060909@microbit.se> (raw)
In-Reply-To: <20130522164710.GE31135@pengutronix.de>
On 2013-05-22 18:47, Sascha Hauer wrote:
> On Wed, May 22, 2013 at 08:52:45AM +0200, Jonas Andersson wrote:
>> compatible = "fsl,imx53-cspi", "fsl,imx35-cspi";
>> reg = <0x63fc0000 0x4000>;
>> interrupts = <38>;
>> clocks = <&clks 55>, <&clks 0>;
> Unlike the eCSPI controller the CSPI controller seems to have only one
> clock. This should probably be
>
> clocks = <&clks 55>, <&clks 55>;
>
This works fine.
Is it the right solution to define both clocks to the same in all the
imx*.dtsi files? imx25.dtsi defines only one clock "ipg" so
spi_imx_probe() will probably fail.
Jonas
next prev parent reply other threads:[~2013-05-23 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 6:52 imx53 cspi clock problem Jonas Andersson
2013-05-22 16:47 ` Sascha Hauer
2013-05-23 8:08 ` Jonas Andersson [this message]
2013-05-23 8:33 ` Sascha Hauer
2013-05-23 8:44 ` Jonas Andersson
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=519DCE9B.2060909@microbit.se \
--to=jonas@microbit.se \
--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).