public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Rob Herring <robh@kernel.org>, <linux-omap@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <tony@atomide.com>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH] mfd: twl6040: Handle mclk used for HPPLL and optional internal clock source
Date: Tue, 7 Jun 2016 12:23:02 +0300	[thread overview]
Message-ID: <b8e0eb46-8697-ef02-eef4-2d3fe8136707@ti.com> (raw)
In-Reply-To: <20160607091739.GD18047@dell>

On 06/07/16 12:17, Lee Jones wrote:
> On Tue, 07 Jun 2016, Peter Ujfalusi wrote:
> 
>> Lee,
>>
>> On 05/16/16 18:02, Rob Herring wrote:
>>> On Wed, May 11, 2016 at 02:13:29PM +0300, Peter Ujfalusi wrote:
>>>> On some boards, like omap5-uevm the MCLK is gated by default and in order
>>>> to be able to use the High performance modes of twl6040 it need to be
>>>> enabled by SW.
>>>> Add support for handling the MCLK source clock via CCF.
>>>> At the same time lover the print priority of the notification that the 32K
>>>> clock is not proveded so it is not going to be handled by the driver.
>>>>
>>>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>>>> ---
>>>>  Documentation/devicetree/bindings/mfd/twl6040.txt |  4 +--
>>>
>>> Acked-by: Rob Herring <robh@kernel.org>
>>
>> Can you take a look at this patch if it is OK to pick?
> 
> Yes, when I get around to it.
> 
> I currently have 75 patch review to conduct in my inbox.  Some of them
> are quite large and complex.  They will be seen to in the order they
> were sent, and you just bumped this patch to "sent today". ;)

I'm sorry for this. I did not intended to interfere with your workflow. I will
be more patient next time, it is hard to know if I should bump the thread or
resend or wait.

Sorry again,
Péter

  reply	other threads:[~2016-06-07  9:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 11:13 [PATCH] mfd: twl6040: Handle mclk used for HPPLL and optional internal clock source Peter Ujfalusi
2016-05-16 15:02 ` Rob Herring
2016-06-07  8:54   ` Peter Ujfalusi
2016-06-07  9:17     ` Lee Jones
2016-06-07  9:23       ` Peter Ujfalusi [this message]
2016-06-16 15:16 ` Lee Jones
2016-06-20  8:53   ` Peter Ujfalusi
2016-06-20  9:57     ` Lee Jones

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=b8e0eb46-8697-ef02-eef4-2d3fe8136707@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tony@atomide.com \
    /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