From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] imx: mx6: Fix incorrect clear mmdc_ch0 handshake mask
Date: Fri, 25 Mar 2016 10:31:57 +0100 [thread overview]
Message-ID: <56F5058D.5010806@denx.de> (raw)
In-Reply-To: <20160325091404.GA22302@linux-7smt.suse>
On 25/03/2016 10:14, Peng Fan wrote:
> Hi Stefano,
>
> On Wed, Mar 09, 2016 at 05:37:28PM +0800, Peng Fan wrote:
>> Hi Stefano,
>>
>> On Wed, Mar 09, 2016 at 10:47:38AM +0100, Stefano Babic wrote:
>>> Hi Peng, Ye,
>>>
>>> On 09/03/2016 09:13, Peng Fan wrote:
>>>> From: Ye Li <ye.li@nxp.com>
>>>>
>>>> Since the MX6UL/SL/SX only has one DDR channel, in CCM_CCDR register
>>>> the bit[17] for mmdc_ch0 is reserved and its proper state should be 1.
>>>> When clear this bit, the periph_clk_sel cannot be set and that
>>>> CDHIPR[periph_clk_sel_busy] handshake never clears.
>>>>
>>>> Signed-off-by: Ye Li <ye.li@nxp.com>
>>>> Signed-off-by: Peng Fan <van.freenix@gmail.com>
>>>> ---
>>>> arch/arm/cpu/armv7/mx6/soc.c | 5 ++++-
>>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/arch/arm/cpu/armv7/mx6/soc.c b/arch/arm/cpu/armv7/mx6/soc.c
>>>> index 91a3deb..bdd41b0 100644
>>>> --- a/arch/arm/cpu/armv7/mx6/soc.c
>>>> +++ b/arch/arm/cpu/armv7/mx6/soc.c
>>>> @@ -278,7 +278,10 @@ static void clear_mmdc_ch_mask(void)
>>>> reg = readl(&mxc_ccm->ccdr);
>>>>
>>>> /* Clear MMDC channel mask */
>>>> - reg &= ~(MXC_CCM_CCDR_MMDC_CH1_HS_MASK | MXC_CCM_CCDR_MMDC_CH0_HS_MASK);
>>>> + if (is_cpu_type(MXC_CPU_MX6SX) || is_cpu_type(MXC_CPU_MX6UL) || is_cpu_type(MXC_CPU_MX6SL))
>>>> + reg &= ~(MXC_CCM_CCDR_MMDC_CH1_HS_MASK);
>>>> + else
>>>> + reg &= ~(MXC_CCM_CCDR_MMDC_CH1_HS_MASK | MXC_CCM_CCDR_MMDC_CH0_HS_MASK);
>>>> writel(reg, &mxc_ccm->ccdr);
>>>> }
>>>>
>>>
>>> Acked-by: Stefano Babic <sbabic@denx.de>
>>>
>>> This is a fix, and my question to you both: is it enough to merge it
>>> after 2016.03 ? I have not read about big issues due to periph_clk_sel,
>>> and maybe we can postponed it (or I merge directly into -next as several
>>> of you have already proposed).
>>
>> Yeah. It's okay to merge after 2016.03.
I do it
Stefano
>
> Will you pick up this patch?
>
> Regards,
> Peng.
>
>>
>> Regards,
>> Peng.
>>
>>>
>>> Best regards,
>>> Stefano Babic
>>>
>>>
>>>
>>> --
>>> =====================================================================
>>> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
>>> 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
>>> =====================================================================
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
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
=====================================================================
prev parent reply other threads:[~2016-03-25 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 8:13 [U-Boot] [PATCH] imx: mx6: Fix incorrect clear mmdc_ch0 handshake mask Peng Fan
2016-03-09 9:47 ` Stefano Babic
2016-03-09 9:37 ` Peng Fan
2016-03-25 9:14 ` Peng Fan
2016-03-25 9:31 ` Stefano Babic [this message]
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=56F5058D.5010806@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 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.