From: Rafael Machado <rafaelrodrigues.machado@gmail.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Accessing I2C GPIO Device
Date: Thu, 22 Dec 2016 11:14:41 +0000 [thread overview]
Message-ID: <CACgnt7-DJ0+W_Y_kTyqHCsDDDy_0JNwo8MYb1-gpZs4TkqGo4A@mail.gmail.com> (raw)
Hi everyone
I have a platform that has a I2C device connected directly to a processor's
I2C pins.
Now I'm researching the way to send and receive information to this device.
The first idea we had was to use the I2C Protocol Stack, but I'd like to
clarify one point.
After reading the documentation related to the I2C Protocol Stack, seems
this is application just in case the system has a I2C bus were other
devices are connected.
As far as I could understand on out case, since the device is attached
directly to the CPU pins, I understand that the correct wai ti access this
device is using the CPU I/O Protocol.
Is my understanding correct?
In case someone has some details about a scenario like this it would be
really helpful.
Thanks and Regards
Rafael R. Machado
next reply other threads:[~2016-12-22 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 11:14 Rafael Machado [this message]
2016-12-22 13:09 ` Accessing I2C GPIO Device Rafael Machado
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-list 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=CACgnt7-DJ0+W_Y_kTyqHCsDDDy_0JNwo8MYb1-gpZs4TkqGo4A@mail.gmail.com \
--to=devel@edk2.groups.io \
/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