From: Sanchayan Maity <maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
stefan-XLVq0VzYD2Y@public.gmane.org,
pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org,
Sanchayan Maity
<maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH v2 0/2] Add DAC driver support for Vybrid SoC
Date: Mon, 15 Feb 2016 12:12:31 +0530 [thread overview]
Message-ID: <cover.1455516083.git.maitysanchayan@gmail.com> (raw)
Hello,
This patchset adds support for the DAC peripheral on Vybrid SoC.
Patchset is based on top of shawn's for-next branch and has been
tested on a Toradex Colibri VF50 module.
@Jonathan
I kept the IIO_SHARED_BY_DIR instead of using IIO_SHARED_BY_ALL
since this gives "out_conversion_mode" allowing me to distinguish
this in the ABI documentation, that this is explicitly for the DAC.
Since 4.5-rc4 was released recently and assuming this makes it with
this or next version, I assumed the target kernel version would be
4.6 and used that in ABI documentation.
Feedbacks and comments most welcome.
Changes since v1:
1. Fix return type of vf610_dac_init function
2. Document conversion modes in sysfs-bus-iio-vf610
3. Remove "indexed" specification from iio_chan_spec
4. Use "return" directly from default case in switch
5. Remove DRIVER_NAME
6. Call vf610_dac_init before iio device registration
7. Define and use vf610_dac_exit function in remove and suspend
8. Add sysfs ABI documentation
v1 of the patchset:
http://www.spinics.net/lists/arm-kernel/msg481190.html
Thanks & Regards,
Sanchayan Maity.
Sanchayan Maity (2):
ARM: dts: vfxxx: Add DAC node for Vybrid SoC
iio: dac: vf610_dac: Add IIO DAC driver for Vybrid SoC
Documentation/ABI/testing/sysfs-bus-iio-vf610 | 9 +
.../devicetree/bindings/iio/dac/vf610-dac.txt | 20 ++
arch/arm/boot/dts/vfxxx.dtsi | 18 ++
drivers/iio/dac/Kconfig | 8 +
drivers/iio/dac/Makefile | 1 +
drivers/iio/dac/vf610_dac.c | 298 +++++++++++++++++++++
6 files changed, 354 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/dac/vf610-dac.txt
create mode 100644 drivers/iio/dac/vf610_dac.c
--
2.7.1
next reply other threads:[~2016-02-15 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 6:42 Sanchayan Maity [this message]
[not found] ` <cover.1455516083.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-15 6:42 ` [PATCH v2 1/2] ARM: dts: vfxxx: Add DAC node for Vybrid SoC Sanchayan Maity
2016-02-15 6:42 ` [PATCH v2 2/2] iio: dac: vf610_dac: Add IIO DAC driver " Sanchayan Maity
2016-02-21 16:48 ` Jonathan Cameron
[not found] ` <02B1DDEF-6BE7-4C4C-AAD0-4EB496734316-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-02-21 19:37 ` 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=cover.1455516083.git.maitysanchayan@gmail.com \
--to=maitysanchayan-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org \
--cc=shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=stefan-XLVq0VzYD2Y@public.gmane.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).