From: Jeremie Samuel <jeremie.samuel.ext@parrot.com>
To: Chris Ball <cjb@laptop.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"Matthieu Castet" <matthieu.castet@parrot.com>,
"Grégor BOIRIE" <gregor.boirie@parrot.com>
Subject: Re: [PATCH 6/8] sdhci: Turn host->lock into a mutex
Date: Mon, 26 Aug 2013 10:37:56 +0200 [thread overview]
Message-ID: <521B13E4.6030800@parrot.com> (raw)
In-Reply-To: <874naev8e1.fsf@octavius.laptop.org>
Hi Chris,
Thank you for the feedback. I'll send you the modifications in
September. But I will not be able to test the changes. I don't have the
hardware.
Regards,
--
Jeremie Samuel Parrot S.A.
Software Engineer 14, quai de Jemmapes
R&D/OS Platform 75010 Paris, France
http://www.parrot.com
On 25/08/2013 03:58, Chris Ball wrote:
> Hi Jeremie, I'm sorry for a very late review.
>
> On Tue, Jul 09 2013, Jeremie Samuel wrote:
>> @@ -118,7 +119,7 @@ struct sdhci_host {
>> enum led_brightness brightness;
>> #endif
>>
>> - spinlock_t lock; /* Mutex */
>> + struct mutex lock; /* Mutex */
>>
>> int flags; /* Host attributes */
>> #define SDHCI_USE_SDMA (1<<0) /* Host is SDMA capable */
> I think you need to modify many of the drivers/mmc/host/sdhci-*
> drivers too -- for example:
>
> sdhci-pxav3.c:
>
> static int sdhci_pxav3_runtime_suspend(struct device *dev)
> {
> struct sdhci_host *host = dev_get_drvdata(dev);
> struct sdhci_pltfm_host *pltfm_host = sdhci_priv(host);
> unsigned long flags;
>
> if (pltfm_host->clk) {
> spin_lock_irqsave(&host->lock, flags);
> [...]
>
>
> sdhci-s3c.c:
>
> static void sdhci_s3c_notify_change(struct platform_device *dev, int state)
> {
> struct sdhci_host *host = platform_get_drvdata(dev);
> #ifdef CONFIG_PM_RUNTIME
> struct sdhci_s3c *sc = sdhci_priv(host);
> #endif
> unsigned long flags;
>
> if (host) {
> spin_lock_irqsave(&host->lock, flags);
> [...]
>
>
> Thanks,
>
> - Chris.
next prev parent reply other threads:[~2013-08-26 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 15:44 [PATCH 0/8] sdhci: Move real work out of an atomic context Jeremie Samuel
2013-07-09 15:44 ` [PATCH 1/8] sdhci: Turn timeout timer into delayed work Jeremie Samuel
2013-07-09 15:44 ` [PATCH 2/8] sdhci: Turn tuning " Jeremie Samuel
2013-07-09 15:44 ` [PATCH 3/8] sdhci: Use work structs instead of tasklets Jeremie Samuel
2013-07-09 15:44 ` [PATCH 4/8] sdhci: Use threaded IRQ handler Jeremie Samuel
2013-07-09 15:44 ` [PATCH 5/8] sdhci: Delay led blinking Jeremie Samuel
2013-07-09 15:44 ` [PATCH 6/8] sdhci: Turn host->lock into a mutex Jeremie Samuel
2013-08-25 1:58 ` Chris Ball
2013-08-26 8:37 ` Jeremie Samuel [this message]
2013-07-09 15:44 ` [PATCH 7/8] sdhci: Get rid of mdelay()s where it is safe and makes sense Jeremie Samuel
2013-07-09 15:44 ` [PATCH 8/8] sdhci: Use jiffies instead of a timeout counter Jeremie Samuel
2013-07-09 15:52 ` [PATCH 0/8] sdhci: Move real work out of an atomic context Philip Rakity
2013-07-11 8:28 ` Jeremie Samuel
-- strict thread matches above, loose matches on Subject: below --
2013-10-16 16:20 Jeremie Samuel
2013-10-16 16:20 ` [PATCH 6/8] sdhci: Turn host->lock into a mutex Jeremie Samuel
2013-05-24 16:00 [PATCH 0/8] sdhci: Move real work out of an atomic context Jeremie Samuel
2013-05-24 16:00 ` [PATCH 6/8] sdhci: Turn host->lock into a mutex Jeremie Samuel
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=521B13E4.6030800@parrot.com \
--to=jeremie.samuel.ext@parrot.com \
--cc=cjb@laptop.org \
--cc=gregor.boirie@parrot.com \
--cc=linux-mmc@vger.kernel.org \
--cc=matthieu.castet@parrot.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.