mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: JosephChan@via.com.tw
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de, ben-linux@fluff.org
Subject: Re: [Patch 1/1 v5] via-sdmmc: VIA MSP card reader driver support
Date: Fri, 10 Apr 2009 20:35:20 +0200	[thread overview]
Message-ID: <20090410203520.6e43acb2@mjolnir.ossman.eu> (raw)
In-Reply-To: <C80EF34A3D2E494DBAF9AC29C7AE4EB808EBD84A@exchtp03.taipei.via.com.tw>

On Wed, 1 Apr 2009 10:24:02 +0800
JosephChan@via.com.tw wrote:

> Hi all,
> 
> The following patch provides VIA MSP SD/MMC card reader driver support.
> This patch is based on 2.6.29 kernel.
> Thanks to Pierre's suggestions.
> Please feel free to contact me if any problem. Thanks in advanced.
> 
> In addition, the SPEC is available in VX800 Programming guide (Device 13 Function 0) on http://linux.via.com.tw
> 

Looking good. There's just a few minor things. See below.

> +
> +nodata:
> +	if (cmd->opcode == MMC_STOP_TRANSMISSION)
> +		cmdctrl |= VIA_CRDR_SDCTRL_STOP;
> +

I didn't check this part properly the last time. I'm assuming you're
telling the hardware that this is a command that terminates a data
transmission? If so, you cannot check the opcode like that. There might
be other stop commands.

What you need to do is to either pass another parameter to your
function when you're calling it with data->stop, or simply have a test
in there if cmd == data->stop (or mrq->stop, whichever is most
convenient).

> +
> +	if (ios->clock >= 40000000)
> +		clock = PCI_CLK_48M;
> +	else if (ios->clock >= 30000000)
> +		clock = PCI_CLK_33M;
> +	else if (ios->clock >= 20000000)
> +		clock = PCI_CLK_24M;
> +	else if (ios->clock >= 15000000)
> +		clock = PCI_CLK_16M;
> +	else if (ios->clock >= 10000000)
> +		clock = PCI_CLK_12M;
> +	else if (ios->clock >=  5000000)
> +		clock = PCI_CLK_8M;
> +	else
> +		clock = PCI_CLK_375K;
> +

This looks a bit strange. Why are you not comparing with the clock
frequency you'll be setting?

> +
> +	mmc->f_min = VIA_CRDR_MIN_CLOCK;
> +	mmc->f_max = VIA_CRDR_MAX_CLOCK;
> +	mmc->ocr_avail = MMC_VDD_32_33 | MMC_VDD_33_34 | MMC_VDD_165_195;
> +	mmc->caps = MMC_CAP_4_BIT_DATA;

You also need to set the bits stating if the controller supports the
high-speed SD and/or MMC mode, otherwise the core won't go over 25/20
MHz.

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.

  reply	other threads:[~2009-04-10 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01  2:24 JosephChan
2009-04-10 18:35 ` Pierre Ossman [this message]
2009-04-10 18:37   ` Pierre Ossman
2009-04-21 17:35   ` JosephChan
2009-04-28 19:49     ` Pierre Ossman
2009-05-25  3:09     ` Harald Welte

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=20090410203520.6e43acb2@mjolnir.ossman.eu \
    --to=drzeus-mmc@drzeus.cx \
    --cc=JosephChan@via.com.tw \
    --cc=arnd@arndb.de \
    --cc=ben-linux@fluff.org \
    --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

all inboxes | Powered by JetHome®