From: "Madhusudhan" <madhu.cr@ti.com>
To: 'Tony Lindgren' <tony@atomide.com>
Cc: "'Gadiyar, Anand'" <gadiyar@ti.com>,
"'Stephen Schwarm, CSDP'" <w3eve@earthlink.net>,
linux-omap@vger.kernel.org
Subject: RE: simple sd card performance bug fix on OMAP
Date: Thu, 10 Jun 2010 10:31:07 -0500 [thread overview]
Message-ID: <005001cb08b1$f349ba40$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <20100610063621.GP32208@atomide.com>
> -----Original Message-----
> From: Tony Lindgren [mailto:tony@atomide.com]
> Sent: Thursday, June 10, 2010 1:36 AM
> To: Madhusudhan
> Cc: 'Gadiyar, Anand'; 'Stephen Schwarm, CSDP'; linux-omap@vger.kernel.org
> Subject: Re: simple sd card performance bug fix on OMAP
>
> * Madhusudhan <madhu.cr@ti.com> [100602 20:13]:
> >
> >
> > > -----Original Message-----
> > > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > > owner@vger.kernel.org] On Behalf Of Gadiyar, Anand
> > > Sent: Friday, May 28, 2010 2:55 PM
> > > To: Stephen Schwarm, CSDP; linux-omap@vger.kernel.org
> > > Subject: RE: simple sd card performance bug fix on OMAP
> > >
> > > Stephen Schwarm, CSDP wrote:
> > > >
> > > > I have not had time to make a formal patch for this but I thought it
> was
> > > > significant enough just to send it out. The problem is on omap
> systems
> > > > that use omap_hsmmc.c to run sd or mmc cards. If the system you are
> > > > using has an 8 wire interface, it will only use a one wire interface
> to
> > > > 4 wire cards (eg, sd class 4 and sd class 6).
> > > >
> > > > In the file driver/mmc/omap_hsmmc.c in the function
> omap_hsmmc_probe:
> > > > at about line 1739 change:
> > > >
> > > > if (mmc_slot(host).wires >= 8)
> > > > mmc->caps |= MMC_CAP_8_BIT_DATA;
> > > > else if (mmc_slot(host).wires >= 4)
> > > > mmc->caps |= MMC_CAP_4_BIT_DATA;
> > > >
> > > > to:
> > > >
> > > > if (mmc_slot(host).wires >= 8)
> > > > mmc->caps |= MMC_CAP_8_BIT_DATA;
> > > > if (mmc_slot(host).wires >= 4)
> > > > mmc->caps |= w;
> > > >
> > > > just delete the word "else". This sets the MMC_CAP_4_BIT_DATA bit
> on
> > > > interfaces that have 8 wire interfaces.
> > > >
> > > > We have seen a BIG performance improvement on our systems.
> > > >
> > >
> > > Thanks for reporting this.
> > >
> > > A similar patch was posted a while ago and is currently marked as
> > > "awaiting upstream", although it looks like it got lost again.
> > >
> > > <https://patchwork.kernel.org/patch/78713/>
> > >
> > A revised version of the same patch was posted.
> >
> > https://patchwork.kernel.org/patch/93519/
> >
> > Tony, Can you please push this?
>
> This needs to get merged via linux-mmc list.
>
Sure. We will repost it.
Regards,
Madhu
> Regards,
>
> Tony
prev parent reply other threads:[~2010-06-10 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 19:05 simple sd card performance bug fix on OMAP Stephen Schwarm, CSDP
2010-05-28 19:53 ` Madhusudhan
2010-05-28 19:54 ` Gadiyar, Anand
2010-06-02 17:18 ` Madhusudhan
2010-06-10 6:36 ` Tony Lindgren
2010-06-10 15:31 ` Madhusudhan [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='005001cb08b1$f349ba40$544ff780@am.dhcp.ti.com' \
--to=madhu.cr@ti.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=w3eve@earthlink.net \
/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).