From: yong.shen@linaro.org (Yong Shen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq for freescale mx51
Date: Thu, 7 Oct 2010 12:10:35 +0800 [thread overview]
Message-ID: <AANLkTikD4J_T+wiikvhMWEEECNiWN3Ri_yJM0_SX++p7@mail.gmail.com> (raw)
In-Reply-To: <201010061315.58771.arnd@arndb.de>
> I still disagree, but it's not important. IMHO most of the uses of
> __raw_readl should be converted to readl or readl_relaxed if you are
> worried about efficiency.
>
> The main difference between __raw_readl and readl_relaxed is that the
> endianess is well-defined on readl_relaxed.
>
> Arnd
>
I agree with you about that. I will keep that in mind and also notice my
colleages this in our future development.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101007/133e8673/attachment-0001.html>
next prev parent reply other threads:[~2010-10-07 4:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 11:58 mx51 cpufreq driver yong.shen at linaro.org
2010-10-05 11:58 ` [PATCH] cpufreq for freescale mx51 yong.shen at linaro.org
2010-10-05 12:25 ` Arnd Bergmann
2010-10-06 5:38 ` Yong Shen
2010-10-06 11:15 ` Arnd Bergmann
2010-10-07 4:10 ` Yong Shen [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-07 5:36 mx51 cpufreq driver yong.shen at linaro.org
2010-10-07 5:36 ` [PATCH] cpufreq for freescale mx51 yong.shen at linaro.org
2010-10-07 8:03 ` Amit Kucheria
2010-10-07 11:33 ` Yong Shen
2010-10-07 11:45 ` Amit Kucheria
[not found] <1285738417-1638-1-git-send-email-yong.shen@linaro.org>
2010-09-30 10:48 ` Amit Kucheria
2010-10-01 4:06 ` Yong Shen
2010-10-04 7:43 ` Amit Kucheria
2010-10-06 9:51 ` Sascha Hauer
2010-10-07 3:36 ` Yong Shen
2010-10-07 7:30 ` Sascha Hauer
2010-10-07 12:00 ` Yong Shen
2010-10-07 7:40 ` Amit Kucheria
2010-10-07 7:50 ` Sascha Hauer
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=AANLkTikD4J_T+wiikvhMWEEECNiWN3Ri_yJM0_SX++p7@mail.gmail.com \
--to=yong.shen@linaro.org \
--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).