From: "yi li" <liyi.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: More on "SD-over-SPI with shared SPI bus"
Date: Fri, 10 Oct 2008 14:08:27 +0800 [thread overview]
Message-ID: <a0e7fce50810092308w16d20017y1bb3ba810b6bc01e@mail.gmail.com> (raw)
Hi Erwin,
You mentioned in your previous mail on August that, you have a patch
to make mmc_spi
share bus with other SPI devices. This is the latest mail I can find
on this topic.
>
> I have done this in a slightly different, rather simple way. I have
> added a new "transfer_end" callback function pointer to the spi_transfer
> structure. This function can have three return values:
>
> <0 ... stop spi message after the transfer
> 0 ... continue with next transfer
> 1 ... repeat current transfer
>
> If the transfer_end callback is not required, the function pointer must
> be set to NULL.
>
> I have modified the bitbang driver for this new functionality. In
> addition, the mmc_spi driver has been changed to make use of the
> callback function. It is necessary to pack all transfers that must be
> done without being interrupted into a single message. I have done a lot
> of testing with a SD card on a shared bus with a lot of other activity,
> and I couldn't see any problems.
I am wondering whether this patch has been finished? Is it possible to
release the patch for testing?
I am planning to implement similar thing, but I hope to base my work
on your patch.
Best Regards,
-Yi
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
reply other threads:[~2008-10-10 6:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a0e7fce50810092308w16d20017y1bb3ba810b6bc01e@mail.gmail.com \
--to=liyi.dev-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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;
as well as URLs for NNTP newsgroup(s).