From: Matthew Garrett <matthew.garrett@nebula.com>
To: Benson Leung <bleung@chromium.org>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"olofj@chromium.org" <olofj@chromium.org>,
"miletus@chromium.org" <miletus@chromium.org>
Subject: Re: [PATCH 1/6] Platform: x86: chromeos_laptop - add i915 gmbuses to adapter names
Date: Thu, 21 Feb 2013 21:43:32 +0000 [thread overview]
Message-ID: <1361483011.2813.1.camel@x230> (raw)
In-Reply-To: <1361477700-26342-2-git-send-email-bleung@chromium.org>
On Thu, 2013-02-21 at 12:14 -0800, Benson Leung wrote:
> Add the two other i2c buses (vga and panel) from i915.
> Chromebook Pixel has input and light sensor devices on these busses.
This is after you put the HDMI encoder on the system i2c bus on the
CR-48? Whatever they're putting in the food there must be good. I'll
queue these.
--
Matthew Garrett | mjg59@srcf.ucam.org
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <matthew.garrett@nebula.com>
To: Benson Leung <bleung@chromium.org>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"olofj@chromium.org" <olofj@chromium.org>,
"miletus@chromium.org" <miletus@chromium.org>
Subject: Re: [PATCH 1/6] Platform: x86: chromeos_laptop - add i915 gmbuses to adapter names
Date: Thu, 21 Feb 2013 21:43:32 +0000 [thread overview]
Message-ID: <1361483011.2813.1.camel@x230> (raw)
In-Reply-To: <1361477700-26342-2-git-send-email-bleung@chromium.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 537 bytes --]
On Thu, 2013-02-21 at 12:14 -0800, Benson Leung wrote:
> Add the two other i2c buses (vga and panel) from i915.
> Chromebook Pixel has input and light sensor devices on these busses.
This is after you put the HDMI encoder on the system i2c bus on the
CR-48? Whatever they're putting in the food there must be good. I'll
queue these.
--
Matthew Garrett | mjg59@srcf.ucam.org
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2013-02-21 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 20:14 [PATCH 0/6] Platform: x86: chromeos_laptop - Add support for Chromebook Pixel Benson Leung
2013-02-21 20:14 ` [PATCH 1/6] Platform: x86: chromeos_laptop - add i915 gmbuses to adapter names Benson Leung
2013-02-21 21:43 ` Matthew Garrett [this message]
2013-02-21 21:43 ` Matthew Garrett
2013-02-21 20:14 ` [PATCH 2/6] Platform: x86: chromeos_laptop - Add a more general add_i2c_device Benson Leung
2013-02-21 20:14 ` [PATCH 3/6] Platform: x86: chromeos_laptop - Add isl light sensor for Pixel Benson Leung
2013-02-21 20:14 ` [PATCH 4/6] Platform: x86: chromeos_laptop - Add support for probing devices Benson Leung
2013-02-21 20:14 ` [PATCH 5/6] Platform: x86: chromeos_laptop - Add Pixel Trackpad Benson Leung
2013-02-21 20:15 ` [PATCH 6/6] Platform: x86: chromeos_laptop - Add Pixel Touchscreen Benson Leung
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-all 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=1361483011.2813.1.camel@x230 \
--to=matthew.garrett@nebula.com \
--cc=bleung@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miletus@chromium.org \
--cc=olofj@chromium.org \
--cc=platform-driver-x86@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.