public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] mxc: Fix SDHC multi-instance clock
Date: Tue, 09 Oct 2012 12:58:01 +0200	[thread overview]
Message-ID: <50740339.5080806@denx.de> (raw)
In-Reply-To: <1850571028.6438072.1349778906864.JavaMail.root@advansee.com>

On 09/10/2012 12:35, Beno?t Th?baudeau wrote:
> Hi Stefano,
> 
> On Monday, October 1, 2012 8:36:25 PM, Beno?t Th?baudeau wrote:
>> On mxc, each SDHC instance has a dedicated clock, so gd->sdhc_clk is
>> not
>> suitable for the multi-instance use case (initialization made
>> directly with
>> fsl_esdhc_initialize()).
>>
>> This patch fixes this issue by adding a configuration field for the
>> SDHC input
>> clock frequency.
>>
>> Signed-off-by: Beno?t Th?baudeau <benoit.thebaudeau@advansee.com>
>> Cc: Stefano Babic <sbabic@denx.de>
>> Cc: Eric B?nard <eric@eukrea.com>
>> Cc: Otavio Salvador <otavio@ossystems.com.br>
>> Cc: Fabio Estevam <fabio.estevam@freescale.com>
>> Cc: Jason Liu <r64343@freescale.com>
>> Cc: Matt Sealey <matt@genesi-usa.com>
>> Cc: Andy Fleming <afleming@gmail.com>
>> ---
>> This patch should be applied after (series of series...):
>> http://patchwork.ozlabs.org/patch/187467/
>> http://patchwork.ozlabs.org/patch/187468/
>> http://patchwork.ozlabs.org/patch/187475/
>>
>> This patch supersedes http://patchwork.ozlabs.org/patch/187476/ .
>>
>> Changes for v2:
>>  - Since this patch will go to /next, extend the original patch with
>>  the mxc
>>    boards newly added to this branch: mx6qsabreauto and mx6qsabresd.
> 
> Did you forget to apply this patch (and
> http://patchwork.ozlabs.org/patch/187468/ before it) when you applied my mx5 and
> mx25 clock series, or is it just still in your TODO list?

No, I did not forget. There are two patches for ESDHC. I wanted to be
sure that PowerPC boards are not broken and I have rechecked it this
morning. They are both ready in my queue to be merged.

> If you could apply them before the Nitrogen6X series (in order to avoid a v3 of
> this patch), I'd be grateful ;) . But if you need more review/test time, of
> course no problem if this is not possible.

I have some patches ready to be merged, but I sent also a pull request
for the -next branch, and it is not yet merged into arm-next. Anyway, I
can modify my pull request including further patches, too.

Best regards,
Stefano


-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

  reply	other threads:[~2012-10-09 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 20:31 [U-Boot] [PATCH] mxc: Fix SDHC multi-instance clock Benoît Thébaudeau
2012-09-28 13:09 ` Benoît Thébaudeau
2012-10-01 18:36 ` [U-Boot] [PATCH v2] " Benoît Thébaudeau
2012-10-09 10:35   ` Benoît Thébaudeau
2012-10-09 10:58     ` Stefano Babic [this message]
2012-10-10 11:29   ` Stefano Babic

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=50740339.5080806@denx.de \
    --to=sbabic@denx.de \
    --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