From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 23D5D21A0483A for ; Wed, 12 Apr 2017 14:03:41 -0700 (PDT) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga104.jf.intel.com with ESMTP; 12 Apr 2017 14:03:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,191,1488873600"; d="scan'208";a="955393291" Received: from orsmsx109.amr.corp.intel.com ([10.22.240.7]) by orsmga003.jf.intel.com with ESMTP; 12 Apr 2017 14:03:40 -0700 Received: from orsmsx111.amr.corp.intel.com (10.22.240.12) by ORSMSX109.amr.corp.intel.com (10.22.240.7) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 12 Apr 2017 14:03:39 -0700 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.59]) by ORSMSX111.amr.corp.intel.com ([169.254.12.79]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 14:03:39 -0700 From: "Kinney, Michael D" To: Rebecca Cran , "edk2-devel@lists.01.org" , "Kinney, Michael D" Thread-Topic: [edk2] Using i2c from UEFI driver or application Thread-Index: AQHSs8Upqaijkb/1pkyPsI9Elin6DqHCN+/A Date: Wed, 12 Apr 2017 21:03:39 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjE3YWVmZmMtMGY2OC00NzM5LTljMGUtOWI0MjA5ZTNmOGU2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlA0Z0ZcL21ObG9ST3JuNk8yQlBcL21OaHBMQnFUWHNmSlpvaEdaWndcL3lDaU09In0= dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.22.254.138] MIME-Version: 1.0 Subject: Re: Using i2c from UEFI driver or application X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2017 21:03:41 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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=20 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 Re= becca > Cran > Sent: Wednesday, April 12, 2017 12:44 PM > To: edk2-devel@lists.01.org > Subject: [edk2] Using i2c from UEFI driver or application >=20 > 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? >=20 > -- > Rebecca > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel