From: Jaehoon Chung <jh80.chung@samsung.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Jae hoon Chung <jh80.chung@gmail.com>
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
Chris Ball <chris@printf.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 1/2] mmc: dw_mmc: poll if CD is broken
Date: Thu, 01 May 2014 17:38:26 +0900 [thread overview]
Message-ID: <53620802.3090504@samsung.com> (raw)
In-Reply-To: <53611424.4050901@linutronix.de>
Hi, Sebastian.
Your patch didn't base on latest mmc-next repository.
You can refer to below git.
http://git.kernel.org/cgit/linux/kernel/git/cjb/mmc.git/
I think you made the patch on v3.12.
Best Regards,
Jaehoon Chung
On 05/01/2014 12:17 AM, Sebastian Andrzej Siewior wrote:
> On 04/30/2014 04:57 PM, Jae hoon Chung wrote:
>> Hi, Sebastian.
>
> Hi Jaehoon,
>
>> I didn't know which Soc you used.
>
> Altera socfpa.
>
>> Do you use the Device-tree? if you use the device-tree, just add the
>> "broken-cd" property.
>
> and with this property the code will rescan the card every few secs? I
> didn't see this in v3.12. I do have "broken-cd" set. And the card will
> not be detected if it is inserted after the driver probed.
>
> But now that you pointed me at it. You say that "broken-cd" will be
> scanned by the core, right? Shouldn't the driver then call
> mmc_of_parse() or am I missing something?
>
>> Best Regards,
>> Jaehoon Chung
>
> Sebastian
>
prev parent reply other threads:[~2014-05-01 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 13:44 [PATCH 1/2] mmc: dw_mmc: poll if CD is broken Sebastian Andrzej Siewior
2014-04-30 13:44 ` [PATCH 2/2] mmc: dw_mmc: print card frequency in debug level Sebastian Andrzej Siewior
2014-05-01 8:42 ` Jaehoon Chung
[not found] ` <CAELcNGT7Ei35tmZzAJ4iCdwMCamd5tC-onRmNG3JL+78_6B0-w@mail.gmail.com>
2014-04-30 15:17 ` [PATCH 1/2] mmc: dw_mmc: poll if CD is broken Sebastian Andrzej Siewior
2014-05-01 8:38 ` Jaehoon Chung [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=53620802.3090504@samsung.com \
--to=jh80.chung@samsung.com \
--cc=bigeasy@linutronix.de \
--cc=chris@printf.net \
--cc=jh80.chung@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.com \
--cc=ulf.hansson@linaro.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.