public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Przemyslaw Marczak <p.marczak@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] DWMMC crontroller in Exynos4412
Date: Wed, 26 Aug 2015 08:53:54 +0200	[thread overview]
Message-ID: <55DD6282.5090607@samsung.com> (raw)
In-Reply-To: <55DD5B63.4040108@samsung.com>

Hi,

On 08/26/2015 08:23 AM, Jaehoon Chung wrote:
> On 08/26/2015 11:26 AM, Simon Glass wrote:
>> +Samsung people
>>
>> Hi,
>>
>> On 25 August 2015 at 13:10, Humberto L?pez Le?n <humberto@uclv.cu> wrote:
>>> Hi Simon,
>>> I'm working on implementing a driver for SD/MMC cards in the framework
>>> GenodeOS. I think you could help me with your experience in this type of
>>> implementation in the u-boot.
>>> The hardware platform on which the driver will work is a ODROID-x2
>>> (exynos4412). I use the DWMMC contoller, but I'm not sure if this is the
>>> right controller to handle SD/MMC cards in Exynos4412 SoC. The SDHCI
>>> controller is most appropriate?
>
> If you're using exynos4412 board, you can choose sdhci or dwmmc controller for eMMC, not SD/SDIO.
> And in my experiment, dwmmc controller is more appropriate than sdhci.(ex, performance)
>

It depends which mmc channel is used. In Exynos4412, there are 5 
channels, but some channel configurations shares GPIO pins:
- MMC0 - sdhci
- MMC1 - sdhci, or MMC0 8-bit
- MMC2 - sdhci - Odroid SD card, 4-bit mode
- MMC3 - sdhci - or MMC2 8-bit
- MMC4 - dwmmc, uses MMC0 pins for 4-bit, and MMC0-1 for 8-bit mode

Odroid is using MMC2(sdhci) and MMC0/4(sdhci or dwmmc).

So for eMMC cards you can use the dwmmc, and as Jaehoon wrote it is 
recommended for the better performance, but for SD card you must use 
sdhci controller.

Best regards,
-- 
Przemyslaw Marczak
Samsung R&D Institute Poland
Samsung Electronics
p.marczak at samsung.com

>>>
>>> Thank you for your help
>>
>> I'm not really sure - the compatible string for that node is:
>>
>> compatible = "samsung,exynos4412-dw-mshc";
>>
>> which is different from what exynos5 uses.
>
> As i know, Some register are difference..but i know it doesn't implemented for those registers at u-boot side.
> If it should be implemented for upper mode than DDR50, it needs to check the compatible.
>
> Best Regards,
> Jaehoon Chung
>
>>
>> Possibly Lukasz / Przemyslaw know about this.
>>
>> Regards,
>> Simon
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>
>

  reply	other threads:[~2015-08-26  6:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 19:10 [U-Boot] DWMMC crontroller in Exynos4412 Humberto López León
2015-08-26  2:26 ` Simon Glass
2015-08-26  6:23   ` Jaehoon Chung
2015-08-26  6:53     ` Przemyslaw Marczak [this message]
2015-08-26 13:40       ` Humberto López León
2015-08-26 14:12         ` Przemyslaw Marczak
2015-08-26 17:24           ` Humberto López León
2015-08-27  6:47             ` Przemyslaw Marczak
2015-09-28 13:27               ` Humberto López León
2015-10-01 11:24                 ` Przemyslaw Marczak
2015-10-07 13:44                   ` Humberto López León
2015-10-07 20:50                   ` Humberto López León
2015-10-08  8:33                     ` Przemyslaw Marczak

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=55DD6282.5090607@samsung.com \
    --to=p.marczak@samsung.com \
    --cc=u-boot@lists.denx.de \
    /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