All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Ujfalusi, Peter" <peter.ujfalusi@ti.com>,
	"Guiriec, Sebastien" <s-guiriec@ti.com>,
	"Lopez Cruz, Misael" <misael.lopez@ti.com>
Subject: Re: [PATCH] ARM: OMAP2+: hwmod data: Fix wrong McBSP clock alias on OMAP4
Date: Mon, 2 Jul 2012 17:45:52 +0200	[thread overview]
Message-ID: <4FF1C230.8030102@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206180957250.9031@utopia.booyaka.com>

Hi Paul,

On 06/18/2012 05:57 PM, Paul Walmsley wrote:
> On Mon, 18 Jun 2012, Cousson, Benoit wrote:
>
>> The commit 503d0ea24d1d3dd3db95e5e0edd693da7a2a23eb
>>    ARM: OMAP4: hwmod data: Add aliases for McBSP fclk clocks
>>
>> added a wrong "prcm_clk" alias for PRCM clock whereas the McBSP
>> driver and previous OMAPs are using "prcm_fck".
>>
>> It thus lead to the following warning.
>>
>> [   47.409729] omap-mcbsp: clks: could not clk_get() prcm_fck
>>
>> Fix that by changing the opt_clk role to prcm_fck.
>>
>> Reported-by: Misael Lopez Cruz <misael.lopez@ti.com>
>> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
>> Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
>> Tested-by: Sebastien Guiriec <s-guiriec@ti.com>
>
> Thanks, will queue this as part of the next 3.5-rc series.

I might be wrong but it seems that this one is not yet in 3.5-rc5.

Thanks,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: hwmod data: Fix wrong McBSP clock alias on OMAP4
Date: Mon, 2 Jul 2012 17:45:52 +0200	[thread overview]
Message-ID: <4FF1C230.8030102@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206180957250.9031@utopia.booyaka.com>

Hi Paul,

On 06/18/2012 05:57 PM, Paul Walmsley wrote:
> On Mon, 18 Jun 2012, Cousson, Benoit wrote:
>
>> The commit 503d0ea24d1d3dd3db95e5e0edd693da7a2a23eb
>>    ARM: OMAP4: hwmod data: Add aliases for McBSP fclk clocks
>>
>> added a wrong "prcm_clk" alias for PRCM clock whereas the McBSP
>> driver and previous OMAPs are using "prcm_fck".
>>
>> It thus lead to the following warning.
>>
>> [   47.409729] omap-mcbsp: clks: could not clk_get() prcm_fck
>>
>> Fix that by changing the opt_clk role to prcm_fck.
>>
>> Reported-by: Misael Lopez Cruz <misael.lopez@ti.com>
>> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
>> Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
>> Tested-by: Sebastien Guiriec <s-guiriec@ti.com>
>
> Thanks, will queue this as part of the next 3.5-rc series.

I might be wrong but it seems that this one is not yet in 3.5-rc5.

Thanks,
Benoit

  reply	other threads:[~2012-07-02 15:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  9:42 [PATCH] ARM: OMAP2+: hwmod data: Fix wrong McBSP clock alias on OMAP4 Cousson, Benoit
2012-06-18  9:42 ` Cousson, Benoit
2012-06-18 15:57 ` Paul Walmsley
2012-06-18 15:57   ` Paul Walmsley
2012-07-02 15:45   ` Benoit Cousson [this message]
2012-07-02 15:45     ` Benoit Cousson

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=4FF1C230.8030102@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=misael.lopez@ti.com \
    --cc=paul@pwsan.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=s-guiriec@ti.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 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.