Hi, Alim.
On 09/17/2014 09:49 PM, Alim Akhtar wrote:
> Hi Jaehoon
>
> On Wed, Sep 17, 2014 at 8:06 AM, Jaehoon Chung wrote:
>> Hi, Alim.
>>
>> On 09/17/2014 07:27 AM, Alim Akhtar wrote:
>>> Hi Jaehoon,
>>>
>>> On Mon, Sep 15, 2014 at 3:56 PM, Jaehoon Chung
>>> wrote:
Almost all case is se
Hi Jaehoon
On Wed, Sep 17, 2014 at 8:06 AM, Jaehoon Chung wrote:
> Hi, Alim.
>
> On 09/17/2014 07:27 AM, Alim Akhtar wrote:
>> Hi Jaehoon,
>>
>> On Mon, Sep 15, 2014 at 3:56 PM, Jaehoon Chung
>> wrote:
>>> Almost all case is selected to 0.
>>> (It's not correct sample-clock value.)
>>> Since it
Hi, Alim.
On 09/17/2014 07:27 AM, Alim Akhtar wrote:
> Hi Jaehoon,
>
> On Mon, Sep 15, 2014 at 3:56 PM, Jaehoon Chung wrote:
>> Almost all case is selected to 0.
>> (It's not correct sample-clock value.)
>> Since it set to wrong value, HS200 mode don't work fine.
> Can you please explain what pr
Hi Jaehoon,
On Mon, Sep 15, 2014 at 3:56 PM, Jaehoon Chung wrote:
> Almost all case is selected to 0.
> (It's not correct sample-clock value.)
> Since it set to wrong value, HS200 mode don't work fine.
Can you please explain what problem you are facing here?
It is not clear from your patch descri
Almost all case is selected to 0.
(It's not correct sample-clock value.)
Since it set to wrong value, HS200 mode don't work fine.
If we want to select the correct value, it has to check from 1 to 7.(skip 0)
Signed-off-by: Jaehoon Chung
---
drivers/mmc/host/dw_mmc-exynos.c |9 -
1 fil
