From: Chris Ball <cjb@laptop.org>
To: zhangfei gao <zhangfei.gao@gmail.com>
Cc: linux-mmc@vger.kernel.org, Eric Miao <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>
Subject: Re: [PATCH v2 1/1]sdhci-pxa: support tune_timming for various cards
Date: Sun, 5 Dec 2010 03:30:36 +0000 [thread overview]
Message-ID: <20101205033035.GC24000@void.printf.net> (raw)
In-Reply-To: <AANLkTi=h1p98z542H=EzFaqnHmEDkQDPZ5QmCQGo4Cik@mail.gmail.com>
Hi Zhangfei,
On Thu, Nov 11, 2010 at 08:19:12AM -0500, zhangfei gao wrote:
> Hi, Chirs & Eric
>
> Thanks for review, here is updated version.
> 1. After clk_gating is enabled, set_clock will transfer clock=0, so
> clk_disable will be called, currently set_clock will never transfer
> clock=0.
> Later tune_timing only occurs once clock is started, currently it will
> happen when clock is changed.
There are still some review comments that haven't been replied to yet:
* Eric asked whether you really need to tune on every clock change, or
if once at initialization time would be enough.
* I asked why we shouldn't just inline tune_timing() at its callsite,
since it's a void function that's only called from one place.
* Philip points out that SD_CLOCK_AND_BURST_SIZE_SETUP is an MMP2-only
register and should be marked as such, and I agree. Even *if*
sdhci-pxa wasn't going to support non-MMP2 SoCs¹, you should still
mark hardware-specific registers with the hardware they're used on.
Speaking generally, please always reply to review comments -- even if
it's just to explain why you considered a suggested change and aren't
going to make it.
Thanks,
- Chris.
¹: (.. which doesn't seem to be the case, since you've since posted a
patchset that generalizes the driver.)
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2010-12-05 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 13:19 [PATCH v2 1/1]sdhci-pxa: support tune_timming for various cards zhangfei gao
2010-11-16 5:52 ` Haojian Zhuang
2010-12-05 3:30 ` Chris Ball [this message]
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=20101205033035.GC24000@void.printf.net \
--to=cjb@laptop.org \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=zhangfei.gao@gmail.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