From: Sergey Yanovich <ynvich@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7
Date: Fri, 20 Apr 2007 12:22:13 +0300 [thread overview]
Message-ID: <46288645.3090201@gmail.com> (raw)
In-Reply-To: <200704200056.33866.arnd@arndb.de>
Hi,
Arnd Bergmann wrote:
> As very general comments, you should have the maintainer of the subsystem
> (Pierre in this case) on Cc when posting a driver, and you should include
> the patch inline in your mail, see Documentation/SubmittingPatches.
>
I have cc'ed both Pierre and Alex, but my first message was blocked
by the list as it contained html.
For inlinning, this is my first kernel patch. I have just followed
http://www.tux.org/lkml/#s2-2.
> You should include the Makefile and Kconfig changes in the same patch/mail,
> no point splitting these out.
>
Once again it was an advise from http://www.tux.org/lkml/#s1-10.
<http://www.tux.org/lkml/#s1-10>
> Don't define your own DBG macro, instead use the predefined dev_dbg()
> that has a similar definition.
>
Somewhere in 0.5-0.6 version this driver has issues with timeouts ,
which were
revealing in a non-debug kernel builds only . So this was a nessecity. I
will purge
them now.
> Your mmc_tifm_irq_chip() function does a _very_ long delay of 100
> miliseconds. This is normally not acceptable, since it is a noticeable
> time in which the system is completely unresponsive. Maybe you can convert
> the tasklet to a workqueue, which lets you call msleep instead of mdelay.
>
This is done intentionally to prevent a race condition when a card is
removed
and immediately reinserted. There may be a more complicated way to solve
this
issue, but didn't think about them. This only happens when an MMC/SD
card is
inserted/removed. And it takes at least as long to process the event in
other
parts of subsystem.
> Your use of pci_map_sg() looks wrong, you simply can't assume that the
> return value is '1' in general. I've stumbled over that same problem
> in the sdhci driver, so it may be inherent to the mmc layer and not
> be driver specific.
>
This is taken as is from [tifm_sd]. I suppose this relates to a hardware
limitation:
+ mmc->max_hw_segs = 1;
+ mmc->max_phys_segs = 1;
Best regards,
Sergey
next prev parent reply other threads:[~2007-04-20 9:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 20:53 [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7 Sergey Yanovich
2007-04-19 22:56 ` Arnd Bergmann
2007-04-20 9:22 ` Sergey Yanovich [this message]
2007-04-25 21:59 ` [PATCH] [mmc] Removes custom debug macro Sergey Yanovich
2007-04-25 21:44 ` Sergey Yanovich
2007-04-25 21:59 ` Sergey Yanovich
2007-04-25 22:15 ` Arnd Bergmann
2007-04-25 21:59 ` [PATCH] [mmc] [tifm] Reduces delay in card insert/removal Sergey Yanovich
2007-04-25 21:44 ` Sergey Yanovich
2007-04-25 21:59 ` Sergey Yanovich
2007-04-25 23:00 ` Arnd Bergmann
2007-04-25 22:13 ` Sergey Yanovich
[not found] <4627D402.8020107@gmail.com>
2007-04-20 2:17 ` [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7 Alex Dubov
2007-04-20 8:20 ` Brad Campbell
2007-04-20 8:31 ` Fabio Comolli
2007-04-20 10:10 ` Sergey Yanovich
2007-04-22 1:34 ` Alex Dubov
2007-04-22 12:15 ` Sergey Yanovich
2007-04-23 7:04 ` Matthew Garrett
2007-04-23 7:29 ` Sergey Yanovich
2007-04-23 13:16 ` Alex Dubov
2007-04-23 14:12 ` Sergey Yanovich
2007-04-24 2:55 ` Alex Dubov
2007-04-24 8:05 ` Sergey Yanovich
2007-04-26 6:36 ` Pierre Ossman
2007-04-27 2:41 ` Alex Dubov
2007-04-27 7:50 ` Sergey Yanovich
2007-04-27 11:23 ` Alex Dubov
2007-04-27 12:14 ` Sergey Yanovich
2007-04-27 16:55 ` Alex Dubov
2007-04-27 18:36 ` Sergey Yanovich
2007-04-28 8:10 ` Alex Dubov
2007-04-28 8:41 ` Sergey Yanovich
2007-04-28 9:08 ` Sergey Yanovich
2007-04-28 11:34 ` Pierre Ossman
2007-04-28 11:44 ` Alex Dubov
2007-04-28 17:07 ` Sergey Yanovich
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=46288645.3090201@gmail.com \
--to=ynvich@gmail.com \
--cc=linux-kernel@vger.kernel.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 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.