From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from muon.cran.org.uk (muon.bluestop.org [74.50.51.35]) (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 B412021A0483A for ; Wed, 12 Apr 2017 12:44:05 -0700 (PDT) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 16E378946D for ; Wed, 12 Apr 2017 19:44:05 +0000 (UTC) Received: from muon.cran.org.uk ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id FOyOXd4KsZmQ for ; Wed, 12 Apr 2017 19:44:04 +0000 (UTC) Received: from [192.168.1.75] (c-73-20-20-155.hsd1.ut.comcast.net [73.20.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA for ; Wed, 12 Apr 2017 19:44:04 +0000 (UTC) To: "edk2-devel@lists.01.org" From: Rebecca Cran Message-ID: Date: Wed, 12 Apr 2017 13:44:04 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 Subject: 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 19:44:05 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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