From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
Andrew Duggan <aduggan@synaptics.com>,
Vincent Huang <vincent.huang@tw.synaptics.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
jmaneyrol@invensense.com, borneo.antonio@gmail.com,
seth.forshee@canonical.com, archana.patni@linux.intel.com,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] HID: i2c-hid: Fix suspend/resume when already runtime suspended
Date: Thu, 12 Mar 2015 17:28:07 +0200 [thread overview]
Message-ID: <20150312152807.GO1563@lahna.fi.intel.com> (raw)
In-Reply-To: <CAD=FV=UGZE6wyve651HkjV1dkiWt2ZqMS=e8efoGq3+oSP5+Hw@mail.gmail.com>
On Thu, Mar 12, 2015 at 08:24:53AM -0700, Doug Anderson wrote:
> Mika,
>
> On Thu, Mar 12, 2015 at 2:10 AM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > That's interesting. So you have an ARM device with i2c-hid compatible
> > device connected to it? Out of curiousity, do you use DT or some
> > platform board file to configure the thing?
>
> Using DT. That's allowed, right? (3d7d248 HID: i2c-hid: add DT bindings)
Of course.
I was just curious because I have only seen i2c-hid devices that are
ACPI enumerated.
prev parent reply other threads:[~2015-03-12 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 19:44 [PATCH v2] HID: i2c-hid: Fix suspend/resume when already runtime suspended Doug Anderson
2015-03-10 12:23 ` Mika Westerberg
2015-03-10 16:12 ` Doug Anderson
2015-03-11 11:20 ` Mika Westerberg
2015-03-11 15:06 ` Doug Anderson
2015-03-12 9:10 ` Mika Westerberg
2015-03-12 11:19 ` Mika Westerberg
2015-03-12 15:24 ` Doug Anderson
2015-03-12 15:28 ` Mika Westerberg [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-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=20150312152807.GO1563@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=aduggan@synaptics.com \
--cc=archana.patni@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=borneo.antonio@gmail.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=jmaneyrol@invensense.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=vincent.huang@tw.synaptics.com \
/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.