public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: "Jennifer Li (TP)" <Jennifer.Li@o2micro.com>
Cc: linux-mmc@vger.kernel.org, Mario_Limonciello@Dell.com,
	Joseph_Yeh@Dell.com, Chris Van Hoof <vanhoof@canonical.com>,
	Rezwanul_Kabir@Dell.com,
	"Shirley Her (SC)" <shirley.her@o2micro.com>,
	"Rich Lin (TP)" <RichLin@o2micro.com>,
	"Samuel Guan(WH)" <samuel.guan@o2micro.com>,
	"Hardys Lv(WH)" <hardys.lv@o2micro.com>,
	"William Lian (TP)" <William.Lian@o2micro.com>
Subject: Re: FW: [PATCH 2.6.32]: Add new device IDs and registersforMULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) cards.
Date: Tue, 30 Nov 2010 04:51:03 +0000	[thread overview]
Message-ID: <20101130045103.GA3451@void.printf.net> (raw)
In-Reply-To: <FC57104DF444434A9D1D8A7B4EBB292308145108@HC-EXCHANGE.nt-fsrvr.o2micro.com>

Hi Jennifer,

On Mon, Nov 29, 2010 at 10:06:18AM +0800, Jennifer Li (TP) wrote:
> Hi Chris,
> 
> 1. We don't need disable ADMA on the 8120 device. For safety, we have
> prepared a device ID for device 8120. 
> 
> 2. 0x01 bit is a lock/unlock bit. The CAPABILITIES register could be
> opened by the 0x01 bit. If we set the 0x01, the CAPABILITIES register
> can be written. We have to set the 0x01 bit.

Perfect, thanks for the answers.  I've added a comment explaining the
unlock bit.

I've queued your patch for inclusion in the Linux 2.6.38 release now.
It'd be great if you could test the 2.6.38-rc1 kernel when it's released
(sometime around February) and check that everything's working on your
hardware.

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

      reply	other threads:[~2010-11-30  4:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22  7:46 FW: [PATCH 2.6.32]: Add new device IDs and registers forMULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) cards Jennifer Li (TP)
2010-11-27  4:59 ` Chris Ball
2010-11-29  2:06   ` FW: [PATCH 2.6.32]: Add new device IDs and registersforMULTIMEDIA " Jennifer Li (TP)
2010-11-30  4:51     ` Chris Ball [this message]

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=20101130045103.GA3451@void.printf.net \
    --to=cjb@laptop.org \
    --cc=Jennifer.Li@o2micro.com \
    --cc=Joseph_Yeh@Dell.com \
    --cc=Mario_Limonciello@Dell.com \
    --cc=Rezwanul_Kabir@Dell.com \
    --cc=RichLin@o2micro.com \
    --cc=William.Lian@o2micro.com \
    --cc=hardys.lv@o2micro.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=samuel.guan@o2micro.com \
    --cc=shirley.her@o2micro.com \
    --cc=vanhoof@canonical.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