From: Chris Ball <cjb@laptop.org>
To: "Jennifer Li (TP)" <Jennifer.Li@o2micro.com>
Cc: linux-mmc@vger.kernel.org,
"Shirley Her (SC)" <shirley.her@o2micro.com>,
"Hardys Lv(WH)" <hardys.lv@o2micro.com>,
"Rich Lin (TP)" <RichLin@o2micro.com>,
"Samuel Guan(WH)" <samuel.guan@o2micro.com>,
Rezwanul_Kabir@Dell.com, Mario_Limonciello@Dell.com,
Joseph_Yeh@Dell.com, Chris Van Hoof <vanhoof@canonical.com>
Subject: Re: [PATCH 2.6.35]: Add new device IDs and registers for MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) cards.
Date: Tue, 9 Nov 2010 15:38:06 +0000 [thread overview]
Message-ID: <20101109153806.GC7977@void.printf.net> (raw)
In-Reply-To: <FC57104DF444434A9D1D8A7B4EBB292307BD1F6D@HC-EXCHANGE.nt-fsrvr.o2micro.com>
Hi Jennifer,
On Tue, Nov 09, 2010 at 02:28:00PM +0800, Jennifer Li (TP) wrote:
> Hi,
>
> This can make MMC/SD driver work on O2 chip.
>
> Best regards,
> Jennifer
Thanks for the patch submission. There are some changes that need to
be made before this can be accepted into the kernel -- you can read
more about the patch guidelines here:
http://www.kernel.org/doc/Documentation/SubmittingPatches
http://www.kernel.org/doc/Documentation/CodingStyle
In particular:
* The patch needs a "Signed-off-by" line.
* Please submit a summary that explains how the patch works in general.
Your directory name mentions "SD_ADMAissue_8220_8320" -- could you
explain what that issue is, and how this patch fixes it? I guess
I'm particularly interested in why you have to make so many PCI
config writes, and what they achieve.
* It would be ideal if you could generate the patch using Git, and if it
could be based on 2.6.36 or newer instead of 2.6.35.
* In lines like this:
ret = pci_read_config_byte(chip->pdev, 0xD3, &scratch);
please use symbolic names -- the name of the register -- instead
of numbers like 0xD3. For example, from via-sdmmc.c:
#define VIA_CRDR_PCI_WORK_MODE 0x40
#define VIA_CRDR_PCI_DBG_MODE 0x41
...
pci_write_config_byte(pcidev, VIA_CRDR_PCI_WORK_MODE, 0);
pci_write_config_byte(pcidev, VIA_CRDR_PCI_DBG_MODE, 0);
* Instead of comments like "// set E0 to 0x73", please describe what's
actually happening to the hardware. For example, from the jmicron
code:
/*
* Turn PMOS on [bit 0], set over current detection to 2.4 V
* [bit 1:2] and enable over current debouncing [bit 6].
*/
(Linux uses "/* */" comments rather than "//" comments.)
* Commented-out code shouldn't be submitted:
+// .quirks = SDHCI_QUICK_ADMA_TABLE_ENTRY,
* The PCI device ID symbols should only be added to include/linux/pci_ids.h.
There's already a space for other O2 devices in there.
* I think it's generally okay not to check the return value on
pci_write_config_byte().
Please fix these and resubmit the patch. Thanks!
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2010-11-09 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 6:28 [PATCH 2.6.35]: Add new device IDs and registers for MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) cards Jennifer Li (TP)
2010-11-09 15:38 ` 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=20101109153806.GC7977@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.