Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] mach-mmp: Support for SD/MMC clock adjustment in brownstone
Date: Mon, 14 Feb 2011 15:46:01 +0000	[thread overview]
Message-ID: <20110214154601.GA31103@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <9C2307EC-8314-40D5-A33B-38834F0F4698@marvell.com>

On Sun, Feb 13, 2011 at 10:56:22PM -0800, Philip Rakity wrote:
> 
> Set timing for brownstone for SD/MMC cards to enable detection
> timing adjustments are needed when speed > 25MHz
> remove limitation on maximum speed of 25MHz
> 
> Signed-off-by: Philip Rakity <prakity@marvell.com>
> ---
>  arch/arm/mach-mmp/brownstone.c |   10 +++++++++-
>  1 files changed, 9 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/mach-mmp/brownstone.c b/arch/arm/mach-mmp/brownstone.c
> index 0e92fd7..35afe60 100644
> --- a/arch/arm/mach-mmp/brownstone.c
> +++ b/arch/arm/mach-mmp/brownstone.c
> @@ -178,14 +178,22 @@ static struct i2c_board_info brownstone_twsi1_info[] = {
>  };
>  
>  static struct sdhci_pxa_platdata mmp2_sdh_platdata_mmc0 = {
> -	.max_speed	= 25000000,
> +	.adjust_clocks	= 1,
> +	.clk_select	= 1,
> +	.clk_delay	= 31,
>  };
>  
>  static struct sdhci_pxa_platdata mmp2_sdh_platdata_mmc1 = {
> +	.adjust_clocks	= 1,
> +	.clk_select	= 1,
> +	.clk_delay	= 15,
>  	.flags		= PXA_FLAG_CARD_PERMANENT,
>  };
>  
>  static struct sdhci_pxa_platdata mmp2_sdh_platdata_mmc2 = {
> +	.adjust_clocks	= 1,
> +	.clk_select	= 1,
> +	.clk_delay	= 31,

You create the new fields in patch 1 and then add values to them in patch 2.
However, they remain unused, so it's impossible to see what the point of
creating them was.

  reply	other threads:[~2011-02-14 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14  6:56 [PATCH 2/2] mach-mmp: Support for SD/MMC clock adjustment in brownstone Philip Rakity
2011-02-14 15:46 ` Russell King - ARM Linux [this message]
2011-02-14 17:44   ` Philip Rakity

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=20110214154601.GA31103@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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