From: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
To: nick@shmanahar.org
Cc: dmitry.torokhov@gmail.com, robh+dt@kernel.org,
mark.rutland@arm.com, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
Subject: [PATCH v5 0/3] Input: atmel_mxt_ts: Add support for optional regulators
Date: Fri, 14 Dec 2018 16:12:11 +0100 [thread overview]
Message-ID: <20181214151214.5391-1-pawel.mikolaj.chmiel@gmail.com> (raw)
This patch series adds optional regulator support to atmel_mxt_ts.
First patch adds regulators to driver.
Second patch ensures that device is ready for communication.
Third patch updates documentation.
Changes from v4:
- Add missing regulator_disable for vdd in case of error,
when enabling avdd regulator
Changes from v3:
- Checkpatch fixes
- Drop punctuation from subject of one of patches
Changes from v2:
- Add reviewed-by to one patch
- Move code for enabling regulators into separate method,
to make code more readable.
- Add wait code, to ensure that device is ready for communication.
Changes from v1:
- Enable regulators only if reset_gpio is present.
- Switch from devm_regulator_get_optional to devm_regulator_get.
Paweł Chmiel (3):
Input: atmel_mxt_ts: Add support for optional regulators
Input: atmel_mxt_ts: Wait for device be ready for communication
Input: atmel_mxt_ts: Document optional voltage regulators
.../bindings/input/atmel,maxtouch.txt | 8 ++
drivers/input/touchscreen/atmel_mxt_ts.c | 78 +++++++++++++++++--
2 files changed, 80 insertions(+), 6 deletions(-)
--
2.17.1
next reply other threads:[~2018-12-14 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 15:12 Paweł Chmiel [this message]
2018-12-14 15:12 ` [PATCH v5 1/3] Input: atmel_mxt_ts: Add support for optional regulators Paweł Chmiel
2018-12-14 15:12 ` [PATCH v5 2/3] Input: atmel_mxt_ts: Wait for device be ready for communication Paweł Chmiel
2019-01-15 0:42 ` Dmitry Torokhov
2018-12-14 15:12 ` [PATCH v5 3/3] Input: atmel_mxt_ts: Document optional voltage regulators Paweł Chmiel
2018-12-16 22:41 ` Sebastian Reichel
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=20181214151214.5391-1-pawel.mikolaj.chmiel@gmail.com \
--to=pawel.mikolaj.chmiel@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nick@shmanahar.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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).