From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 3.15.4 runs *significantly* slower than 3.15.3 on iMX233 CPU
Date: Mon, 07 Jul 2014 21:29:21 +0200 [thread overview]
Message-ID: <lpeseg$lip$1@ger.gmane.org> (raw)
In-Reply-To: <20140707191430.GA23004@roeck-us.net>
On 07/07/2014 09:14 PM, Guenter Roeck wrote:
> Are you sure this did not just happen when you booted the new kernel
> for the first time ? I have seen similar behavior with some distributions.
I did some more tries and found out that I had disabled some of my
patches until I reached 3.15.4 (latest version) where I decided to do
needed modifications to get my patches back in.
I tracked the problem down to the following patch:
diff --git a/arch/arm/boot/dts/imx23-olinuxino.dts
b/arch/arm/boot/dts/imx23-olinuxino.dts
index d107c4a..993da2e 100644
--- a/arch/arm/boot/dts/imx23-olinuxino.dts
+++ b/arch/arm/boot/dts/imx23-olinuxino.dts
@@ -64,7 +64,14 @@
compatible = "fsl,imx23-spi";
pinctrl-names = "default";
pinctrl-0 = <&spi2_pins_a>;
+ clock-frequency = <1000000>;
status = "okay";
+
+ spidev0: spidev@0 {
+ compatible = "spidev";
+ spi-max-frequency = <1000000>;
+ reg = <0>;
+ };
};
};
I need this to add spidev support. But I don't understand why this
change kills performance? Maybe the "high" value in "clock-frequency"?
Can someone give me some information on how to fix this?
Thank you very much in advance.
Greetings,
Manuel
next prev parent reply other threads:[~2014-07-07 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 18:21 3.15.4 runs *significantly* slower than 3.15.3 on iMX233 CPU Manuel Reimer
2014-07-07 19:14 ` Guenter Roeck
2014-07-07 19:29 ` Manuel Reimer [this message]
2014-07-07 19:42 ` Guenter Roeck
2014-07-07 19:55 ` Manuel Reimer
2014-07-07 20:37 ` Geert Uytterhoeven
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='lpeseg$lip$1@ger.gmane.org' \
--to=manuel.spam@nurfuerspam.de \
--cc=linux-kernel@vger.kernel.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