public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: smohideen@mx2.labs.rootshell.ws
To: Ben Dooks <ben-linux@fluff.org>
Cc: sdhci-devel@list.drzeus.cx, linux-kernel@vger.kernel.org,
	drzeus-sdhci@drzeus.cx
Subject: Re: [patch 1/8] SDHCI: Add timeout hooks
Date: Tue, 2 Dec 2008 22:16:50 +0530	[thread overview]
Message-ID: <20081202164650.GA6414@debian> (raw)
In-Reply-To: <20081202154112.009165156@fluff.org.uk>

On Tue, Dec 02, 2008 at 03:40:19PM +0000, Ben Dooks wrote:
> Some controllers do not provide clock information in their
> capabilities (in the Samsung case, it is because there are
> multiple clock sources available to the controller). Add hooks
> to allow the system to supply clock information.
> 
> Signed-off-by: Ben Dooks <ben-linux@fluff.org>
> 
> Index: linux.git/drivers/mmc/host/sdhci.c
> ===================================================================
> --- linux.git.orig/drivers/mmc/host/sdhci.c	2008-12-01 19:11:54.000000000 +0000
> +++ linux.git/drivers/mmc/host/sdhci.c	2008-12-01 19:24:14.000000000 +0000
> @@ -1606,18 +1606,26 @@ int sdhci_add_host(struct sdhci_host *ho
>  
>  	host->max_clk =
>  		(caps & SDHCI_CLOCK_BASE_MASK) >> SDHCI_CLOCK_BASE_SHIFT;
> +	host->max_clk *= 1000000;
>  	if (host->max_clk == 0) {
> -		printk(KERN_ERR "%s: Hardware doesn't specify base clock "
> -			"frequency.\n", mmc_hostname(mmc));
> +		if (host->ops->get_max_clock)
> +			host->max_clk = host->ops->get_max_clock(host);
> +		else
> +			printk(KERN_ERR
> +			       "%s: Hardware doesn't specify base clock "
> +			       "frequency.\n", mmc_hostname(mmc));
>  		return -ENODEV;
>  	}
> -	host->max_clk *= 1000000;
>  
>  	host->timeout_clk =
>  		(caps & SDHCI_TIMEOUT_CLK_MASK) >> SDHCI_TIMEOUT_CLK_SHIFT;
>  	if (host->timeout_clk == 0) {
> -		printk(KERN_ERR "%s: Hardware doesn't specify timeout clock "
> -			"frequency.\n", mmc_hostname(mmc));
> +		if (host->ops->get_timeout_clock)
> +			host->timeout_clk = host->ops->get_timeout_clock(host);
> +		else
> +			printk(KERN_ERR
> +			       "%s: Hardware doesn't specify timeout clock "
> +			       "frequency.\n", mmc_hostname(mmc));
>  		return -ENODEV;
>  	}
>  	if (caps & SDHCI_TIMEOUT_CLK_UNIT)
> Index: linux.git/drivers/mmc/host/sdhci.h
> ===================================================================
> --- linux.git.orig/drivers/mmc/host/sdhci.h	2008-12-01 19:11:54.000000000 +0000
> +++ linux.git/drivers/mmc/host/sdhci.h	2008-12-01 19:17:55.000000000 +0000
> @@ -267,6 +267,8 @@ struct sdhci_host {
>  
>  struct sdhci_ops {
>  	int		(*enable_dma)(struct sdhci_host *host);
> +	unsigned int	(*get_max_clock)(struct sdhci_host *host);
> +	unsigned int	(*get_timeout_clock)(struct sdhci_host *host);
>  };
>  

	Can we cache the multiple dereferences. Here host->ops can be
	saved to a local, instead of multiple dereference several time.

	

  reply	other threads:[~2008-12-02 16:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 15:40 [patch 0/8] Update Samsung SDHCI Ben Dooks
2008-12-02 15:40 ` [patch 1/8] SDHCI: Add timeout hooks Ben Dooks
2008-12-02 16:46   ` smohideen [this message]
2008-12-21 13:16     ` Pierre Ossman
2008-12-02 15:40 ` [patch 2/8] SDHCI: Print ADMA status and pointer on debug Ben Dooks
2008-12-02 15:40 ` [patch 3/8] SDHCI: Add set_ios hook Ben Dooks
2008-12-21 13:22   ` Pierre Ossman
2008-12-02 15:40 ` [patch 4/8] SDHCI: Add quirk for controller with no end-of-busy IRQ Ben Dooks
2008-12-02 15:40 ` [patch 5/8] SDHCI: Samsung SDHCI (HSMMC) driver Ben Dooks
2008-12-21 13:32   ` Pierre Ossman
2008-12-02 15:40 ` [patch 6/8] SDHCI: Check DMA for overruns at end of transfer Ben Dooks
2008-12-21 13:49   ` Pierre Ossman
2008-12-02 15:40 ` [patch 7/8] SDHCI: Add change_clock callback for glue drivers Ben Dooks
2008-12-21 14:07   ` Pierre Ossman
2008-12-02 15:40 ` [patch 8/8] SDHCI: Add maintainers entry for Samsung SoC Ben Dooks
2008-12-21 14:09   ` Pierre Ossman

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=20081202164650.GA6414@debian \
    --to=smohideen@mx2.labs.rootshell.ws \
    --cc=ben-linux@fluff.org \
    --cc=drzeus-sdhci@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdhci-devel@list.drzeus.cx \
    /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