From: Subhash Jadavani <subhashj@codeaurora.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Vinit Shenoy <vinit.shenoy@st.com>,
cjb@laptop.org, viresh.kumar@linaro.org,
linux-mmc@vger.kernel.org, spear-devel@list.st.com
Subject: Re: [PATCH 1/1] mmc: debugfs: Set frequency to maximum possible on higher request
Date: Mon, 03 Sep 2012 18:05:52 +0530 [thread overview]
Message-ID: <5044A428.6040907@codeaurora.org> (raw)
In-Reply-To: <CAHp75Ves-htU9bPtsXjum9KWADADenM+oZHeBHHUCDhDBOyf=g@mail.gmail.com>
On 9/3/2012 6:00 PM, Andy Shevchenko wrote:
> On Mon, Sep 3, 2012 at 2:50 PM, Subhash Jadavani
> <subhashj@codeaurora.org> wrote:
>> As such this is ok if you want this behaviour. But i see other issue which
>> is not related to your patch.
>> Let's say if the host supports 400KHz, 25 MHz, 50MHz, 100MHz and currently
>> card is operating in HS (High Speed) mode@50MHz. and now if someone tries to
>> change the frequency to 100MHz, then we should just don't let the clock
>> change to 100MHz before we put the card in appropriate bus speed mode (in SD
>> cards case, it would be SDR50 and eMMC case it would be HS200). Although
>> this is anyway not an issue created by your patch but this is just to let
>> you know that frequency can't be changed indepently without informing the
>> card beforehand.
> That's why the file is located under debugfs. There is an assumption
> that developer understands
> what he or she is doing by changing this parameter.
Agreed. Thanks.
>
>
>
prev parent reply other threads:[~2012-09-03 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 11:08 [PATCH 1/1] mmc: debugfs: Set frequency to maximum possible on higher request Vinit Shenoy
2012-09-03 11:36 ` Andy Shevchenko
2012-09-03 11:50 ` Subhash Jadavani
2012-09-03 12:30 ` Andy Shevchenko
2012-09-03 12:35 ` Subhash Jadavani [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=5044A428.6040907@codeaurora.org \
--to=subhashj@codeaurora.org \
--cc=andy.shevchenko@gmail.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=spear-devel@list.st.com \
--cc=vinit.shenoy@st.com \
--cc=viresh.kumar@linaro.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).