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,
Sanchayan Maity
<maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH v1 0/2] Add DAC driver support for Vybrid SoC
Date: Tue, 9 Feb 2016 10:56:04 +0530 [thread overview]
Message-ID: <cover.1454939346.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.
I had one query as to whether my implementation under the
IIO_CHAN_INFO_SCALE correct? I am not clear on exactly on how
the voltage_scale parameter is suppose to be set and used.
Feedbacks and comments most welcome.
Thanks & Regards,
Sanchayan.
Sanchayan Maity (2):
ARM: dts: vfxxx: Add DAC node for Vybrid SoC
iio: dac: vf610_dac: Add IIO DAC driver for Vybrid SoC
.../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 | 302 +++++++++++++++++++++
5 files changed, 349 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/dac/vf610-dac.txt
create mode 100644 drivers/iio/dac/vf610_dac.c
--
2.7.1
WARNING: multiple messages have this Message-ID (diff)
From: Sanchayan Maity <maitysanchayan@gmail.com>
To: jic23@kernel.org
Cc: linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, shawnguo@kernel.org, stefan@agner.ch,
Sanchayan Maity <maitysanchayan@gmail.com>
Subject: [PATCH v1 0/2] Add DAC driver support for Vybrid SoC
Date: Tue, 9 Feb 2016 10:56:04 +0530 [thread overview]
Message-ID: <cover.1454939346.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.
I had one query as to whether my implementation under the
IIO_CHAN_INFO_SCALE correct? I am not clear on exactly on how
the voltage_scale parameter is suppose to be set and used.
Feedbacks and comments most welcome.
Thanks & Regards,
Sanchayan.
Sanchayan Maity (2):
ARM: dts: vfxxx: Add DAC node for Vybrid SoC
iio: dac: vf610_dac: Add IIO DAC driver for Vybrid SoC
.../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 | 302 +++++++++++++++++++++
5 files changed, 349 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/dac/vf610-dac.txt
create mode 100644 drivers/iio/dac/vf610_dac.c
--
2.7.1
WARNING: multiple messages have this Message-ID (diff)
From: maitysanchayan@gmail.com (Sanchayan Maity)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/2] Add DAC driver support for Vybrid SoC
Date: Tue, 9 Feb 2016 10:56:04 +0530 [thread overview]
Message-ID: <cover.1454939346.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.
I had one query as to whether my implementation under the
IIO_CHAN_INFO_SCALE correct? I am not clear on exactly on how
the voltage_scale parameter is suppose to be set and used.
Feedbacks and comments most welcome.
Thanks & Regards,
Sanchayan.
Sanchayan Maity (2):
ARM: dts: vfxxx: Add DAC node for Vybrid SoC
iio: dac: vf610_dac: Add IIO DAC driver for Vybrid SoC
.../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 | 302 +++++++++++++++++++++
5 files changed, 349 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-09 5:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 5:26 Sanchayan Maity [this message]
2016-02-09 5:26 ` [PATCH v1 0/2] Add DAC driver support for Vybrid SoC Sanchayan Maity
2016-02-09 5:26 ` Sanchayan Maity
[not found] ` <cover.1454939346.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-09 5:26 ` [PATCH v1 1/2] ARM: dts: vfxxx: Add DAC node " Sanchayan Maity
2016-02-09 5:26 ` Sanchayan Maity
2016-02-09 5:26 ` Sanchayan Maity
2016-02-09 5:26 ` [PATCH v1 2/2] iio: dac: vf610_dac: Add IIO DAC driver " Sanchayan Maity
2016-02-09 5:26 ` Sanchayan Maity
2016-02-09 5:26 ` Sanchayan Maity
[not found] ` <5a699d45c89d239f3e49fa83d16a9b467016e219.1454939346.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-09 6:43 ` Peter Meerwald-Stadler
2016-02-09 6:43 ` Peter Meerwald-Stadler
2016-02-09 6:43 ` Peter Meerwald-Stadler
[not found] ` <alpine.DEB.2.02.1602090729130.22963-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>
2016-02-12 6:34 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-02-12 6:34 ` maitysanchayan at gmail.com
2016-02-12 6:34 ` maitysanchayan
[not found] ` <20160212063403.GA3056-2b/appYahYAQpivJYWJ5AnfHJb42ZiuNiBNltiLz+yw@public.gmane.org>
2016-02-13 13:29 ` Jonathan Cameron
2016-02-13 13:29 ` Jonathan Cameron
2016-02-13 13:29 ` Jonathan Cameron
[not found] ` <56BF2FC3.3070502-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-02-13 15:14 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-02-13 15:14 ` maitysanchayan at gmail.com
2016-02-13 15:14 ` maitysanchayan
2016-02-13 15:26 ` Jonathan Cameron
2016-02-13 15:26 ` Jonathan Cameron
2016-02-13 15:26 ` Jonathan Cameron
2016-02-09 22:44 ` Jonathan Cameron
2016-02-09 22:44 ` Jonathan Cameron
2016-02-09 22:44 ` Jonathan Cameron
2016-02-12 14:51 ` Rob Herring
2016-02-12 14:51 ` Rob Herring
2016-02-12 14:51 ` Rob Herring
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.1454939346.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.