Hi Wolfgang,
On Sun, Oct 10, 2010 at 2:48 PM, Wolfgang Denk wd@denx.de wrote:
Dear Lei Wen,
In message AANLkTi=qBk7N+SdW_6K1=ywKM1ZKo5F-518Q7qceNXws@mail.gmail.com you wrote:
Although the common code is named as mmc.c, I think a lot of people use it to work for sd too, since they are compatible in most case.
Right. And where SD drivers differ, such differeng code should be provided by the SD drivers, and not pulled into the common code parts.
the driver cannot do nothing unless a mess change.
Please explain why that shouldnot be possible. It's the driver that accesses your hardware, so it has full control over everything going on.
You are right, certainly driver cuold make this, but this would bring a lot of complexity for it... As I mentioned in the last mail, the multi-write command semantic consist by multi-write command + stop transmission command.
Send what kind of command is the job of platform, and how to send the command is the job of driver. If I implement this seperation in the driver level, the driver must send another stop transmission command during each internal seperation, which is so ugly and error prone..
So this is why I intend to put the code in the platform level...
Best regards, Lei