From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-boot] [Patch v4 3/6] keystone2: msmc: add MSMC cache coherency support for K2L SOC
Date: Mon, 20 Oct 2014 18:20:45 +0300 [thread overview]
Message-ID: <5445284D.9020708@ti.com> (raw)
In-Reply-To: <20141020151354.GN25506@bill-the-cat>
On 10/20/2014 06:13 PM, Tom Rini wrote:
> On Wed, Oct 15, 2014 at 02:55:29AM +0300, Ivan Khoronzhuk wrote:
>> From: Hao Zhang <hzhang@ti.com>
>>
>> This patch adds Keystone II Lamar (K2L) SoC specific definitions
>> to support MSMC cache coherency.
>>
>> Acked-by: Vitaly Andrianov <vitalya@ti.com>
>> Signed-off-by: Hao Zhang <hzhang@ti.com>
>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
>> ---
>> arch/arm/cpu/armv7/keystone/init.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/arch/arm/cpu/armv7/keystone/init.c b/arch/arm/cpu/armv7/keystone/init.c
>> index a8f8aee..a0ecfa2 100644
>> --- a/arch/arm/cpu/armv7/keystone/init.c
>> +++ b/arch/arm/cpu/armv7/keystone/init.c
>> @@ -32,6 +32,9 @@ int arch_cpu_init(void)
>> #ifdef CONFIG_SOC_K2E
>> msmc_share_all_segments(13); /* PCIE 1 */
>> #endif
>> +#ifdef CONFIG_SOC_K2L
>> + msmc_share_all_segments(14); /* PCIE 1 */
>> +#endif
>>
>> /*
>> * just initialise the COM2 port so that TI specific
> Where does 13/14 come from and can we just define what that means in a
> K2-foo specific header so we can always do
> msmc_share_all_segments(K2_MSMC_SEGMENTS_NR) or whatever? Thanks!
>
Ok, I will update it.
But, currently, there is newer version,
[U-boot] [Patch v5 0/6] keystone2: add k2l SoC and k2l_evm board support
https://www.mail-archive.com/u-boot at lists.denx.de/msg150245.html
--
Regards,
Ivan Khoronzhuk
next prev parent reply other threads:[~2014-10-20 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 23:55 [U-Boot] [U-boot] [Patch v4 0/6] keystone2: add k2l SoC and k2l_evm board support Ivan Khoronzhuk
2014-10-14 23:55 ` [U-Boot] [U-boot] [Patch v4 1/6] ARM: keystone2: add K2L device hardware definitions Ivan Khoronzhuk
2014-10-14 23:55 ` [U-Boot] [U-boot] [Patch v4 2/6] keystone2: clock: add K2L clock definitions and commands Ivan Khoronzhuk
2014-10-20 15:13 ` Tom Rini
2014-10-20 15:41 ` Ivan Khoronzhuk
2014-10-20 15:55 ` Tom Rini
2014-10-22 13:51 ` Ivan Khoronzhuk
2014-10-14 23:55 ` [U-Boot] [U-boot] [Patch v4 3/6] keystone2: msmc: add MSMC cache coherency support for K2L SOC Ivan Khoronzhuk
2014-10-20 15:13 ` Tom Rini
2014-10-20 15:20 ` Ivan Khoronzhuk [this message]
2014-10-14 23:55 ` [U-Boot] [U-boot] [Patch v4 4/6] ARM: keystone2: spl: add K2L SoC support Ivan Khoronzhuk
2014-10-14 23:55 ` [U-Boot] [U-boot] [Patch v4 5/6] keystone2: enable OSR clock domain for K2L SoC Ivan Khoronzhuk
2014-10-14 23:55 ` [U-Boot] [U-boot] [Patch v4 6/6] keystone2: k2l-evm: add board support Ivan Khoronzhuk
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=5445284D.9020708@ti.com \
--to=ivan.khoronzhuk@ti.com \
--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.