From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Rebecca Cran <rebecca@bluestop.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: Using i2c from UEFI driver or application
Date: Wed, 12 Apr 2017 21:03:39 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F57D168C4F@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <daef0d76-52cb-cedc-3a73-05c204f6db7c@bluestop.org>
Rebecca,
PI conformant drivers can use PI spec Protocols/PPIs such as I2C.
A UEFI Driver or UEFI Application can use PI Protocols, but the
UEFI Driver/App must look for the PI Protocol and fail gracefully,
provide reduced functionality, or provide an alternate implementation
of the feature if the PI Protocol is not found.
Thanks,
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Rebecca
> Cran
> Sent: Wednesday, April 12, 2017 12:44 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] Using i2c from UEFI driver or application
>
> I'm writing an application (it may also end up being a DXE driver) that
> needs to access the i2c bus. The issue I'm seeing is that the i2c/SMBus
> access protocols etc. seem to be from the PI spec, and my understanding
> is that drivers or applications aren't supposed to use PI-specific
> functionality. Is my understanding correct, or is there some other way
> for drivers/applications to access i2c devices?
>
> --
> Rebecca
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-04-12 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 19:44 Using i2c from UEFI driver or application Rebecca Cran
2017-04-12 21:03 ` Kinney, Michael D [this message]
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=E92EE9817A31E24EB0585FDF735412F57D168C4F@ORSMSX113.amr.corp.intel.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