From: Chris Ball <cjb@laptop.org>
To: Barry Song <21cnbao@gmail.com>
Cc: linux-mmc@vger.kernel.org, Binghua.Duan@csr.com,
andreiw@motorola.com, prakity@marvell.com
Subject: Re: [PATCH] mmc:sdhci:add support to request/free pins for controllers sharing hardware bus
Date: Mon, 25 Apr 2011 23:48:37 -0400 [thread overview]
Message-ID: <m3d3k9u0yy.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <BANLkTinj4pnDG=cCJY3JGYGXOYoVPHtA9A@mail.gmail.com> (Barry Song's message of "Tue, 26 Apr 2011 11:34:20 +0800")
Hi Barry,
On Mon, Apr 25 2011, Barry Song wrote:
> From: Bin Shi <bin.shi@csr.com>
>
> some controllers share data bus or other pins between
> multi-controllers and need to switch the functions of shared pins
> runtime.
> this patch requested those shared pins before actual hardware access
> and release them after access
>
> Signed-off-by: Bin Shi <bin.shi@csr.com>
> Cc: Binghua Duan <binghua.duan@csr.com>
> Cc: Andrei Warkentin <andreiw@motorola.com>
> Cc: Philip Rakity <prakity@marvell.com>
> Signed-off-by: Barry Song <21cnbao@gmail.com>
* The patch is corrupt:
fatal: corrupt patch at line 11
You can check whether the patch is okay by first e-mailing it to
yourself and checking that git can apply it.
* Where is the patch that implements the get_shared_pins() hook in
your driver?
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-04-26 3:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5EB3BFCD089AD643B9BB63439F5FD5E9A127@SHAASIEXM01.ASIA.ROOT.PRI>
2011-04-26 3:34 ` [PATCH] mmc:sdhci:add support to request/free pins for controllers sharing hardware bus Barry Song
2011-04-26 3:48 ` Chris Ball [this message]
2011-04-26 3:50 ` Barry Song
2011-04-26 6:58 ` Wolfram Sang
2011-04-26 7:27 ` Barry Song
2011-04-26 13:00 ` Chris Ball
2011-04-26 15:28 ` Philip Rakity
2011-04-28 1:14 ` Barry Song
2011-04-28 1:16 ` Barry Song
2011-04-26 3:48 ` Philip Rakity
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=m3d3k9u0yy.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=21cnbao@gmail.com \
--cc=Binghua.Duan@csr.com \
--cc=andreiw@motorola.com \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.com \
/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