From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 781D082382 for ; Thu, 22 Dec 2016 03:14:53 -0800 (PST) Received: by mail-qt0-x22a.google.com with SMTP id d45so9461375qta.1 for ; Thu, 22 Dec 2016 03:14:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=KXwHLs95i7/XBvXJ/TitWHcFkgfkoNrmXz0VdKIZEs4=; b=SZR12Ipn3xalO/PULSw8vZ3p7CZVMF4y8VOFMHxoaMNyV7Oav8O8QrbajX6nFoe/AA ZTSGYkGWU/juc87M8PDYslhpO8df0I1CwKmfQzOS8LFEbKM/VMJiYuMV+5aJU5f4y5QG TFBwHKrYRW/9Aq0y4J8u3cZLUjeOe5uO0GXxe1LF3X4XjaolH1xq7J7DcpdKE17+323b AvrVS9ifNqidI9K4xOD15/IZqPWdAEStF4UR9BxfJ1XBtvUHaCDmZUIH5HUyV8DvGNyO Jdit2EBmroK8qcDuRsN3mtywFIU/2lVx81vgml76XG05IrgeBWwjC850fAu8+nSOxlKJ 7/Hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=KXwHLs95i7/XBvXJ/TitWHcFkgfkoNrmXz0VdKIZEs4=; b=XQA/a9/I+CmX6rAdpYClN5NLlN7NHlx0TPc6rA0DRfsg+4lwNU7ojrqKy2+S07+80Y hOsRdDdblq9VRWc7tamr3fImIm6Z4N1ixYsHVO3c7fTHtK+eyXdtYEtHbg+mozDRShgA JItmATz8gYn83CaYYmNW752mnOUJO9fpAnWJG6f0ass7XdlXp66cUkv+51DTRhcB4ID/ B0ox+DdsGVtHfiyJQaWojxTAL3vYELHGo5xoTF0f0YL8KEoAA0V/LazNKo+3Sd3fe8wS 2VhWg+kO8yw97kD/9Ysk6cjorBPoT+CijFphb86Xw0OWobpL5QfZoNXjUs9O3I24CBSC 4aqg== X-Gm-Message-State: AIkVDXJSUXzf8P6EZ7IzMdBrvK3SCtwW7exKdev0QOwLPpU+vtxy3xWSAdLQd2hYL9Zcw8b8GEGPi8a2P9OSWg== X-Received: by 10.237.53.119 with SMTP id b52mr10356594qte.74.1482405292399; Thu, 22 Dec 2016 03:14:52 -0800 (PST) MIME-Version: 1.0 From: Rafael Machado Date: Thu, 22 Dec 2016 11:14:41 +0000 Message-ID: To: "edk2-devel@lists.01.org" X-Content-Filtered-By: Mailman/MimeDel 2.1.21 Subject: Accessing I2C GPIO Device X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2016 11:14:53 -0000 Content-Type: text/plain; charset=UTF-8 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