All of lore.kernel.org
 help / color / mirror / Atom feed
From: Soeren Moch <smoch@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] board: tbs2910: Gate clock when switching async clock muxes
Date: Thu, 19 Feb 2015 00:28:52 +0100	[thread overview]
Message-ID: <54E52034.6@web.de> (raw)
In-Reply-To: <54E51B64.50009@denx.de>

Hi Stefano,

On 19.02.2015 00:08, Stefano Babic wrote:
> Hi Soeren,
> 
> On 18/02/2015 16:43, Soeren Moch wrote:
>>> According to the i.MX6Q Reference Manual, clocks must be gated when
>>> switching input clocks of async clock muxes. So use clock gates. Avoid
>>> ldb_di0_ipu clock, because there is no clock gate for this signal.
>>>
>>> There have never been any complaints about problems with the old code,
>>> but the new approach is in line with the recommendations in the manual.
>>>
>>> Signed-off-by: Soeren Moch <smoch@web.de>
>>> -- 
>>> Cc: Stefano Babic <sbabic@denx.de>
>>
>> Stefano,
>>
>> this patch missed several commit cycles now. Do you think it should not
>> be merged?
>>
> 
> No, but it was not in my list on patchwork - I checked now and the patch
> was delegated to York. Maybe he is also asking why, because it is
> strictly i.MX related.
> 
> I set the patch to myself and I will merge it. Thanks for raising this.
> 
> Best regards,
> Stefano Babic
> 

Ah, ok. Is there any opportunity to assign a patch in patchwork when
sending it?

However, no problem.

Thanks, Soeren

  reply	other threads:[~2015-02-18 23:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 18:03 [U-Boot] [PATCH] board: tbs2910: Gate clock when switching async clock muxes Soeren Moch
2015-02-18 15:43 ` Soeren Moch
2015-02-18 23:08   ` Stefano Babic
2015-02-18 23:28     ` Soeren Moch [this message]
2015-02-19 18:44       ` Stefano Babic
2015-02-23  8:19 ` 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=54E52034.6@web.de \
    --to=smoch@web.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 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.