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, 14 Dec 2015 18:43:59 +0800 [thread overview]
Message-ID: <566E9D6F.4040101@freescale.com> (raw)
In-Reply-To: <BLUPR03MB1340CAB83D9D80F17CA8B4483ED0@BLUPR03MB134.namprd03.prod.outlook.com>
On 12/14/2015 06:35 PM, Yuan Yao-B46683 wrote:
> Hi York,
>
> I'm sorry I'm late replies.
>
> Thanks for reminding me.
> We have some investigates and then depend on the document we think both snoop request and DVM are supported on those port.
> So we think the setting should be ok in here.
>
I think your conclusion is correct but not your reasoning. I did some digging
myself. These registers (snoop control) have top two bits indicating if a slave
interface supports snoop and/or DVM messages. If the feature is disabled,
writing the enabling bit is ignored.
No more action for you.
York
next prev parent reply other threads:[~2015-12-14 10:43 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
2015-12-14 10:35 ` Yao Yuan
2015-12-14 10:43 ` York Sun [this message]
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=566E9D6F.4040101@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