mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: "Kumar, Purushotam" <purushotam@ti.com>
Cc: "davinci-linux-open-source@linux.davincidsp.com" 
	<davinci-linux-open-source@linux.davincidsp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] DaVinci: MMC: V4: MMC/SD controller driver for DaVinci family.
Date: Tue, 28 Apr 2009 21:45:31 +0200	[thread overview]
Message-ID: <20090428214531.23950257@mjolnir.ossman.eu> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301CCA0190F@dbde02.ent.ti.com>

On Fri, 17 Apr 2009 16:34:22 +0530
"Kumar, Purushotam" <purushotam@ti.com> wrote:

> > > +
> > > +	if (mmc_freq > mmc_req_freq)
> > > +		mmc_push_pull = mmc_push_pull + 1;
> > 
> > The naming of the divider is a bit confusing here. :)
> 
> I am thinking to change " mmc_push_pull" to " mmc_push_pull_divider". Please suggest other appropriate name.
> 

Or just "divider". The rest should be clear from the context.

> > > +	if (ios->bus_mode == MMC_BUSMODE_OPENDRAIN) {
> > > +		u32 temp;
> > > +
> > > +		/* Ignoring the init clock value passed for fixing the inter
> > > +		 * operability with different cards.
> > > +		 */
> > > +		open_drain_freq = ((unsigned int)cpu_arm_clk
> > > +				/ (2 * MMCSD_INIT_CLOCK)) - 1;
> > > +
> > > +		if (open_drain_freq > 0xFF)
> > > +			open_drain_freq = 0xFF;
> > > +
> > > +		temp = readl(host->base + DAVINCI_MMCCLK) & ~MMCCLK_CLKRT_MASK;
> > > +		temp |= open_drain_freq;
> > > +		writel(temp, host->base + DAVINCI_MMCCLK);
> > > +
> > > +		/* Convert ns to clock cycles */
> > > +		ns_in_one_cycle = (1000000) / (MMCSD_INIT_CLOCK/1000);
> > 
> > I'm still not sure why you need this. Open drain mode is always used at
> > a low frequency anyway.
> 
> 
> If my understanding is correct you are suggesting that at lower freq. there is no need to update the timeout parameter and can use the default value of ns_in_one_cycle.
> 
> The mmc_davinci_prepare_data() may  be called even during open drain frequency mode and here we are calculating the timeout value and updating the timeout reg. So ns_in_one_cycle should hold a proper value once we call mmc_davinci_prepare_data(). I think there is no harm in having this calculation here.
> 

I see. I thought this was some fiddling to override the core's decision
on clock frequency.

Why do you need to calculate the timeout differently based on
push-pull/open drain mode though?

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org
  TigerVNC, core developer          http://www.tigervnc.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

      parent reply	other threads:[~2009-04-28 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02  9:56 Purushotam Kumar
2009-04-10 19:41 ` Pierre Ossman
2009-04-17 11:04   ` Kumar, Purushotam
2009-04-17 19:38     ` David Brownell
2009-04-21 14:14       ` Kumar, Purushotam
2009-04-28 19:45     ` Pierre Ossman [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=20090428214531.23950257@mjolnir.ossman.eu \
    --to=drzeus-mmc@drzeus.cx \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=purushotam@ti.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

all inboxes | Powered by JetHome®