RE: [patch] split MMC_CAP_4_BIT_DATA


Hi,all

I'd like to say something about this issue.
Currently,the blackfin on chip SD host ONLY support 1-bit MMC while
support 1-bit/4-bit SD/SDIO.
And we want our driver to support both 1-bit MMC and 4-bit SD/SDIO.but
the current MMC driver framework
Only allow us to set one kind of bus width,either 1-bit or 4-bit.So in
order to meet our case,we need more flexible mechanism
To inform the upper commom driver to know our situation.

Cliff



-----Original Message-----
From: Bryan Wu [mailto:cooloney.lkml@xxxxxxxxx]
Sent: Wednesday, January 09, 2008 10:33 AM
To: Pierre Ossman; cliff.cai@xxxxxxxxxx
Cc: Mike Frysinger; linux-kernel@xxxxxxxxxxxxxxx
Subject: Re: [patch] split MMC_CAP_4_BIT_DATA

On Jan 9, 2008 4:49 AM, Pierre Ossman <drzeus-mmc@xxxxxxxxx> wrote:
On Tue, 8 Jan 2008 14:40:49 -0500
Mike Frysinger <vapier.adi@xxxxxxxxx> wrote:


i dont understand what's confusing. the Blackfin on chip host
controller only supports 1-bit MMC, but it supports 4-bit SD/SDIO.
this is a fact. while it may be a stupid decision, it is what it
is, and i need the framework made more flexible in order to get the
Blackfin driver merged cleanly. we do software for hardware, we
dont do hardware.

Well, since I've seen no _hardware_ differences between 4-bit MMC and
4-bit SD, "support" in this case must me "vendor will guarantee it
works". And that is not the kind of "support" that needs a distinction
in the code.

So, again, if you feel that there is a hardware difference between
4-bit MMC and 4-bit SD then please elaborate as it is my understanding
that they are identical.


As Mike said, the reason split this flag is because Blackfin on-chip
SDIO controller's limitation.
Cliff is working on it for a long time, so I dropped him in. Hope he can
clarify the confusing things.

Thanks
-Bryan Wu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [patch] split MMC_CAP_4_BIT_DATA
    ... And we want our driver to support both 1-bit MMC and 4-bit SD/SDIO.but ... Blackfin BF54x on-chip SDIO host controller is supposed to ...
    (Linux-Kernel)
  • Re: Block request processing for MMC/SD over SPI bus
    ... I began developing a driver for MMC access over SPI on the Analog Devices ... Blackfin DSPs, running uClinux this spring. ...
    (Linux-Kernel)
  • Re: [patch] split MMC_CAP_4_BIT_DATA
    ... And we want our driver to support both 1-bit MMC and 4-bit SD/SDIO.but ... So if you want this patch to go in you need to explain why there is a difference for the blackfin controller. ...
    (Linux-Kernel)
  • Re: MMCv4 support (8-bit support missing)
    ... myself which adds support for both MMC 4.0 and 4.2. ... support in the MMC core with small changes to do bus testing procedure ... > leave the controller handling part to the controller driver. ...
    (Linux-Kernel)
  • [PATCH -mm 4/4] Blackfin: on-chip Two Wire Interface I2C driver
    ... As GPIO based blackfin driver will be replaced by I2C-GPIO generic ... we just update this latest version of blackfin on-chip TWI I2C ... * GNU General Public License for more details. ...
    (Linux-Kernel)