From: Jaehoon Chung <jh80.chung@samsung.com>
To: Kyungmin Park <kyungmin.park@samsung.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH 0/2] mmc: core: pre-patch for next eMMC version
Date: Fri, 14 Sep 2012 16:13:01 +0900 [thread overview]
Message-ID: <5052D8FD.1010900@samsung.com> (raw)
In-Reply-To: <CAH9JG2XwdBao=L3KOxDOtbyhcTuq6rKUEpwWU9+zqhU3HeteQw@mail.gmail.com>
Hi Ulf and Chris,
Could you have any opinion?
If you have no more, could you merge the patch for eMMC5.0?
Best Regards,
Jaehoon Chung
On 08/29/2012 08:59 PM, Kyungmin Park wrote:
> Hi Ulf,
>
> On 8/29/12, Ulf Hansson <ulf.hansson@linaro.org> wrote:
>> Hi Jaehoon,
>>
>> On 28 August 2012 06:33, Jaehoon Chung <jh80.chung@samsung.com> wrote:
>>> Hi Ulf,
>>>
>>> This patch is to support eMMC5.0.(already discussing on eMMC5.0.)
>>> Revision value is defined the 0x7 into ext_csd register.(in eMMC5.0's
>>> case)
>>
>> Until the spec is really set we should not add some new code for this,
>> it does not make sense to kind of guess.
> It's not guess. it's determined and will be discussed at JEDEC soon.
>
> Revision 1.7 (for MMC V5.0)
>
> Thank you,
> Kyungmin Park
>>
>>>
>>> And case of Quirks is preparation patch to prevent the problem that should
>>> exist.
>>> That Quirks can also use for backward compatibility.
>>> (if card is greater version than eMMC4.5 and need to use only eMMC4.5
>>> feature?
>>> then can use quirks and known_rev.)
>>
>> It is just speculations about potential problems with eMMC 5.0. I
>> think we can leave this to later, if/when we see a need for it.
>>
>> Kind regards
>> Ulf Hansson
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-09-14 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 0:23 [PATCH 0/2] mmc: core: pre-patch for next eMMC version Jaehoon Chung
2012-08-27 12:04 ` Ulf Hansson
2012-08-28 4:33 ` Jaehoon Chung
2012-08-29 11:53 ` Ulf Hansson
2012-08-29 11:59 ` Kyungmin Park
2012-09-14 7:13 ` Jaehoon Chung [this message]
2012-09-14 9:34 ` Ulf Hansson
2012-09-14 9:38 ` Jaehoon Chung
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=5052D8FD.1010900@samsung.com \
--to=jh80.chung@samsung.com \
--cc=cjb@laptop.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox