public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] ls102xa: Enable snoop and DVM message requests.
Date: Mon, 7 Dec 2015 08:58:10 -0800	[thread overview]
Message-ID: <5665BAA2.7090003@freescale.com> (raw)
In-Reply-To: <1449298754-7541-4-git-send-email-yao.yuan@freescale.com>



On 12/04/2015 10:59 PM, Yuan Yao wrote:
> Signed-off-by: Yuan Yao <yao.yuan@freescale.com>
> ---
> 
>  arch/arm/cpu/armv7/ls102xa/soc.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/cpu/armv7/ls102xa/soc.c b/arch/arm/cpu/armv7/ls102xa/soc.c
> index 6036473..97ba6d5 100644
> --- a/arch/arm/cpu/armv7/ls102xa/soc.c
> +++ b/arch/arm/cpu/armv7/ls102xa/soc.c
> @@ -40,8 +40,14 @@ int arch_soc_init(void)
>  
>  	/*
>  	 * Enable snoop requests and DVM message requests for
> -	 * Slave insterface S4 (A7 core cluster)
> +	 * All the slave insterfaces.
>  	 */
> +	out_le32(&cci->slave[0].snoop_ctrl,
> +		 CCI400_DVM_MESSAGE_REQ_EN | CCI400_SNOOP_REQ_EN);
> +	out_le32(&cci->slave[1].snoop_ctrl,
> +		 CCI400_DVM_MESSAGE_REQ_EN | CCI400_SNOOP_REQ_EN);
> +	out_le32(&cci->slave[2].snoop_ctrl,
> +		 CCI400_DVM_MESSAGE_REQ_EN | CCI400_SNOOP_REQ_EN);
>  	out_le32(&cci->slave[4].snoop_ctrl,
>  		 CCI400_DVM_MESSAGE_REQ_EN | CCI400_SNOOP_REQ_EN);
>  
> 

Yuan,

I'm not sure both snoop request and DVM are supported on every port. Do you need
to check them before setting?

York

  reply	other threads:[~2015-12-07 16:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05  6:59 [U-Boot] [PATCH v3 0/5] arm: ls1021a: merge SoC specific code in a separate file Yuan Yao
2015-12-05  6:59 ` [U-Boot] [PATCH 1/5] " Yuan Yao
2015-12-15  0:55   ` York Sun
2015-12-05  6:59 ` [U-Boot] [PATCH 2/5] arm: ls102xa: enable all the snoop signal for masters Yuan Yao
2015-12-15  0:58   ` York Sun
2015-12-05  6:59 ` [U-Boot] [PATCH 3/5] ls102xa: Enable snoop and DVM message requests Yuan Yao
2015-12-07 16:58   ` York Sun [this message]
2015-12-14 10:35     ` Yao Yuan
2015-12-14 10:43       ` York Sun
2015-12-15  0:59   ` York Sun
2015-12-15  2:14     ` Yao Yuan
2015-12-05  6:59 ` [U-Boot] [PATCH v2 4/5] armv7/fsl-ls102xa: Workaround for DDR erratum A008514 Yuan Yao
2015-12-15  1:00   ` York Sun
2015-12-05  6:59 ` [U-Boot] [PATCH v3 5/5] move erratum a008336 and a008514 to soc specific file Yuan Yao
2015-12-15  1:00   ` York Sun
  -- strict thread matches above, loose matches on Subject: below --
2015-12-04  9:37 [U-Boot] [PATCH 0/5] arm: ls1021a: merge SoC specific code in a separate file Yuan Yao
2015-12-04  9:37 ` [U-Boot] [PATCH 3/5] ls102xa: Enable snoop and DVM message requests Yuan Yao
2015-11-26  7:57 [U-Boot] [PATCH 1/5] arm: ls1021a: merge SoC specific code in a separate file Yuan Yao
2015-11-26  7:58 ` [U-Boot] [PATCH 3/5] ls102xa: Enable snoop and DVM message requests Yuan Yao
2015-11-05 10:26 [U-Boot] [PATCH v2 1/5] arm: ls1021a: merge SoC specific code in a separate file Yuan Yao
2015-11-05 10:26 ` [U-Boot] [PATCH 3/5] ls102xa: Enable snoop and DVM message requests Yuan Yao
2015-10-21 10:14 [U-Boot] [PATCH 1/5] arm: ls1021a: merge SoC specific code in a separate file Yuan Yao
2015-10-21 10:14 ` [U-Boot] [PATCH 3/5] ls102xa: Enable snoop and DVM message requests Yuan Yao

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=5665BAA2.7090003@freescale.com \
    --to=yorksun@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox