From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, Pierre Ossman <pierre@ossman.eu>,
devicetree-discuss@ozlabs.org, sdhci-devel@lists.ossman.eu
Subject: Re: [PATCH] sdhci: Add support for hosts that are only capable of 1-bit transfers
Date: Thu, 18 Jun 2009 00:13:29 +0400 [thread overview]
Message-ID: <20090617201329.GA9149@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <fa686aa40906130840lfb751a7xc9e24646c860a76d@mail.gmail.com>
On Sat, Jun 13, 2009 at 09:40:02AM -0600, Grant Likely wrote:
> On Thu, Jun 11, 2009 at 2:15 PM, Anton
> Vorontsov<avorontsov@ru.mvista.com> wrote:
> > Some hosts (hardware configurations, or particular SD/MMC slots) may
> > not support 4-bit bus. For example, on MPC8569E-MDS boards we can
> > switch between serial (1-bit only) and nibble (4-bit) modes, thought
> > we have to disable more peripherals to work in 4-bit mode.
> >
> > Along with some small core changes, this patch modifies sdhci-of
> > driver, so that now it looks for "mode" property in the device-tree.
> >
> > Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> > ---
> >
> > Pierre, I'm not sure if a quirk would be appropriate here. If so,
> > I can redo the patch with FORCE_1_BIT_DATA quirk.
> >
> > Thanks,
> >
> > Documentation/powerpc/dts-bindings/fsl/esdhc.txt | 2 ++
> > drivers/mmc/host/sdhci-of.c | 7 +++++++
> > drivers/mmc/host/sdhci-pci.c | 1 +
> > drivers/mmc/host/sdhci.c | 2 +-
> > 4 files changed, 11 insertions(+), 1 deletions(-)
> >
> > diff --git a/Documentation/powerpc/dts-bindings/fsl/esdhc.txt b/Documentation/powerpc/dts-bindings/fsl/esdhc.txt
> > index 5093ddf..298b865 100644
> > --- a/Documentation/powerpc/dts-bindings/fsl/esdhc.txt
> > +++ b/Documentation/powerpc/dts-bindings/fsl/esdhc.txt
> > @@ -10,6 +10,8 @@ Required properties:
> > - interrupts : should contain eSDHC interrupt.
> > - interrupt-parent : interrupt source phandle.
> > - clock-frequency : specifies eSDHC base clock frequency.
> > + - mode : specifies eSDHC mode, valid values are: "1-bit" and "4-bit".
> > + If mode is unspecified, then 4-bit mode is assumed.
>
> In light of Pierre's comment that 4-bit is mandatory and this is a
> deviation, perhaps it would be better to define an empty property to
> indicate that only 1-bit transfers work. Maybe something along the
> lines of "sdhc-1-bit-only"?
Yeah, since it turned up to be a quirk, we'd better use a named
property.
(I think that by convention we should use commas for
controller-specific properties, i.e. "sdhci,property".)
Thanks!
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-06-17 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 20:15 [PATCH] sdhci: Add support for hosts that are only capable of 1-bit transfers Anton Vorontsov
2009-06-13 11:05 ` Pierre Ossman
2009-06-13 15:40 ` Grant Likely
2009-06-17 20:13 ` Anton Vorontsov [this message]
2009-06-17 20:14 ` [PATCH v2] " Anton Vorontsov
2009-06-17 20:55 ` Grant Likely
2009-06-19 19:21 ` 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=20090617201329.GA9149@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=devicetree-discuss@ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=pierre@ossman.eu \
--cc=sdhci-devel@lists.ossman.eu \
/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).