From: Stephen Boyd <swboyd@chromium.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dmitry Torokhov <dtor@chromium.org>,
Doug Anderson <dianders@chromium.org>
Subject: [PATCH v3 0/2] Add another regulator to i2c-hid
Date: Thu, 21 Jun 2018 19:27:15 -0700 [thread overview]
Message-ID: <20180622022717.134300-1-swboyd@chromium.org> (raw)
The wacom w9013 device has two supplies that need to be turned
on and in some cases these come from two different power supplies.
This patch series supports that case.
Changes from v1:
* Use the bulk regulator APIs instead of open coding it (Dmitry)
Changes from v2:
* Split out devm for allocation into another patch (Dmitry)
* Drop errant error print that snuck in across port
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Dmitry Torokhov <dtor@chromium.org>
Cc: Doug Anderson <dianders@chromium.org>
Stephen Boyd (2):
HID: i2c-hid: Use devm to allocate i2c_hid struct
HID: i2c-hid: Add vddl regulator control
.../bindings/input/hid-over-i2c.txt | 3 +-
drivers/hid/i2c-hid/i2c-hid.c | 57 +++++++++----------
include/linux/platform_data/i2c-hid.h | 7 +--
3 files changed, 32 insertions(+), 35 deletions(-)
--
Sent by a computer through tubes
next reply other threads:[~2018-06-22 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 2:27 Stephen Boyd [this message]
2018-06-22 2:27 ` [PATCH v3 1/2] HID: i2c-hid: Use devm to allocate i2c_hid struct Stephen Boyd
2018-06-22 7:16 ` Benjamin Tissoires
2018-06-22 9:13 ` Hans de Goede
2018-06-22 22:39 ` Dmitry Torokhov
2018-06-22 2:27 ` [PATCH v3 2/2] HID: i2c-hid: Add vddl regulator control Stephen Boyd
2018-06-25 13:14 ` [PATCH v3 0/2] Add another regulator to i2c-hid Jiri Kosina
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=20180622022717.134300-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dianders@chromium.org \
--cc=dtor@chromium.org \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).