From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
knaack.h@gmx.de, pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
stefan.popa@analog.com, alexandru.Ardelean@analog.com
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-usp@googlegroups.com
Subject: [PATCH 0/3] Add devicetree support for ad5933
Date: Sat, 8 Dec 2018 16:18:18 -0200 [thread overview]
Message-ID: <cover.1544292845.git.marcelo.schmitt1@gmail.com> (raw)
This series of patches change voltage regulator error handling for the
ad5933.
It also add an option to specify external clock reference using a clock
framework and remove the old platform data structure.
Finally it adds binding documentation for devicetree.
Marcelo Schmitt (3):
staging: iio: ad5933: change regulator binging for vref
staging: iio: ad5933: use clock framework for clock reference
staging: iio: ad5933: add binding doc for ad5933
.../iio/impedance-analyzer/ad5933.txt | 26 +++++++++
.../staging/iio/impedance-analyzer/ad5933.c | 57 +++++++++----------
2 files changed, 54 insertions(+), 29 deletions(-)
create mode 100644 Documentation/devicetree/bindings/iio/impedance-analyzer/ad5933.txt
--
2.17.1
next reply other threads:[~2018-12-08 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 18:18 Marcelo Schmitt [this message]
2018-12-08 18:19 ` [PATCH 1/3] staging: iio: ad5933: change regulator binging for vref Marcelo Schmitt
2018-12-16 12:13 ` Jonathan Cameron
2018-12-08 18:19 ` [PATCH 2/3] staging: iio: ad5933: use clock framework for clock reference Marcelo Schmitt
2018-12-16 12:14 ` Jonathan Cameron
2018-12-08 18:19 ` [PATCH 3/3] staging: iio: ad5933: add binding doc for ad5933 Marcelo Schmitt
2018-12-10 21:27 ` Jonathan Cameron
2018-12-16 12:16 ` Jonathan Cameron
2018-12-08 18:56 ` [PATCH 0/3] Add devicetree support " Marcelo Schmitt
2018-12-08 21:10 ` Greg KH
2018-12-10 21:27 ` Jonathan Cameron
2018-12-11 10:31 ` Ardelean, Alexandru
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=cover.1544292845.git.marcelo.schmitt1@gmail.com \
--to=marcelo.schmitt1@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.Ardelean@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kernel-usp@googlegroups.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=stefan.popa@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox