From: Florian Vaussard <florian.vaussard@gmail.com>
To: devicetree@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Martin Kepplinger <martink@posteo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Florian Vaussard <florian.vaussard@heig-vd.ch>
Subject: [PATCH 0/3] iio: adc: max1363: Fix missing parts and add device tree
Date: Tue, 21 Jun 2016 09:09:26 +0200 [thread overview]
Message-ID: <1466492969-2185-1-git-send-email-florian.vaussard@heig-vd.ch> (raw)
Hello,
This series first fix missing i2c_device_id for several MAX1164x parts.
It then introduces the necessary device tree binding to perform DT boot.
Tested with MAX11644 (DT boot).
Best regards,
Florian
Florian Vaussard (3):
iio: adc: max1363: Fix missing i2c_device_id for MAX1164x parts
iio: adc: max1363: Add device tree binding documentation
iio: adc: max1363: Add device tree binding
.../devicetree/bindings/iio/adc/max1363.txt | 63 ++++++++++++++++++++++
drivers/iio/adc/max1363.c | 62 ++++++++++++++++++++-
2 files changed, 124 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/iio/adc/max1363.txt
--
2.5.0
next reply other threads:[~2016-06-21 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 7:09 Florian Vaussard [this message]
2016-06-21 7:09 ` [PATCH 1/3] iio: adc: max1363: Fix missing i2c_device_id for MAX1164x parts Florian Vaussard
2016-06-26 17:02 ` Jonathan Cameron
2016-06-21 7:09 ` [PATCH 2/3] iio: adc: max1363: Add device tree binding documentation Florian Vaussard
2016-06-21 21:49 ` Rob Herring
2016-06-22 6:18 ` Florian Vaussard
2016-06-26 17:02 ` Jonathan Cameron
2016-06-21 7:09 ` [PATCH 3/3] iio: adc: max1363: Add device tree binding Florian Vaussard
2016-06-21 11:44 ` kbuild test robot
2016-06-26 17:01 ` Jonathan Cameron
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=1466492969-2185-1-git-send-email-florian.vaussard@heig-vd.ch \
--to=florian.vaussard@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.vaussard@heig-vd.ch \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martink@posteo.de \
--cc=pawel.moll@arm.com \
--cc=pmeerw@pmeerw.net \
--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).