From: Govert Overgaauw <govert.overgaauw@prodrive-technologies.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: Stef van Os <stef.van.os@prodrive-technologies.com>
Subject: MCTP LPC FW binding
Date: Fri, 11 Mar 2022 14:02:02 +0000 [thread overview]
Message-ID: <AM9PR02MB6499C2AB30799F6A97D92095C10C9@AM9PR02MB6499.eurprd02.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Hello,
I was wondering if anyone is/was successful in using the MCTP over LPC binding with an intel platform? I read through the documents, it seems to me the binding was designed to use LPC firmware cycles. To me it is unclear if the ast2500 supports memory cycles on the LPC2AHB bridge (datasheet seems to list it in the features, not much explanation). The problem is that the C620 chipset doesn't support firmware cycles (only memory and I/O cycles). And having a properly mapped window in the C620 chipset and reserved memory in Linux. Writing and Reading to it only returns ('1s').
Writing a simple test on x86 that keeps writing a value to the mapped registers, seems to trigger LAD[3:1] = 0xF readout on the BMC LPC host controller register 0 (that has some debug registers to see the state of the LPC bus). 0xF is the stop frame of a standard LPC memory cycle.
Kind Regards,
Govert Overgaauw
[-- Attachment #2: Type: text/html, Size: 2293 bytes --]
next reply other threads:[~2022-03-14 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 14:02 Govert Overgaauw [this message]
2022-03-15 22:42 ` MCTP LPC FW binding Andrew Jeffery
2022-03-17 15:42 Govert Overgaauw
2022-03-18 3:49 ` Andrew Jeffery
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=AM9PR02MB6499C2AB30799F6A97D92095C10C9@AM9PR02MB6499.eurprd02.prod.outlook.com \
--to=govert.overgaauw@prodrive-technologies.com \
--cc=openbmc@lists.ozlabs.org \
--cc=stef.van.os@prodrive-technologies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).